BizTalk receive ports shutting down


we have had biztalk 2006 production environment , running last 2 years no major issues. due adding of more applications our production environment, number of receive locations has increased. since file receive locations have been shutting down on regualr basis on production environment.

applying registry fixes recommended following link has not helped:
http://kbalertz.com/952556/receive-locations-disabled-computer-running-biztalk-server-biztalk-server.aspx,
neither has increasing retry count on receive ports worked.

is there other fixes known issue
note: biztalk production environment hosted on 2 servers , polling share on different server. regsitry settings have been applied 3 servers no effect issue keeps reoccuring frequently.

the error message keeps popping follows:

service unavailable: receive location shutting down. unable find application source biztalk server 2006 message 5649 [-1061153263] \\in\error\*.xml. file receive location \\in\error\*.xml exhausted network retry attempts.

any thoughts or comments on issue appreciated
rajan

your comment increasing retry count has not helped,makes me think that  potentially have problem:

 

http://support.microsoft.com/kb/943859/

 

symptoms

consider following scenario. create receive location in microsoft biztalk server 2006. receive location uses file adapter receive data remote universal naming convention (unc) path. configure receive location retry network failures. in scenario, receive location not retry when network failure occurs. additionally, receive location disabled immediately.


BizTalk Server  >  BizTalk Server General



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