Using ApiLogger.exe
| Microsoft Office Live Communications Server 2005 with SP1 |
Using ApiLogger.exe
The ApiLogger.exe application is provided with Live Communications Server to assist in the debugging of Live Communications Server applications. Any SIP-related error generated by the Live Communications Server will be registered in the log and can be viewed by running ApiLogger.exe. For each error, a line is present with one of the following messages:
| Application error message | Meaning |
|---|---|
| "Branched requests must be sent on new client transactions." | The application is attempting to call ClientTransaction.SendRequest twice on a ClientTransaction instance. Only one request may be sent per ClientTransaction instance. |
| "Cannot proxy more than once if ServerTransaction.EnableForking is set to false." | The application is attempting to call ServerTransaction.CreateBranch on the same ServerTransaction a second time, but ServerTransaction.EnableForking has been set to false. (ServerTransaction.EnableForking is set to true by default. |
| "Failed to proxy message. Are you trying to proxy the same response twice?" | Your application has attempted to proxy the same response for the same ServerTransaction instance at least twice. |
| "Invalid status code." | The application supplied an invalid status code in the Response.StatusCode property of the Response object passed to ServerTransaction.SendResponse. |
| "Cannot send two requests on the same transaction." | The application is attempting to send two different requests via the same ClientTransaction object. Check your code and make sure that you are not passing more than one Request object for the same ClientTransaction instance by calling ClientTransaction.SendRequest more than once on it. |
| "Cannot proxy multiple final responses." | Your application has attempted to proxy two different final responses for the same ServerTransaction instance. |
| "Cannot proxy. Transaction is in canceled / timed out state." | The Transaction object (ServerTransaction or ClientTransaction) timed out while attempting to service a request or response. Examine the message log for the specific message that might have caused the time-out or unexpected cancelation. |
| "Only sip: URIs are supported." | The application attempted to proxy a message with a "tel:", "sips:" or other URI scheme that is not specifically "sip:". Consider filtering all messages whose URIs are not of scheme "sip:" if they will be encountered frequently. |
Internal Error Messages
Internal error messages represent internal Live Communications Server failures, such as unavailable memory for specific operations. Internal error messages are prefixed with "Internal error:".
| What did you think of this topic? |
| © 2008 Microsoft Corporation. All rights reserved. |