Description

Domain Cache sweep interval set to {param1}.

Message #

Domain Cache sweep interval set to {param1}

Fields #

Description

Synthesized POSIX offset for SID {param1}; computer {param2}. For more information about the compatibility of this operation with your configuration; see Knowledge Base article Q306552.

Message #

Synthesized POSIX offset for SID {param1}; computer {param2}. For more information about the compatibility of this operation with your configuration; see Knowledge Base article Q306552.

Fields #

Description

Connected to Mapping Server at host {param1} ({param2}).

Message #

Connected to Mapping Server at host {param1} ({param2})

Fields #

Description

Subsystem for UNIX-based Applications status: {param1}.

Message #

Subsystem for UNIX-based Applications status: {param1}

Fields #

Description

Unusable PsxOffset {param1} from domain SID {param2} with domain name {param3}. See Knowledge Base article Q306552 for more information.

Message #

Unusable PsxOffset {param1} from domain SID {param2} with domain name {param3}. See Knowledge Base article Q306552 for more information.

Fields #

Description

PSXSS has encountered a user or group ID with a value that requires careful POSIX offset management. See Knowledge Base article Q306552 for more information. The internal UID is 0x{param1}{param2}.

Message #

PSXSS has encountered a user or group ID with a value that requires careful POSIX offset management.  See Knowledge Base article Q306552 for more information. The internal UID is 0x{param1}{param2}.

Fields #

Message #

PSXSS has encountered a user or group ID with a value too large to convert to a uid_t; and converted it to a reserved UID value. See Knowledge Base article Q306552 for more information. The internal UID is 0x{param1}{param2}.

Fields #

Description

The status value {param1} was converted to EACCES. While this is an informational message only; your system administrator should be informed that this event occurred.

Message #

The status value {param1} was converted to EACCES.  While this is an informational message only; your system administrator should be informed that this event occurred.

Fields #

Description

Could not connect to Mapping Server at host {param1}:while connecting {param2}.

Message #

Could not connect to Mapping Server at host {param1}:while connecting {param2}

Fields #

Description

Could not open registry key {param1}: NtStatus {param2}.

Message #

Could not open registry key {param1}: NtStatus {param2}

Fields #

Description

Internal Error: TLS Client not as expected at {param1} line {param2}.

Message #

Internal Error: TLS Client not as expected at {param1} line {param2}

Fields #

Description

Unexpected Exception pid={param1} cid={param2}.{param3} code={param4} fc={param5}.

Message #

Unexpected Exception pid={param1} cid={param2}.{param3} code={param4} fc={param5}

Fields #

Description

The POSIX offset for domain {param1} is {param2}; which is invalid. The domain will be ignored and inaccessible. See Knowledge Base article Q306552 for more information.

Message #

The POSIX offset for domain {param1} is {param2}; which is invalid.  The domain will be ignored and inaccessible. See Knowledge Base article Q306552 for more information.

Fields #

Description

Subsystem for UNIX-based Applications is unable to load a DLL; pid={param1} cid={param2}.{param3} code={param4} fc={param5}.

Message #

Subsystem for UNIX-based Applications is unable to load a DLL; pid={param1} cid={param2}.{param3} code={param4} fc={param5}

Fields #

Description

Subsystem for UNIX-based Applications detected a hard error. The exception vector contains: {param1}.

Message #

Subsystem for UNIX-based Applications detected a hard error. The exception vector contains: {param1}

Fields #

Description

Connection to port {param1} failed; Subsystem for UNIX-based Applications terminated during startup.

Message #

Connection to port {param1} failed; Subsystem for UNIX-based Applications terminated during startup.

Fields #

Description

Could not connect to Mapping Server at host {param1}:while connecting: Hostname Resolution failed.

Message #

Could not connect to Mapping Server at host  {param1}:while connecting: Hostname Resolution failed.

Fields #

Description

A fatal condition has occurred during subsystem startup. The condition is {param1} and the status code is {param2}.

Message #

A fatal condition has occurred during subsystem startup. The condition is {param1} and the status code is {param2}

Fields #