Can't start Shadowinstance during EHP Upgrade

[michael_dwehus]

Hello SCN,

i'm trying to Upgrade ERP6.0 EHP5 to EHP6 on Windows 2008 and MaxDB 7.9.08.08.

In Phase MAIN_SHDPREPUT/START_SHDI_PREPUT i get Severe Error becuase the shadow instance won't get up.

Error

Severe error(s) occurred in phase MAIN_SHDPREPUT/START_SHDI_PREPUT! Last error code set: Shadow instance couldn't be started, check 'STARTSSC.LOG' and 'DEVTRACE.LOG': RFC login to system EMT ashost SAPTEST01 nr 02 gwhost SAPTEST01 gwservice sapgw02 failed with code 1 key RFC_COMMUNICATION_FAILURE: <br/> LOCATION CPIC (TCP/IP) on local host with Unicode<br/> ERROR partner '192.168.97.2:3302' not reached<br/> TIME Wed Nov 27 15:05:01 2013<br/> RELEASE 721<br/> COMPONENT NI (network interface)<br/> VERSION 40<br/> RC -10<br/> MODULE nixxi.cpp<br/> LINE 3285<br/> DETAIL NiPConnect2: 192.168.97.2:3302<br/> SYSTEM CALL connect<br/> ERRNO 10061<br/> ERRNO TEXT WSAECONNREFUSED: Connection refused<br/> COUNTER 66<br/>

dev_w0 of shadow instance says:

"

C  *** ERROR => Connect to database failed, rc = -10757 (XUSER error (the USERKEY is unknown))

[dbsdbsql.cpp 115]

C  Try to connect (SQLOPT) on connection 0 ...

C  *** ERROR => Connect to database failed, rc = -10709 (Connection failed (RTE:Authentication failed (Cannot eval connect packet.).))

[dbsdbsql.cpp 139]

B  ***LOG BV3=> severe db error -10709    ; work process is stopped [dbsh        1241]

B  ***LOG BY2=> sql error -10709 performing CON [dblink      544]

B  ***LOG BY0=> Connection failed (RTE:Authentication failed (Cannot eval connect packet.).) [dblink      544]

M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c  1497]

M  in_ThErrHandle: 1

M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c  11348]

M  "

i did some research and found SAP Note 1444798:

Note 1444798

I) Creating the XUSER key "UPGSHD" on the remote shadow instance For SAP upgrades or Enhancement Package installations with SAP kernel 7.20 or higher (that is, NetWeaver 7.0 or higher, Enhancement Package 2 as well as BS 7i2010e or higher), you must create the XUSER key UPGSHD in the remote shadow instance. This should occur immediately after the PREPARE. To do so, execute the following command as the SAP system administrator sidadm on the host of the remote shadow instance:   xuser -U UPGSHD -u SAP<SID>SHD,<password> -d <DBSID>   -n <DBHostname> -S SAPR3 -t 0 -I 0 set For Windows, you must also execute the following command:   xuser -c SAPService<SID> -U UPGSHD -u SAP<SID>SHD,<password>   -d <DBSID> -n <DBHostname> -S SAPR3 -t 0 -I 0 set The password is the password specified in the phase INITSHD. Check the existence of the XUSER key after its creation using:   xuser -U UPGSHD list For Windows, use the following also:   xuser -c SAPService<SID> -U UPGSHD list If the XUSER key does not exist, starting the shadow instance leads to the following error (log file of work processes):   *** ERROR => Connect to database failed,   rc = -10757 (XUSER error (the USERKEY is unknown)) After completing the SAP upgrade or the Enhancement Package installation, you must delete the XUSER key:   xuser -U UPGSHD clear For Windows, also:   xuser -c SAPService<SID> -U UPGSHD clear

I tryed this Solution and added the Xuser Keys for UPGSHD

When i try to test connection i get this Error:

dbmcli -d EMT -U UPGSHD

Error! Connection failed to node SAPTEST01 for database EMT:

-24950, ERR_USRFAIL: User authorization failed.

do you have any ideas?

best regards

[matus_petrek2]

Hello Michael,

what are the test results as per 1444798?

Check the existence of the XUSER key after its creation using:

  xuser -U UPGSHD list

For Windows, use the following also:

  xuser -c SAPService<SID> -U UPGSHD list

Is this check successful? If you try to bring the shadow instance up you got same error about XUSER in dev_w* ?

I found http://scn.sap.com/docs/DOC-40842 but your error is different:

"Cannot eval connect packet."

Is not there any communication problem on your Windows server? Check file for services or perhaps if port is not being used.

Regards,

Matus

[michael_dwehus]

Hi Matus,

xuser list shows the entry for UPGSHD.

but the command:

dbmcli -d EMT -U UPGSHD

shows Error:

Error! Connection failed to node SAPTEST01 for database EMT:

-24950, ERR_USRFAIL: User authorization failed.

SID, dbhost, saphost and user+password are correct!

SYSLOG of SAPMMC when starting manually shows this:

SAP Basis System: Initialization DB-Connect Failed, Return Code 000256

[matus_petrek2]

Hello Michael,

can you past the commands you used and output? Did you execute it for correct DB scheme? E.g. in the note there is SAPR3, I imagine you need to execute it for SAPSR3.

Please also attach whole dev_w0 file.

Regards,

[michael_dwehus]

Dear Matus,

i typed in cmd in admin mode:

