I recently upgraded from Vault Pro 2015 to Vault Pro 2015 R2. I can log in with the thin client. I am unable to obtain a license with any thick client from 2013 to 2015 R2. I've read in another post that there is a configuration error in the license manger if no license can be obtained. I've gone step-by-step through the license manager help/setup and still am unable to obtain a license from a thick client. Any suggestions?
Solved! Go to Solution.
Solved by minkd. Go to Solution.
What error do you see in the AVFS-log when you try to login from the thick client?
-Dave
It looks like error 319. Is it possible I didn't give a license server prior to the upgrade/installation? While still in server 2015 R1, I had no issues with licensing. If I didn't set the license server, what is required to set it now?
9/9/2014 1:41:22 PM *******************************************************************
Error: Soap Exception ( mesg-id = 635458668828016118 )
Exception: LicensingError [319] (20)
Stacktrace: at Connectivity.Filestore.Licensing.LicenseCheckOut(Int64 userId, String username, Byte[] p)
at Connectivity.Filestore.AuthenticationService.CreateSession(AuthCredentials creds, String dataServer, String knowledgeVault, Boolean isLicensed, Byte[] p)
at Connectivity.Web.Filestore.v19.AuthService.SignInAltLicense(String dataServer, String userName, String userPassword, String knowledgeVault, Byte[] p)
at SyncInvokeSignInAltLicense(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
In the install directory, there is a file called LICPATH.lic which should look something like:
SERVER license_manager_hostname 000000000000
USE_SERVER
Change "license_manager_hostname" to the name of the host where the license manager is running.
-Dave
You are the man! It was pointing to the wrong server. I must have fat fingered it.
Thank you,
Eric....