SMSQL errors on initial configuration wizard setup

[lrhvidsten]

I'm guessing there's some obvious configuration step I'm missing here...probably on my mostly default SQL Server setup.

I'm receiving errors every time I try to run the configuration wizard script to migrate my databases from the local drives to the iSCSI luns. The error occurs after the pre-migration DBCC checkdb and the remapping of the system dbs. Then the config wizard script stops the sql server, and continually fails to restart the sql server services. At this point, it's unable to connect and fails with SQL-DMO authentication errors. I've checked my settings and can't seem to find anything wrong. This problem first occurred yesterday. Today, I uninstalled Snapmanager and SQL server 2005 from the machine. I then reinstalled both products. I left Snapdrive alone as it seemed to be working fine. SQL Server 2005 with sp3 is what I've been using.

Please help!

Note: SQL server services are using a domain user service account with no admin privs per MS best practices.

Snapdrive and SMSQL are using a domain administrator service account.

Windows 2003 R2 SP2 host using iSCSI initiator 2.08

Snapdrive 6.1

SMSQL 5.0R1

FAS2020A

Data ONTAP 7.2.5.1

Even with the fresh install of SMSQL and SQL Server today, I'm getting the same errors.

Here is the SMSQL log of events...

[19:05:50.317]  Retrieving ONTAP virtual disks information...
[19:05:56.259]
[19:05:56.259]  *** SnapManager for SQL Server Report

[19:05:56.259]  Configuration Time Stamp: 04-14-2009_19.05.28
[19:05:56.259]  Host Name: SAWTOOTH
[19:05:56.259]  New default SnapInfo directory for [SAWTOOTH] : H:\SMSQL_SnapInfo
[19:05:56.259]
[19:05:56.259]  Database: master
[19:05:56.259]  [PRIMARY] New database file - 1 : [I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf]
[19:05:56.259]  [PRIMARY] Original database file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf]
[19:05:56.259]  New log file - 1 : [I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf]
[19:05:56.259]  Original log file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf]
[19:05:56.274]  System Database: Yes
[19:05:56.274]
[19:05:56.274]  Database: model
[19:05:56.274]  [PRIMARY] New database file - 1 : [I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\model.mdf]
[19:05:56.274]  [PRIMARY] Original database file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\model.mdf]
[19:05:56.274]  New log file - 1 : [I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog.ldf]
[19:05:56.274]  Original log file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog.ldf]
[19:05:56.274]  System Database: Yes
[19:05:56.274]
[19:05:56.274]  Database: msdb
[19:05:56.274]  [PRIMARY] New database file - 1 : [I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf]
[19:05:56.274]  [PRIMARY] Original database file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf]
[19:05:56.274]  New log file - 1 : [I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf]
[19:05:56.274]  Original log file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf]
[19:05:56.274]  System Database: Yes
[19:05:56.274]
[19:05:56.274]  There is no change for SQL Server user database.
[19:05:56.274]  Maximum databases of concurrent backup: 255

[19:05:56.274]  New default SnapInfo directory for [SAWTOOTH] :
[19:05:56.290]  H:\SMSQL_SnapInfo
[19:05:56.290]  Set SnapInfo Directory...
[19:05:56.290]  Copying new loginfo sml file...
[19:05:56.290]  Set LogInfo directory path to registry...
[19:05:56.290]  New LogInfo Path for Server SAWTOOTH: [H:\SMSQL_SnapInfo]

[19:05:56.290]  Configuration of the normal Snapinfo directory completed.

[19:05:56.290]  Configuration of the multiple databases per disk SnapInfo directory completed.

[19:05:56.306]  Checking SQL Server [SAWTOOTH]...

