Wolfgang: try putting Profile 1 back in.

see if the following helps:

open the Services Console (Run: services.msc), then highlight Remote Procedure Call 
(RPC), right-click the service and select Properties.

under the Log On tab, set the account under which the service is executed; which 
should show as enabled for at least one Hardware Profile (Profile 1).
click the Enable button if Profile 1 is shown as Disabled.

under the Recovery tab, for first, second and subsequent failures; select: "Restart 
the Computer" (unless you prefer one of the other choices).

under the General tab, verify that the path to the executable looks like:
C:\WINDOWS\system32\svchost
and the Startup type set to: Automatic
and the Service status set to: Start 

may require a Restart.

let me know if this helps...





On Friday, June 20, 2003 at 8:37 am, Wolfgang Hatscher-Buelk wrote:
>Hello,
>
>I Tryed the described Method, but it don't funczioned. I ran into this Problem by 
>deaktivating the "profile1" in the RPC profile list. This causes that the RPC didn't 
>start because there was not valid profile. This cause that the Propertys can't be 
>changed.
>
>Have anybody another idea for reactivating the RPC Service?
>
>