Thick Client install errors due to mismatch in CustomMethods dll


 Product(s):APM Implementation and Performance Management
 Version(s):7
 Environment:N/A
 Area:N/A
 Subarea:N/A

Problem Description

User installed a thick client on his work laptop and received an error message when running the client: "The ODBC Dsn APM Dev does not exist. Please create it using the Microsoft ODBC Data Source Administrator and install the package again". Reviewing the DSN showed that there was no issue with accessing the database.  

Solution

When a a thick client is run, not all messages in the error log pertain to the main problem being experienced in launching the client. In this particular case, the user was experiencing a crash which was not being recorded in the log so the user was actually seeing an error message from before the crash. The crash on launch was due to the thick client instance not having a local version of the CustomMethods.dll. When a user has custom code not all of the customization details are stored in the database. Much of the customization data resides in the CustomMethods.dll so when then user launched the thick client it would crash because of the missing file. When a user sets up a thick client, the should first run the Ivara Configuration tool's Test on the instance, in this case the user reran the Test after install and found that their local instance did not have the correct CustomMethods.dll. Using the environment migration wizard, the user was able to package the Custom Methods.dll from the smart client server and then apply the package to his local machine.

See also

https://communities.bentley.com/products/assetwise/asset_performance_management/w/wiki/31692/promoting-customizations-from-one-environment-to-another

https://communities.bentley.com/products/assetwise/asset_performance_management/w/wiki/38961/apm-warns-user-that-custom-dlls-not-in-correct-version-when-trying-to-create-thick-client-shortcut