BizTalk 2009 MQSeries adapter in 64-bit mode


has installed biztalk 2009 mqseries adapter in 64-bit mode before?

technet states possible haven't been able find detailed instructions install process.

http://msdn.microsoft.com/en-us/library/aa560166(bts.10).aspx

"the mqseries adapter supported in both 32-bit , 64-bit processes. adapter has mqseries agent runs on ibm websphere mq server on windows. mq fix pack 6.0.2.1 agent supported 32-bit process running under wow64."

how go configuring mqseries agent run under wow64?

nikolai

the mqseries adapter (part of biztalk 2009 base) installs fine without wmq running on biztalk server. on several 64-bit servers work on w2k8 r2.

if mean mqsc adapter - part of biztalk adapters host systems (bah), should able install wmq software first, biztalk , bah install mqsc adapter show up. have thread going on issue though might check out: http://social.msdn.microsoft.com/forums/en-us/biztalkr2adapters/thread/0544b0cc-2044-499b-a824-5fefde90e77e

i think mqseries agent should run under wow64 default. 32-bit installs work fine on 64-bit w2k8 server due wow64.

thanks,
if answers question, please use "answer" button | ben cline


BizTalk Server  >  BizTalk Server Adapters and Adapter Pack



Comments

Post a Comment

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

having same error microsoft.azure.documents.documentclientexception: message: {"errors":["owner resource not exist"]} , scenario. when deployed webapp azure , try document docdb throws error. docdb exists in azure , contains document looking for. weird local machine(running vs) works fine. i'm using same settings in azure , local. have , idea this. thanks Microsoft Azure  >  Azure Cosmos DB
Read more

job syspolicy_purge_history job fail in sqlserver 2008

Image
hello guys, when installed sqlserver,it automatically created 1 job name job syspolicy_purge_history. but failed @ step 1. the reason is: date                11/6/2010 2:00:00 am log                job history (syspolicy_purge_history) step id                1 server                mxosv-otsdb01 job name                syspolicy_purge_history step name                verify automation enabled. duration                00:00:00 sql severity                16 sql message id                34022 operator emailed                operator net sent                operator paged                retries attempted                0 message executed user: nt authority\system. policy automation turned off. [sqlstate 42000] (error 34022).  the step failed. have run statement: select msdb.dbo.fn_syspolicy_is_automation_enabled the returned valus 0. what can resolve it? or can delete job manually.   thanks in advance. if haven't things want,be
Read more

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'

when trying register against public azure adfs azure stack error below. logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  and  \\azs-ercs01\c$\maslogs error occurred checking stamp information: system.management.automation.remoteexception: term 'get-azurestackstampinformation' not recognized name of cmdlet, function, script file, or operable program. check spelling of name, or if path included, verify path correct , try again. @ c:\azurestack-tools-master\registration\registerwithazure.psm1:1106 char:5 +     throw "logs can found at: $global:azureregistrationlog  and  \ ... +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : operationstopped: (logs can fou... , try again.:string) [], runtimeexception     + fullyqualifiederrorid : logs can found at: c:\maslogs\azurestack.azureregistration.2017-10-12.01-31-23.log  a    nd  \\azs-ercs01\c$\maslogs error occurred chec
Read more