Troubleshooting Tips

This section provides troubleshooting tips to troubleshoot iServices related issues:

Tip 1

Ensure that all prerequisites are configured before using iServices.

Tip 2

If you encounter the following error when an iService method is executed, perform the steps given in the Solution section.

Copy 
<?xml version="1.0" ?>
- <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
- <soap:Header>
- <wsu:Timestamp xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility">
<wsu:Created>2007-10-16T01:10:24Z</wsu:Created>
<wsu:Expires>2007-10-16T01:15:24Z</wsu:Expires>
</wsu:Timestamp>
</soap:Header>
- <soap:Body>
- <soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>System.Web.Services.Protocols.SoapHeaderException: Server unavailable, please try
later ---> System.FormatException: Invalid length for a Base-64 char array. at
System.Convert.FromBase64String(String s) at
Microsoft.Web.Services.Security.Nonce.LoadXml(XmlElement element) at
Microsoft.Web.Services.Security.UsernameToken.LoadXml(XmlElement element) at
Microsoft.Web.Services.Security.SecurityToken..ctor(XmlElement element) at
Microsoft.Web.Services.Security.UsernameToken..ctor(XmlElement element) at
Microsoft.Web.Services.Security.Security.LoadXml(XmlElement element) at
Microsoft.Web.Services.Security.SecurityInputFilter.ProcessMessage(SoapEnvelope envelope) at
Microsoft.Web.Services.Pipeline.ProcessInputMessage(SoapEnvelope envelope) at
Microsoft.Web.Services.WebServicesExtension.BeforeDeserializeServer(SoapMessage message) ---
End of inner exception stack trace ---</faultstring>
<faultactor>http://localhost/ContactiService/Contact.asmx?WSDL</faultactor>
</soap:Fault>
</soap:Body>
</soap:Envelope>

Cause

The error is encountered due to the following reasons:

  • The Soap header contains incorrect CampusNexus CRM login credentials.

  • In Microsoft Component Services, the User Identity set for TalismaCacheService and other iServices is inconsistent.

Solution

  1. Ensure that you specify the correct CampusNexus CRM login credentials in the SOAP header.

  2. In Microsoft Component Services, ensure that the same User Identity is set for TalismaCacheService, and all other iServices.

Note Note

In Microsoft Component Services, to check whether the same User Identity is set for TalismaCacheService and all other iServices, follow these steps:

  1. Open Microsoft Component Services.

  2. Navigate to the Component Services/Computers/My Computer/COM+ Applications node.

  3. Right-click on the TalismaCacheService node.

  4. Select Properties from the shortcut menu.

    The Properties window is displayed.

  5. Click the Identity tab, and check the User Account set for the iService.

  6. Click OK.

  7. Click the node of each iService in the Component Services/Computers/My Computer/COM+ Applications node, and repeat steps 4 through 7 for each iService.

  8. Ensure that the same User Identity is set for the TalismaCacheService and all other iServices.

Tip 3

Enable Traces for iServices to generate input and output traces for an iService call.

To enable trace, perform the following steps on the computer where iServices are installed:

  1. Navigate to the folder where iServices are installed and select the iService folder for which trace needs to be enabled.

    For example, to enable trace for the Account iService, select the Account folder.

  2. Open the Web.config in edit mode.

  3. In the Web.config file, locate the following code snippet:

    Copy 
       <diagnostics>
<trace enabled="false" input="InputTrace.webinfo" output="OutputTrace.webinfo" />
<detailedErrors enabled="false" />
</diagnostics>

  4. In the above code snippet, set enabled="true" for the trace tag.

  5. Save and close the Web.config file.

Tip 4

If you receive any HTTP call failures during iService call then enable failed request tracing in Internet Information Service and identify the reason for the problem.

Tip 5

For any database failure during an iService method call you can collect Profiler trace. This helps in identifying which stored procedure failed.

Tip 6

Enable trace for the Application Server with process specific traces enabled. This generates Application Server Trace for the process and helps to troubleshoot issues that result from iServices call failures on the Application Server.

To enable process specific trace for the Application Server, perform the following steps on the computer where Application Server is installed:

  1. Navigate to the <Drive name>:\Program Files\Common Files\Talisma Shared folder, and double-click TalismaTraceClient.exe.

    The Talisma Trace Client window is displayed.

  2. In the Process area, select Talisma Application Server and select Process-specific Settings option in the Settings area.

    The Talisma Application Server - Trace Options window is displayed.

  3. In the Trace Folder field, specify the path where the Traces will be generated, and click Apply.

Tip 7

If you encounter an issue while working with CampusNexus CRM, the system generates one or more error codes corresponding to the issue. You can refer to the CampusNexus CRM Error Codes guide to further troubleshoot and isolate the cause of the problem.