Author |
Message
|
manojsu |
Posted: Mon Dec 20, 2010 3:37 am Post subject: Upgrade to WMQ v7 |
|
|
Centurion
Joined: 19 Jul 2006 Posts: 147 Location: Bangalore
|
Hi Guys,
I have upgraded the WMQ client from v6, v7.0.1.3, and when the service is being started, it crashes when trying to process an application.. with an FDC being generated.
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Mon December 20 2010 11:20:45 GMT Standard Time |
| UTC Time :- 1292844045.298000 |
| UTC Time Offset :- 0 (GMT Standard Time) |
| Host Name :- CAT-RF-CNP2 |
| Operating System :- Windows XP, Build 3790: SP2 |
| PIDS :- 5724H7220 |
| LVLS :- 7.0.1.3 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- XC001004 |
| Application Name :- MQM |
| Component :- xcsInitialize |
| SCCS Info :- lib/cs/amqxitc0.c, 1.224.1.1 |
| Line Number :- 1254 |
| Build Date :- Aug 18 2010 |
| CMVC level :- p701-103-100818 |
| Build Type :- IKAP - (Production) |
| UserID :- commnp |
| Process Name :- c:\fiservcbs\catuk\communicator\62\np2\services\mq |
| manager\mqmanager.exe |
| Addressing mode :- 32-bit |
| Process :- 00001208 |
| Thread :- 00000001 |
| UserApp :- FALSE |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- xecI_S_FAIL |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (40006004) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 1073766404 40006004 |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
xcsInitialize
xcsFFST
MQM Trace History
{ xcsGetEnvironmentInteger
-{ xcsGetEnvironmentString
-} xcsGetEnvironmentString rc=xecE_E_ENV_VAR_NOT_FOUND
} xcsGetEnvironmentInteger rc=xecE_E_ENV_VAR_NOT_FOUND
I suspect its some sort of environment thing..
Any advise on where i am doing wrong. |
|
Back to top |
|
 |
Vitor |
Posted: Mon Dec 20, 2010 5:44 am Post subject: Re: Upgrade to WMQ v7 |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
manojsu wrote: |
{ xcsGetEnvironmentInteger
-{ xcsGetEnvironmentString
-} xcsGetEnvironmentString rc=xecE_E_ENV_VAR_NOT_FOUND
} xcsGetEnvironmentInteger rc=xecE_E_ENV_VAR_NOT_FOUND
I suspect its some sort of environment thing..
|
Well based on the message it does seem likely doesn't it???
If this happens when the service starts, what happens when you start the queue manager manually with strmqm from a command prompt?
Do you have any exits or additional code running with the queue manager or the channels? That ProbeId has previously been associated with using .NET and the assemblies getting hosed. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
manojsu |
Posted: Mon Dec 20, 2010 5:55 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006 Posts: 147 Location: Bangalore
|
Its a client installation, and the service starts fine but immediately crashes soon after it.
It is a .net Application and have tried to use the gacutil to manually add the amqmdnet files, but even that fails with an error.
Failure adding assembly to the cache: Unknown Error |
|
Back to top |
|
 |
Vitor |
Posted: Mon Dec 20, 2010 6:00 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
manojsu wrote: |
Its a client installation, and the service starts fine but immediately crashes soon after it. |
Oops. I saw "service" and my brain made up the words "queue manager"
manojsu wrote: |
It is a .net Application and have tried to use the gacutil to manually add the amqmdnet files, but even that fails with an error. |
Does v7 use the same .NET file names as v6? Or am I making that up like I imagined this was a queue manager?
I'd pull the client entirely off, install the v7 client clean from scratch & try again. Rebooting a few times in between. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Dec 20, 2010 6:14 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Sorry, is it your client application or a third party?
Did you build it against v7, if it's yours? |
|
Back to top |
|
 |
manojsu |
Posted: Mon Dec 20, 2010 6:20 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006 Posts: 147 Location: Bangalore
|
Its a 3rd party application and we know nothing about it.
I have uninstalled 6 completely, installed 7 and then rebooted it.. no change till now... |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Dec 20, 2010 6:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
manojsu wrote: |
Its a 3rd party application and we know nothing about it. |
Then you need to talk to the provider of the app about whether or not it's supported on MQ v7 or if you can just go ahead and do what you've done or not. |
|
Back to top |
|
 |
manojsu |
Posted: Mon Dec 20, 2010 6:35 am Post subject: |
|
|
Centurion
Joined: 19 Jul 2006 Posts: 147 Location: Bangalore
|
Have checked with the provider and they have not tested it WMQ v7, but they say it should work fine with v7... not a very great answer.. but it is wat we got..
any known issues with .NET, IIS and WMQ v7... |
|
Back to top |
|
 |
mvic |
Posted: Mon Dec 20, 2010 6:39 am Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
|
Back to top |
|
 |
|