We have 2 clients each receiving this error after an 8.5 upgrade from 7.0.x clients. The server/client environment is almost complete to 8.5 but this issue only seemed to appear after upgrading the mail design to the 8.5 template. Any advice or direction toward a root cause would be greatly appreciated.
Not a sub or function name: SIGNERCRYPTPOLICY
Not much on a google search but there was a reference to a corrupt database index. I am planning to run some database utilities on the affected mail files, but was wondering if anyone else has seen this issue and how it was addressed.
Respectfully submitted.
Subject: Open a PMR with support
Can you provide some more details, like when the users get the error, how often, etc?
Try opening a PMR with support if you can’t figure out what the issue is
andy@us.ibm.com
Subject: Most common cause.
Hi,
The most common cause of “Not a sub or function name: …” when upgrading your mail template is not upgrading the folders.
Your created folders create a snapshot of the current folder design and don’t normally get updated when you update the design. So it may reference code that has changed in the design that is no longer there (which is what this error message is telling you).
See the following tech note on upgrading your folder design.
http://www-01.ibm.com/support/docview.wss?uid=swg21291792
Subject: Problem resolved
We had some clients with 3rd party password management software on them. We knew this to be a problem and had pushed a removal of the application via SMS. Apparently, a couple of the clients were missed from this process. After removing the password management software, the clients behaved normally. Thanks for all of the responses.
Subject: replace design
It looks as though the upgraded template did not receive the new script library MiscMailCS, which contains the subroutine SignEncryptPolicy.
When you upgraded, how did you upgrade the mail file? Try running a maual Replace Design on the mail file.
Subject: Fixing errors after upgrade to 8.5
I hit the same problem you did. I fixed it by going into my e-mail, going to the “More” drop down menu, and selecting “Refresh Template Design”.
It took about 5 minutes, but that fixed all the errors I was getting, including the one you posted about. Note - I had to do this twice to eliminate all the errors, but in the end, it worked.
So it appears that your mail template didn’t fully refresh - so hopefully this will fix it.