| Event Id | 4099 |
| Source | KXRpc |
| Description | Runtime info : (Error : Access is denied. (0x5/5) GetLocalGroups() : NetUserGetLocalGroups on : <server>/<server> failed for <domain>/<server>)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. |
| Event Information | This information from some newsgroups may help you: ------------------------------------------------------------------------------ ScriptLogic now uses a new service called the ScriptLogic Service. This service incorporates the functionality of all the prior version’s services (KiXtart RPC, ScriptLogic RPC and ScriptLogic RunAdmin) into one. Before the new version of ScriptLogic will execute for any users, this new service must be installed and started on the designated domain controllers/servers and the new configuration files must be replicated. The first time Server Manager is loaded, you will be prompted to remove the old services. When you are ready to replicate the new files, allow Server Manger to remove the old services. Once the old services are stopped and removed, the previous version of ScriptLogic will not be fully functional until the new configuration files are replicated. If you choose not to remove the legacy services at this time, you will be prompted each time you go into Server Manager. The legacy service columns in the Server Manager will only be shown if the legacy services are detected. Upon exiting the Server Manager, you will be prompted to replicate the new settings. Once the new service has been installed and started, your configuration files should be replicated. The SLtrace file reports detailed information about a users logon session. This file will include time stamped details about the user, the workstation and the configurations that ScriptLogic (or Desktop Authority) attempted during logon. This can be helpful when trying to pinpoint why settings are not applied or to check the status of client services. When the diagnostic trace file is enabled, an additional diagnostic file named SLexec.log is created in the same location as the trace file. The SLagent.log file provides additional information about the events processed by the ScriptLogic Service. |
| Reference Links | Script Logic forum |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.