Resolving Client-Side Certificate Errors

Problem: A remote client does not run when using a client-side certificate, and an error is reported, such as -403 HTTP or -413 HTTP.

Workaround:

Take action based on the error reported:
- -403 HTTP error – the IIS server reports this Unauthorised Error if you do not supply the identity and identity_password correctly.
  Verify that you provided the correct values for the Stream parameter as described in Running the Client.
- - 413 HTTP error – the IIS server may not have the entire certificate.
  Try running this script:
```
cscript adsutil.vbs set w3svc/1/uploadreadaheadsize 65536
```
- StreamErrorCode=SECURE_TRUSTED_CERTIFICATE_FILE_NOT_FOUND.
  Verify that the certificate files have been correctly copied to the emulator or device, and that the value of Output_File_Folder is correct.
- StreamErrorCode=SECURE_CERTIFICATE_NOT_TRUSTED.
  Verify that the certificate files are correct. If they are correct, the IIS server may not be configured correctly for client-side certificate authentication.
- Other errors – these may indicate the IIS server is not configured correctly for client-side certificate authentication.
  Check the IIS configuration as described in Setting Up RS_Client for Client-Side Certificate Authentication.
To learn more about Microsoft IIS-related errors, see: http://technet.microsoft.com/en-us/library/cc737382(WS.10).aspx