| Author |
Message
|
| kwelch |
 Posted: Tue Sep 30, 2003 10:06 am Post subject: viewing WMQI error messages in the event viewer |
 |
|
Master
Joined: 16 May 2001
Posts: 255
|
Hi,
I used to be able to view WMQI error messages from a remote pc from my pc. I used to get nice clear error messages like this:
( HIGPLSBX1.PL_KW_TEST ) Message Translation Interface Parsing Errors have occurred:
Message Set Name : 'CA_APD_ASSIGNIN_MSGSET'
Message Set Level : '1'
Message Format : 'XML'
Message Type Path : 'AssignmentTransaction0100'
Review further error messages for an indication to the cause of the errors.
( HIGPLSBX1.PL_KW_TEST ) Message Validation failure. An element, that has been deemed complete, does not meet the minOccurs constraint.
Element, TransactionHeader0100, has 0 instances on the logical tree, but has been defined or qualified with a minOccurs Constraint of 1 within it's parent type/element t_AssignmentTransaction0100_cmType of index 1.
Adjust the minOccurs Constraint downwards and redeploy to the broker or increase the instances of the element in the bitstream or through ESQL.
Now I recieve the following kind of vague messages:
( HIGPLSBX1.PL_KW_TEST ) Message Translation Interface Parsing Errors have occurred.
Errors have occurred during parsing.
Review further error messages for an indication to the cause of the errors.
The description for Event ID ( 5374 ) in Source ( WMQIv210 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: HIGPLSBX1.PL_KW_TEST, TransactionHeader0100, 0, 1, t_AssignmentTransaction0100_cmType, 1.[color=black][/color]
Has anyone experienced this? If so, how do I get my good error messages back? Thanks for your help.
Sincerely,
Karen |
|
| Back to top |
|
 |
| EddieA |
| Posted: Tue Sep 30, 2003 10:44 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Karen,
This is usually caused by running the Event Viewer from a system where you haven't installed WMQI.
It's something in the Registry that tells the Event Viewer where to find the enumeration values. If I can remember/find it I'll post the info.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| kwelch |
| Posted: Tue Sep 30, 2003 10:53 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
Hi EddieA,
It is true I do not have a broker on my pc, but I do have WMQI control center and do a lot of development in WMQI. I used to receive the clearer error messages, then all of a sudden I started getting the vague ones. Thanks for anything you might have that could help with this.
Karen |
|
| Back to top |
|
|
| EddieA |
| Posted: Tue Sep 30, 2003 10:59 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Karen,
OK, it's key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\WMQIv210
And this has the values:
EventMessageFile = 'C:\Program Files\IBM\WebSphere MQ Integrator 2.1\messages\imbmsgv210.dll'
TypesSupported=dword:00000007
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| kwelch |
| Posted: Wed Oct 01, 2003 6:11 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
Hi Eddie,
Excuse my lack of knowledge on this. I don't go into the registry often. I have the correct file specified for EventMessageFile. For the TypeSupported I have 7 and off to the side it says type REG_DWORD and data 0x00000007 (7). I am guessing this is the same as what you specified below of TypeSupported=dword:00000007.
It seems this is not my problem with viewing the error messages. Thanks for your help though. Any other ideas?
Karen |
|
| Back to top |
|
|
| KSkelton |
| Posted: Wed Oct 01, 2003 8:13 am Post subject: |
|
|
Apprentice
Joined: 28 Oct 2001
Posts: 45
|
We had this happen when our Tech Services staff removed security from our group on the Windows server!
Make sure you still have the same security level as you used to. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 01, 2003 9:04 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I had a developer with a Control Center only install that had similar problem.
He copied the .dll into a new <wmqi>/messages folder on his machine from where it had been installed in <wmqi>/Tool. This fixed his problem.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| gr00ve |
| Posted: Mon Jul 26, 2010 11:28 pm Post subject: |
|
|
Newbie
Joined: 26 Jul 2010
Posts: 1
|
Had a similar problem with error descriptions when accessing event log remote.
Problem was different broker versions and paths in the windows registry
Local key:
| Code: |
| [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\WebSphere Broker v6105] |
Server key:
| Code: |
| [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Application\WebSphere Broker v6103] |
Solution was, on my local computer, to export the key and rename to correct version and then import it.
Then it worked! |
|
| Back to top |
|
|
|
|
