Problem:
- Product Name: VisiBroker
- Product Version: 6.0
- Product Component: Notification Service (VisiNotify)
- Platform: Solaris 8
When they try to start VisiNotify by running "visinotify", a message "unknown exception" is printed out and the process exits.
The osagent has already running on the same machine. PATH, LD_LIBRARY_PATH, BES_LIC_DIR, VBROKER_ADM, OSAGENT_PORT are all set properly.
What could be the reason?
Resolution:
The user who starts VisiNotify have no write access on the current directory.
Change the write access and you should be getting the "visinotify" running. The message error should output something more meaningful rather than "unknown exception".
#notificationservice
#VisiNotify
#unknown
#Security
#VisiBroker
