OSF DCE Problem Determination Guide

0x1260a58b GDS_S_ILLSTATE_EVENT_ERR

Severity: Fatal Component: gds / GDS_S_GENERAL

Text: Illegal state/event combination detected (state = %d, event = %d)

Explanation: Stub process has detected a state/event combination not described by the

state/event table

Action: Evaluate state resp. event value. Report the problem to the responsible software

engineer.

0x1260a196 GDS_S_INCONS_INSTREAM

Severity: Fatal Component: gds / GDS_S_GENERAL

Text: An input ﬁle contains insufﬁcient information.

Explanation: The program has tried to read some input, but didn’t ﬁnd it in the input

stream.

Action: Provide the expected input stream.

0x1260a89a GDS_S_INITDSA

Severity: Notice Component: gds / GDS_S_GENERAL

Text: DSA of Directory ID: %d has initialized.\n

Explanation: The Directory Service Agent for the speciﬁed Directory ID has read the

schema information and has attached to IPC.

Action: No action required.

0x1260a8a2 GDS_S_INIT_SEC_ERR

Severity: Warning Component: gds / GDS_S_GENERAL

Text: Initializing credentials failed for auth. mech. %d, name of the target DSA: %s,

\nmessage from security interface: %s.\n

Explanation: The Directory Service Agent (DSA) could not initialize the credentials for

the speciﬁed authentication method. This means the DSA can not chain a request to the

target DSA via Directory System Protocol (DSP). So the result of an operation may not

be the expected one. The following authentication mechanisms can appear:

2 = Simple Unprotected Authentication

5 = DCE Authentication

Action: Check whether the message which was supplied by the security interface can

help. If DCE Authentication was used:

Check whether the attributes Principal-Name and

Authentication-Mechanism of the target Directory Service Agent (DSA)

are entered correctly in the Directory Database.

Check whether the DCE security daemon is active.

2− 290 Tandem Computers Incorporated 124330