Service Desk Practitioners Forum

OVSD5.0> is work banner?

Super Contributor.

OVSD5.0> is work banner?

banner is not work..


but not working..

Acclaimed Contributor.

Re: OVSD5.0> is work banner?


You should replace the / with \ unless you are using Unix.
Try placing the
%OvInstallDir%/bin/OvSdBanner.bat between " because there are spaces in the path.

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Super Contributor.

Re: OVSD5.0> is work banner?

OK.. thanks.

I changed configuration follow..


follow log is ok.. but banner is not working.

2006. 2. 13. FM 5:21:21;4879;19;com.hp.ov.obs;information;: Rule Executing: banner test, item: 00000000-0000-0000-02e9-a89ca8dc97ba.
2006. 2. 13. FM 5:21:21;4880;19;com.hp.ov.obs;information;Dispatching action. Rule: banner test, Action: banner (command execute action) host: 10.x.x.x command: "C:\Program Files\HP OpenView\bin\OvSdBanner.bat" test description
Super Contributor.

Re: OVSD5.0> is work banner?

Maybe Known Problem... follow

284029 - Agent does not show banner

Agent does not show banner

How to reproduce:

1 OV Configuration> Actions & Rules> Rules> database Rules> Incident

2 Create a new database rule:

3 When Incident is create or modified, click Next

4 Click Condition, click New criterion

5 Select Field Description, Operator 'contains (AND)', Value 'agenttest'

6 Click OK, OK, Next

7 Click New> Command Exec action. Set Name 'agenttest', set Command line to "%OvInstallDir%/bin/OvSdBanner.bat" (including the quotes)

Note: if 284028 is solved, command line should be "%OvInstallDir%bin/OvSdBanner.bat"

8 Next to 'Parameters' click 'Insert Attribute' and select Description

9 Click OK, Next

10 Set Name to 'agenttest' and click Finish

11 Click on workspace Incident (in the Service Desk group) and press ctrl+N. This should open up a new Incident form

12 Fill in Description and set it to 'agenttest'

13 Save&Close the Incident.

Expected results:

· Banner shows.

· If the banner cannot be shown, the agent should report a warning, or better: queue the execution of the action until a user logs on and the banner can be shown.

Actual results:

Banner does not show, banner process is hanging in the background.

Log-file from server:

Aug 15, 2005 7:31:04


Rule "agenttest", item: 190737533980939914 condition: Description (*) contains agenttest (value: agenttest): true

Aug 15, 2005 7:31:04 PM;76;19;com.hp.ov.obs;INFO;: Rule

Executing: agenttest, item: 00000000-0000-0000-02a5-a2c6ce44968a.

Aug 15, 2005 7:31:04 PM;77;19;com.hp.ov.obs;INFO;Dispatching action. Rule:

agenttest, Action: agenttest (Command Exec Action) host: fcstevel command:

"C:/Program Files/HP OpenView/bin/OvSdBanner.bat" agenttest

Log-file from agent:

Aug 15, 2005 7:31:06

PM;0;10;com.hp.ov.xpl.log.OvLogConfig;;com.hp.ov;INFO;Logging system is


Aug 15, 2005 7:31:07 PM;1;10;com.hp.ov.obs;INFO;Starting class from C:\Program Files\HP


Aug 15, 2005 7:31:07 PM;2;10;com.hp.ov.obs;INFO;Arguments passed to main:


So everything looks OK, but the banner does not show!

A javaw process is started that users can only close with the task manager. This kind of behavior can consume all memory on a Client PC.

Super Contributor.

Re: OVSD5.0> is work banner?