This document describes a situation in which the creation of an infinite event causes a malfunction with the Macro Component and the Schedule Database.
An already running installation of ROSA NMS 4.9 had its Macro Component and Schedule Database malfunction after an event was defined as infinite.
The Macro Component did not load the configuration and it did not initialize correctly. The application got stuck and the only way to close it was to terminate the process with the Windows Task Administrator.
There are no specific requirements for this document.
The information in this document is based on ROSA NMS 4.9. The problem was not reported on other instalations and it was not reproducible in the lab installation.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
A ROSA NMS 4.9 installation had it's Macro Component and Schedule Database malfunction after a NOC operator created an event defined as infinite. The forementioned components displayed a stalled window with no possibility to navigate through the tabs. The only way to close the window was to forcefully terminate the process with the use of the Windows Task Manager:
No error messages or alarms were displayed.
Problem replication in the lab was unsuccessful as the Macro component worked fine after the creation of an infinite event.
To fix this issue the Macro Schedules had to be removed and recreated.
Steps needed to perform the removal of Macro Schedules:
1. Take backup of ROSA NMS server (run the Server Backup Component). 2. Stop ROSA NMS Server. 3. Search and delete MacroSchedules.bin in Copernicus/resources directory. 4. Start ROSA NMS Server.
At the time of troubleshoot, there were no log entries to signalize the problem.
Other things that must be checked before you attempt the fix:
1. Time synchronization for the windows machine.
2. Windows logs only display the forced close action when the GUI crashes.
3. Windows had the firewall on but when you disabled it, it did not have any effects.
4. The Account used on the client was Administrator.