it would be a good idea to upgrade to the latest version of portalshield which is mcafee security for microsoft sharepoint (msms)2.5.
that should take care of any portalshield database issues you are having.
if you are not able to do that can you give the build number of portalshield so we know what specific
version you are running?
in the gui main page click on the product information tab and look at the product version information.
From EPO I am seeing 2.0 minor rev. of 273.110. On that one server I cannot even launch the GUI as I get "Either the McAfee PortalShield service is currently not running or you do not have sufficient privileges." Screen only has that plus File and Change Server at the top. Nothing else. When I log into the server even after a fresh reboot says I have one unhandled error for RPCSERV.EXE and then when I try to manually stop and restart the PS services I still cannot get into the GUI. Any thoughts?
you are currently running portalshield 2.01. would you be able to install the latest version of portalshield which is msms 2.5? that should fix your db issue which is preventing you from accessing the db.
My main question however is how something breaks when the configurations have never been changed, and of the seven servers running 2.0.1 I have a single production server that is bombing over and over. It happens immediately at windows startup and throws this event log error but all credentials are identical across the server farm.
it's not the config that is broken. it is the process that postgres is going though to create the db that is causing the issue. as long as postgres doesn't start up properly the gui isn't going to open. the main area where we see problems is with the postgres user account that we create to run the db processes. if it has any admin rights or the password doesn't meet the password policy you have set then it will fail to create/initialize the db. Since the password for the user is randomly generated there is a chance that it creates a password that doesn't meet your policy requirements. This could be why all the other servers are working and this one isn't. while you can change the password of the user manually you are still running on an older version of postgres that has known performance issues.
with the newer version in msms 2.5 we use the system account to run the postgres process instead of a local account. And with the newer version we have not seen any of the performance issues that could occur with the 8.1 version.
So if I change via windows that local account password to test, do I need to make changes elsewhere for that to be known?
in regedit goto hklm\software\wow6432node\mcafee\portalshield\repository\variables
change the dbpassword value to match what you reset the password to. then restart portalshield