STARTSAP_NBAS - status NO SYSTEM START

Question

Hi all,
I'm upgrading R/3 4.7 to ERP 6.0 SR3 NUC; Windows 2008 + SQL Server 2008. I'm in weekend downtime. In phase status STARTSAP_NBAS I have the error:
UPGRADEPHASE STARTSAP_NBAS
...started at 20140222060031
# Reading Parameter File "D:\usr\sap\put\bin\ALPALL.LST" at 20140222060031
..finished at 20140222060636 with status NO SYSTEM START.
...begin dialogue at 20140222060636
tp.ECO log:
SAPup>  Starting subprocess tp.exe with id 5024 at 20140222061006
EXECUTING D:\usr\sap\<SID>\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\SHADOW.TPP unlocksys <SID>
Environment: dbms_type=mss
Environment: dbs_mss_schema=<sid>
initial value of NLS_LANG: '<NULL>'
This is D:\usr\sap\<SID>\SYS\exe\run\tp.exe version 372.05.88 (release 700)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
TRACE-INFO: 1:  [     dev trc,00000]  Sat Feb 22 06:10:08 2014                                                         2182  0.002182
TRACE-INFO: 2:  [     dev trc,00000]  DlLoadLib success: LoadLibrary("dbmssslib.dll"), hdl 0, addr 0000000187740000
TRACE-INFO: 3:                                                                                                           10  0.002192
TRACE-INFO: 4:  [     dev trc,00000]      using "D:\usr\sap\<SID>\SYS\exe\run\dbmssslib.dll"                                9  0.002201
TRACE-INFO: 5:  [     dev trc,00000]  Thread ID:5516                                                                   1590  0.003791
TRACE-INFO: 6:  [     dev trc,00000]  Thank You for using the SLODBC-interface                                           11  0.003802
TRACE-INFO: 7:  [     dev trc,00000]  Using dynamic link library 'D:\usr\sap\<SID>\SYS\exe\run\dbmssslib.dll'              19  0.003821
TRACE-INFO: 8:  [     dev trc,00000]  dbmssslib.dll patch info                                                           40  0.003861
TRACE-INFO: 9:  [     dev trc,00000]    SAP patchlevel  0                                                                 9  0.003870
TRACE-INFO: 10:  [     dev trc,00000]    SAP patchno  353                                                                  8  0.003878
TRACE-INFO: 11:  [     dev trc,00000]    Last MSSQL DBSL patchlevel 0                                                     11  0.003889
TRACE-INFO: 12:  [     dev trc,00000]    Last MSSQL DBSL patchno         350                                               9  0.003898
TRACE-INFO: 13:  [     dev trc,00000]    Last MSSQL DBSL patchcomment Work process can not be cancelled (1740162)         12  0.003910
TRACE-INFO: 14:  [     dev trc,00000]  lpc:(local) connection used on SAP<SID>                                             534  0.004444
TRACE-INFO: 15:  [     dev trc,00000]  ERROR: -1 in function ExecuteAndFlush (SQLExecDirect) [line 5520]               78212  0.082656
TRACE-INFO: 16:  [     dev trc,00000]  (15157) [42000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Setuser failed because of one of the following reasons: the database principal '<sid>_shd' 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.
TRACE-INFO: 17:                                                                                                           29  0.082685
TRACE-INFO: 18:  [     dev trc,00000]  <if user_name() != '<sid>_shd' setuser '<sid>_shd'> failed -- connect terminated       32  0.082717
TRACE-INFO: 19:  [    dblink  ,00433]  ***LOG BY2=>sql error 15157  performing CON [dblink#8 @ 433]                       57  0.082774
TRACE-INFO: 20:  [    dblink  ,00433]  ***LOG BY0=>Setuser failed because of one of the following reasons: the database principal '<sid>_shd' 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. [dblink#8 @ 433]
TRACE-INFO: 21:                                                                                                           23  0.082797
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0232
tp finished with return code: 232
meaning:
  connect failed
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: Connect to <SID> failed (20140222061008, probably wrong environment).
Process with ID 1756 terminated with status 232
<SID>Adm User has this environment variables:
dbms/type = mss
dbs/mss/server = <HOST>
dbs/mss/dbname = <SID>
dbs/mss/schema = <sid>
I check the following SAP Notes:
- 128126 - Database connect for external tools
- 525677 - Problems when starting shadow instance
- 592514 - MSSQL: internal database users, permissions and security
- 1294762 - SCHEMA4SAP.VBS
- 1727986 - Upgrade Phase MAIN_NEWBAS/STARTSAP_NBAS: Error Starting SAP
- 1910759 - Start of Shadow Instance Failed during upgrade
but any of them, help me to fix the stopper.
Can anybody give me any idea, please?

Answer 1

Hi Javier,
Have you tried by executing script mssupgsps.sql ,which you can find under D:\usr\sap\put\bin.This script will create stored procedure sap_upg_getrelease.
After execution provide grant with following
add setuser '<sid>'
grant all on sap_upg_getrelease to <sid>_shd
Hope this will help you.
Regards,
Gaurav