I am currently working on integration project that is utilising BizTalk
2004. We are receiving intermittent exceptions occurring in the BizTalk
framework which we believe could be down to a network infrastructure issue.
Occasionally we are unable to ping any of the BizTalk servers for about 10
seconds - this is very intermittent and we believe it causes the following
error:

The following stored procedure call failed: " { call
[dbo].& #91;bts_AdminPreemptiveOperateOnInstance
s_OrchestrationHost]( ?, 
?, ?, ?,
?)}". SQL Server returned error string: "The statement has been
terminated.;Cannot insert the value NULL into column 'strDBServer', table
'MsgBox.dbo.TrackingData'; column does not allow nulls. INSERT fails.;The
statement has been terminated.;Cannot insert the value NULL into column
'strDBServer', table 'MsgBox.dbo.TrackingData'; column does not allow nulls.
INSERT fails.;The statement has been terminated.;Cannot insert the value
NULL into column 'strDBServer', table 'MsgBox.dbo.TrackingData'; column does
not allow nulls. INSERT fails.;The statement has been terminated.;Cannot
insert the value NULL into column 'strDBServer', table
'MsgBox.dbo.TrackingData'; column does not allow nulls. INSERT fails.".


It appears from the above entry in the application event log that when the
BizTalk framework attempts to resolve\validate a computer name and stored
the result in the 'strDBServer' parameter - if it fails this value is null.
When the SP on the MsgBox database is called it fails because of the null
value.

I believe the issues we are having are related to connectivity to our
DNS\WINS server. To prove the point to our network infrastructure team I
need to get some better understanding of what exactly causes this issue in
BizTalk. So the questions I have are:

Does anyone know what steps occur in code before the
'[dbo].& #91;bts_AdminPreemptiveOperateOnInstance
s_OrchestrationHost]( ?,
 ?, ?,
?, ?)}' stored procedure is called - specifically the code that sets the
'strDBServer' variable?

If the server name is resolved\validated before the
'[dbo].& #91;bts_AdminPreemptiveOperateOnInstance
s_OrchestrationHost]( ?,
 ?, ?,
?, ?)}' stored procedure is called is the result of the
resolution\validation cached in BizTalk?

Cheers in advance

Ollie Riches

[ Post a follow-up to this message ]

Have you run SQL Profiler on the msgbox machine to see what's going on from
its point of view?

"Ollie Riches" <ollie.riches@phoneanalyser.net> wrote in message
news:uT9FdrqZFHA.2520@TK2MSFTNGP09.phx.gbl...
>I am currently working on integration project that is utilising BizTalk
> 2004. We are receiving intermittent exceptions occurring in the BizTalk
> framework which we believe could be down to a network infrastructure
> issue.
> Occasionally we are unable to ping any of the BizTalk servers for about 10
> seconds - this is very intermittent and we believe it causes the following
> error:
>
> The following stored procedure call failed: " { call
> [dbo].& #91;bts_AdminPreemptiveOperateOnInstance
s_OrchestrationHost]( ?
, ?, ?,
> ?,
> ?)}". SQL Server returned error string: "The statement has been
> terminated.;Cannot insert the value NULL into column 'strDBServer', table
> 'MsgBox.dbo.TrackingData'; column does not allow nulls. INSERT fails.;The
> statement has been terminated.;Cannot insert the value NULL into column
> 'strDBServer', table 'MsgBox.dbo.TrackingData'; column does not allow
> nulls.
> INSERT fails.;The statement has been terminated.;Cannot insert the value
> NULL into column 'strDBServer', table 'MsgBox.dbo.TrackingData'; column
> does
> not allow nulls. INSERT fails.;The statement has been terminated.;Cannot
> insert the value NULL into column 'strDBServer', table
> 'MsgBox.dbo.TrackingData'; column does not allow nulls. INSERT fails.".
>
>
> It appears from the above entry in the application event log that when the
> BizTalk framework attempts to resolve\validate a computer name and stored
> the result in the 'strDBServer' parameter - if it fails this value is
> null.
> When the SP on the MsgBox database is called it fails because of the null
> value.
>
> I believe the issues we are having are related to connectivity to our
> DNS\WINS server. To prove the point to our network infrastructure team I
> need to get some better understanding of what exactly causes this issue in
> BizTalk. So the questions I have are:
>
> Does anyone know what steps occur in code before the
> '[dbo].& #91;bts_AdminPreemptiveOperateOnInstance
s_OrchestrationHost]( 
?, ?, ?,
> ?, ?)}' stored procedure is called - specifically the code that sets the
> 'strDBServer' variable?
>
> If the server name is resolved\validated before the
> '[dbo].& #91;bts_AdminPreemptiveOperateOnInstance
s_OrchestrationHost]( 
?, ?, ?,
> ?, ?)}' stored procedure is called is the result of the
> resolution\validation cached in BizTalk?
>
> Cheers in advance
>
> Ollie Riches
>
>

