Re: Event viewer Account specified is different" errors


Wesley Vogel wrote:
SSDP Discovery Service is only needed for WMP if you have some sort of
Portable Media Device.

Open Services...
Start | Run | Type: services.msc | Click OK |
Scroll down to and double click: SSDP Discovery Service |
On the Log On tab, Local System account should be selected |
Allow service to interact with desktop should NOT be selected

Allow service to interact with desktop
[[Specifies whether the service provides a user interface on a desktop that
can be used by whomever is logged on when the service is started. This
option is available only if the service is running as a LocalSystem
account.]]

SSDPSRV should be started by LocalService.

The Local System account is a predefined local account that can start a
service and provide the security context for that service. The actual name
of the account is NT AUTHORITY\System.

The Local Service account is a special built-in account that has reduced
privileges similar to an authenticated local user account. The actual name
of the account is NT AUTHORITY\LocalService.

SSDP Discovery Service = SSDPSRV

To display the WIN32_EXIT_CODE error that SCM encountered when trying to
start the program, at the command prompt, type:

sc query ssdpsrv

See this...

ID: 7000
Source: Service Control Manager
http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.2&EvtID=7000&EvtSrc=Service%20Control%20Manager&LCID=1033

--
Hope this helps. Let us know.

Wes


Thank you for the prompt help.

I recently bought a Philips SA1105 "digital audio player", but have
seen that SSDP Discovery is not needed for using it. I have disabled
the SSDPD again.

However, I continued to see several other services giving the same
("The account specified for this service is different from the
account specified for other services running in the same process")
message on the Event Viewer: Following up the lead given by you, I
changed the account of the 'erring' services. I am the only user of
the computer, and so have only two accounts, Administrator and
"_Myself_", and no password for _Myself_. Therefore, I deleted the
"password" for "NT AUTHORITY\LocalService" and left it blank.
Now *no more errors* of wrong account!
However, there were repetitive and different complaints about DCOM,
MSDTC, etc., which too I **seem to have** got rid of by disabling
MSDTC, enabling DCOM, and so on. The annoying red blotches in Event
Viewer have now disappeared, but I get a feeling a number of unwanted
services may be running on the computer.
Where can a non-expert like me get advice on configuring the Services
-- including the CHOICE OF ACCOUNT -- for one's specific needs? I
simply don't like to do it by trial-and-error.
Thanks again.

.

Relevant Pages

  • Re: Event viewer Account specified is different" errors
    ... Scroll down to and double click: SSDP Discovery Service | ... Local System account should be selected | ... [[Specifies whether the service provides a user interface on a desktop that ...
    (microsoft.public.windowsxp.general)
  • Re: Changing the log on for the RPC service.
    ... My Remote Procedure Call (RPC) Properties, Log On tab page is all grayed out ... from the This Account tick mark to the Local System account tick mark. ... account, and allows me to switch to Local System account, but not back. ... rpcss = "RpcSs" the Remote Procedure Call ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Impersonating Users
    ... running the service as Local System Account, ... //Logon to user acount and Impersonate. ... confers no rights. ... >> service as Local System Account, ...
    (microsoft.public.platformsdk.security)
  • Re: c# widows services...
    ... remote WMI services when connecting from a process that runs as a local ... | Local System account. ... | to access network resources. ... | Another major difference when running under the Local System account is ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: security and service start up account
    ... is that the local system account can't access the ... > You should consider using a local account with just enough rights to run ... > Microsoft SQL Server Support ... > Protection Program and to order your FREE Security Tool Kit, ...
    (microsoft.public.sqlserver.security)
Loading