cancel
Showing results for 
Search instead for 
Did you mean: 

ECC system did not restart after windows update

Former Member
0 Kudos

The ECC system did not restart after Windows Update.

  • Windows 2008 R2;
  • ECC 6 EHP6.0;
  • NetVeaver 731;
  • Kernel 721.

sapstartsrv

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

trc file: "sapstartsrv.log", trc level: 0, release: "721"

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

pid        3372

[Thr 3360] Mon Mar 16 11:50:25 2015

SAP HA Trace: SAP Microsoft Cluster library '721, patch 300, changelist 1498740' initialized

CCMS agent initialization: WARNING: cannot recognize instance type, checking profile parameter "system/type".

CCMS agent initialization for instance type ABAP: return code 0.

CCMS agent start: return code 0.

Initializing SAPControl Webservice

Starting AutoRestart thread

AutoRestart thread started, version check is enabled

Starting WebService SSL thread

Starting WebService Named Pipe thread

Starting WebService thread

Webservice named pipe thread started, listening on port \\.\pipe\sapcontrol_00

Webservice thread started, listening on port 50013

Webservice SSL thread started, listening on port 50014

CATALA\ecqadm is starting SAP System at 2015/03/16 11:52:19

SAP HA Trace: FindClusterResource: OpenCluster failed: 1060 [sapwinha.cpp, line 214]

SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_FAIL [sapwinha.cpp, line 936]

CATALA\ecqadm is starting SAP System at 2015/03/16 12:45:20

SAP HA Trace: FindClusterResource: OpenCluster failed: 1060 [sapwinha.cpp, line 214]

SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_FAIL [sapwinha.cpp, line 936]

Accepted Solutions (0)

Answers (4)

Answers (4)

0 Kudos

Hi - we had the identical issue this evening.  Same circumstances (windows updates pushed).  And, after the server reboot the application would not start.  Same identical errors as indicated above.

In our case, we had to reconstruct line by line the Instance Profile.  Somehow, it was "corrupt".  Although, we could read it, etc.

Kisselev, how did you solve it?  Was it also a problem with your instance profile?

I'm very curious if the root cause was the windows patches.

Former Member
0 Kudos

Hi,

First, please, check what profile is using in SAP<SID>_00 service. In  old systems there shoul be START  profile, but now SAP removed START profile and replace it with DEFAULT profile.

Check SAP Note 1528297 Merge start profile with instance profile.

Former Member
0 Kudos

This issue was resolved.

Former Member
0 Kudos

Congratulations! But how?

Johan_sapbasis
Active Contributor
0 Kudos

Hi Yevgeniy,

Please attach a dev_w0 trace file also from when you try to start as well as dev_disp and dev_ms trace files.

This would really be of better assistance.

Regards,

J

Former Member
0 Kudos

This is log file:

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

trc file: "sapstartsrv.log", trc level: 0, release: "721"

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

pid        880

[Thr 2848] Mon Mar 16 14:51:32 2015

SAP HA Trace: SAP Microsoft Cluster library '721, patch 300, changelist 1498740' initialized

CCMS agent initialization: WARNING: cannot recognize instance type, checking profile parameter "system/type".

CCMS agent initialization for instance type ABAP: return code 0.

CCMS agent start: return code 0.

Initializing SAPControl Webservice

Starting AutoRestart thread

AutoRestart thread started, version check is enabled

Starting WebService SSL thread

Starting WebService Named Pipe thread

Starting WebService thread

Webservice named pipe thread started, listening on port \\.\pipe\sapcontrol_00

Webservice thread started, listening on port 50013

Webservice SSL thread started, listening on port 50014

CATALA\ecqadm is starting SAP System at 2015/03/16 14:52:22

SAP HA Trace: FindClusterResource: OpenCluster failed: 1060 [sapwinha.cpp, line 214]

SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_FAIL [sapwinha.cpp, line 936]

CATALA\ecqadm is starting SAP System at 2015/03/16 14:57:34

SAP HA Trace: FindClusterResource: OpenCluster failed: 1060 [sapwinha.cpp, line 214]

SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_FAIL [sapwinha.cpp, line 936]

trusted named pipe user is stopping SAP System at 2015/03/16 15:02:14

SAP HA Trace: FindClusterResource: OpenCluster failed: 1060 [sapwinha.cpp, line 214]

SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_FAIL [sapwinha.cpp, line 936]

CATALA\ecqadm is starting SAP System at 2015/03/16 15:03:35

SAP HA Trace: FindClusterResource: OpenCluster failed: 1060 [sapwinha.cpp, line 214]

SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_FAIL [sapwinha.cpp, line 936]

Former Member
0 Kudos

Hello Kisselev,

Is that a cluster one?

I found a note that indicates that SAP_HA_FAIL error should not be a problem if it's not clustered system:

1929468 - SAP_HA_FAIL error outputed in the sapstartsrv.log on non clustered system

Maybe there are some other error logs as well?

And check also if the regional settings, timezone settings, etc of the SAPservice user seem OK after Windows patch.

Regards,

Serhat