[CONNECT C#] Addin is not trusted

Hoping someone can help me with this problem.

I made a c# wpf addin for MicroStation, its a dll. I can load it fine on my end. but i have sent this to someone else and when they try and load it they get error message that says 'OHDOTSHEETMANAGER' is not trusted. OHDOTSHEETMANAGER is the name of the app.

then in the Message Details it says this...

'OHDOTSHEETMANAGER' could not be loaded because 'OHDOTSHEETMANAGER' does not have an authorized digital signature.

i found this post. 

https://communities.bentley.com/products/microstation/w/microstation__wiki/15724/utility-cannot-be-loaded-because-its-not-digitally-signed

but i checked and the user has MS_SECURITY = NONE. 

so i shouldn't need to have it have an authorized digital signature. 

anyone run into this before? i works fine on my computer, are there additional things within MicroStation that control this?

JD 

Parents
  • All i think i have finally tracked this down. Mark North from Osborn Engineering should get the credit, but wanted to provide the solution here.

    I found this website that really describes whats going on and fixes 

    https://support.microsoft.com/en-us/help/303650/intranet-site-is-identified-as-an-internet-site-when-you-use-an-fqdn-o

    basically the server (network drive) the workspace is on that contains the MicroStation addin  is not identified as an intranet site or a trusted site.

    you can see these by opening internet options > clicking on the security tab.

    from there you will see a Local intranet icon and a trusted sites icon. your server location need to be listed either as a local intranet or a trusted site.

    Here at Ohio DOT we have added them to the local intranet sites, but Mark North added theirs as a trusted site. so either one should work. I'm gonna go with local intranet might make more sense.

    So select Local Intranet then click the sites button 

    now in the dialog that opens up click the advanced button

    in the dialog that opens up you can add your server. Ohio DOT for example has a couple different ones but and example of what we have added as a local intranet site is...

    *.dot.state.oh.us 

    take a look at your server share name and that should help you figure out the name to add

    Now this should probably be handled by your I.T. department as there is probably a group policy set up and your manual entry could just get wiped out.

    Answer Verified By: John Drsek 

  • Hi ,

    Thank you for providing the final (running Microsoft remote addin) solution for this type of issue and I am glad to hear you and your users are now able to be up and running.

    Bob



Reply Children
No Data