[19:05:56.306]  Connecting to SQL Server [SAWTOOTH]...
[19:05:56.321]  Getting SQL Server Agent status...
[19:06:01.372]  DBCC CHECKDB (N'master')
[19:06:04.953]  DBCC results for 'master'.
Service Broker Msg 9675, State 1: Message Types analyzed: 14.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.
Service Broker Msg 9667, State 1: Services analyzed: 3.
Service Broker Msg 9668, State 1: Service Queues analyzed: 3.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
DBCC results deleted for brevity
CHECKDB found 0 allocation errors and 0 consistency errors in database 'master'.
DBCC results for 'mssqlsystemresource'.
Service Broker Msg 9675, State 1: Message Types analyzed: 14.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.
Service Broker Msg 9667, State 1: Services analyzed: 3.
Service Broker Msg 9668, State 1: Service Queues analyzed: 3.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
DBCC results deleted for brevity
CHECKDB found 0 allocation errors and 0 consistency errors in database 'mssqlsystemresource'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
[19:06:04.953]
[19:06:04.953]  DBCC CHECKDB completed successfully.

[19:06:04.953]  DBCC CHECKDB (N'model')
[19:06:05.219]  DBCC results for 'model'.
Service Broker Msg 9675, State 1: Message Types analyzed: 14.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.
Service Broker Msg 9667, State 1: Services analyzed: 3.
Service Broker Msg 9668, State 1: Service Queues analyzed: 3.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
DBCC results deleted for brevity
CHECKDB found 0 allocation errors and 0 consistency errors in database 'model'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
[19:06:05.235]
[19:06:05.235]  DBCC CHECKDB completed successfully.

[19:06:05.235]  DBCC CHECKDB (N'msdb')
[19:06:05.938]  DBCC results for 'msdb'.
Service Broker Msg 9675, State 1: Message Types analyzed: 16.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 7.
Service Broker Msg 9667, State 1: Services analyzed: 5.
Service Broker Msg 9668, State 1: Service Queues analyzed: 5.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
DBCC results deleted for brevity
CHECKDB found 0 allocation errors and 0 consistency errors in database 'msdb'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
[19:06:05.938]
[19:06:05.938]  DBCC CHECKDB completed successfully.

[19:06:05.970]  Set SQL Server to start with T3608...
[19:06:06.064]  Stopping SQL Server...
[19:06:06.173]  Description: This server has been disconnected.  You must reconnect to perform this operation.
[19:06:14.179]  SQL Server was stopped.

[19:06:18.183]  Copying file...
[19:06:18.198]  From:
[19:06:18.198]  C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\model.mdf
[19:06:18.198]  To:
[19:06:18.198]  I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\model.mdf
[19:06:18.214]  From:
[19:06:18.214]  C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog.ldf
[19:06:18.214]  To:
[19:06:18.214]  I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog.ldf
[19:06:18.230]  50% copied
[19:06:18.245]
[19:06:18.245]  Copying file...
[19:06:18.245]  From:
[19:06:18.245]  C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf
[19:06:18.245]  To:
[19:06:18.245]  I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf
[19:06:18.323]  From:
[19:06:18.323]  C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf
[19:06:18.323]  To:
[19:06:18.323]  I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf
[19:06:18.386]  50% copied
[19:06:18.417]
[19:06:18.417]  Restarting SQL Server[SAWTOOTH]...
[19:06:21.435]  [SQL-DMO API Error]: Source: Microsoft SQL-DMO
Error Message: IDispatch error #20793

Description: [SQL-DMO]Unexpected parameter value or other condition.
[19:06:21.435]  SQL-DMO Error Code: 0x80045339

[19:06:21.435]  [SQL-DMO API Error]: Source: Microsoft SQL-DMO
Error Message: IDispatch error #20793

Description: [SQL-DMO]Unexpected parameter value or other condition.

