Biztalk : Error Threshold on Receive Locations and receive location disabled automaticaly

we have one receive location of type SQL in our Biztalk Application on productin server and it got disabled after some days and logged an error in event log  like that "Threshol on Receive Location"

it was very annoying for us to enable it manually and we were not be able to find the root cause of this problem, then after some R&D i have come to know that

Biztalk keeps polling sql server after  every x milliseconds. In some cases its configurable. For some adapters its not.

we have error threshold value set to 5 , mean after 5 continous error from sql server the receive location would be disable as Microsoft says about Error Trhreshold :

The Error Threshold is used to specify the maximum number of continuous errors received before disabling the receive handler.

so when for some maintaine work or with due ot any other reason if sql server is down and Biztalk got 5 continous error from sql server then it disabled the receive location and put some error in log related to threshold.

so what we did just change the value of ErrorThreshold from 5 to 500 and restart the host instance then we did not face this issue again.

Biztalk Error X2044 : symbol Object is already defined; the first definition is in assembly c:\###.dll

Yesterday I was hacing an error  in Biztalk 2010  ,

symbol '###' is already defined; the first definition is in assembly c:\###.dll , in my case it was saing that a porttype is alrdeay defined, so what how to fix these kind of issues in biztalk. error x2044

1. Open the orchestration in Notepad (In my case SchoolOrchestration.odx)


2. find (Ctrl+F) for “#endif // __DESIGNER_DATA”


3. Delete all the code below that line


4. Save your file in Notepad


5. Say yes when Visual Studio asks if you want to update your file


6. Recompile

that's it .

Source : http://biztalkia.blogspot.com/2005/12/solving-biztalk-error-x2044.html

Biztalk 2010 service not started after windows restart in windows 2008 server R2

To resolve this issue, configure the Enterprise Single Sign-on service and each BizTalk Service service to use the Automatic (Delayed Start) startup type. To do this, follow these steps:

1. Click Start, type services in the Start Search box, and then select Services in the Programs list. If you are prompted for an administrator password or for a confirmation, type the password, or click Continue.


2. Under Name, right-click Enterprise Single Sign-on Service, and then click Properties.


3. In the Startup type box, click Automatic (Delayed Start), and then click OK.


4. Under Name, right-click a BizTalk Service service, and then click Properties.


5. In the Startup type box, click Automatic (Delayed Start), and then click OK.


6. Repeat steps 4 and 5 for any remaining BizTalk Service services.

Source : http://support.microsoft.com/kb/942284

Biztalk Error System.String must be Xml serializable to be a message part type

I was doing some development in Biztalk 2006 with Vs 2005 . I created an orchestration and there was one message in it that has type System.String. When I tried to compile my prjoect i was getting following error

"Biztalk Error System.String must be Xml serializable to be a message part type"

I checked the System.String and it was already serializable and I was surprised why this error is occurred.

I was unable to solve the problem then at last I closed the visual studio and started it again and tried to compile my project and it was build successfully .

So the solution is : just restart the visual studio and enjoy