Thursday, December 10, 2009

ST-SnTT - The dreaded STPOLICY.EXE Error

Attention bleeding edge people, this is for you most likely.

Sametime 8.0.2 as we all know is NOT certified to run on Domino 8.5 or 8.5.1.

But as we also know, it does work.
(these are Windows servers I had problems with and I am ONLY discussing Windows 2003 server)

However some details must be known to get this to work correctly.

First, Install Domino 8.0.2, then Sametime 8.0.2.
Once all of that is okay, then upgrade Domino to 8.5 or 8.5.1.

Sametime will NOT install over Domino 8.5/8.5.1 so don't waste your time.

Great? All good? no

You may start to see this error(100's of times!?) in your server console and logs:

12/10/2009 07:35:33 AM Process C:\Program Files\IBM\Lotus\Domino\stpolicy.exe (6968/0x1B38) has terminated abnormally

This has plagued me before and I have fixed it. But as some asked me about it here are some more details.

A hint to fixing this came from IBM Technote # 1279888

It outlines how to fix this by stating:
The following JVM argument should be provided under the [Policy] section of sametime.ini file:

POLICY_VM_ARGS=-Xmx128m -Xms128m -Xgcpolicy:optavgpause

Possible workaround:
1. Shut down the Domino/Sametime server by executing the quit command.
2. Using Task manager, if nnotesmm.exe still exists, terminate it.
3. Delete pid.nbf from the data directory
4. Restart the server.

Great, why didn't I just use this after all its from ST 7.5?
Because the policy line is already in my servers!
If it isn't in yours, do this first, then do the next steps.

You see, I had fixed this earlier as I see the line in my sametime.ini.

BUT now we have one more thing to do, with a few steps to it.

1) Shut down the Domino/Sametime server.
2) Check all the Sametime and Lotus Domino services have stopped
3) Open the Services running on the server and tell the Lotus Domino Diagnostics to stop running
4) Run NSD -kill on it if services are still running or server looks like it is not completing the tasks

Keep in mind, if you have not updated the Java code on the machine lately, do this as well, get it at

And if there are OS updates now is as good as time as any to add them, after all the server is down anyway.

Then bring the Domino server back up and all is well.

While I can not substantiate this yet, I believe that Microsoft and/or other updates, perhaps even Java which get pushed down without one's intervention may be causing the server to restart without waiting for all the Sameitme services to fully complete shut down. Which could explain why this error just "pops up".

EDITED 12/22/2009: If you still get the stpolicy error, try adding this to the end of the sametime.ini line above so after "optavgpause" add -Xrs with a space after pause. This shortens the java cycle to clean up.