[19:06:23.437]  Re-trying to start SQL Server [SAWTOOTH], please wait...
[19:06:26.439]  Waiting for server to start...
[19:06:29.442]  Waiting for server to start...
[19:06:32.444]  Waiting for server to start...
[19:06:35.446]  Waiting for server to start...
[19:06:38.449]  Waiting for server to start...
[19:06:41.451]  Waiting for server to start...
[19:06:44.454]  Waiting for server to start...
[19:06:47.456]  Waiting for server to start...
[19:06:50.458]  Waiting for server to start...
[19:06:53.461]  Waiting for server to start...
[19:06:56.463]  Waiting for server to start...
[19:06:59.466]  Waiting for server to start...
[19:07:02.468]  Waiting for server to start...
[19:07:05.470]  Waiting for server to start...
[19:07:08.473]  Waiting for server to start...
[19:07:11.475]  Waiting for server to start...
[19:07:14.478]  Waiting for server to start...
[19:07:17.480]  Waiting for server to start...
[19:07:20.482]  Waiting for server to start...
[19:07:23.485]  Waiting for server to start...
[19:07:26.487]  [SQL-DMO API Error]: Source: Microsoft SQL-DMO
Error Message: IDispatch error #20793

Description: [SQL-DMO]Unexpected parameter value or other condition.
[19:07:26.487]  SQL-DMO Error Code: 0x80045339

[19:07:26.487]  [SQL-DMO API Error]: Source: Microsoft SQL-DMO
Error Message: IDispatch error #20793

Description: [SQL-DMO]Unexpected parameter value or other condition.

[19:07:28.489]  Re-trying to start SQL Server [SAWTOOTH], please wait...
[19:07:31.491]  Waiting for server to start...
[19:07:34.494]  Waiting for server to start...
[19:07:37.496]  Waiting for server to start...
[19:07:40.498]  Waiting for server to start...
[19:07:43.501]  Waiting for server to start...
[19:07:46.503]  Waiting for server to start...
[19:07:49.506]  Waiting for server to start...
[19:07:52.508]  Waiting for server to start...
[19:07:55.510]  Waiting for server to start...
[19:07:58.513]  Waiting for server to start...
[19:08:01.515]  Waiting for server to start...
[19:08:04.518]  Waiting for server to start...
[19:08:07.520]  Waiting for server to start...
[19:08:10.522]  Waiting for server to start...
[19:08:13.525]  Waiting for server to start...
[19:08:16.527]  Waiting for server to start...
[19:08:19.530]  Waiting for server to start...
[19:08:22.532]  Waiting for server to start...
[19:08:25.534]  Waiting for server to start...
[19:08:28.537]  Waiting for server to start...
[19:08:31.539]  [SQL-DMO API Error]: Source: Microsoft SQL-DMO
Error Message: IDispatch error #20793

Description: [SQL-DMO]Unexpected parameter value or other condition.
[19:08:31.539]  SQL-DMO Error Code: 0x80045339

[19:08:31.539]  [SQL-DMO API Error]: Source: Microsoft SQL-DMO
Error Message: IDispatch error #20793

Description: [SQL-DMO]Unexpected parameter value or other condition.

[19:08:33.541]  Re-trying to start SQL Server [SAWTOOTH], please wait...
[19:08:36.543]  Waiting for server to start...
[19:08:39.546]  Waiting for server to start...
[19:08:42.548]  Waiting for server to start...
[19:08:45.550]  Waiting for server to start...
[19:08:48.553]  Waiting for server to start...
[19:08:51.555]  Waiting for server to start...
[19:08:54.558]  Waiting for server to start...
[19:08:57.560]  Waiting for server to start...
[19:09:00.562]  Waiting for server to start...
[19:09:03.565]  Waiting for server to start...
[19:09:06.567]  Waiting for server to start...
[19:09:09.570]  Waiting for server to start...
[19:09:12.572]  Waiting for server to start...
[19:09:15.574]  Waiting for server to start...
[19:09:18.577]  Waiting for server to start...
[19:09:21.579]  Waiting for server to start...
[19:09:24.582]  Waiting for server to start...
[19:09:27.584]  Waiting for server to start...
[19:09:30.586]  Waiting for server to start...
[19:09:33.589]  Waiting for server to start...
[19:09:33.589]  Failed to start SQL Server.
[19:09:33.589]  Waiting for SQL Server to start, please wait...
[19:09:33.589]  SnapManager failed to restart SQL Server during system database migration.

[19:09:33.589]  Deleting newly copied system database files after failure...
[19:09:33.589]  Deleting file:
[19:09:33.589]  I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\model.mdf
[19:09:33.589]  Deleting file:
[19:09:33.589]  I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog.ldf
[19:09:33.589]  Database files are deleted.

