Discussion moved from Community Interface Help to Security for Microsoft Sharepoint (PortalShield)
When I see this it usually that psPickerx64Srv process is trying to run with account with insuffient privileges to allow the process to launch or there are multiple ones listed in task manager (not closed during an upgrade possibly)
You could try something like this - use the farm admin as a test - this can be changed at any time and there is a section in the guide to assist in creating an account with least privileges required (appendix A) .... but give this a go ..
In Services applet - stop the McAfee Portalshield service.
Access task manager and ensure all our processes have left task manager. These are:-
Safeservice.exe, RPCServ.exe (2), several Postgres.exe processes and PSPickerx64Srv.exe.
(Kill any of these processes that remain).
Run Cmd prompt with fulll admin account - Right click CMD Icon and select "Run with Administrator" if User Access Control in enabled in Windows
In this cmd prompt window cd to <msms install folder>bin and run setsqlact.exe as follows
SetSqlAct.exe /USER=SPFarmAdmin /PASSWORD=ThePassword! /DOMAIN=SPDomain.
(Obviously substitute the correct entries for your Domain\SPFarmadmin and password)
It should state the user credentials have successfully been changed once done.
Now start the McAfee Portalshield Service again.
- OAS should show enabled
- Test OD Scan config - you should be able to select "Scan Selected Folder" and expand Workspaces.
(This will be blank if wrong account is used)
Check Task Manager
Safeservice.exe, RPCServ.exe (2), several Postgres.exe processes should all be loaded under system account
PSPickerx64Srv.exe - should be loaded under your SPFarmAdmin account.
As stated you can change the account at any time with SetSQLAct - but - that account must have sufficient privileges as per details in Guide.