Can’t delete service instances from the HAT or why you shouldn’t rename a SQL Server

By patrickwellink
November 12, 2004
1

Well for sure everybody knew this but I found out the hard way.


We were running a biztalk server and when things went right everything was fine. But every now and then we had to terminate a running orchestration. That would leave us with a entry in the HAT that we could not get rid of…….The only solution to get rid of these entries, was running config framework again…….If we tried to delete the entry from the HAT, we would get a message in the eventlog like the one below:


Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 6912
Date: 11/11/2004
Time: 9:53:55 AM
User: N/A
Computer: XXXXXXXX
Description:


The following stored procedure call failed: ” { call [dbo].[bts_AdminPreemptiveOperateOnInstances_BizTalkServerApplication]( ?, ?, ?, ?, ?)}”. SQL Server returned error string: “The statement has been terminated.;Cannot insert the value NULL into column ‘strDBServer’, table ‘BizTalkMsgBoxDb.dbo.TrackingData’; column does not allow nulls. INSERT fails.;The statement has been terminated.;Cannot insert the value NULL into column ‘strDBServer’, table ‘BizTalkMsgBoxDb.dbo.TrackingData’; column does not allow nulls. INSERT fails.;The statement has been terminated.;Cannot insert the value NULL into column ‘strDBServer’, table ‘BizTalkMsgBoxDb.dbo.TrackingData’; column does not allow nulls. INSERT fails.”.


Today I finally found out what had happened….


This stored procedure ( or one of the sub sub sub stored procs) get’s some data from the sysservers table, and this table is completely empty on the production server. I don’t know why this is but an incorrect server entry would have the same results…. And renaming a server would never update this table. I have a dark brown (dutch expression) suspicion that the server was renamed once in it’s lifetime.


So there it is, this is why you should NEVER rename a SQL server !!!!!


I would like to thank Sijmen Koffeman from Microsoft who figured this out !

Comments: 1

  1. Patrick Wellink says:

    Is the correct servername in the SysServers table if it’s not it defenitely is the cause !

Comments are closed.

  • Recent Posts
  • Recent Comments
  • Archives
  • Categories
  • Meta