WebSphere MQ 6.*, MQSC Adapter and BizTalk 2006
Posted by biztodo on October 30, 2007
1.The adapter “MQSC” raised an error message. Details “Failure encountered while attempting to open queue.
ErrorCode 2058 or 2059
***************************************************************************
2.The IP protocol ‘IPv4/IPv6′ is not available on the system.
An attempt to use an IP protocol that is not available on the system has been made.
Install the required IP protocol or use an IP protocol that is available on the system. This error can also occur if the system is short of memory or other system resources.
****************************************************************************
If you have WebSphere MQ 6.0.* version client, BizTalk Adapters for Host Systems – you are bound to run into one of these issues with the MQSC adapter.
Or maybe only i was the unlucky ones. This left me handicapped for a few days when i needed to push critical fixes and could not test my orchestrations because of the dependency on the queues.
I upgraded from MQ 6.0 to MQ 6.0.2.1 and started receiving these errors whenever i enabled my receive locations which were MQSC receives.
I used ProcessMon to narrow down the issue.
I started ProcessMon and then enabled the receive and then stopped processmon.
The key events to look for would be from BTSNTSvc.exe process. If you follow the reads it would lead you to amqxms0n.dll. This dll is used to write to the error log for WebShphere MQ in folder X:\Program Files\ibm\WebSphere MQ\errors. So thats too far. If you look at the last read before accessing the error logger dll and follow its stack trace; you will possibly be able to trace it.
In my case what happened was one the WebSphere dll’s loaded was from the X:\windows\system32 which was older than the one available in the X:\Program Files\ibm\WebSphere MQ\bin folder. The latest ones i got during the upgrade. SO i had to identify and physically move them.
The errors seems more cryptic though and i spent more time researching based on the error messages which lead me nowhere.
Most of the issues i dealt with earlier too i was able to narrow down to path problems or missing dlls in specific paths using FileMon.
The error thrown by MQSC seems to be the wrong lead to follow.
