Hello,
We recently upgraded our assyst production environment to version 11.6.3, and converted off the legacy numbering system. Since the change, our implementation of the assyst Mailbox Reader and our assystETM installation are both creating events which have negative incident_ref values. This did not happen in any of our non-production environments during our testing.
A couple of examples are below:
Has anyone run into this before?
Thanks,
Duncan
Best answer by DuncanK
Update: We were able to resolve this issue.
The cause of the issue was that when we changed the "Use Legacy Event ID Ranges” System Parameter to false during our upgrade, we restarted all of our web server services, but we failed to restart the assystEnterprise services which are running locally on our integration servers. Since our MBR and ETM use local installations of assystREST to log events, they were getting the negative values. I assume this was a feature put in place to ensure there are no conflicts if that parameter is changed but the service was not restarted on one or more servers.
I have confirmed the events are now logging correctly.
Update: We were able to resolve this issue.
The cause of the issue was that when we changed the "Use Legacy Event ID Ranges” System Parameter to false during our upgrade, we restarted all of our web server services, but we failed to restart the assystEnterprise services which are running locally on our integration servers. Since our MBR and ETM use local installations of assystREST to log events, they were getting the negative values. I assume this was a feature put in place to ensure there are no conflicts if that parameter is changed but the service was not restarted on one or more servers.
I have confirmed the events are now logging correctly.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
