HajinStudioGroup
asked on
Is MSDTC problems creating issues with Biztalk connecting to the database
OS Windows 2003 64bit SP1, SQL Server 2005 SP1, BizTalk 2006
Over the past few days an error occurs which requires me to restart the database server which sits on a separate host to allow BizTalk Components to function correctly.
In error state:
From within the Biztalk Administrator if you refresh the group hub, it errors out with a SQL connection error
From within the Biztalk Configuration Tool if you select Group you get a data not available error.
This all seems to point to the DB connectivity issue as the error log below details. My question is the closets thing I can track this do is possible problems with MSDTC, but I am cautions to start making changing based just on a article I found - http://msdn2.microsoft.com/en-us/library/aa561924.aspx when I dont have a better handle on the actual root cause. Does anyone have any experience with this type of problem?
A failure occurred when executing a Windows service request.
Service request: Start
BizTalk host name: BizTalkServerApplication
Windows service name: BTSSvc$BizTalkServerApplic
Additional error information:
Error code: 0xc0c0153f
Error source: BizTalk Server 2006
Error description: A failure occurred when connecting to the BizTalk management database BizTalkMgmtDb.
Please verify the Windows account used by the BizTalk host instance belongs to a Windows group configured for the host BizTalk Group.
Additional error information:
Error code: 0xc0c01b3d
Error source:
Error description: A database failure occurred due to database connectivity problems.
Over the past few days an error occurs which requires me to restart the database server which sits on a separate host to allow BizTalk Components to function correctly.
In error state:
From within the Biztalk Administrator if you refresh the group hub, it errors out with a SQL connection error
From within the Biztalk Configuration Tool if you select Group you get a data not available error.
This all seems to point to the DB connectivity issue as the error log below details. My question is the closets thing I can track this do is possible problems with MSDTC, but I am cautions to start making changing based just on a article I found - http://msdn2.microsoft.com/en-us/library/aa561924.aspx when I dont have a better handle on the actual root cause. Does anyone have any experience with this type of problem?
A failure occurred when executing a Windows service request.
Service request: Start
BizTalk host name: BizTalkServerApplication
Windows service name: BTSSvc$BizTalkServerApplic
Additional error information:
Error code: 0xc0c0153f
Error source: BizTalk Server 2006
Error description: A failure occurred when connecting to the BizTalk management database BizTalkMgmtDb.
Please verify the Windows account used by the BizTalk host instance belongs to a Windows group configured for the host BizTalk Group.
Additional error information:
Error code: 0xc0c01b3d
Error source:
Error description: A database failure occurred due to database connectivity problems.
I faced this problem several times workaround is go to SQL SErver
Management --> Processes, kill the Windows NT \System process ..This process will be in the Suspended state. This process creates locks You need to kill all the suspended process for Windows NT. Once this is done your problem will be solved.
I believe this happened bcos BizTalk MAnagement Databases looses name of SQL server it is hosting on. you can restore the name of server by doing following
use master go select * from sysservers go
2. Identify the name of the local server in the list. If the name exists, and the server id is anything other than 0, run the following statement and replace "yourservername" with the name of the local server:
sp_dropserver 'yourservername','droplogi
If a non-local server has a server id value of 0, then you need to drop that entry and run the sp_dropserver stored procedure.
3. Add the local server back to the list by running this code:
sp_addserver 'localservername', 'local'
Management --> Processes, kill the Windows NT \System process ..This process will be in the Suspended state. This process creates locks You need to kill all the suspended process for Windows NT. Once this is done your problem will be solved.
I believe this happened bcos BizTalk MAnagement Databases looses name of SQL server it is hosting on. you can restore the name of server by doing following
use master go select * from sysservers go
2. Identify the name of the local server in the list. If the name exists, and the server id is anything other than 0, run the following statement and replace "yourservername" with the name of the local server:
sp_dropserver 'yourservername','droplogi
If a non-local server has a server id value of 0, then you need to drop that entry and run the sp_dropserver stored procedure.
3. Add the local server back to the list by running this code:
sp_addserver 'localservername', 'local'
ASKER
I will look into this right away.
ASKER
The server ID seems to be correct as the local host has a value of 0. I am going on 72 hours without a reoccurrence, this is after I disabled SQLSafe a backup tool. This was the first time I saw the issue go away without a reboot. Other SQL servers have the same backup tool with no problems.
Not that I want to see it come back, but if it does I will just the SQL processes to see if this corrects the issue without a reboot. Thanks for the reply.
Not that I want to see it come back, but if it does I will just the SQL processes to see if this corrects the issue without a reboot. Thanks for the reply.
ASKER
Just to update this some...
My testing has shown that this problem is most likely related to the SQL Safe product we have on the DB server. In the error state if I disable the service the problem goes away. When I have this service disabled I have gone 72 hours without the problem and it only occurs when the service is on.
My testing has shown that this problem is most likely related to the SQL Safe product we have on the DB server. In the error state if I disable the service the problem goes away. When I have this service disabled I have gone 72 hours without the problem and it only occurs when the service is on.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I ran the DTCtester tool, and got an error but bigger then that I encountered and condition where I could access the DB server using RDP, but from within the server I could not reach any other server. Seems like a networking problem,
The browser service was unable to retrieve a list of servers from the browser master \\MSRAPDC on the network \Device\NetBT_Tcpip
Why I can't explain how I can get to the host via RDP but can't even ping out or access a file share from the host this explains to me why a reboot fixes the issue.
For now I disabled the 2nd network card as some events point to this, the error has not occurred in 48 hours, previously it happened every 12 hours, I will allow a little more time to see status.