Yes I have seen that. What is happening is the procedure is at the point where it is either trying to fix a lost or orphaned user and it is attempting to do it the SQL 2000 way, which is to update the system tables directly.

If you look at the line right after the PRINT statement that reads either

'PRINT '????????Fixing Lost User????:????' + @name' OR 'PRINT '????????Removing Orphan User:????' + @name'

If you have my latest version of the script, it should read

'IF @SvrLevel NOT IN ('90','10')'

Checking to see if this is prior to SQL 2005/2008. If not, then please recopy the script since I have made several changes to the script.

If this is what you have and it is not working, e-mail me at mtutor@gmail.com