Custom ScriptsSearch the knowledge base:
Agent running wrong custom script | Rating | Views | |
|---|---|---|---|
|
This commonly happens when the first field of the uptmagent file isn't unique. The first field - the secretpassword - is used as a line identifier to decide which script should be launched.... By: CSS | Date Created: 8-28-2010 | Last Modified: 8-13-2011 | Index: 499 |
 
|
2058 |
Custom monitor not matching correct output | Rating | Views | |
|---|---|---|---|
|
|
When executing your custom script from a windows monitoring station using a ".bat" file you may find that the following items need to be addressed. 1) Ensure you have "echo off" in your bat file.... By: CSS | Date Created: 8-13-2010 | Last Modified: 8-13-2011 | Index: 482 |
|
1602 |
Custom script returns ERR | Rating | Views | |
|---|---|---|---|
|
|
Proper agentcmd.exe usage format: agentcmd.exe -s -p "rexec ... By: CSS | Date Created: 10-10-2009 | Last Modified: 8-10-2011 | Index: 426 |
|
2274 |
erdcloader java exception: Content is not allowed in prolog | Rating | Views | |
|---|---|---|---|
|
|
Problem: - using erdcloader to add a custom script monitor in up.time produces the following java exception: "org.xml.sax.SAXParseException: Content is not allowed in prolog" Reason: - closer... By: CSS | Date Created: 10-10-2009 | Last Modified: 8-13-2011 | Index: 413 |
|
2167 |
Error running Custom Script or Agent-Side Script | Rating | Views | |
|---|---|---|---|
|
|
Symptom: script is unable to successfully pass the value for a variable name. Resolution: try using %UPTIME_VARIABLENAME% (add UPTIME_ in front of the variable name in your XML script). By: CSS | Date Created: 7-12-2011 | Last Modified: 8-11-2011 | Index: 543 |
|
2038 |