Skip to Content
avatar image
Former Member

"start_call_sick" dump when starting newly installed 6.20

I have now got 6.20 Test Drive running ok, except for this:

When I first bring up R3 after powering up, I get a START_CALL_SICK short dump. The error analysis shows:

-


Error analysis

-


The error probably occurred when installing the

R/3 system.

Error message of the error that appeared first:

"no application server offers an ENQ service".

I can ignore the error and process ok from then on. Subsequent logons do not display this problem.

Do I have an installation error? Are others experiencing this same problem? Is there any action I can take to resolve this?

I have the short dump as a text file, and can send it to anyone who would like to see it...

Thanks.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Apr 30, 2004 at 10:17 AM

    Hi David,

    call TA sick and check it out. If there really is no WP configured as Enqueue service you want to enter one in the Instance profile (rdisp/wp_no_enq = 1).

    Import the profiles in TA RZ10, Utilities -> Import profiles -> of active servers. Then you can maintain it out of R/3 or change manually in file System.

    Dont forget to run TA SE06 and SGEN and to configure STMS after initial installation.

    Cheers,

    Andi

    Add comment
    10|10000 characters needed characters exceeded