cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to start SAP

Former Member
0 Kudos

Hi,

We just restored an SQL database..2005/ECC 6.0 via the Net backup client.

The restore was successful, however SAP refuses to start.

dev_w* show the foll. error:

Error/Message: (err 15157, sev 0), Setuser failed because of one of the following reasons: the database principal 'ecd' does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.

C Procname: [ExecuteAndFlush - no proc]

C setuser 'ecd' failed -- connect terminated

C failed to establish conn. 0

B ***LOG BY2=> sql error -1 performing CON [dbsh#2 @ 1208] [dbsh 1208 ]

pls. help..

Thanks,

S.

Accepted Solutions (1)

Accepted Solutions (1)

former_member524429
Active Contributor
0 Kudos

Hi,

Have you run STM (SAP Tool for MSSQL) after such successful SQL DB Restore ?

Download it from http://service.sap.com/msplatforms -> SQL Server.

Please refer this SAP Note 683447 - SAP Tools for MS SQL Server to get more information.

Regards,

Bhavik G. Shroff

Former Member
0 Kudos

Hi,

Thanks for your quick reply..I downloaded the tool & ran it using the db completion option..

however the tool doesn't support dual stack systems:(

I've evn changed the DB owner to server\sidadm...initially it was the person who restored the database..bt it has'nt helped..

Thanks

S

Edited by: Saba Sheikh on Feb 27, 2010 12:42 PM

former_member524429
Active Contributor
0 Kudos

Hi,

Have you referred this [SAP Note 151603 - Copying an SQL Server database|https://service.sap.com/sap/support/notes/151603] before performing such SQL DB Restore ?

Regards,

Bhavik G. Shroff

Former Member
0 Kudos

Ya..I've seen this note..

what happened is...we had an OS crash n the system was restored successfully via sapinst, however the export was a little old..n since we had the latest veritas full backup, we restored it via the Net client.

i din't use sapinst again, since CI was already installed..

Thanks

former_member524429
Active Contributor
0 Kudos

Hi,

Please post the content of trans.log file by executing R3trans -d under <sid>adm user.

Ensure that <sid>adm and SAPService<SID> OS users are the member of "Administrators" group.

Also check the status of MS SQL Services on the SAP Server host.

All the required environment variables are set properly ? such as dbs/mss/schema . .

SAP Kernel is up-to-date ? DBSL library is latest ?

Please refer the following SAP Notes to get more information and compare your restore process/settings.

Note 193816 - Restore with SQL Server

Note 1420452 - FAQ: Restore and recovery with MS SQL Server

Regards

Bhavik G. Shroff

Edited by: Bhavik G. Shroff on Feb 27, 2010 6:01 PM

Former Member
0 Kudos

Hi,

My problem's finally solved:)

Post the Veritas restore, the SQL (msdb) permisisons were a complete mess:(

Hence I finally used SAPINST to do the restore (using the existing DB option)..

Thanks,

-S

Answers (0)