[19:09:33.589]  Deleting newly copied system database files after failure...
[19:09:33.589]  Deleting file:
[19:09:33.589]  I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf
[19:09:33.589]  Deleting file:
[19:09:33.589]  I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf
[19:09:33.589]  Deleting directory:
[19:09:33.589]  I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA
[19:09:33.589]  Deleting directory:
[19:09:33.589]  I:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
[19:09:33.589]  Deleting directory:
[19:09:33.589]  I:\Program Files\Microsoft SQL Server\MSSQL.1
[19:09:33.589]  Deleting directory:
[19:09:33.589]  I:\Program Files\Microsoft SQL Server
[19:09:33.589]  Deleting directory:
[19:09:33.589]  I:\Program Files
[19:09:33.589]  Database files are deleted.

[19:09:33.604]  Failed to migrate database. Error code: 0x80045339
[19:10:34.997]  Error Code 80040000
Description: SQL Server does not exist or access denied.
ConnectionOpen (Connect()).
[19:10:34.997]  [SQL-DMO API Error]: Source: Microsoft SQL-DMO (ODBC SQLState: 08001)
Error Message: Invalid OLEVERB structure

Description: SQL Server does not exist or access denied.
ConnectionOpen (Connect()).
[19:10:34.997]  SQL-DMO Error Code: 0x80040000

[19:10:34.997]  [SQL-DMO API Error]: Source: Microsoft SQL-DMO (ODBC SQLState: 08001)
Error Message: Invalid OLEVERB structure

Description: SQL Server does not exist or access denied.
ConnectionOpen (Connect()).
[19:10:34.997]  Failed to find the T3608 flag. Error code = 0x80040000
[19:10:34.997]  [SQL-DMO API Error]: Source: Microsoft SQL-DMO (ODBC SQLState: 08001)
Error Message: Invalid OLEVERB structure

Description: SQL Server does not exist or access denied.
ConnectionOpen (Connect()).
[19:10:34.997]  SQL Server (MSSQLSERVER) is in minimally configured mode. Please remove this flag via SQL Server Configuration Manager before migrating any database.
[19:10:35.013]  Failed to migrate SQL Server system databases.

[19:10:35.013]  Error occurred during system database migration.

[19:10:35.013]  ***ADD MSISCSI SERVICE AS A DEPENDENCY OF [MSSQLSERVER]
[19:10:35.013]
[19:10:35.013]  Adding service [MSiSCSI] as a dependency of [MSSQLSERVER]...
[19:10:35.013]  Service [MSiSCSI] was successfully added to the dependency list of the specified service.

[19:10:35.029]  Configuring the SQLServer Maximum Worker Threads Option...
[19:10:35.029]
[19:10:35.029]  *** SNAPMANAGER CONFIGURATION JOB ENDED AT: [04-14-2009 19.10.35]
[19:10:35.029]  [SQL-DMO API Error]: Source: Microsoft SQL-DMO
Error Message: IDispatch error #20793

Description: [SQL-DMO]Unexpected parameter value or other condition.

And the error message that pops up at the end:

[lrhvidsten]

Bump. Appreciate any ideas anyone might have. Netapp support still hasn't contacted me since I created my ticket over 24hrs ago...other than to assign an agent to the ticket. Is this typical for premium support contracts?

[draj]

Hi,

I suspect this is some thing to do with the admin privileges; this is what SMSQL IAG says:

SQL Server

authentication

When using SQL Server authentication, the SQL Server administrator must have

sysadmin server role privileges on the SQL Server instance. SnapManager

requires that the database administrator have the required privileges to mount and

unmount databases and backup and restore data and transaction log files. The

system administrator role fulfills all these permissions requirements.

Windows

authentication

When using Windows authentication, the Windows account that you are logged

onto the system with must have system administrator privileges on the SQL

Server. This account is presumably the same account running SnapDrive.

However, some organizations give different categories of administrators different

responsibilities and therefore different levels of access. For example, one group

