## Troubleshooting

The following resources and descriptions of common issues may help troubleshoot issues with your web services client application.

Resources

- Symantec Endpoint Protection Manager system audit logs

  These logs include any changes that are made by web service calls. A log entry includes the administrator ID and identifies the source as a web service request.

- Debug logging

  The `catalina.log` and `catalina.err` log files can help diagnose startup issues. They can be found in the following location:

  `Symantec_Endpoint_Protection_Manager_installation_folder/logs/tomcat`

The following issues can be checked in the PowerShell scripts, or in any equivalent calls that your web service client makes.

Common issues

- You get a navigation error when your client tries to connect to Symantec Endpoint Protection Manager to perform any task, including registration. Check that the Symantec Endpoint Protection Manager hostname/IP address or web services port number are correct. See Registering an application with Symantec Endpoint Protection Manager.

  These values must be correct in the following locations:

  - `Config.xml` if you are testing the sample PowerShell scripts. See Using the sample PowerShell scripts.

  - `Get-SepmRmmWsAccessToken.ps1`, if you choose to test getting and setting an access token manually. `Write-AccessTokenToConfig.ps1` takes care of this issue for you.

  - The WSDL files

- You get an error message like "Full authentication is required to access this resource." Check to make sure that you include the access token in your HTTP header or URL. Check to make sure that the access token is not expired. If the access token is expired, use the refresh token to get a new access token. Your code should also handle the situation where an access token is revoked gracefully.See Including the OAuth token in calls to web services. See Authorizing an application to call Symantec Endpoint Protection Manager web services.

- You get an InvalidArgumentServiceException error. For more information about errors in individual web methods, see the Reference Guide. Common causes of these errors include the following:

  - Out-of-date WSDL files. Check to make sure that you are using WSDL files from the SDK that was provided with the Symantec Endpoint Protection Manager that you are building your client against, or generate the WSDL files dynamically. See Managing WSDL files for your web service calls.

  - For errors in calls to the methods of PolicyService, Message Transmission Optimization Mechanism (MTOM) is not enabled. Check to make sure that MTOM is enabled in your client.

  - For errors in calls to the methods of PolicyService, the policyFileContentID (CID) parameter does not match the CID of an actual policy file. Verify the CID request in your client.

See Creating a web services client application.