error Response
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
Contains diagnostic error information when the server failed to process a request.
Syntax
<error code="integer value" subCode="integer value" reason="string value" detail="string value">
</error>
Attributes
Attribute |
Data Type |
Description |
---|---|---|
Code |
integer |
Communicator Web Access Server error code. |
SubCode |
integer |
Communicator Web Access Server subcode |
Reason |
string |
Describes the condition that can give unexpected results. |
Detail |
string |
Descriptive error message. |
Element Information
Parent Elements
Element |
Description |
---|---|
Holds the synchronous response to an HTTP POST request carried over through a command channel. It is used to inform the client of the initial status of a request. |
|
Contains diagnostic error information when the server failed to process a request. |
|
The request contained elements that were unrecognized by the Communicator Web Access Server |
Child Elements
Element |
Occurrence |
Description |
---|---|---|
0 or more |
Indicates SIP-related errors. |
|
0 or more |
A detailed trace of the call stack of CWA. To receive the stackTrace element, debug must be enabled in the initiateSession request. |
Examples
In the following example, debug has been enabled in initiateSession. The error element contains stack trace information.
Example 1:
Request failed event.
<requestFailed eid="102" rid="6">
<error code="18201" reason="Operation failed" detail="The requested operation failed.">
<sipResponse code="485" reason="Duplicate group name">
<ms-diagnostics>errorId="2";reason="Unknown
Failure";source="red-lsapf-
02.exchange.corp.microsoft.com";
AppUri=http://www.microsoft.com/LCS/UserServices
</ms-diagnostics>
</sipResponse>
<stackTrace> ... </stackTrace>
</error>
</requestFailed>
Example 2:
Polling failure event.
<cwaResponses requestProcessed="0">
<error code="18100" reason="Session not found" subCode="2"
detail="Sign-in to OCS failed"/>
<stackTrace>
at Microsoft.Rtc.Signaling.SipAsyncResult.ThrowIfFailed()
at Microsoft.Rtc.Signaling.Helper.EndAsyncOperation[T]
(Object owner, IAsyncResult asyncResult)
at Microsoft.Rtc.Signaling.SipEndpoint.
EndRegister(IAsyncResult result)
at Microsoft.Rtc.Internal.Collaboration
.CollaborationEndpoint.SipEndpoint_RegistrationComplete
(IAsyncResult asyncResult)
</stackTrace>
</error>
</cwaResponses>