more quick actions
minimize quick actions
Hello all,
my customer has its own usermgr.dll, tested on the dev-machine. now in productive environment, the dll can not be loaded.
Error: "The xxx.dll cannot be loaded" ;-).
the difference between dev and prod is: Win7 on dev and Win2008 on prod.
My question is:
1. Does anybody has an idea?
2. Is there a possibility to get more information about the failure? (extended Logs, etc. )
3. What does that error mean in context of LifeCycle, is PcVue not able to load it, or does it crash?
4. Do we have a referent on SV Manger Toolkit ? (no Nico, there isn't one in your post)
5. Which developer to contact? It must run tomorrow midday ;-).
Thank you in advance.
Posted : 06/10/2015 6:36 pm
Ciao Johannes.
I encountered a similar behaviour in the past. In my case it was due to the fact that each PcVue "family" (not exactly build, update or something like that) have its C++ "include" files. So the first thing I suggest you is to recompile your DLL using the "include" file provided with the setup package (development toolkit) from the PcVue version/update/build that the customer is really using on the production environment.
I don't know who is the referent, but for sure the master of SvMgr is Emmanuel Duval.
Hope it helps.
Posted : 06/10/2015 11:29 pm
Hi Johannes
Filippo suggestion is correct. Make sure that:
1 - The dll is compile using the correct include provided on the PcVue version the customer machine runs
2 - Make sure that the DLL is compiled in Release mode and not debug. If compiled in Debug the dll loads on the dev machine but not on the client machine (since it does not have the dev environment installed)
After to reply to your questions
1. and 2. If the DLL does not load that is all you get. Please refer to point 1 and 2 above to hopefully solve the issue.
3. The rule is to always recompile the DLL with the include of the version of the target machine. So it is important to know the exact PcVue version of the target machine.
The message simply say that it does not load the DLL. it should not result in any PcVue crash. if in doubt you can just rename the usrmgr.dat file into usrmgr.sav so that PcVue does not try to load the DLL.
5. Yes we could say I am the referent regarding svmgr. Please note that Raphael has also experience on that.
Bye for now
Manu
Posted : 07/10/2015 12:37 pm
Hello guys,
just to hold you up to date:
the customer claimed, that the DLL was compiled in release mode. We were not able to find a solution at all.
After that I made some tests with the DLL and the result was, that the DLL can be loaded if Visual Studio is installed. So it should be either the debug mode (maybe some references in debug mode) or some references only available with visual studio.
So I passed the investigations to the customer and wait for an answer.
Thank you.
Posted : 09/10/2015 6:06 pm
OK. The customer is strange.
It is up to him to sort this out. We can only give him pointers.
To prove it. You can create a empty svmgr and compile it in debug and you will get the same result.
Posted : 09/10/2015 6:19 pm