I ran into the following problem and I am looking for some advise. I have MQWF 3.5 installed on a Windows 200 server and I am trying to migrate it to a new server running Windows 2003 server. I have MQWF 3.5 and DB2 installed on the E: drive on the existing system. On my new system I am installed everything on the C: drive. I migrated the database and started up the configuration only to find the following error messages in the Fmcerr.log. As you can see from the error messages below there is a reference somewhere in the database to the E drive, which is from the old system. Is there any way to fix this?
Report creation = 5/16/2008 3:09:29 PM
Related message = FMC31050E An error has occurred which has terminated processing.
Error location = File=e:\v360\src\fmccdifs.cxx, Line=4562, Function=FmcFmlsDevice::GetFromQueue
Error data = FmcFMLException, MQReturnCode=2, MQReasonCode=2162, MQObjectName=FMC.FMCGRP.FMCSYS.ADM, severe error
This topic has been locked.
2 replies Latest Post - 2008-05-20T11:39:39Z by SystemAdmin
Pinned topic Migrating MQWF to new Hardware
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2008-05-20T11:39:39Z at 2008-05-20T11:39:39Z by SystemAdmin
jmac_EmeriCon 110000S3HB26 PostsACCEPTED ANSWER
Re: Migrating MQWF to new Hardware2008-05-17T13:00:42Z in response to KriersdDave:
No Idea what to do if it is really in the database, but did you check the Profile entries in the Registry? Perhaps there is something there that points back to the old drive? Not likely, but something I would check.
SystemAdmin 110000D4XK2340 PostsACCEPTED ANSWER
Re: Migrating MQWF to new Hardware2008-05-20T11:39:39Z in response to KriersdHi,
the error that you are seeing has nothing to do with the E: drive of your
(instead it is the location where the product has been built on IBM's
You are getting an MQ error 2162 that terminates your server.
MQ 2162 means that MQ is being stopped. Make sure that you do not stop MQ
Series while MQWF servers are still running.
Make sure that MQ Series is not stopped implicitely by logging off from
IBM WebSphere Process server Development