topic Re: Vault Professional 2017 SDK - licensing crash AGAIN in Vault Forum

Vault Professional 2017 SDK - licensing crash AGAIN

Anonymous — Mon, 12 Dec 2016 12:52:46 GMT

Hi to everybody.

I have a problem acquiring a vault 2017 floating license using a software developed with Autodesk Vault 2017 SDK.

The program cannot get a valid license, and retries the error Failed to acquire a license. Please restart the product

To avoid any mistakes i've tested a simple connection with the "VaultList" project, which came with the official SDK from Autodesk; the result is exactly the same.

I quickly realized that the problem is the missing installation of the Vault Client, and its license configuration process.

I have tried all the solutions posted here
https://forums.autodesk.com/t5/vault-forum/vault-professional-2017-licensing-crash/m-p/6266784/highlight/true#M62385

and here
https://knowledge.autodesk.com/support/vault-products/troubleshooting/caas/sfdcarticles/sfdcarticles/Autodesk-Vault-Failed-to-acquire-a-license-Please-restart-the-product.html

without any success.

My company, at the moment, has just floating licenses, but NOT all users need Client Vault (about 190 computers)- we also have special industrial machines that through Vault SDK, since 3 years old, they download designs without any human intervention, and where the Vault Client is really impossible to install.

We understand that Autodesk has changed the licensing system in order to improve it, but without good support for new bugs introduced by developers, our work is stopped

As @Anonymous says at the bottom of the first link, it's necessary to have a Vault 2017 SDK Prerequisites with ALL WHAT IS NEEDED to work correctly, including the ability to set up the license manually without any human intervention, or through DOS commands executable via a batch file.

As i said before, for us it's impossible install the Vault Client, set up the connection and then uninstall it...just to have a simple service-on-demand working.

Our local reseller has no solution for this problem, so I'm here to ask for a quick solution to the problem (NO release in 2018 for instance), because it is getting really serious for us. In the event that the solution does not exist, I would appreciate an official response by Autodesk directly, so that it can then contact my dealer and give answers to my company management on how to proceed for the future.

Waiting for a response, I thank everyone in advance

- Dave

Re: Vault Professional 2017 SDK - licensing crash AGAIN

ihayesjr — Mon, 12 Dec 2016 18:22:42 GMT

Hello Dave,

Sorry for the issues you are now experiencing with Vault 2017. The changes in the license model for Vault was moving all of the license requests from the server on to the clients. Therefore, to create an external application that connects to the Vault server and consume a Vault license, the client needs to be installed and remain installed for the application to work. You will not be able to uninstall the client and keep the custom application working. This will not change for future releases.

The first link you provided was address an issue that is unrelated to the issue you are having.

One question I have for you, based off of your post, is your application only performing a Read operation to the Vault server? If so, this type of operation doesn't require a license.

Re: Vault Professional 2017 SDK - licensing crash AGAIN

Anonymous — Tue, 13 Dec 2016 08:59:19 GMT

Hi Irvin,

thanks for your answer.

I'm very disappointed about your answer, first of all because IT'S NOT A SOLUTION...you don't told me something new, but all things that, unfortunately, i already know.

I know that a only-Read operation doesn't require a license....but if i'm here to ask a solution for a Autodesk bad programming issue, probably i need to do much much more than a Read only operation...do you agree with me?

The REAL reason makes me angry Is that NOBODY knew this "requirement", and NOWHERE in the Vault 2017 Help CHM is mentioned this problem!!!

"Therefore, to create an external application that connects to the Vault server and consume a Vault license, the client needs to be installed and remain installed for the application to work. You will not be able to uninstall the client and keep the custom application working."

As i told in my original post, my company has special industrial machines whith a particular Windows modded edition, where is impossible to install the client (I omit the details because they are not needed to Autodesk),and also for different users it is dangerous to have the client installed.

So, what i have to do now? I have different collaborators around the world that sometimes came back here at headquarter...again: i don't really know what to do to update our software ASAP.

If i was aware about this problem, probably i don't update our systems from 2016 to 2017, without considering the frequent Inventor crash (but this is not the right section for this topic)

"This will not change for future releases"

.....forgive me if don't agree with you and i'm laughing

I think you will understand if I say that we have paid to use the software, and must work at least as the previous version.

My company more than 4 years ago chose Autodesk products mainly for the ability to customize the software with its SDK - now that choice is giving us problems. We do not intend to change ... unless being forced.

Waiting for a concrete solution, have a nice day

- Dave