Script Monitor Errors When String “not found” Is Parsed

When running a script on any OS environment, the tool and monitor both fail to execute the script when the output contains the string: "not found". However if the output contains: "Not found", SiteScope doesn’t fail.

The script can be manually executed without a problem and the output is being printed successfully. Why is SiteScope is failing to execute with: "not found"?

By default, SiteScope searches for certain common error strings to indicate a problem running the script. The default settings can be found in the <SS>groupsmaster.config file under the following parameters:

_scriptMonitorErrorMsgs=not found,Not Found,denied,Denied,cannot execute,such file or directory

_scriptMonitorErrorMsgs2=Failed to .* Error code:

If a script will execute correctly but report any of the above default strings, then the parameters need to be modified when the SiteScope service is stopped. Simply remove the problematic string and modify the entry in this case to:

_scriptMonitorErrorMsgs=Not Found,denied,Denied,cannot execute,such file or directory

_scriptMonitorErrorMsgs2=Failed to .* Error code:

Additionally, if there are particular script error codes specific to a script that should indicate an error, that string can be added to the above parameters so that SiteScope will error when they are parsed.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s