Issue with Biztalk 2006 talking to one of our SQL boxes

Hi All

I am getting lots of 5740 & 5743 logged in the app log of our Biztalk Server.

The adapter "SQL" raised an error message. Details "[DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.".

The adapter failed to transmit message going to send port "SQL-DeriveItemCode" with URL "SQL://1**SQL4/pepsibilling/". It will be retransmitted after the retry interval specified for this Send Port. Details:"[DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.".


Basically the queues build up and the transactions eventually get through.

I have searched high and low and found a MS KB that I thoguth was related but ot hasn't made any difference.

http://support.microsoft.com/kb/961180

Anyway it could well be our SQL box in question. The box is win2k3 Ent SP1 (SQL 2000 Ent SP4)

Any suggestions would be great.

Thanks

Arm
LVL 1
ArmstrongIntAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

YeatsieCommented:
Check for network related errors in the Biztalk server's event logs, in the SQL 2000 error logs, and in that servers event logs also. This will give you more of a picture as to the state of the network.
Rgds Simon
0
ArmstrongIntAuthor Commented:
Hi Simon

Thanks for coming back to me, There is nothing related in the SQL 2000 boxes event logs which leads me to think its a biztalk server issue.

I have been monitoring networking, no packet loss between servers, plenty of bandwidth.

Thanks Arm
0
ArmstrongIntAuthor Commented:
FYI this has been esculated to MS support.

Thanks

Arm
0
ArmstrongIntAuthor Commented:
Solution is here

http://support.microsoft.com/?id=154628

However in my case the SQL wasn't logging any errors but the regisrty addition fixed teh issue.

Thansk

Arm
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
YeatsieCommented:
Wow, super-cryptic. Well done Arm.
What backlog value did you set the registry to? Sounds like a good reason to upgrade from SQL2000 also.
rgs Simon
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.