of administrators might run SnapManager to manage the SQL Server databases

while another group of administrators might run SnapDrive to manage the LUNs.

In this case, separate accounts would be used for SnapDrive and SnapManager.

The SnapManager server would still run under the SnapManager user account.

And one work around which I can think of as of now, is to go into SQL Server Configuration Manager --> Properties --> Startup Parameters and remove the trace flag (T3608) and then try to restart sql server services. If this works, I guess you should be able to continue with SMSQL.

Let me know the results.

Thanks,

Raj

[netapp4mhipa · Accepted solution]

Had the same problem. I added the account running sql server service and the account running snapdrive to the local admin group and it worked. I don't think you have to add the snapdrive account but for sure you have to add the sql service account.

[qzhang]

Could you check the application event log and SQL Server log around the time [19:06:18.417]?

[19:06:18.417]  Restarting SQL Server[SAWTOOTH]...
[19:06:21.435]  [SQL-DMO API Error]: Source: Microsoft SQL-DMO
Error Message: IDispatch error #20793

What SMSQL was trying to do is to start SQL Server with T3608 parameter before it can migrate the model and MSDB databases. Somehow it cannot restart the server after this parameter is set. The SQL Server log should give me information about the error.

You may need to manually remove the T3608 startup parameter before you retry the migration.

Also can you restart the service now manually? I believe the T3608 parameter is still there, likely you will get the same error when you restart the service manaully.

Thanks,

-Qing

[netapp4mhipa]

Thanks for your feedback. This problem is fixed.

Adding the domain account that the SQL Server service uses to the local admin group fixed the problem. I have restarted the service several times with no problems.

[sojdehei]

Hello

IHAC that is having similar issue with the Wizard trying to do a migration.  We tried your recommendations in this email thread, but it's still not working?  Any thoughts on a workaround is apprecited.  Thankk you!    Below is a copy of the error log:

SnapManager for SQL Server

Host Name: SOL-SBX

Database: SLS

[PRIMARY] New database file - 1 : [M:\SLSDATA1\SLSDATA1\SLSDATA1.mdf]

[PRIMARY] Original database file : [S:\SLSDATA1\SLSDATA1.mdf]

[PRIMARY] New database file - 2 : [M:\SLSDATA2\SLSDATA2\SLSDATA2.ndf]

[PRIMARY] Original database file : [S:\SLSDATA2\SLSDATA2.ndf]

[PRIMARY] New database file - 3 : [M:\SLSDATA3\SLSDATA3\SLSDATA3.ndf]

[PRIMARY] Original database file : [S:\SLSDATA3\SLSDATA3.ndf]

New log file - 1 : [L:\SLSLOG1\SLSLOG1\SLSLOG1.ldf]

Original log file : [S:\SLSLOG1\SLSLOG1.ldf]

Database: master

[PRIMARY] New database file - 1 : [M:\SLSSYSDB\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf]

[PRIMARY] Original database file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf]

New log file - 1 : [M:\SLSSYSDB\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf]

Original log file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf]

System Database: Yes

Database: model

[PRIMARY] New database file - 1 : [M:\SLSSYSDB\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\model.mdf]

[PRIMARY] Original database file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\model.mdf]

New log file - 1 : [M:\SLSSYSDB\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog.ldf]

Original log file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog.ldf]

System Database: Yes

Database: msdb

[PRIMARY] New database file - 1 : [M:\SLSSYSDB\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf]

[PRIMARY] Original database file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf]

New log file - 1 : [M:\SLSSYSDB\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf]

Original log file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf]

System Database: Yes

Retrieving ONTAP virtual disks information...

*** SnapManager for SQL Server Report

Configuration Time Stamp: 05-04-2009_12.46.27

Host Name: SOL-SBX

Database: SLS

[PRIMARY] New database file - 1 : [M:\SLSDATA1\SLSDATA1\SLSDATA1.mdf]

[PRIMARY] Original database file : [S:\SLSDATA1\SLSDATA1.mdf]

[PRIMARY] New database file - 2 : [M:\SLSDATA2\SLSDATA2\SLSDATA2.ndf]

