Is there anything that can short-circuit the Custom Module initialization? Or a way to for ProjectWise to verify it is executing those steps? We have a set of customizations with a well-defined installation procedure that has worked well for years now, but they will not load on one user's machine. The registry settings have been verified. The DLL is in PWBIN. There's no obvious reason why they're not loading, but they're not.
The issue is consistent for multiple users on the same machine, so I don't think it's the user's profile.
Just wondering if anyone has a trick to track this down.
Carl, not much detail to go on. What OS is this on, what version of ProjectWise, etc.
If the problem is isolated to one machine, then the obvious question is what is different between that machine and the ones that work OK?
One thing to check is to see if the troublesome machine has different versions for any dependencies for the customizations. ProjectWise Explorer, as you know, looks in the registry for "matching" modules to load at startup but will unload them if anything fails, including if the custom module itself can't load, which could happen for a number of reasons, most of which you probably have already checked (security, path, etc.).
Yes, unfortunately, ProjectWise Explorer will continue on if a custom module fails to load without any indication that something went wrong.
You might consider installing your development environment onto the troublesome machine and compile the code and run it in the debugger to see if you can see if your custom initialization function is even being called, and if it is walking through that function might give you a hint of what the underlying problem is. Personally, I would first check to see what's different as far as dependencies.
Another approach might be to create a simple customization, perhaps one that just opens a "Hello" dialog message box from your initialization function, and see if that works on the troublesome box or not. That might give you a clue as well since such a customization would only have dependencies that match what ProjectWise Explorer would have. If that doesn't work, recheck the registry entries, perhaps a different "bitness" on this machine and the registry entries are in the wrong hive or key in the registry?
Dan, thanks for the response. I did try a different "Hello World" type custom module with the same result. It works everywhere else but this one machine. The custom module at issue has no dependencies at startup either and we've never had an issue pushing it out with only the one DLL and setting the registry; all of which I've verified, of course. I was hoping maybe there might be known issue that was known to short-circuit the modules loading (Windows 10 and PWE 10.0.3.167, btw) that we could look for, but wasn't expecting we'd get that lucky.
Have you tried uninstalling, rebooting, and then re-installing ProjectWise on the troublesome machine? If the same customization and configuration works on all other machines (same OS, same "bitness", same versions of OS, ProjectWise, dependencies), then perhaps it is the installation of ProjectWise (or some other dependency) on the troublesome machine that is the root cause of the problem.