The adapter "MQSC" raised an error message. Details: "Could not load file or
assembly "Microsoft.Biztalk.Adapter.Msqc.ImqWrapperCommon, version 7.0.2300.0
or one of its dependencies. The system cannot find the file specified.
I have look in the GAC and the assembly is there with all the other MQSC
assembly.
Can someone help me? I dont know where to search to resolved this issue.
Thanks for your help.
--
Fred
Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP
https://mvp.support.microsoft.com/profile=BE66F0D8-9D78-47EF-840A-08E6D8522A2D
http://www.linkedin.com/in/neilpike
- Make sure you have the MQ client installed and the box rebooted after you
did that.
- If this is a 64-bit OS, make sure the BizTalk Host instance is running as
a 64-bit process and not set to "32-bit only" which for some reason is the
default setting. With HIS 2009 we support running the MQSC adapter in native
64-bit and not in Wow64, but this means that you need to have MQ 7.0 on the
box if it is 64-bit.
Thanks...
--
Stephen Jackson
Microsoft� HIS Support
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only. This posting is provided "AS IS"
with no warranties, and confers no rights.
"Neil Pike" <neil...@compuserve.com> wrote in message
news:VA.00006dd...@compuserve.com...
I've got the same error and I've fixed it using the following steps :
1. Make sure that your windows PATH supports more than 1024 caracters
(in my case the PATH was already too long so that the IBM MQ Client
could not be loaded correctly)
2. Install the IBM MQ Client 7.0.0.2 (the only one that has correctly worked
in my case)
3. Install the BizTalk Adapters for Host Systems 2.0
4. If you directories are secured, think of unsecure (changing the ACLs) on
IBM MQ Client and BAHA2.0
Kind Regards,
Steve
"Fred" <Fr...@discussions.microsoft.com> wrote in message
news:A32542BB-9992-4B73...@microsoft.com...
Also I have changed my bts host to run has 64bit since my OS is windows2008
on 64 bit.
Now I'm having another issue, so I assume that this one is resolved. I'll
post a new case for that issue.
Thanks everyone for the quick reply.
Fred
--
Fred