[PRIMARY] Original database file : [S:\SLSDATA2\SLSDATA2.ndf]

[PRIMARY] New database file - 3 : [M:\SLSDATA3\SLSDATA3\SLSDATA3.ndf]

[PRIMARY] Original database file : [S:\SLSDATA3\SLSDATA3.ndf]

New log file - 1 : [L:\SLSLOG1\SLSLOG1\SLSLOG1.ldf]

Original log file : [S:\SLSLOG1\SLSLOG1.ldf]

Database: master

[PRIMARY] New database file - 1 : [M:\SLSSYSDB\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf]

[PRIMARY] Original database file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf]

New log file - 1 : [M:\SLSSYSDB\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf]

Original log file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf]

System Database: Yes

Database: model

[PRIMARY] New database file - 1 : [M:\SLSSYSDB\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\model.mdf]

[PRIMARY] Original database file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\model.mdf]

New log file - 1 : [M:\SLSSYSDB\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog.ldf]

Original log file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog.ldf]

System Database: Yes

Database: msdb

[PRIMARY] New database file - 1 : [M:\SLSSYSDB\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf]

[PRIMARY] Original database file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf]

New log file - 1 : [M:\SLSSYSDB\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf]

Original log file : [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBLog.ldf]

System Database: Yes

Maximum databases of concurrent backup: 255

No change to default SnapInfo directory of [SOL-SBX] :

M:\SNAPINFO\SMSQL_SnapInfo

Copying new loginfo sml file...

Set LogInfo directory path to registry...

New LogInfo Path for Server SOL-SBX: [M:\SNAPINFO\SMSQL_SnapInfo]

Configuration of the normal Snapinfo directory completed.

Configuration of the multiple databases per disk SnapInfo directory completed.

Checking SQL Server [SOL-SBX]...

Connecting to SQL Server [SOL-SBX]...

Getting SQL Server Agent status...

Set SQL Server to start with T3608...

Stopping SQL Server...

Description: This server has been disconnected.  You must reconnect to perform this operation.

SQL Server was stopped.

Copying file...

From:

C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\model.mdf

To:

M:\SLSSYSDB\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\model.mdf

Error Code: 0x80070050

The file exists.

Failed to copy database file

Error Code: 0xc004085a

Unable to copy the database file during SnapManager database migration.

Failed to copy database file, skipping migration of this database...

Copying file...

From:

C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf

To:

M:\SLSSYSDB\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf

Error Code: 0x80070050

The file exists.

Failed to copy database file

Error Code: 0xc004085a

Unable to copy the database file during SnapManager database migration.

Failed to copy database file, skipping migration of this database...

Restarting SQL Server[SOL-SBX]...

[SQL-DMO API Error]: Source: Microsoft SQL-DMO

Error Message: IDispatch error #20793

Description: [SQL-DMO]Unexpected parameter value or other condition.

SQL-DMO Error Code: 0x80045339

[SQL-DMO API Error]: Source: Microsoft SQL-DMO

Error Message: IDispatch error #20793

Description: [SQL-DMO]Unexpected parameter value or other condition.

Re-trying to start SQL Server [SOL-SBX], please wait...

Waiting for server to start...

Waiting for server to start...

Waiting for server to start...

Waiting for server to start...

The user has terminated this operation...

Error Code: 0xc0040819

The operation was cancelled by the administrator. However, portions of the operation might have already completed. Check the the report log for details.

SnapManager failed to restart SQL Server during system database migration.

Failed to migrate database. Error code: 0xc0040819

The user has terminated this operation...

Failed to find the T3608 flag. Error code = 0xc0040819

Error Code: 0xc0040819

The operation was cancelled by the administrator. However, portions of the operation might have already completed. Check the the report log for details.

SQL Server (MSSQLSERVER) is in minimally configured mode. Please remove this flag via SQL Server Configuration Manager before migrating any database.

Failed to migrate SQL Server system databases.

Error occurred during system database migration.

The user has terminated this operation...

