Author |
Message
|
wischlei |
Posted: Tue Mar 13, 2007 4:59 am Post subject: Problem Starting server channel on Windows MQ 6.0.2.0 |
|
|
Novice
Joined: 11 Feb 2004 Posts: 21 Location: Germany
|
Hi,
I could not find anything like this error message in the forums:
Event ID 9224
Invalid registry value.
WebSphere MQ registry value name 'Library2' is either not valid or has invalid value data.
Correct the registry value and retry the operation.
What does this mean, and : how can I fix it?
MQ: 6.0.2.0 p600-200-060921
Thanks a lot in advance. _________________ Winfried Schleipen |
|
Back to top |
|
 |
Michael Dag |
Posted: Tue Mar 13, 2007 5:15 am Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
does anything with the name Library2 ring a bell with you?
what's in Library2 then? use regedit to find out.
could there be a mismatch betweeen the language of the OS and the language of MQ (since you are from Germany ) _________________ Michael
MQSystems Facebook page |
|
Back to top |
|
 |
wischlei |
Posted: Tue Mar 13, 2007 6:20 am Post subject: |
|
|
Novice
Joined: 11 Feb 2004 Posts: 21 Location: Germany
|
Hi
thanks for the fast reply althought it does not help me a bit. The language seems to be ok. The library2 Values can be set in the queue manager properties. The TCP library1 and library2 values are emtpy as a assume they have been always. The problem occurred only today so I think that there is another problem on the machine.
Any further suggestions? _________________ Winfried Schleipen |
|
Back to top |
|
 |
wischlei |
Posted: Wed Mar 14, 2007 2:37 am Post subject: |
|
|
Novice
Joined: 11 Feb 2004 Posts: 21 Location: Germany
|
Hi,
I solved the problem by setting the TCP/Library2 Value to some random value like 'abc' storing it and resetting it to the empty string in the MQ Explorer. I then restarted the listener (which did not work before). This still did not work, however, the Library2 Value was magically resetted to WSOCK32. I copied this to the Library1 value and now -- magic -- the Listener started again.
The cause of the problem seems to be a microsoft update that mangled the registry or registry access control. _________________ Winfried Schleipen |
|
Back to top |
|
 |
Michael Dag |
Posted: Wed Mar 14, 2007 2:55 am Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
|
Back to top |
|
 |
|