topic Re: autodesk.connectivity.webservices.interop error on an app from AU2016. in Vault Forum

autodesk.connectivity.webservices.interop error on an app from AU2016.

JacksonBrent — Wed, 07 Dec 2016 16:28:54 GMT

Hello,

I'm using a program that was given to me at Autodesk University that does automatic advanced searches and saves that data to spreadsheets. I have it close to working, but I am getting this error that won't let me log in. If anyone has any input into this it would be very helpful.

InvalidServer: Could not load file or assembly 'Autodesk.Connectivity.WebServices.Interop, Version=22.0.0.0, Culture=neutral, PublicKeyToken=aa20f34aedd220e1' or one of its dependencies. An attempt was made to load a program with an incorrect format.

Thanks!!!

-Brent

Re: autodesk.connectivity.webservices.interop error on an app from AU2016.

paul.gunn — Thu, 08 Dec 2016 14:50:34 GMT

Hi Brent,

The 'incorrect format' error means that you have some mix of x86 and x64 DLLs / EXEs. It is possible you just need to use the appropriate bit-ness (x86/x64) of the SDK needed for your purposes.

Paul

Re: autodesk.connectivity.webservices.interop error on an app from AU2016.

JacksonBrent — Thu, 08 Dec 2016 20:02:33 GMT

Do you know how to determine the correct Bit-ness when running this? I have the source code and have tried recompiling it as x64, but the program that it spits out won't launch, it just "installs" I might be approaching this incorrectly though. I can't find anywhere in the code to change it to x64 or 86 accept when changing the solutions platform. I'm a little over my pay-grade at this point coding wise.

Re: autodesk.connectivity.webservices.interop error on an app from AU2016.

paul.gunn — Thu, 08 Dec 2016 20:32:50 GMT

Hi Brent,

Really either bit-ness (x86 or x64) would be fine. The main thing is to have the consistency across the board.

Based on your description, it is hard to envision what is going wrong. One thing I am wondering: Vault server supports backwards compatibility for N-2 releases. So if your app is already working in Vault 2016, you should be able to run it as-is against Vault 2017.

Would that be an option for you vs. recompiling with the 2017 SDK?

Paul

Re: autodesk.connectivity.webservices.interop error on an app from AU2016.

paul.gunn — Thu, 08 Dec 2016 20:37:56 GMT

FYI - this thread might also be useful. Talks about the x64 vs. x86 DLLs required.

http://forums.autodesk.com/t5/vault-customization/log-in-won-t-work-in-vault-2017/td-p/6688589

Paul

Re: autodesk.connectivity.webservices.interop error on an app from AU2016.

JacksonBrent — Thu, 08 Dec 2016 22:17:17 GMT

That does help me understand what might be the problem, but I don't really know how to add it to the project. I'm not great with Visual Studio, still a bit new. Also, as I said, I didn't write this program, this is just what they gave me at AU2016.

Re: autodesk.connectivity.webservices.interop error on an app from AU2016.

paul.gunn — Fri, 09 Dec 2016 18:38:50 GMT

Hi Brent,

It is hard for me to say specifically what is going wrong (or what needs to be done) as I'm not really familiar with the AU2016 app you mention.

My advice would be to take a look at some of the Vault SDK example applications (installed with Vault server) and use those as a basis of comparison. The dlls are added to the various projects as 'references' (visible under each project) - if you take the references configured for the sample apps as a model, that should hopefully guide you to getting the right references set up in your app.

I'm sorry I don't have any more specific advice than this. Hopefully this will help get you on the right path,

Paul

Re: autodesk.connectivity.webservices.interop error on an app from AU2016.

JacksonBrent — Fri, 09 Dec 2016 19:23:04 GMT

Thank you. I will look into that and see if I can find a solution. I know it was an open ended question, I was hoping to get pointed in the right direction.

Re: autodesk.connectivity.webservices.interop error on an app from AU2016.

danmachen — Tue, 05 Dec 2017 14:13:17 GMT

Stuck at this same point. Was there ever a solution found?

This is the AU Class that references the Vault SDk reporting app.

Dashboard Smashboard - Vault Reporting on Steroids hosted by @ihayesjr & Tim Bourdois

http://au.autodesk.com/au-online/classes-on-demand/class-catalog/classes/year-2016/vault-professional/pl20911#chapter=0

The demo starts on the video at 45:10.

I attached a screen clipping of the issue I came across when entering the script into the command prompt.

Hopefully someone can help!