xuser -U UPGSHD -u SAPEMTSHD,<password removed> -d EMT -n SAPTEST01 -S SAPR3 -t 0 -I 0 set

and

xuser -c SAPServiceEMT -U UPGSHD -u SAPEMTSHD,<password removed> -d EMT -n SAPTEST01 -S SAPR3 -t 0 -I 0 set

Commands work properly without output.

when i type xuser list -U UPGSHD i get XUSER Entry 5 UPGSHD. As i said this did not work.

i tryed to set SAPSR3 but get error: Illegal sqlmode specified: SAPSR3 (ignored)

attached dev_w0

thanks

dev_w0.txt.zip

[matus_petrek2]

Hello Michael,

thank you, SAPR3 seems to be correct. The log you sent me is from yesterday, I thought you tried it also today, but never mind.

I am wondering why are you using old SQLDBC client:

C  Loading SQLDBC client runtime ...

C  SQLDBC Module  : E:\sapdb\programs\pgm\libSQLDBC77.dll

C  SQLDBC SDK     : SQLDBC.H  7.7.7    BUILD 043-123-246-426

C  SQLDBC Runtime : libSQLDBC 7.7.7    BUILD 043-123-246-426

if you are running MaxDB vsersion 7.9.08.08. Did you do recent update of DB version?

Perhaps you forgot to update environment/client software?

Check notes 822271 and 649814 if these can be helpful for you.

Also you could give a try to update kernel of shadow instance.

Regards,

Matus

[matus_petrek2]

Hello,

regarding MaxDB client, please also check SAP note 1357452, this could be also your case.

Let me know.

Regards,

[Former Member]

Hi Michael,

Let us know if your problem is still there?Kindly let us know if you are facing any issues till now.As I have already sent you a reply on 10:18 AM today itself.

Many thanks

Ajitabh

[michael_dwehus]

Hi,

i upgraded MaxDB client to 7.9 and now the whole system won't start up...

[Former Member]

Hi Michael,

What exactly error you are facing now?Can you please paste the logs here.So that we can analyze the issue.

Many Thanks

Ajitabh

[michael_dwehus]

Hi Ajitabh,

Disp+Work of DVBEMGS stopped. After starting the instance.

when is try to login with dbmcli -d EMT -U DEFAULT

i get this Error:

C:\Windows\system32>dbmcli -d EMT -U DEFAULT

Error! Connection failed to node SAPTEST01 for database EMT:

-24950,ERR_USRFAIL: User authorization failed

the other Xuser Profiles work.

I tried to set Xuser entry DEFAULT but still getting same Error.

dev_jcontrol.txt.zip

dev_w1.txt.zip

dev_disp.txt.zip

[michael_dwehus]

when i run command:

dbmcli -u EMTADM,<password> -d EMT

i get the same Error:

Error! Connection failed to node SAPTEST01 for database EMT:

-24950,ERR_USRFAIL: User authorization failed

But User and PW are correct! they work on normal windows Logon, SAP MMC etc..

[matus_petrek2]

Michael, but according to dev_w1.log you are still with client 7.7.7. Did you check note 1357452? You didn't answer if there was recent DB upgrade - maybe you should review all steps cause something is missing here.

Also:

C  Try to connect (DEFAULT) on connection 0 ...

C  *** ERROR => Connect to database failed, rc = -10709 (Connection failed (RTE:Database name is missing))

[dbsdbsql.cpp 139]

Check note 39439 and try to create DEFAULT connection in same way.

Regards,

Matus

[Former Member]

Hi Michael,

Please check the logs in the work directory like disp+work to know the reason for the issue.

And also please try if you are able to start the system manually.

Kindly refer the Logs noted in SAPEhpi.log files of the upgrade tool directory.

And let me know the output for the same.

Many Thanks

Ajitabh

[michael_dwehus]

Hi Ajitabh,

i tryed starting the system manually several times. disp+work goes green but after one minute it turns to: "stopped"

in the attachement dev_disp of shadow instance

dev_disp.txt.zip

[Former Member]

Hi Michael,

1. As per your dev_w0 logs Maybe your MaxDB software directory is not accessible. Can you make the permission as 777 and try again.Also try to keep the DVD path smaller.

2. Suggest you to put the new kernel in the path  /usr/sap/SID/SUM-ehp/abap/exenew and /usr/sap/SID/SUM-ehp/abap/exe and after that restart the SUM tool.

3.Can you please check and attach the dev_disp trace file in the work directory of the shadow instance if there is some issue in starting the dispatcher

Also check shadow instance profiles and make sure that there are no duplicate profiles in the profile

directory. From the SAPup.ECO file, u can find the commands used by the upgrade to start the shadow instance may be u can try to start the shadow instance manually.

4.Check the SAP Note 525677:Problems when starting Shadow Instance.

5.Note 39439 might be helpful to recreate the XUSER entries.

6.Try with the DEFAULT connection for your User YourDomain\SAPServiceSID

Hope this will work i.e.

On Windows, the XUSER entries are stored in the registry. For the operating system users <sid>adm and SAPService<SID>, create the XUSER entries mentioned below. As of MaxDB Version 7.5 and above, an operating  system user that has administrator rights can store the XUSER entries  for SAPService<SID>. To do this, use the XUSER option '-c'; for example:

xuser -c <domain>\SAPService<SID> ...

Kindly let me know if any of the above Points worked for you.If it worked then please provide the Points for this.

Many Thanks

Ajitabh