Monitor Token values which include double quotes causes VBScript tasks to fail
| Article:TECH154599 | | | Created: 2011-03-02 | | | Updated: 2011-03-30 | | | Article URL http://www.symantec.com/docs/TECH154599 |
| NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made. |
Problem
A customer has a VB Script Client side task associated with a Rule. The issue is that the output from a token produces double-quotes and is causing that VBscript based task to fail.
Error
VBScript fails to run. Script syntax error generated.
Environment
Monitor Solution for Servers 7.1
Monitor Pack for Servers 7.1
Cause
The problem is that the quotes are not escaped. Vbscript will not allow you to process this in any away since the script already exists with the “bad” string in it.
Solution
A Solution to this issue is to use Javascript, since javascript allows you to use single quotes for a literal. As an example, you can have something such as ‘Name="SysmonLog": SysmonLog’.
|
|
Article URL http://www.symantec.com/docs/TECH154599
Terms of use for this information are found in Legal Notices
Thank you.