Geeks With Blogs
Mark Wiggins blog

Error: "exhausted the network retry attempts"

Do you have over 50 receive locations that you use for Biztalk 2004/2006. Have you ever found them disabled because of Exhausted Network Retries? The problem is not Biztalk but Windows Server 2003 and NetBIOS. Basically it comes down to a default value of connections to a particular server. The default value is 50. You can set this value up to 65000. We used 100 as the value and run at 91 connections constantly. This article will help: http://support.microsoft.com/default.aspx?scid=kb;en-us;810886

 

Here is the basics of what you need to do:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters
3. In the right pane, double-click the MaxCmds value.
4. In the Value data box, verify that the value is 50 or more.

Note In a Microsoft Windows Terminal Services environment, you may have to set the MaxCmds registry value to 500 or more. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
232476 (http://support.microsoft.com/kb/232476/) Terminal Server client connections and logon limited by MaxWorkItem and MaxMpxCt values
5. Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
Note Make sure that you make this change to the lanmanserver\parameters registry key and not to the lanmanworkstation\parameters registry key mentioned in step 2.
6. In the right-pane, double-click the MaxMpxCt value.

Note On SMB servers that are running a version of Windows earlier than Windows 2000, the MaxMpxCt registry entry is named MaxMpxCount, but has the same function.
7. In the Value data box, verify that the value is 50 or more.

Note The MaxMpxCt value determines the maximum number of simultaneous, active requests that the server permits from an individual client.
8. Quit Registry Editor.

 

I did all of these things on an install of BizTalk 2006 running on Windows Server 2003 and I have not had another receive location disable because of exhausted network retries.

Posted on Thursday, September 14, 2006 2:44 PM | Back to top


Comments on this post: BizTalk Receive Locations Disabling

# re: BizTalk Receive Locations Disabling
Requesting Gravatar...
Hi everyone,
Just though I would let you know that I was running into the same issue at our oganizations. We are using BTS2004 with Windows Server 2003 (On both the BTS and the file server) with about 150 file received location pointing to the same server. I made the changes as described but it didn't help one bit. In fact we didn't even have those registry entries on our servers.

What I did do was (since the server we were having a problem with had FTP server already loaded) I moved about %50 of our file transports over to FTP transports and our Shutdowns have completedly stopped over the last week. I know it's not the best solution but it is one that definitely works!!

Good luck!
John
Left by John Capra on Oct 23, 2008 7:37 AM

# re: BizTalk Receive Locations Disabling
Requesting Gravatar...
If the registry keys are not there then create them. This will fix the problem. We had to create the keys.
Left by mark on Oct 23, 2008 9:13 AM

# re: BizTalk Receive Locations Disabling
Requesting Gravatar...
I did add the entries and it did nothing. Added it to both the BTS server and the server where we were pulling from and they continued to shut down. I even went through all the ports to change the service window to see if that would help and all that did was just have them shut down at sepcific times.

Seems like a lot of b.s. to go through to just have BTS do what it was intended to do.
Left by John Capra on Oct 28, 2008 4:28 AM

# re: BizTalk Receive Locations Disabling
Requesting Gravatar...
Sounds like you may have a different problem. Not sure what it is but if the problem is as described then this is the fix. If you have another issue which you may have then perhaps it is not the answer for you. If you have found another way to handle your problem I suggest going and blogging about it.
Left by Mark on Oct 28, 2008 10:48 AM

# re: BizTalk Receive Locations Disabling
Requesting Gravatar...
Is a reboot required ?
I am familiar with the problem, we already did a lot of servers a couple of years ago within the company, and we always assumed we needed to reboot. Now we have a server which is sensitive of rebooting, and i question myself if a reboot is necessary ?

Thanks,
S.
Left by stefvb on Jan 12, 2009 8:03 PM

# re: BizTalk Receive Locations Disabling
Requesting Gravatar...
That is a good question. I think typically when a registry key is edited a reboot is required. Can you try it without rebooting and let me know if the key is picked up. Easy enough test I think. Let me know if you cannot do it on a test machine.
Left by Mark on Jan 13, 2009 12:49 AM

# re: BizTalk Receive Locations Disabling
Requesting Gravatar...
I have changed all the necessary registry settings on both Biztalk live servers and the server that hosts the unc shares. In addition, I have increased the retry attempts. This had not made a bit of difference and I still have around 20 receive locations disabling on a 25 minute basis with "exhausted the network retry attempt" error. I wonder if you can suggest anything else I can try?
Left by jules on Apr 13, 2011 2:39 AM

Your comment:
 (will show your gravatar)


Copyright © Mark Wiggins | Powered by: GeeksWithBlogs.net