

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hello,
I have a script alert that is generating a generic error message on one of my SiteScope instances. I use the same alert configuration and script template on two different instances, but this is only occurring on one of them and just for this alert trigger..
The error is: ERROR: , Bad file descriptor (9)
I am unsure how to troubleshoot this one. The script simply sends a template to the OM connector, which as mentioned, works fine on one instance. I use the OM connector for any alerts that need to go to OM so it does work for other alerts, just not this specific one. I use the same alert template on both instances and send the same 4 extra variables (alert::description, etc).
Thanks!
Accepted Solutions


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
This turned out to be some textual data in the script output (the Mainproperties variable) that must have caused some type of exception. So, basically, i had to remove that variable for this to process properly. Something in the text must have been an escape character or something that caused the output to break the script.
This was specifically using the OM/opcMsg method to read a script template file for opcMsg processing..
Anyhow, it's resolved.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi,
Could you please go to the master.config and review if you have the same information in the both instances:
_scriptMonitorExtensions=
_scriptInterpreters=
Regards.


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Those entries do not exist the master.config file for either instance..
Thanks,
Lance


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
This turned out to be some textual data in the script output (the Mainproperties variable) that must have caused some type of exception. So, basically, i had to remove that variable for this to process properly. Something in the text must have been an escape character or something that caused the output to break the script.
This was specifically using the OM/opcMsg method to read a script template file for opcMsg processing..
Anyhow, it's resolved.