Connection client not installed error 112235

User can sign into the cloud datasource without any issues, but when he uses my app it can't login and display's a login error dialog.

No other user experiences this error.

ProjectWise Explorer 10.00.3.434
Connection Client 11.00.01.109

ProjectWise SDK 10.00.3140
Windows 10

 

Parents
  • ,

    More details and explanation would be helpful.

    How is the user signing into "the cloud datasource"?  If the user is not signed into the CONNECTION Client and clicks on the "Log in" button when "Bentley IMS" is the Authentication" selection, the user should be prompted to sign into the CONNECTION Client.  If the user is not signed in and continues, then the user will get this error.

    I was able to reproduce this on my box by signing out of the CONNECTION Client and then trying to sign into a datasource hosted by Bentley. When I see the log in dialog, and click on the "Log in" button, I get prompted to sign into the CONNECTION Client.  If I skip signing into the CONNECTION Client, then I get the same error message.

    Please verify that the user is actually signed into the CONNECTION Client before running your app and see if that changes the behavior.

    Answer Verified By: Kevin Cox 

Reply
  • ,

    More details and explanation would be helpful.

    How is the user signing into "the cloud datasource"?  If the user is not signed into the CONNECTION Client and clicks on the "Log in" button when "Bentley IMS" is the Authentication" selection, the user should be prompted to sign into the CONNECTION Client.  If the user is not signed in and continues, then the user will get this error.

    I was able to reproduce this on my box by signing out of the CONNECTION Client and then trying to sign into a datasource hosted by Bentley. When I see the log in dialog, and click on the "Log in" button, I get prompted to sign into the CONNECTION Client.  If I skip signing into the CONNECTION Client, then I get the same error message.

    Please verify that the user is actually signed into the CONNECTION Client before running your app and see if that changes the behavior.

    Answer Verified By: Kevin Cox 

Children