ASP.NET Application with Autodesk Vault webservice doesn't work on IIS

[Anonymous]

Hi Everybody,

I'm doing an application in ASP.NET that it use web service Autodesk Vault 2017, but locally all works very well, I'm using windows authentication and I could get data from Vault.

The problem is when I publish the application on IIS server, I get an error 312, and checking the SDK vault information and said: WinAuthUserNotFound could be auto create is disabled or could not find a valid AD group.

I hope someone can help me with this problem.

Kind Regards.

[Jason.Courtemanche]

Hi @Anonymous,

With an error: "WinAuthUserNotFound [312]", it sounds like the server you are using may not have the correct IIS module (Windows Authentication) installed or it's not fully configured. I would try testing with Vault Client locally and remote to confirm before trying to try to connect with sdk.  

Regards,

Jason

[Anonymous]

Hi @Jason.Courtemanche,

Thank you very much for the reply, and effectively I think that some configuration is missing on IIS, right now Windows Authentication is enabled in server, but seems not working.

Locally all works fine, when I execute the visual studio solution, the web service connect without problem, I can use it.

Only when I publish the solution on IIS doesn't work. I have worked with Windows Authentication in other web applications but never with Autodesk Vault web service, for that reason I don't Know much about the needed configuration.

I hope that you can try some configuration that works. It really would be greate.

Kind regards,

Jonathan

[Jason.Courtemanche]

Hi @Anonymous,

Thanks for the update. Maybe if you try capturing the issue with vapiTrace plugin for fiddler you will see what data is missing compared to the data the Vault Client sends on login to help narrow down where the issue is coming from. Also, remember that the Vault client when connecting to Vault through windows user also communicates with the domain to validate the user credentials. You would need to use Wireshark to capture those packets and or process monitor to see that the application is making the calls to the domain. Make sure the app has access to also communicate with the domain controller or this will also cause issues. 

I have seen similar errors and just needed to clean the .net temp folder (C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files) on the Server and do a IISRESET.

Regards,

Jason 

[Anonymous]

Hi @Jason.Courtemanche,

I have followed your instructions to analyze the network traffic, but I don't get any relevant stuff that can help me to solve this.

I have done more test on IIS and the last error that I obtained is the next:

How you can see the error show me the reference Autodesk.Connectivity.WebServicesTools.

I was thinking that maybe could be a corrupt library, but I have reimported all libraries and always get the same error.

I hope that you can help me with this more specific error.

King regards,

Jonathan

[psaarloos]

Hi,

Please take a look at a posting of me from last week: https://forums.autodesk.com/t5/vault-forum/vault-2018-web-app-login-issue/td-p/7273764

It explains a bit what you need to do to get a Connection through the Vault API in IIS. You need to do some things because of the new licensing mechanism and the way IIS works. There is also a sample project in the posting, please try to run this sample on your environment. First use a Vault user account to log in. If that works you could try to create the WebServiceManager with Windows Authentication.

Hope it helps.

[psaarloos]

Hi Jonathan,

Have you been able to resolve the issue already?

[Anonymous]

Hi @psaarloos,

To right now my application doesn't work, but I am waiting because I don't have direct access to IIS, so I couldn't perform all steps except for for the solution.

I hope as soon the changes on IIS can be proved, I will inform you the results.

As long as I continue working locally.

Thank you very much for the support.

Kind regards,

Jonathan Nevarez

[Anonymous]

Hi @psaarloos,

I tested directly on the IIS server the same application using Autodesk Vault WeService, I made different configurations in order to get success in the use of professional license, but I still getting the same error:

Exception of type 'Autodesk.Connectivity.WebServices.VaultLicenseException' was thrown

1st Configuration(SUCCESS IN READ ONLY MODE😞

The platform of the application was x86, for this case I set the option Enable 32-Bit Aplication from application pool in true.
I published the solution in read only mode access with the next configuration:

• <Licensing edition="None" />
• AccessWindowsAuth = new WinAuthCredentials(identities, "DATABASE", true);
  webservicemanager = new WebServiceManager(AccessWindowsAuth);

And with this configuration I could obtain the information and displayed in the website.

2nd Configuration(UNSUCCESSFULLY WITH PROFESSIONAL EDITION😞

So the next step was trying to use the Professional license in order to write or modify information, for this I use the same configuration but in this case set the license to Professional edition and disable the read only mode:

• <Licensing edition="Professional" appPath="C:\User\Projects\AUTV\SOURCE CODE\Autodesk_APP\Autodesk_APP\bin\x86\"/>

• AccessWindowsAuth = new WinAuthCredentials(identities, "DATABASE", false);
  webservicemanager = new WebServiceManager(AccessWindowsAuth);

With this configuration I obtain the error of license:
Exception of type 'Autodesk.Connectivity.WebServices.VaultLicenseException' was thrown.

3rd Configuration(UNSUCCESSFULLY X64😞

Another test that I did was change the platform of the application from x86 to x64 and changed the DLL's files and al configuration related with platform.
I executed the applcation locally and works fine, so I published it in the server and for that I set Enable 32-Bit Aplication from application pool in false and the application runs fine but when I tried to connect with the server I git the same error from license:

Exception of type 'Autodesk.Connectivity.WebServices.VaultLicenseException' was thrown.

In this case I changed the platform, thinking in maybe had been a issue with the license compatibility, but it was not like that.

The Vault version in server is: Autodesk Vault Professional 2017.

I don't know if I missing something for that my application can works.

Kind Regards,

Jonathan Nevarez