Front-end file system cache problems might occur after a SharePoint configuration database restore.

March 25, 2010   17:41

Last week I was working at a client who just restored one of their SharePoint environments because of a site error. Everything was functioning like normal, until we discovered a major issue with the InfoPath forms publishing mechanism.

For some of the Infopath forms we received an error while upgrading the form to a newer version. The error statement told us that we could not update the form because of an object in the database with the same ID.

To resolve the error we tried to remove the existing form, but instead of removing the form, SharePoint decided to do the opposite and it tried to start some kind of upgrade process. We had no more options to upgrade or even delete the existing form.

(more…)

Posted in Errors, SQL Server, SharePoint | Permalink | Read 1 comment

Troubleshoot disconnected SQL Server users

July 3, 2007   12:15

If you move a database export to a new server, you might experience login problems inside your applications.

The exported database will contain your users, but they are no longer connected to valid SQL Server logins. Even if the same users are existing on the new SQL Server, their ID’s might be different. One of the options is to just recreate and configure the users, but sometimes this is not an option; You might have a lot of users or complicated user rights that you don’t want to check, test and document.

SQL Server contains stored procedure in the Master database to connect your database users with the available SQL Server users. This stored procedure is called “sp_change_users_login”. Just take the steps below to attach your users:

1. Create the (new) required login in the Security database if it doesn’t exist.
2. Run the following SQL and replace the coloured items with your values:
   USE [Your database]
   go
   EXEC sp_change_users_login ‘Update_One’, ‘Original username‘, ‘SQL Server user name‘

Narayana Vyas Kondreddi has written more detailed information about this subject at his website which contains a handy stored procedure “ShowOrphanUsers” which provides you with a list of all unconnected users.

Documentation about the “sp_change_users_login” stored procedure can be found at the MSDN website.

Posted in SQL Server | Featured url | Permalink | Post first comment