Log in won't work in Vault 2017.

[Anonymous]

I've converted two programs to Vault 2017 (from 2016). In one of the program the log in works in debug mode, but not in released and published version any longer. In the other program the log in doesn't work in debug mode either even though I use the exact same method. I've tried to find if the programs have different settings, but it looks to be the same. Does anyone have a tip to what it can be? Below is the log in line.

Dim results As VDF.Vault.Results.LogInResult = VDF.Vault.Library.ConnectionManager.LogIn("server", "vault", "administrator", "password", VDF.Vault.Currency.Connections.AuthenticationFlags.Standard, Nothing)

[wayne.brill · Accepted solution]

Hi,

Here are some things to check:

1. If you are logging into a vault from the API with read/write permission, the installation of the Vault Client on the system is mandatory.

2. A licensing problem is can be caused by clmloader.dll not being found. Can you see if having clmloader.dll in the same directory as your program helps?
Get the x86 clmloader.dll from here:
C:\Program Files (x86)\Autodesk\Autodesk Vault 2017 SDK\bin\x86
Get the x64 clmloader.dll from here:
C:\Program Files (x86)\Autodesk\Autodesk Vault 2017 SDK\bin\x64

The need for clmloader.dll is documented in the help file.
>> >>
Clic Licensing with the Vault SDK
...
New Components
One of the most obvious changes is in inclusion of new DLLs in the SDK. Specifically, clmloader.dll and Autodesk.Connectivity.WebServices.Interop.dll have been introduced. Also, there are x86 and x64 flavors all each of these components, but that is discussed in detail in the section below. Although Vault SDK applications will not have to consume any types or methods from these two new DLLs, they are required by the other SDK components and so they must be deployed alongside the Vault SDK DLLs. For applications that do not deploy the Autodesk.Connectivity.WebServices.dll (extension apps), deploying these components shouldn't be necessary as they should already be loaded by the host application.

<< <<

Thanks,

Wayne

[PetterMoldestad]

Hello.

It was the clmloader.dll file. I had copied to the program folder, but I hadn't included it in the project. When I did, I got it to work both in debug and in finished released program.

[gavbath]

How did you manage to add clmloader.dll as a project reference? I get this message when I try to add it:

[Anonymous]

Hi Gavin.

If you copy clmloader.dll to your programming folder, you will see it in your project. Then you can right click and include it in your project.

Afterwards you must select Copy to Output Directory.

That worked for me.