LifeCycle Event Editor not working with Vault 2017

LifeCycle Event Editor not working with Vault 2017

b.graaf
Advocate Advocate
960 Views
4 Replies
Message 1 of 5

LifeCycle Event Editor not working with Vault 2017

b.graaf
Advocate
Advocate

Hello,

 

We have several Windows 10 Workstations with Autodesk Product Design Suites and Vault professional 2017.0.2

There are several jobs which are executed when some specific state changes. To configure this jobs, we always use the LifeCycle Event Editor from the Vault SDK.

 

Unfortunatelly, after migration to 2017, on fresh installed Windows 10 machines, the LifeCycle Event Editor gives an license error (see attachment).

 

This happens on all machines, which are all new installed with the same Windows.

The strange thing is, that the Vault Explorer and Vault inventor addin gets a license with no problem.

 

Does somebody has any idea?

0 Likes
Accepted solutions (2)
961 Views
4 Replies
Replies (4)
Message 2 of 5

wayne.brill
Collaborator
Collaborator

Hi,

 

I am not sure what is wrong. LifecycleEventEditor.exe in this folder is working ok on my Windows 7 System.

C:\Program Files (x86)\Autodesk\Autodesk Vault 2017 SDK\util\LifecycleEventEditor

 

Are you running LifecycleEventEditor.exe in that SDK folder? (with all the other dlls)

 

It would help to know where clmloader.dll is being looked for. You could use a tool like processmonitor to see this when you run LifecycleEventEditor and the error occurs.

http://technet.microsoft.com/en-us/sysinternals/cb56073f-62a3-4ed8-9dd6-40c84cb9e2f5.aspx

 

Thanks,

Wayne

 

 

 

 

 

 



Wayne Brill
Developer Technical Services
Autodesk Developer Network

0 Likes
Message 3 of 5

tolgay.hickiran
Advisor
Advisor
Accepted solution
What is your system language? We have been having big problems with system language and it solves a lot of problems. We are using our windows in Turkish but we had to change the region to en-US just to be able to open Vault Client. After that we had problems with office 2016 addin. We created a folder named tr-TR in CLM and it also solved the problem.

So this might be linked with that.

Some worthwhile ideas
Copy Design should rename ilogic Rules too!
Why Nastran In-CAD doesn't have an SDK?IMPLEMENTED!

Tolgay Hickiran
Founding Partner
SignatureSignature

website
emailskypelinkedinyoutubeemail

0 Likes
Message 4 of 5

b.graaf
Advocate
Advocate
Accepted solution

Thank you both for your replies.

It was indeed in the localization files. I did tried that, but it didn't work in the first place....

 

Turns out, that for this application, you do not need to copy the langauge folder in this location:

C:\Program Files\Common Files\Autodesk Shared\CLM\V3\MSVC14\resources\adlm

 

but in this location instead:

C:\Program Files (x86)\Common Files\Autodesk Shared\CLM\V3\MSVC14\resources\adlm

 

Now it works,

Tnx!

0 Likes
Message 5 of 5

tolgay.hickiran
Advisor
Advisor
Just like i've thought.

We've spent around a month for these issues via phone with support. I think Vault team needs to work on localization in the near future.

Some worthwhile ideas
Copy Design should rename ilogic Rules too!
Why Nastran In-CAD doesn't have an SDK?IMPLEMENTED!

Tolgay Hickiran
Founding Partner
SignatureSignature

website
emailskypelinkedinyoutubeemail

0 Likes