SQL Server 2005 April CTP - Invalid SSPI Packet Size

SQL Server 2005 April CTP - Invalid SSPI Packet Size

• Foris Zoltan

  I have a some questions which will help me troubleshoot this problem.
  
  Is this problem reproducible Does it happen everytime after you bring up SSMS Do you install SQL Server management studio in the application tier, trying to understand why it impacts installing the application tier 
  
  SSMS uses ADO.net (sqlclient) so does the same problem reproduce with your sqlclient apps
  
  Srik
  
  

• Andreiciuc Dan

  Please do post the stack trace.  We are currently investigating this issue.  We know where in code this error is raised.  We also have a theory as to what might trigger this.  What is not clear though is why it happens only the first time. I will keep you posted after we investigate this further.
  
  

• Sune D. Moeller

  Is there any news about this issue I just runned into the same problem when i tried to install TFS.

  
  
  

• Dirk Rombauts

  We are having the same problem with the SQL Server 2005 June CTP.  It's preventing us from installing the TFS Beta 2. 
  
  Does anyone know when the next TFS CTP will be
  

• Mark McLain

  Has anyone been able to resolve this We're having the same issue.
  
  

• MosIdiot

  The root cause of the problem is because the SSPI token size is (generated during integrated authentication) getting to be larger than was allowed.  If the account that we're tryign to connect as is a member of a large number of groups it can result in the SSPI blob becoming large.  This bug is fixed and should be available in Whidbey RTM.
  
  What is still unclear though is why only the first connection attempt fails and subsequent connections succeed. To determine this we'll need to enable TDS tracing on the server to see what the SSPI token looks like on the wire. 
  
  

• Alvarohhhhhh

  We have af ix for this problem in Whidbey.  This fix should be be picked up by the next TFS CTP drop.  The root cause again is a large SSPI blob generated by the Windows SSPI API's.  I don't know of any other workaround to this, other than not use Integrated Auth, which may not be a possibility for TFS.  Also with respect to the user account being a member of a large number of groups, I beleive it is one of the factors that could contribute to a large SSPI size but not necessarily the only one. The SSPI token is a black box to us and is returned by the Windows SSPI API's.
  
  

• sgcuda

  Yes, it happens every time I bring up SSMS. However, it only happens the very first time I try to authenticate.  After that it works fine without the error.  The reason why it impacts the application tier is that it also affects the Report Server in the same way.  The first time I bring up report server I get the same error message.  If I refresh the browser, report server authenticates and works fine. 
  
  When installing the application tier I get an error 32000 setting up the warehouse.  The error is this same Invalid SSPI Packet Size when I run the setupwarehouse step from the command line.  I can post a stack trace of this if it would help.
  
  Brandon
  

• Daniel Pravat

  Here is the stack trace:
  
  Error 32000.The Commandline '"C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\SetupWarehouse.exe" -n -s "chaos-sql" -d BisDWDB -c "C:\Program Files\Microsoft Visual Studio 2005 Enterprise Server\BISIISDIR\bisdwserver\bin\Consolidated.xml" -a "WINNTDOM\umproject" -ra "WINNTDOM\umproject" -v -l "C:\DOCUME~1\UMSHAR~1\LOCALS~1\Temp\setupwarehouse.log"' returned non-zero value: 3.
  
  System.ArgumentException: Invalid SSPI packet size.
     at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup)
     at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
     at System.Data.SqlClient.SqlInternalConnectionTds..ctor(SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
     at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
     at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
     at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
     at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
     at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
     at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
     at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
     at System.Data.SqlClient.SqlConnection.Open()
     at Microsoft.VisualStudio.Bis.Warehouse.MetaData.WarehouseSchemaCreator.CreateWarehouseDatabase(String accessUser, String dataReaderAccount)
     at Microsoft.VisualStudio.Bis.Tools.WarehouseSetup.SetupWarehouse()
  
  Please let me know when you have a workaround or fix.  My team would like to look into team system to see if it will work for us.  Thanks.
  
  Brandon
  

• Vasil Trifonov

  Have you tried posting this question in the NET Framework inside SQL Server forum
  http://forums.microsoft.com/msdn/ShowForum.aspx ForumID=43
  
  

• jhoney

  I'm seeing the SSPI packet size error in the June CTP as well.  I've observed it on two different domains. 
  
  I opened a bug in the "MSDN Product Feedback Center" (aka Ladybug) with bugid FDBK30644 to reflect that the June CTP did not fix this.
  
  If anyone else is still seeing this error message in the June CTP it might help to either validate or add a comment to that bug.
  

• Z.Fan

  I don't think this is the case with the user I am using to install TFS.  My user is only member of 4 groups.  It seems a bit unrealistic to say that this is something we need to wait for Whidbey to get fixed - because this, in essence, means that we will not get to even install TFS until after the full release of VS2005.  Is there a workaround available now   Thank you much for your attention.
  

• Giovanni Mastichio

  Have you heard any response about this   I am having the same issue.
  
  Thanks
  

• S Eisenberg

  I would be interested in doing the trace since my user is only a member of a few groups.  Just let me know what I need to to. 
  
• SQL Server 2005 April CTP - Invalid SSPI Packet Size