disp+work.exe Dispatcher status Stopped

[hari_sai15]

Hello Guys...

I have Netweaver 7.31 (demo server) and could not able to up the server for ECC system. As I could see disp+work.exe status stopped in Console Root.

It will be "Green" the moment I start the server but when we click on SAP logon it will become "Yellow" and disp+work.exe status shows stopped.

Is there any solution for the above situation??

Thank you....

[Former Member]

Hi Hari,

check the kernel files and your database is up and running

[divyanshu_srivastava3]

Check dev_disp and dev_W0 logs.

Also. check log area which might be full in case it's MAX DB.

Regards,

[hari_sai15]

Hello Srivastava,

Thanks for your quick reply.

I am new to this tool can you please provide me much more information how to get into dev_disp and dev_w0 logs..and also to check MAX DB.

Thanks again...

[isaias_freitas]

Hello,

The dev_disp and dev_w0 files should be located at the "work" folder (\usr\sap\<SID>\<instance name>\work).

If you share these files we can see why the instance did not start.

Regards,

Isaías

[hari_sai15]

Hi Isaías,

Some how I got those files in below path:

D:\usr\sap\EC5\DVEBMGS00\work

I have attached those two files here...plz let me know where is the issue.

Thank you,

dev_disp.txt.zip

dev_w0.txt.zip

[isaias_freitas]

Hello,

At the dev_disp I can see that all work processes are unable to start.

At the dev_w0 I see the reason: the logon to the database is failing:

B Tue Jul 28 10:56:39 2015
B  Library 'D:\usr\sap\EC5\DVEBMGS00\exe\dbmssslib.dll' loaded
B  Version of 'D:\usr\sap\EC5\DVEBMGS00\exe\dbmssslib.dll' is "720.00", patchlevel (0.45)
B  New connection 0 created
C  Callback functions for dynamic profile parameter registered
C  Thread ID:3580
C  Thank You for using the SLODBC-interface
C  Using dynamic link library 'D:\usr\sap\EC5\DVEBMGS00\exe\dbmssslib.dll'
C  dbmssslib.dll patch info
C    SAP patchlevel  0
C    SAP patchno  46
C    Last MSSQL DBSL patchlevel 0
C    Last MSSQL DBSL patchno         45
C    Last MSSQL DBSL patchcomment Setuser replaced by EXECUTE AS (1459172)
C  ODBC Driver chosen: SQL Server Native Client 10.0 native
C  lpc:(local) connection used on PIECC
C  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2056]
C  (18456) [28000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'PIECC\SAPServiceEC5'.
C  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2056]
C  (4060) [42000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot open database "EC5" requested by the login. The login failed.
C  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2056]
C  (18456) [28000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'PIECC\SAPServiceEC5'.
C  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2056]
C  (4060) [42000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot open database "EC5" requested by the login. The login failed.

, what do you think?

Cheers!

Isaías

[hari_sai15]

I could see some warning message in SQL Server Management Studio ....Is this because of this...? If yes..how can make online this ??

[former_member184473]

Hello Hari,

Is your database up and running?
When this issue started?
Have you performed any system copy (detach/attach or backup/restore) related activities?

Maybe, note 1294762 (schema repair script) might solve this issue.

Best regards,
Eduardo Rezende
SAP Support

[hari_sai15]

Hi Eduardo,

Yes, it was working fine earlier...issue started today only ....yes I have performed the backup activity I removed database files and restore with new copy. But I could see my PI server working fine...only problem with ECC....

As I do not have access for SAP market place in order to download the schema repair script...

Is there any alternative way to resolve the issue?

Thank you....

[former_member184473]

Hello Hari,

After the restore some authorizations are lost.
Kindly contact the person in your company which has access to the market place, download script from from note 1294762 and execute the schema repair script.

Regards,

Eduardo

[hari_sai15]

Hi Edurado...

Will try to do that...Thanks for your inputs....

[Sriram2009]

Hi Hari

In Ms Sql management studio still the DB showing as same? if it is yes, Kindly refer the solution link

https://support.managed.com/kb/a398/how-to-repair-a-suspect-database-in-mssql.aspx

Regards

SS