Archive for January, 2010

Windows Server 2008 is killing my network connections!

Recently, I have setup some systems on a 10G Network connecting to iSCSI solid state storage. This setup is REALLY fast but I have seen some problems with it recently. In fact, just the other day one of the systems became unresponsive and I saw the following error in the event log:

tcp/ip has detected high memory utilization and has terminated some existing connections to  maintain system stability.

Also in the event logs shortly after that I saw entries about the iSCSI initiator losing connection to the storage and other nasty messages of that sort. After searching around a bit I came to a couple of potential fixes for this problem:

  1. Removing the Symantec Endpoint Firewall from this system, as this could be cause problems when inspecting every packet that comes across  that 10G port.
  2. Disabling Memory Pressure Protection in Windows – article discussing this topic

Hopefully between the two this will solve the problem. I didn’t know that such a feature even existed in Windows. But basically this “feature” will start dropping packets if windows detects an attack on that port. I don’t really know what Microsoft considers an attack, but I am sure 10G of traffic across a port is something that might seem odd to the application.

You learn more and more!

Microsoft SQL Server 2005 and SQL Server 2008 Fix Orphaned Users

This is really for my benefit, but the quick and easy way to detect and fix orphaned Microsoft SQL Server users:

  1. Open a query in SQL Server and select the database you want to fix
  2. Run the following command query analyzer: sp_change_users_login 'Report'
  3. Create a list of the users that get reported back
  4. Make sure the users exist on the new servers, if they do not be sure to create the users
  5. Delete the command form query analyzer in step # 2
  6. Run the following command in query analyzer, replace “UserName” with the user name you want fix: sp_change_users_login 'Auto_Fix', 'UserName'

Y0u can find a lot of articles going into lots of detail on how to fix this problem, but i know when I look it up I just want to see the command not why it does what it does. If you want a really good detailed article you can view this really good article.

Return top