| Author |
Message
|
| veda |
 Posted: Wed Dec 01, 2010 5:37 am Post subject: Error after installation of mb runtime fixpack 7.0.0.1 |
 |
|
Novice
Joined: 01 Dec 2010
Posts: 24
|
I have installed the broker runtime fixpack and when the broker component starts , a error pops up like
The Procedure entry point? activeMQService@ImbAdminAgentStartParameters@@QAE_NXZ could not be located in the dynamic link library PlatformSupport.dll.
MQ version is 7.0
any  would be appreciated!
Thank You |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Dec 01, 2010 5:43 am Post subject: Re: Error after installation of mb runtime fixpack 7.0.0.1 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| veda wrote: |
| MQ version is 7.0 |
What maintenance level?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| veda |
| Posted: Wed Dec 01, 2010 5:47 am Post subject: Re: Error after installation of mb runtime fixpack 7.0.0.1 |
|
|
Novice
Joined: 01 Dec 2010
Posts: 24
|
| Vitor wrote: |
| veda wrote: |
| MQ version is 7.0 |
What maintenance level? |
Name: WebSphere MQ
Version: 7.0.1.2
CMVC level: p701-102-100504
BuildType: IKAP - (Production) |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Dec 01, 2010 6:00 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Did you install the fixpack for windows 32bit on a windows 64 bit platform, or vice versa?
Are you using a supported version of Windows? |
|
| Back to top |
|
|
| veda |
| Posted: Wed Dec 01, 2010 6:16 am Post subject: |
|
|
Novice
Joined: 01 Dec 2010
Posts: 24
|
| mqjeff wrote: |
Did you install the fixpack for windows 32bit on a windows 64 bit platform, or vice versa?
Are you using a supported version of Windows? |
No, I have installed fixpack(win32) on Windows XP(32bit).
The Version that I am using is
Windows XP professional Version 2002 Service pack 3. |
|
| Back to top |
|
|
| veda |
| Posted: Wed Dec 01, 2010 9:15 am Post subject: |
|
|
Novice
Joined: 01 Dec 2010
Posts: 24
|
Thank You All.. 
The problem has been resolved. I have reinstalled the runtime fixpack and started the component from command console. |
|
| Back to top |
|
|
|
|