*** SNAPMANAGER CONFIGURATION JOB ENDED AT: [05-04-2009 12.47.00]

Error Code: 0xc0040819

The operation was cancelled by the administrator. However, portions of the operation might have already completed. Check the the report log for details.

An email notification message is sent.

Preparing for Sending Filer AutoSupport...

A filer autosupport message is sent on failure.

Error Code: 0xc0040819

The operation was cancelled by the administrator. However, portions of the operation might have already completed. Check the the report log for details.

- Mitchell

[lrhvidsten]

Thanks everyone for your help and suggestions. Netapp4mhipa, I awarded you with the correct answer, though it wasn't the entire answer for me. In fact, there still a showstopper or two here that NetApp needs to address...

1. This problem only affects migrating system databases, since restarting MSSQL is required which causes the authentication errors. Simply migrating a user db shouldn't cause any problems as no MSSQL restart is needed. Also, all of my testing pertains only to SQL Server 2005 SP2 and/or SP3. I don't know if these problems affect SQL Server 2000 or 2008.

2. After spending around 7-8 hours of support with NetApp over a few weeks, we finally were able to complete a successful migration of the system dbs from local storage to the NetApp lun when, as netapp4mhipa suggested, the sql server service account and the snapdrive/snapmanager service account had local system administrator privileges. However, this alone didn't fix it for us...the other critical setting was in the Database Migration Settings screen of the Configuration Wizard. Do NOT enable the DBCC check after migration. The NetApp support technician was as baffled as me, this setting alone, when enabled, will trigger the error and halt migration even if the snapdrive/smsql and mssql system accounts have administrator privileges.

The other critical thing I realized...

3. Support's workaround for me was found using SQL Server 2005 SP2, SMSQL 2.1.2, and SD 6.0.1 because they had me downgrade earlier on as part of the troubleshooting process. I was originally using SMSQL 5.0R1, SD6.1, and MSSQL 2005 SP3 which we could never get to work. I wanted to be on more current NetApp software, so I did some more testing with various combinations of SMSQL, SD, and MSSQL SP2/SP3.

I did find another showstopper here: MSSQL 2005 SP3. I have not yet successfully migrated the system databases using the config wizard with any combination of NetApp snap software and MSSQL 2005 SP3. I even migrated all the db's first under MSSQL 2005 SP2, then I upgraded to MSSQL 2005 SP3. In that scenario, everything seemed to work, until I attempted to do a system database restore which resulted in more authentication errors. I'm guessing the only workaround for this situation would be to do a traditional restore within Sql Server Management Studio off the .fbk backup (as I believe it works just like a .bak).

Currently, I'm running successfully with SMSQL 5.0R1, SD 6.1, and MSSQL 2005 SP2 w/ MS09-004 hotfix. But, until NetApp fixes their authentication issues with SP3, I will stay away. I'm also disappointed that the MSSQL service account needs local administrator privileges, for SMSQL to work. This goes against Microsoft's recommendation to give this account the least privileges it requires. Normally, this account works fine as a normal user account with SQL Server alone.

-----------------------------------

In summary,

1. MSSQL and NetApp service accounts need be in the local administrator group.

2. Leave DBCC check after migration UNCHECKED in the config wizard setup.

3. If using MSSQL 2005, don't use SP3.

Hopefully, NetApp can fix the issues caused by #2 and #3. #1 would be icing on the cake.

--Leif

[qzhang]

Leif,

What is the log on user account which SnapManager Service is using when running SMSQL 5.0R1 and you were having problem during migration? That user account is the user who should assign the permission to perform the migration.

Thanks,

-Qing

[lrhvidsten]

Our setup is pretty simple.

I used 1 service account for SQL Server that's in the local admin group, let's just call it 'sqlaccount'

I used 1 service account for SnapDrive and SnapManager that's in the local admin group, let's just call that 'netapp'.

The 'netapp' account always has had admin privileges in my setup. In fact, initially it was a domain administrator, but I changed that since I knew that was unnecessary. It's the SQL server account that I initially had setup as only a user account. Config wizard migration of system dbs will not work unless that account is a local administrator. I initially didn't have that setup as local admin since Microsoft recommends that you give it the least permissions needed.

