Author |
Message
|
anoop.vishnoi@gmail.com |
Posted: Wed Feb 18, 2009 2:11 am Post subject: unable to move queue managers under MSCS control |
|
|
Newbie
Joined: 30 Jan 2009 Posts: 7
|
Hi, I'm trying to move my queue managers to the SAN disk (virtual) but am unable to do so. I'm using MQ 5.3 with CSD 12
I'm following this article http://www-01.ibm.com/support/docview.wss?uid=swg21251099
The infrastructure was working fine until yesterday. It was only after running the windows update my queue managers got corrupted thus had to delete and recreate them. No when I try to move them to the SAN disk using hamvmqm utility, i get the following error.
An error occurred whilst creating/accessing the destination directories
below are the FDC's logged.
Please help !!!
--Anoop
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wed February 18 09:13:19 GMT Standard Time 2009 |
| Host Name :- VLONP71D01 (Windows Ver 5.2 Build 3790: Service Pack |
| 1) |
| PIDS :- 5724B4100 |
| LVLS :- 530.12 CSD12 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- MC171012 |
| Application Name :- MQM |
| Component :- MQMMigrateCMQMSCSApp::CreateMQDirectory |
| Build Date :- Dec 8 2005 |
| CMVC level :- p530-12-L051208 |
| Build Type :- IKAP - (Production) |
| UserID :- admin-vishnoia |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\hamvmqm.exe |
| Process :- 00006152 |
| Thread :- 00000001 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| (Failed to create directory '“S:\') |
| FDCSequenceNumber :- 0 |
| Comment1 :- Failed to create directory '“S:\' |
| |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wed February 18 09:13:19 GMT Standard Time 2009 |
| Host Name :- VLONP71D01 (Windows Ver 5.2 Build 3790: Service Pack |
| 1) |
| PIDS :- 5724B4100 |
| LVLS :- 530.12 CSD12 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- MC173020 |
| Application Name :- MQM |
| Component :- MQMMigrateCMQMSCSApp::CheckAndCreateMQ |
| Build Date :- Dec 8 2005 |
| CMVC level :- p530-12-L051208 |
| Build Type :- IKAP - (Production) |
| UserID :- admin-vishnoia |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\hamvmqm.exe |
| Process :- 00006152 |
| Thread :- 00000001 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| (Cannot create directory structure) |
| FDCSequenceNumber :- 1 |
| Comment1 :- Cannot create directory structure |
| |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wed February 18 09:13:19 GMT Standard Time 2009 |
| Host Name :- VLONP71D01 (Windows Ver 5.2 Build 3790: Service Pack |
| 1) |
| PIDS :- 5724B4100 |
| LVLS :- 530.12 CSD12 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- MC168007 |
| Application Name :- MQM |
| Component :- MQMMigrateCMQMSCSApp::ProcessShellCmd |
| Build Date :- Dec 8 2005 |
| CMVC level :- p530-12-L051208 |
| Build Type :- IKAP - (Production) |
| UserID :- admin-vishnoia |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\hamvmqm.exe |
| Process :- 00006152 |
| Thread :- 00000001 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| (Cannot create/access destination directories) |
| FDCSequenceNumber :- 2 |
| Comment1 :- Cannot create/access destination directories |
| |
| |
+-----------------------------------------------------------------------------+ |
|
Back to top |
|
 |
exerk |
Posted: Wed Feb 18, 2009 2:19 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
What errors (if any) are being reported in eventvwr? _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
anoop.vishnoi@gmail.com |
Posted: Wed Feb 18, 2009 2:27 am Post subject: |
|
|
Newbie
Joined: 30 Jan 2009 Posts: 7
|
here are the eventvwr entries:
Event Type: Warning
Event Source: WebSphere MQ
Event Category: None
Event ID: 6183
Date: 2/18/2009
Time: 9:13:17 AM
User: N/A
Computer: servername
Description:
An internal WebSphere MQ error has occurred.
An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process 7900.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
Event Type: Error
Event Source: WebSphere MQ
Event Category: None
Event ID: 6177
Date: 2/18/2009
Time: 9:13:17 AM
User: N/A
Computer: servername
Description:
An internal WebSphere MQ error has occurred.
An error has been detected, and the MQ error recording routine has been called.
Details of the error have been stored at C:\Program Files\IBM\WebSphere MQ\errors\AMQ07900.0.FDC. A synopsis is given in the data section below. Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
Event Type: Error
Event Source: WebSphere MQ
Event Category: None
Event ID: 6119
Date: 2/18/2009
Time: 9:13:19 AM
User: N/A
Computer: servername
Description:
An internal WebSphere MQ error has occurred (Failed to create directory '“S:\')
MQ detected an unexpected error when calling the operating system. The MQ error recording routine has been called.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
Event Type: Error
Event Source: WebSphere MQ
Event Category: None
Event ID: 6119
Date: 2/18/2009
Time: 9:13:19 AM
User: N/A
Computer: servername
Description:
An internal WebSphere MQ error has occurred (Cannot create directory structure)
MQ detected an unexpected error when calling the operating system. The MQ error recording routine has been called.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
Event Type: Error
Event Source: WebSphere MQ
Event Category: None
Event ID: 6119
Date: 2/18/2009
Time: 9:13:19 AM
User: N/A
Computer: servername
Description:
An internal WebSphere MQ error has occurred (Cannot create/access destination directories)
MQ detected an unexpected error when calling the operating system. The MQ error recording routine has been called.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved. |
|
Back to top |
|
 |
exerk |
Posted: Wed Feb 18, 2009 2:42 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
OK, that looks like the Application element of eventvwr, what about Security etc.?
What update was applied? Anything specific to that update on the IBM/Microsoft websites? _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
anoop.vishnoi@gmail.com |
Posted: Wed Feb 18, 2009 2:54 am Post subject: |
|
|
Newbie
Joined: 30 Jan 2009 Posts: 7
|
updates were normal update from Windows Update website. Security and all is intact across all the folders ... still this fails  |
|
Back to top |
|
 |
anoop.vishnoi@gmail.com |
Posted: Wed Feb 18, 2009 3:03 am Post subject: FIXED |
|
|
Newbie
Joined: 30 Jan 2009 Posts: 7
|
Hi, I could move the queuemanagers to SAN disk. The culprit was one of the COM+ application (BizTalk Adapter for MQ Series/MQSAgent2) which was holding locks on the locations. I stopped the application and disabled it to create and move the qm's under MSCS.
Thanks alot for all your help
--Anoop |
|
Back to top |
|
 |
|