Multiple SiteMinder Policy Server Processes (smpolicysrv.exe) processes on windows.

Products

• CA Single Sign On Secure Proxy Server (SiteMinder)
• CA Single Sign On SOA Security Manager (SiteMinder)
• CA Single Sign-On

Issue/Introduction

Description:

Customer has several SiteMinder Processes running at the same time on his windows box.

SiteMinder Policy Server log shows multiple policy server processes running:

<- Begin

[8680/8004][Wed Apr 29 2009 14:51:17][SmAuthDsCache.cpp:65][INFO] Flushing user directory cache
[1640/3672][Wed Apr 29 2009 14:51:17][SmAuthDsCache.cpp:65][INFO] Flushing user directory cache
[8232/3584][Wed Apr 29 2009 14:51:17][SmAuthDsCache.cpp:65][INFO] Flushing user directory cache
[8240/8808][Wed Apr 29 2009 14:51:17][SmAuthDsCache.cpp:65][INFO] Flushing user directory cache
[9840/5244][Wed Apr 29 2009 14:51:17][SmAuthDsCache.cpp:65][INFO] Flushing user directory cache
-> End

Task Manager shows the Policy Server processes too:

<Please see attached file for image>

Customer is facing a hang condition and he would like to understand how the policy server got into this state.

Solution:

Memory dump of the process shows several SiteMinder Processes in a funky state:

From Process_list.txt:

<- Begin

0 32 8240 smpolicysrv.exe
Command Line: smpolicysrv.exe -z

0 32 8680 smpolicysrv.exe
Command Line: smpolicysrv.exe -z

0 32 9840 smpolicysrv.exe
Command Line: smpolicysrv.exe -z

0 32 1640 smpolicysrv.exe
Command Line: smpolicysrv.exe -z

0 32 10112 SERVIC~2.EXE Svcs: SmPolicySrv
Command Line: C:\PROGRA~1\NETEGR~1\SITEMI~1\bin\SERVIC~2.EXE

0 32 8232 smpolicysrv.exe
Command Line: smpolicysrv.exe -z

-> End

Memory Dump also shows the hang condition of the policy server and options were used to start the process:

<- Begin

ProcessID: 1640

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [D:\SteveDesk\Cases\18132346 - PGA\Hang_Mode_Date_04-29-2009_Time_15-25-5151\PID-1640_SMPOLICYSRV.EXE_full_2b78_2009-04-29_15-25-55-436_0668.dmp]
User Mini Dump File with Full Memory: Only application data is available

WARNING: Minidump contains unknown stream type 0x13
Comment: 'Full dump in Hang Mode for SMPOLICYSRV.EXE_running_on_PL-SM3'
Symbol search path is: srv*srv*D:\SteveDesk\Cases\18132346 - PGA\sysmbols
Executable search path is:
Windows Server 2003 Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Debug session time: Wed Apr 29 15:25:57.000 2009 (GMT-4)
System Uptime: 73 days 23:06:33.046
Process Uptime: 73 days 23:02:05.000

-> End

The above output shows that the SiteMinder Policy Server was started using Terminal Server. As posted in the SiteMinder Management guide, you should not use or start the SiteMinder Policy Server using Terminal Server, unless access as console over Terminal Services

Snippet of SiteMinder Management Guide:

<- Begin

Note: On Windows, do not run the smpolicysrv commands from a remote desktop or Terminal Services window. The smpolicysrv commands are dependent on an interprocess communication that do not work if you run the smpolicysrv process from a remote desktop or Terminal Services window.

-> End

Environment

Release:
Component: SMPLC