[qzhang]

There are two requirements for an account running SnapManager service:

1. The account must have system administrator privileges on the SQL Server;

2. The account must be part of local administarator group.

When you say "The 'netapp' account always has had admin privileges in my setup", do you mean the 'netapp' account has system administrator privileges on the SQL Server?

I don't think which user account is running SQL Server is important to SMSQL, as long as the SQL Server works.

Thanks,

-Qing

[lrhvidsten]

The 'netapp' account for our snapmanager/snapdrive services has always fulfulled both requirements:

1. system admin on sql server (by default all local windows administrator accounts have this in the local sql server instance)

2. part of local admin group

During the process with support we never needed to modify this 'netapp' account because it was setup correctly from the beginning.

It was the service account running sql server that had to be modified...amongst the other things I described above.

Your statement about the sql server service account never needing to be modified is likely true if you originally setup SQL server to run under the built-in local system account. However, I didn't originally do this, I had set it up with a domain user account with only local user privileges per Microsoft's recommendation.

Unfortunately, with a domain user account, the sql server service then needs local administrator privileges for netapp's config wizard migration to work for system databases. Essentially, the built-in system account already had these privileges, so a setup with that account doesn't have to explicitly assign them. This is too bad, as it goes directly against Microsoft's published best practices of maintaining least privileges for the sql server accounts.

Pages 6-7 starting at 'Service Account Selection and Management' better explains what I'm getting at:

http://download.microsoft.com/download/8/5/e/85eea4fa-b3bb-4426-97d0-7f7151b2011c/SQL2005SecBestPract.doc

That's why I referred above that it would be 'icing on the cake' if NetApp could find a more secure solution for this.

[qzhang]

Thanks for the info, Leif!

I would think we will have to get MSFT involved since SMSQL uses MSFT documented procedures to migrate system dbs, only automates the procedures, unless the procedures are broken.

Thanks,

-Qing

[lrhvidsten]

Just had a thought, I will try keeping the SQL service accounts as regular user accounts and only change them to local administrator when either a system db migration or a system database restore is needed. Might be one possible workaround as either of these events are extremely rare.

It would be nice to hear any feedback from NetApp on the other 2 issues I mentioned above pertaining to MSSQL 2005 SP3 and the config wizard setting of running a dbcc check after the migration.

Thanks,

Leif

[qzhang]

Sure NetApp engineer will look into those problems.

Thanks,

-Qing

[ophir]

Hi ,

IHAC that running SQL2005 SP3 with Ontap 7.2.6.1P3 and FAS3140 and SMSQL 5.0.R1

I migrate almost all of the DB the only DB that I can't migrate is the master DB.

I am getting the same errors when I am tring to do this migration.

I did the steps that this customer did but I have the same problem.

I check the account permission and it look right and also it worked for all of the other drivers.

Any idea ?    

Thanks

Ophir Rom

PSE / Israel

[lrhvidsten]

Hello,

If you look at my one of my posts above (http://communities.netapp.com/message/10993#10993), you'll see I was never able to complete a successful migration when using MSSQL 2005 SP3, though the exact same setup worked fine with SP2.

My only suggestions are:

1. Rollback to MSSQL 2005 SP2

2. Move the master db (and mssqlsystemresource) with Microsoft's tools (Configuration Manager and Management Studio) onto the LUN and directory where you'd like it to be. Then, run the SMSQL config wizard again to pick up this changed location for the master db.

Use this reference on how to move the master db: http://msdn.microsoft.com/en-us/library/ms345408%28SQL.90%29.aspx

Rolling back to SP2 could be quite difficult, but option 2 should work. However, if your client ever needs to do a restore of the master db from a SnapManager .fbk backup, they will probably run into the same error. I'm guessing the only workaround for this situation would be to do a traditional restore within Management Studio off the .fbk backup (as I believe it works just like a .bak).

Hopefully NetApp finds a resolution to this SMSQL problem with SP3 soon...

--Leif