"Stack overflow dump not possible" error messages are logged in the SQL Server error log on a computer that is running SharePoint Team Services and Microsoft SQL Server (888843)

RESOLUTION

To remove the existing foreign keys, use Microsoft SQL Query Analyzer on the computer that is running Microsoft SQL Server to run a query to remove the existing foreign keys from the UserInfo table, and then restart Microsoft Internet Information Services (IIS).

Note Microsoft Office XP Service Pack 3 (SP3) for SharePoint Team Services removes the foreign key limitation that is set for the UserInfo table in SharePoint Team Services. After you install Office XP SP3 for SharePoint Team Services on the server, the foreign key limitation does not apply to new Web sites that you create. For more information about Office XP Service Pack 3 for SharePoint Team Services, click the following article number to view the article in the Microsoft Knowledge Base: Installing Office XP SP3 for SharePoint Team Services does not remove existing foreign keys. Office XP SP3 for SharePoint Team Services only prevents new foreign keys from being created. If the number of foreign keys that currently are in the UserInfo table exceeds the maximum number of foreign keys, use SQL Query Analyzer to run a script to remove the existing foreign keys.

To use SQL Query Analyzer to remove existing foreign keys from the UserInfo table, follow these steps:

1. Use SQL Query Analyzer to run a query to remove the existing foreign keys. To do this, follow these steps:
   1. Click Start, point to Programs, point to Microsoft SQL Server, and then click Query Analyzer.
   2. In the Connect to SQL Server dialog box, specify the instance of SQL Server that you want to connect to, specify the type of authentication that you want to use, and then click OK.
   3. In the list that is displayed in the toolbar, click the DOWN ARROW, and then click the database that is used by SharePoint Team Services.
   4. Copy and then paste the following query to the Editor pane of SQL Query Analyzer:

      USE "databaseName"
      GO
      DECLARE @TableName nvarchar(256)
      DECLARE @KeyName nvarchar(256)
      DECLARE @DropSQL nvarchar(1024)
      DECLARE FKCursor CURSOR FOR
      SELECT dbo.sysobjects.name AS KeyName, sysobjects_1.name AS ParentName
      FROM dbo.sysobjects INNER JOIN dbo.sysobjects sysobjects_1 ON dbo.sysobjects.parent_obj = sysobjects_1.id
      WHERE (dbo.sysobjects.type = 'F') AND (sysobjects_1.name <> N'Lists')
      
      OPEN FKCursor
      FETCH NEXT FROM FKCursor INTO @KeyName, @TableName
      
      WHILE @@FETCH_STATUS = 0
      BEGIN
          SET @DropSQL = 'ALTER TABLE ' + @TableName
          SET @DropSQL = @DropSQL + ' DROP CONSTRAINT ' + @KeyName
          EXECUTE (@DropSQL)
          FETCH NEXT FROM FKCursor INTO @KeyName, @TableName
      END
      
       CLOSE FKCursor
       DEALLOCATE FKCursor
      

   5. Click Execute Query.
2. Restart IIS. To do this, click Start, click Run, type iisreset in the Open box, and then click OK.

Note If you delete a user from the Web site, and then you use the Server Health Check feature to check server health, the user's information is deleted from the UserInfo table in the database. The user's information is deleted from the UserInfo table even though the user still owns list items and documents. Therefore, when you view documents and list items that are owned by that user on Web pages in the Web site, the name of the user is not listed in the Modified By and Created By fields of the documents and of the list items. Instead, the user ID of the user is listed in the Modified By and Created By fields. This condition does not affect the functionality of the Web site.