Autodesk Vault Pro Failed to acquire a license

[Anonymous]

Good Afternoon,

I'm trying to set up an Autodesk Vault Professionnal 2013 server (for third party development purpose) and I didn't succede to resolve the "Failed to acquire a license" issue.

I did set up the FLEXnet service, and when I check server status via "Perform Status Enquiry" I get the following message :

Status
--------
Flexible License Manager status on Wed 3/27/2013 14:56

[Detecting lmgrd processes...]
License server status: [email protected]
    License file(s) on 10.180.105.43: C:\Program Files\Autodesk Network License Manager\License\VLTM2013enlicense.lic:

10.180.105.43: license server UP (MASTER) v11.10

Vendor daemon status (on 10.180.105.43):

  adskflex: UP v11.10
Feature usage info:

Users of 85987VLTM_2013_0P:  (Total of 5 licenses issued;  Total of 0 licenses in use)

Witch seems to be all ok.

I turned off both server and client Firewalls (so it's not a blocked port issue).

According to this page : http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=13107015&linkID=9261340
 I have also disabled IPv6 (its a Windows XP x64 Workstation) and rebooted it.

I also changed the hostname for the IP adress in the %Program Files%\Autodesk\ADMS Professional 2013\LICPATH.LIC file, and as it wasn't still working, I changed it also in the %Program Files%\Autodesk Network License Manager\License\VLTM2013enlicense.lic license file.

The only thing I might have done that isn't usual, is that the Autodesk Network License Manager is installed on the C: drive, when the Vault is installed on the E: drive. But as it seems to communicate through services, I don't think that configuration have any impact, do it ?

Do someone have an idea to resolve my issue ?

Also, do someone have a list of services that have to be started for the vault to be up and running ? I noticed that "FLEXnet Licensing Service" was always stopped, and when I start it and then fail to connect to the vault, the service is again stopped, is it normal ?

Thanks in advance for any help,

NC

[minkd]

An error should be reported in the vault server log (aka vlog) at the same time as you tried to login.

Can you post those error details?

Also, in the same folder as where the vlog resides, there should be a file called "licensingLog.txt" which may have additional information about the failure to acquire a license.

-Dave

[Anonymous]

Sure, here is the vault server log :

28/03/2013 4:06:30 PM *******************************************************************
Error: Soap Exception ( mesg-id = 635000835907482472 )
Exception: LicensingError [319] (20)
Stacktrace: 
Server stack trace: 
   at Connectivity.Core.Security.Licensing.LicenseCheckOut(User user, ProductLicenseType productType)
   at Connectivity.Core.Services.SecurityService.CreateLicensedToken(User user, String knowledgeVaultName, Boolean readOnly, ProductLicenseType licType, Byte[] p)
   at Connectivity.Core.Services.SecurityService.SignIn(String userName, String userPassword, String knowledgeVaultName, Boolean readOnly)
   at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Connectivity.Core.Services.SecurityService.SignIn(String userName, String userPassword, String knowledgeVaultName, Boolean readOnly)
   at Connectivity.Web.Services.v17.SecurityService.SignIn(String userName, String userPassword, String knowledgeVault)

 And the Licensing log :.

5456	2013/03/28	16:06:30	Reason=Fatal error
5456	2013/03/28	16:06:30	ComputerName=LIPPS-034940
5456	2013/03/28	16:06:30	OS=5.2.3790.Service Pack 2
5456	2013/03/28	16:06:30	File=AdlmIntNWFBLicense.cpp,Line=769
5456	2013/03/28	16:06:30	VendorID=3 [FLEXLM-NW]
5456	2013/03/28	16:06:30	VendorError=-5 [No such feature exists]
5456	2013/03/28	16:06:30	FLEXLM-NW=v11.10.0.0 build 95001 x64_n6
5456	2013/03/28	16:06:30	Reason=Fatal error
5456	2013/03/28	16:06:30	ComputerName=LIPPS-034940
5456	2013/03/28	16:06:30	OS=5.2.3790.Service Pack 2
5456	2013/03/28	16:06:30	File=AdlmIntNWFBLicense.cpp,Line=752
5456	2013/03/28	16:06:30	AdlmIntError=20 [License check out failed]

[DarrenP]

can you ping the license server by hostname from the vault client machine?

are the license manger and the ADMS console on the same machine?

[Anonymous]

I can ping the server from the client, and I have installed the license manager on the same machine than Autodesk Vault, but not on the same drive (license on C:, ADMS on E:, both local disks).

[DarrenP]

you can try modifying the windows hosts file as per the below thread

http://forums.autodesk.com/t5/Installation-Licensing/Network-License-Error-1-5-15-and-IPv6/td-p/2982...

[minkd · Accepted solution]

I didn't notice this before, but your license file contains "Pre-Release" licenses:

    Users of 85987VLTM_2013_0P:  (Total of 5 licenses issued;  Total of 0 licenses in use)

The "0P" indicates "Pre-Release", which is typically used for betas; although the Vault Pro 2013 beta did not require licensing at all.

If you are using the 2013 RTM, you need FCS licenses (they will have a "0F" suffix).

-Dave

[Anonymous]

Oh. I'm a ADN member and I asked for those licenses through this procedure http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=18275350&linkID=9240617 with our "ADN membership CAD and Geospatial Serial Number".

Do I have chosen the wrong product in the procedure (I would say no, but I'm not sure now) ? Or is it another procedure to retrieve those licenses for ADN developers ?

[minkd]

I'm not familiar with ADN related processes, but ADN is a support organization; so you should be able to open a support case so you can get FCS licenses instead of Pre-Release.  Both license-types allow for NFR licenses, which I assume is what you end up with.

-Dave

[Anonymous · Accepted solution]

Getting the corresponding licenses solved my issues.

Thanks for your help !

[Anonymous]

Hello, I recently ran into the same problem, but with NFR (0F) license. After some investigation, it turned out that our company network is an IPv4/IPv6 hybrid, and the installed license manager is an IPv4 only. After downloading and installing the IPv6 NLM from here our problem has been solved.