kmt333
asked on
migrating sharepoint: trying to transfer the logins between SQL 2005 and receiving ddl statement issues
Hi,
I am moving a WSS 3.0 install to a new SBS 2008 server (sql2005) from Windows 2K3/sql2005 environment. I backed up and restored the databases easily. I need to transfer the logins now and began working through the steps in http://support.microsoft.com/kb/918992/. However, it appears that the WSS database will not allow me to alter/change it and, as a result, I cannot saved the stored procedures that allow me to transfer the logins. Whenever I try to run the query, I get the following response:
Msg 33003, Level 16, State 1, Procedure sp_hexadecimal, Line 27
DDL statement is not allowed.
Msg 33003, Level 16, State 1, Procedure sp_help_revlogin, Line 97
DDL statement is not allowed.
I need to get WSS 3.0 running on the new server. Help!
KMT
I am moving a WSS 3.0 install to a new SBS 2008 server (sql2005) from Windows 2K3/sql2005 environment. I backed up and restored the databases easily. I need to transfer the logins now and began working through the steps in http://support.microsoft.com/kb/918992/. However, it appears that the WSS database will not allow me to alter/change it and, as a result, I cannot saved the stored procedures that allow me to transfer the logins. Whenever I try to run the query, I get the following response:
Msg 33003, Level 16, State 1, Procedure sp_hexadecimal, Line 27
DDL statement is not allowed.
Msg 33003, Level 16, State 1, Procedure sp_help_revlogin, Line 97
DDL statement is not allowed.
I need to get WSS 3.0 running on the new server. Help!
KMT
QUERY from MS KB Article:
USE master
GO
IF OBJECT_ID ('sp_hexadecimal') IS NOT NULL
DROP PROCEDURE sp_hexadecimal
GO
CREATE PROCEDURE sp_hexadecimal
@binvalue varbinary(256),
@hexvalue varchar (514) OUTPUT
AS
DECLARE @charvalue varchar (514)
DECLARE @i int
DECLARE @length int
DECLARE @hexstring char(16)
SELECT @charvalue = '0x'
SELECT @i = 1
SELECT @length = DATALENGTH (@binvalue)
SELECT @hexstring = '0123456789ABCDEF'
WHILE (@i <= @length)
BEGIN
DECLARE @tempint int
DECLARE @firstint int
DECLARE @secondint int
SELECT @tempint = CONVERT(int, SUBSTRING(@binvalue,@i,1))
SELECT @firstint = FLOOR(@tempint/16)
SELECT @secondint = @tempint - (@firstint*16)
SELECT @charvalue = @charvalue +
SUBSTRING(@hexstring, @firstint+1, 1) +
SUBSTRING(@hexstring, @secondint+1, 1)
SELECT @i = @i + 1
END
SELECT @hexvalue = @charvalue
GO
IF OBJECT_ID ('sp_help_revlogin') IS NOT NULL
DROP PROCEDURE sp_help_revlogin
GO
CREATE PROCEDURE sp_help_revlogin @login_name sysname = NULL AS
DECLARE @name sysname
DECLARE @type varchar (1)
DECLARE @hasaccess int
DECLARE @denylogin int
DECLARE @is_disabled int
DECLARE @PWD_varbinary varbinary (256)
DECLARE @PWD_string varchar (514)
DECLARE @SID_varbinary varbinary (85)
DECLARE @SID_string varchar (514)
DECLARE @tmpstr varchar (1024)
DECLARE @is_policy_checked varchar (3)
DECLARE @is_expiration_checked varchar (3)
DECLARE @defaultdb sysname
IF (@login_name IS NULL)
DECLARE login_curs CURSOR FOR
SELECT p.sid, p.name, p.type, p.is_disabled, p.default_database_name, l.hasaccess, l.denylogin FROM
sys.server_principals p LEFT JOIN sys.syslogins l
ON ( l.name = p.name ) WHERE p.type IN ( 'S', 'G', 'U' ) AND p.name <> 'sa'
ELSE
DECLARE login_curs CURSOR FOR
SELECT p.sid, p.name, p.type, p.is_disabled, p.default_database_name, l.hasaccess, l.denylogin FROM
sys.server_principals p LEFT JOIN sys.syslogins l
ON ( l.name = p.name ) WHERE p.type IN ( 'S', 'G', 'U' ) AND p.name = @login_name
OPEN login_curs
FETCH NEXT FROM login_curs INTO @SID_varbinary, @name, @type, @is_disabled, @defaultdb, @hasaccess, @denylogin
IF (@@fetch_status = -1)
BEGIN
PRINT 'No login(s) found.'
CLOSE login_curs
DEALLOCATE login_curs
RETURN -1
END
SET @tmpstr = '/* sp_help_revlogin script '
PRINT @tmpstr
SET @tmpstr = '** Generated ' + CONVERT (varchar, GETDATE()) + ' on ' + @@SERVERNAME + ' */'
PRINT @tmpstr
PRINT ''
WHILE (@@fetch_status <> -1)
BEGIN
IF (@@fetch_status <> -2)
BEGIN
PRINT ''
SET @tmpstr = '-- Login: ' + @name
PRINT @tmpstr
IF (@type IN ( 'G', 'U'))
BEGIN -- NT authenticated account/group
SET @tmpstr = 'CREATE LOGIN ' + QUOTENAME( @name ) + ' FROM WINDOWS WITH DEFAULT_DATABASE = [' + @defaultdb + ']'
END
ELSE BEGIN -- SQL Server authentication
-- obtain password and sid
SET @PWD_varbinary = CAST( LOGINPROPERTY( @name, 'PasswordHash' ) AS varbinary (256) )
EXEC sp_hexadecimal @PWD_varbinary, @PWD_string OUT
EXEC sp_hexadecimal @SID_varbinary,@SID_string OUT
-- obtain password policy state
SELECT @is_policy_checked = CASE is_policy_checked WHEN 1 THEN 'ON' WHEN 0 THEN 'OFF' ELSE NULL END FROM sys.sql_logins WHERE name = @name
SELECT @is_expiration_checked = CASE is_expiration_checked WHEN 1 THEN 'ON' WHEN 0 THEN 'OFF' ELSE NULL END FROM sys.sql_logins WHERE name = @name
SET @tmpstr = 'CREATE LOGIN ' + QUOTENAME( @name ) + ' WITH PASSWORD = ' + @PWD_string + ' HASHED, SID = ' + @SID_string + ', DEFAULT_DATABASE = [' + @defaultdb + ']'
IF ( @is_policy_checked IS NOT NULL )
BEGIN
SET @tmpstr = @tmpstr + ', CHECK_POLICY = ' + @is_policy_checked
END
IF ( @is_expiration_checked IS NOT NULL )
BEGIN
SET @tmpstr = @tmpstr + ', CHECK_EXPIRATION = ' + @is_expiration_checked
END
END
IF (@denylogin = 1)
BEGIN -- login is denied access
SET @tmpstr = @tmpstr + '; DENY CONNECT SQL TO ' + QUOTENAME( @name )
END
ELSE IF (@hasaccess = 0)
BEGIN -- login exists but does not have access
SET @tmpstr = @tmpstr + '; REVOKE CONNECT SQL TO ' + QUOTENAME( @name )
END
IF (@is_disabled = 1)
BEGIN -- login is disabled
SET @tmpstr = @tmpstr + '; ALTER LOGIN ' + QUOTENAME( @name ) + ' DISABLE'
END
PRINT @tmpstr
END
FETCH NEXT FROM login_curs INTO @SID_varbinary, @name, @type, @is_disabled, @defaultdb, @hasaccess, @denylogin
END
CLOSE login_curs
DEALLOCATE login_curs
RETURN 0
GO
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
this ended up being an issue where we got Microsoft involved and spent 15+ hours resolving the problem (corruption in SQL DB).
ASKER
thanks for the help. your info is correct, it just ended up being an entirely different problem with corruption of the db.
As kmt333 commented you are unable to allow remote connections on the WID (Windows Internal Database). However...
It seems, in most cases, that the database has been created by using the "Administrator" account, which will be disabled afterwards.
So when you change the password for the "Administrator" account, enable the account and logon use that account you are able to grant all the rights needed to a more appropriate account.
Afterwards you are able by using a named pipes connection to alter the connections to the database. Also you may elevate your own right to for example sysadmin.
Maybe this could be helpful..
P.S. DO NOT FORGET to disable de Administrator account afterwards
It seems, in most cases, that the database has been created by using the "Administrator" account, which will be disabled afterwards.
So when you change the password for the "Administrator" account, enable the account and logon use that account you are able to grant all the rights needed to a more appropriate account.
Afterwards you are able by using a named pipes connection to alter the connections to the database. Also you may elevate your own right to for example sysadmin.
Maybe this could be helpful..
P.S. DO NOT FORGET to disable de Administrator account afterwards
ASKER
1) create a tempdb on serverA and use SSIS to transfer logins to DB that allows remote connections.
2) connect to tempdb from serverB and use SSIS to transfer logins to new MICROSOFT##SSEE that houses SharePoint.
I think this could work since the problem seems to be that I do not have the rights I need or the ability to remotely connect to the MICROSOFT##SSEE database. If you know of a workaround that will either allow me to save a stored proc or connect remotely to this db, please let me know.
KMT