Previous Topic: Troubleshooting the Notification WebsiteNext Topic: Secure the Notification Website


New CA-Supplied NM Policy Definitions Not Included

Symptom:

The Release Notes for this release states that new NM policy definitions were added, but these new policy definitions are not in my NM database.

Solution:

The install program attempts to load any new NM policy additions into the existing NM database during a product upgrade. If the install program cannot load these new definitions, you may need to merge manually these additions into your existing NM database using the following command from a REXX program:

ADDRESS VOX “NMDBMERGE PATH(installDir\sample\nm\nmdbupdates)”

Login Message

Symptom:

I remained logged in to the Notification Website with no activity and was prompted to log back in again. What happened?

Solution:

You are logged out of the Notification Website after 30 minutes of inactivity.

RC=6040 Error

Symptom:

I attempted to update a contact schedule, but after clicking Commit, I received an RC=6040 error stating that the Times key specified does not exist.

Solution:

This situation can occur when multiple users are updating the same contact at the same time. Both users get the same data from the database, but once one user makes changes and commits them to the database, the data on the second user screen is out of date. If the second user commits changes, the updates may be to time blocks that no longer exist. To correct this error, return to the Modify Contact page and reselect the contact you are attempting to update. This obtains the latest information from the database. If there is still a problem at this point, contact your notification administrator.