An error has occurred during the execution of the Register services with new start profiles step

[former_member280828]

Hello All,

We are upgrading our portal from 7.0 to 7.3 using SUM patch 9. We are stuck in phase "Execution" in step -  "Register services with new start profiles".

We have 4 Dialog instances and before the downtime phase start we have stopped all 4 dialog instances.

From the SUM logs it's trying to register service on dialog instance i.e TPPDIA114 we got below error message from log file REGISTER-SERVICES.LOG:

<!--LOGHEADER[START]/-->

<!--HELP[Manual modification of the header may cause parsing problem!]/-->

<!--LOGGINGVERSION[2.0.7.1006]/-->

<!--NAME[/usr/sap/TPP/SUM/sdt/log/SWITCH/REGISTER-SERVICES.LOG]/-->

<!--PATTERN[REGISTER-SERVICES.LOG]/-->

<!--FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%6s]: %m)]/-->

<!--ENCODING[UTF8]/-->

<!--LOGHEADER[END]/-->

Dec 8, 2013 1:07:37 AM [Info  ]: Registering service of instance J00 with new profile /sapmnt/TPP/profile/TPP_J00_TPPDIA114.

Dec 8, 2013 1:08:40 AM [Error ]: The following problem has occurred during step execution: com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: java.net.ConnectException: Connection timed out.

Please let us know if anyone encountered such error in portal upgrade.

Thanks,

Rbk

[former_member185239 · Accepted solution]

Hi,

1. stop if any sapstratsrv process is running on dialog host

    then restart the sum tool.

or

2. Start your dialog instances

With Regards

Ashutosh Chaturvedi

[former_member280828 · Accepted solution]

Hi Ashutosh,

After stopping all dialog instances I have stopped/kill all sap processes also tried to start one of the dialog instance but it fails below error I guess SUM still has to update the kernel and secstore and after the completion of upgrade only we can start all dialog instances.

com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "/usr/sap/TPP/SYS/global/security/data/SecStore.properties" is invalid: software version 6.30.000.001 is incompatible with file version 7.00.000.001..

Thanks,

Rbk

[Former Member · Accepted solution]

Hi,

Please check the below note.

1795971 - FileInvalidException:SecStore.properties is invalid: software version is incompatible with...

Thanks

Rishi Abrol

[former_member185239 · Accepted solution]

Hi SBIL,

During the upgrade process , the dialog instances are locked by the central instance in safe and upgrade mode. During the upgrade , it created the Jupgrade key and properties similar to securestorage.properties and key.

Just follow the steps below

Backup the directory '/usr/sap/<SID>/SYS/global/sltools'

Backup file /usr/sap/<SID>/<inst.number>/j2ee/cluster/version.bin

Delete the directory /usr/sap/<SID>/SYS/global/sltools

Delete the file  /usr/sap/<SID>/<inst.number>/j2ee/cluster/version.bin

Restart the instance (this should resynchronize the corresponding directory)

Follow the steps :

1795971 - FileInvalidException:SecStore.properties is invalid: software version is incompatible with file version

I think deployment of  portal and java component.completed right?

With Regards

Ashutosh Chaturvedi

[former_member280828 · Accepted solution]

Hi Ashutosh / Rishi,

Thanks for your kind help here.

We have resolved the problem after opening 1128/1129 (bi directional) on all DI's & CI after that we tried and it worked.

Thanks again.

Rbk