September 9, 2010 at 12:49 pm
Scenario: our website runs on ASP.NET 1.1 (think) and gets data from a SQL Server 2005 instance we have running on a virtual instance of Windows Server 2008 Standard guest OS in Hyper V which runs on a Windows Server 2008 Datacenter host.
It's been working fine up till this Friday, and as far as I can tell, we didn't make any changes that day that could possibly affect this.
The errors we get several times a day, as viewed in the browser when we pull up the website, are one of two:
1.
An error was caught on the web site at 9/9/2010 10:01:04 AM .Net SqlClient Data Provider Cannot generate SSPI context.
Unable to traverse server variables. STACK TRACE
at Microsoft.VisualBasic.CompilerServices.LateBinding.LateGet(Object o, Type objType, String name, Object[] args, String[] paramnames, Boolean[] CopyBack)
at RiccaChemical.techtip.Page_Load(Object sender, EventArgs e) in c:\inetpub\wwwroot\RiccaChemical\include\techtip.ascx.vb:line 37 .Net SqlClient Data Provider Cannot generate SSPI context.
or
2.
An error was caught on the web site at 9/9/2010 10:01:03 AM .Net SqlClient Data Provider Cannot generate SSPI context.
Unable to traverse server variables. STACK TRACE
at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnection.Open()
at System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState)
at System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
at RiccaChemical.getTechTip.Page_Load(Object sender, EventArgs e) in c:\inetpub\wwwroot\RiccaChemical\getTechTip.aspx.vb:line 118 .Net SqlClient Data Provider Cannot generate SSPI context.
When we get this error, we reboot the database server and we're good to go for a while, but obviously, that's not a solution.
I've done some SSPI googling and it seems to have something to do with the user we named "web", which is what the ASP.NET code uses to interact with the database.
Should I delete that user and re-create it? Change password? Is there something else I am missing?
September 9, 2010 at 2:35 pm
Are you running IIS on the same box as SQL, if so, perhaps you could move it to another VM. A good Idea to isolate things. Also, if you havn't made any changes, review the windows installer logs to see if a patch has been added. Perhaps you have alot more users accessing your site?
September 9, 2010 at 7:58 pm
we just got it fixed. It turns out this error will occur when you have the DB server with a different time (in this case, it was 12 minutes off) than the domain controller.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply