Event id 1185 File Networking Windows Server 2003
THE SCENARIO
We have 4 web servers (Win 2008 R2) hosting 9 websites and 2 file servers (Win 2003 servers) which serves the images for all our websites.
When a user is requesting a page from our website and the images from the page must be displayed, we got the error below, and on the site it doesn't show the images it shows the default image icon.
We tried many different scenarios from other posts but nothing seems to help:
The problem that was temporary solved it was fixed with registry values (below) after windows server was updated and restarted the problem appeared again.
The event id that is displayed is 1185 file networking error.
Failed to start monitoring changes to '\\example.local\VPP\PageFiles\a3\5f' because the network BIOS command limit has been reached. For more information on this error, please refer to Microsoft
knowledge base article 810886. Hosting on a UNC share is not supported for the Windows XP Platform.
Application virtual path: '/'
Registery values:
Windows 2008 R2 (I've got four):
lanmanworkstation\MaxCmds = 8192
Windows 2003 File Server (Two servers. All values decimal):
lanmanserver\EnableOplocks = 0
lanmanserver\MaxFreeConnections = 100
lanmanserver\MaxMpxCT = 8192
lanmanserver\MaxRawWorkItems = 512
lanmanserver\MaxWorkItems = 65536
lanmanserver\MinFreeConnections = 32
MaxCmds (on the webservers) and MaxMpxCT (on the file servers) to: 65536
Any other opinions?
Thank youwillockss
August 30th, 2012 9:53am
Hi,
Thank you for the post.
1.Please note: max value of MaxCmds, MaxMpxCt and MaxWorkItems is 65535 not 65536.
2.Try to set FCNMode registry value to 2 and install KB911272 on your web server.
http://support.microsoft.com/kb/911272
http://blogs.msdn.com/b/carloc/archive/2009/09/06/hosting-on-a-unc-share-is-not-supported-for-the-windows-xp-platform.aspx
If there are more inquiries on this issue, please feel free to let us know.
RegardsRick Tan
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
September 3rd, 2012 4:07am
Hi again,
The problem it's still persist, and we do not have .net 2.0, we have .net 4.0.willockss
September 18th, 2012 9:38am