[ Post a follow-up to this message ]

Good afternoon Hugo!

We did run the profiler and we found that the message box sql server machine
had somehow 'lost' it's @@servername value which was causing the problem.

It goes live tomorrow 

Ollie Riches




"Hugo Rodger-Brown" <hugo@rodger-brown.com> wrote in message
news:O7O8D83aFHA.3184@TK2MSFTNGP15.phx.gbl...
> Have you run SQL Profiler on the msgbox machine to see what's going on
from
> its point of view?
>
> "Ollie Riches" <ollie.riches@phoneanalyser.net> wrote in message
> news:uT9FdrqZFHA.2520@TK2MSFTNGP09.phx.gbl... 
10[vbcol=seagreen] 
following[vbcol=seagreen] 
?,[vbcol=seagreen] 
table[vbcol=seagreen] 
fails.;The[vbcol=seagreen] 
the[vbcol=seagreen] 
stored[vbcol=seagreen] 
null[vbcol=seagreen] 
in[vbcol=seagreen] 
?,[vbcol=seagreen] 
?,[vbcol=seagreen] 
>
>

[ Post a follow-up to this message ]

Have you renamed the server after SQL was installed? Then you have to run
sp_removeserver oldname and sp_addserver newname,local

Best regards
Niklas Engfelt


"Ollie Riches" <ollie.riches@phoneanalyser.net> wrote in message
news:eu4f3cCbFHA.2440@TK2MSFTNGP10.phx.gbl...
> Good afternoon Hugo!
>
> We did run the profiler and we found that the message box sql server
> machine
> had somehow 'lost' it's @@servername value which was causing the problem.
>
> It goes live tomorrow 
>
> Ollie Riches
>
>
>
>
> "Hugo Rodger-Brown" <hugo@rodger-brown.com> wrote in message
> news:O7O8D83aFHA.3184@TK2MSFTNGP15.phx.gbl... 
> from 
> 10 
> following 
> ?, 
> table 
> fails.;The 
> the 
> stored 
> null 
> in 
> ?, 
> ?, 
>
>

[ Post a follow-up to this message ]

No we didn't rename the server was installed, we are aware this could have
caused the issue but we no for a fact that it has not been reinstalled. It
also happened on our UAT system as well.

Cheers for the info

Ollie Riches

"Niklas E" <raven_tln0sp4m@hotmail.com> wrote in message
news:eLRlAAocFHA.3040@TK2MSFTNGP14.phx.gbl...
> Have you renamed the server after SQL was installed? Then you have to run
> sp_removeserver oldname and sp_addserver newname,local
>
> Best regards
> Niklas Engfelt
>
>
> "Ollie Riches" <ollie.riches@phoneanalyser.net> wrote in message
> news:eu4f3cCbFHA.2440@TK2MSFTNGP10.phx.gbl... 
>
>

[ Post a follow-up to this message ]