Microsoft Codename “Trust Services” Troubleshooting

Microsoft Codename “Trust Services” Troubleshooting

This page discusses known issues and troubleshooting steps for Microsoft Codename "Trust Services" Lab

If you have an issue not resolved here, Azure Labs Support Forum is a good place to ask questions about Trust Services. You can also email Trust Services team about your experience with the lab:

Error when starting Trust Services Shell

Problem: You start Trust Services Shell (TrustServicePS.bat) and get one of the following errors:

  1. Add-PSSnapin : The Windows PowerShell snap-in 'Microsoft.SqlAzure.Trust.EcmPSLib' is not installed on this machine.
  2. Add-PSSnappin : No snap-ins have been registered for Windows Powershell version 2.

Possible cause 1: This may happen at the end of installation if you launched the MSI file directly from 32-bit IE or from a 32-bit command prompt (or another 32-bit shell, like FAR Manager).
Solution: You can safely ignore this error. Close the launched command line window and start Trust Services Shell using the shortcut on the desktop or in the Start Menu.

Possible cause 2: This may happen if you installed 64-bit Trust Services, but try to run TrustServicePS.bat from 32-bit command prompt (or another 32-bit shell, like FAR Manager).
Solution 1: Use the desktop or Start Menu shortcuts (created by the installer) to launch the Trust Services Shell, or launch a 64-bit command prompt and run TrustServicePS.bat in it.
Solution 2: If you do need to use Trust Services from 32-bit programs, install 32-bit Trust Services, even if you have 64-bit OS. It is OK to have both 32-bit and 64-bit versions of Trust Services installed side-by-side on a single machine.

Samples build error

Problem: You may get an error when building samples.
Possible cause: the SDK path is different from the path used by sample.

  • Open project properties, switch to Reference Paths tab
  • Add BIN folder from the Trust Service SDK installation directory to reference paths
    This folder should look something like: C:\Program Files\Microsoft\Trust Services Lab SDK and Shell (x64)\bin
  • Save project, build

    Trust Services SDK Installation Failure

    Problem: During setup you get an error popup "There was a problem with this installer package. A program run ... did not finish as expected ..."
    Possible cause: There was an incorrect MSI available at the download site initially.
    Solution: Re-download the installer from Trust Services SDK download page.

    Debugging PowerShell errors

    Problem: While using the "New-Ecm" or "New-SqlEcm" cmd lets, you might get the error "System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation."
    Possible cause: Not easy to figure out with the generic error message that is thrown. It could be communication error, bad input, etc. Need a way to see inner exception to understand the real issue.
    After the error occurs, run the following command to display complete error details:
    $error | fl -Force

    Here "$error" is the inbuilt variable that stores the default errors occurred in the current session. In the command above we are asking to display a full listing of the errors. If you would like to clear all the errors to avoid noise you can run $error.clear() method and repro the problem again.

    Connections Errors

    Problem: You get connection errors to Trusts Services web endpoint.

    For example, from PowerShell window you may get the following error:

    New-Ecm : Error occured while communicating with Trust Services: There was no endpoint listening at that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.. Activity ID : f620c7c7-31d9-451d-99c2-4b666dcc5536
    At TrustPortTest.ps1:28 char:12
    +     New-Ecm <<<<  -Admin -ServerName $trustServerName -ServerUrl $trustServiceUrl `
        + CategoryInfo          : NotSpecified: (:) [New-Ecm], EcmTSAvailabilityException
        + FullyQualifiedErrorId : Microsoft.SqlAzure.Trust.EcmExceptions.EcmTSAvailabilityException,Microsoft.SqlAzure.Trust.EcmPSLib.NewEcmCommand

    Possible cause: Your corporate firewall or proxy might be blocking outbound https connections to port 4433 used by Trust Services Web Service.
    Solution 1: Reconfigure the firewall or proxy. Verify that you can access the above URL from a browser window.

    Quick Links

Leave a Comment
  • Please add 6 and 8 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Sort by: Published Date | Most Recent | Most Useful
  • Richard Mueller edited Revision 27. Comment: Removed (en-US) from title, added tag

Page 1 of 1 (1 items)
Wikis - Comment List
Sort by: Published Date | Most Recent | Most Useful
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
  • Richard Mueller edited Revision 27. Comment: Removed (en-US) from title, added tag

Page 1 of 1 (1 items)