| Robert Rijsdijk 2005-05-10, 5:55 pm |
| At one of our customers we installed a complete new BizTalk infrastructure to
improve the performance (throughput).
The following machines are involved:
1 x SQL Server dedicated to master message box processing wit publication
disabled, single default instance.
Software
Microsoft SQL Server 2000 with SP3a and BizTalk SQL Hotfix
SQL2000-KB810185-8.00.0878-ENU.exe
Microsoft Windows Server 2003 SP1
Database Instance BizTalkMsgBoxDb
2 x SQL Servers dedicated to message box publication, each 1 named instance.
Software
2 x Microsoft SQL Server 2000 with SP3a and BizTalk SQL Hotfix
SQL2000-KB810185-8.00.0878-NU.exe
Microsoft Windows Server 2003 SP1
Database Instance BizTalkMsgBoxPubDb1 , BizTalkMngmtDb , EDIDb , SSO ,
etc
Database Instance BizTalkMsgBoxPubDb2 , BizTalkDTADb
1 x BizTalk 2004 Server Machine DL380 3 GB of RAM
Software
Microsoft BizTalk Enterprise Edition 2004 SP1
Microsoft Windows Server 2003 SP1
MDAC 2.8
MSXML / SQLXML
When BizTalk uses one singe MessageBox on the Master Message Box Machine
there are no errors generated, BizTalk works fine. When we enable the one or
two extra Publication MessageBoxes (via the BizTalk Server Administration
Console), the BizTalk Engine starts with Network Errors.
“An attempt to connect to “BizTalkMsgBoxPubDb2“ SQL Server Database on
Server “<SERVERNAME>“ failed with error:
“[DBNETLIB][ConnectionWrite(send())]. General network error. Check your
network documentation.“.
This has something to do with ACK's and FIN's I read in some discussion
groups.
What I saw on the SQL Server where the Publication Message Box is configured
were many SQL Server Locks.
BizTalk Server 2004 Engine starts up the connection with his own message
boxes one minute later.
Any idea how we can fix this network problem or anyone got an idea ?
Many thanks for your input.
|