I am quite tired, what a day. I was overwhelmed by support requests ranging from how to setup a detail view leader, to a model with a “wrong” cutlist quantity, but it had the same body modeled in 3 different places with slightly different dimensions and they were deliberately removed from the bom…all while all my scripts broke down badly with 24h2 as a big wave of new pcs was delivered.
long story short.
clean sw install, i updated some addin i install together with sw admin image.
the addin startup checks do not stay checked and the addin fails to load.
if I install an old version it works and upgrading that old version with the same files I use with the admin image it works.
I am too tired and it is already laye for dinner. Looking for ideas. tomorrow log files analysis
2 Likes
We had another issue with our VAR addin and our VAR is suggesting us to reboot the pdm server.
Object reference not set to an instance of an object
this message is coming out on some machines. win10 and win11.
Some PCs worked flawlessy some cannot use this addin even if the CAF file is copied and extracted correctly from the archive server
Best guess: there’s a file or folder that is being requested by the add-in, but some machines don’t have it. The code isn’t checking for this and null is being returned.
1 Like
do you think process monitor could catch it?
I’ve never used PM to debug an add-in since I wrote all of them myself and have the Visual Studio debugger. Any chance you can upload the CAF? Or even the DLL if there are multiple and you know which one is having the issue.
DLL for PDM server addin installation
EPDM.rar (738.8 KB)
Is the icon in the error dialog a white X in a circle with a red background? This helps narrow down which MessageBox call is happening.
As a follow up, I was able to solve yhe issue with @JimSculley help.
I debugged a bit the addin dll and I discovered it was scraping the registry for a certain key of all the past SW versions. This triggered
an exception when an already unistalled SW version left some incomplete keys behind in the registry.
Forwarded the issue to developers and fixed with a script cleaning the registry during deployment.