An error while saving assembly file

Submitted by Praveenkumarkn on Sun, 07/24/2016 - 21:12
Forums: 
General Discussion

Hello All,

I recently facing an issue in NX, if I try to save any of the assembly it gives an error message

"Failed to load image
File name :\\..server path...\Drafting_Attributes_UserExit.dll
Function Name : ufput"

and if I click on OK, the process continues. But I am getting this warning/error message as soon as I hit the save button.

Please let me know if it is related to userexit.dll file ?
Will it be possible to find out the root cause for this issue ?
And also if possible solution for this issue.

Thank you very much

Best Regards,
Praveen

NXJournaling - Mon, 07/25/2016 - 06:02

Have you written custom code to run when the part is saved? If so, you may need to update the code to resolve an error.

The first thing to do is look at your log file for any clues as to what is going wrong. The log file can be found at menu -> help -> log file. The log file records everything that happens during your NX session. Right after you get the error, open the log file and scroll to the bottom (the latest events are at the end of the file).

Praveenkumarkn - Mon, 07/25/2016 - 21:27

Thank you for the reply

Yes there is custom code written for save due to integration with PDMLink (Windchill PDM), this kind of error happens only when PDMLink is integrated to NX but not when NX is run without integrating to PDMLink.
Earlier we were not facing this issue, recently we have been upgraded our PDMLink to the latest patch, Since then we are getting an error as specified.

I checked the log, but it only refers to the lines what I mentioned previously.
&MACRO MESSAGE_BOX -2 Failed to load image - see log file for details
&MACRO MESSAGE_TEXT
&MACRO MESSAGE_TEXT File name: \\ server path \Drafting_Attributes_UserExit.dll
&MACRO MESSAGE_TEXT
&MACRO MESSAGE_TEXT Function name: ufput

NXJournaling - Tue, 07/26/2016 - 06:09

A few ideas:

Have you recently upgraded NX or PDMLink (new version or patch)? If so, the custom code likely needs to be re-compiled for the new version.

Is the custom dll file in the appropriate NX "startup" or "application" folder? Most custom code that runs at a user exit is kept in one of these locations so that NX can load it when NX initializes.

Did you develop this custom code? If not, contact the developer for an update.

Praveenkumarkn - Sun, 08/21/2016 - 22:42

Yes, we have recently upgraded the PDMlink Patch, since then it is not working as expected.
Our developer has an idea about these codes, I was in touch with them for these long days and they have come up with the fix for the issue.

The custom code runs in our Master server, and then Robo copied to the local servers.

Thank you very much for your kind advice and help.