Quantcast
Channel: VMware Communities : Popular Discussions - VMware Server Archives
Viewing all articles
Browse latest Browse all 69891

Event log errors on Win2k3 SP1 Host OS installing GSX Server 3.2.1

$
0
0

Has anyone seen these event log errors after installing GSX Server on a fresh install of Win2k3 Serv EE SP1.

 

Source: Dcom

Event:   (10016)

 

Discription: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

\{BA126AD1-2166-11D1-B1D0-00805FC1270E}

to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20).  This security permission can be modified using the Component Services administrative tool.

 

The link says to edit the registry for the GUID in the error. But the specific key to be editied does not exist, which is

   - HKCR\Clsid\clsid value\localserver32

the localserver32 does not exsist.

 

User Action

Verify that the user has the appropriate permissions to start the DCOM server.

 

To assign permissions

 

    1 Using Regedit, navigate to the following registry value

       HKCR\Clsid\clsid value\localserver32[/b]

       The clsid value is the information displayed in the message.

    2 In the right pane, double-click Default. The Edit String dialog box

       is displayed. Leave this dialog box open.

    3 Click Start, and then click Control Panel.

    4 Double-click Administrative Tools, and then double-click Component

       Services.

    5 In the Component Services snap-in, expand Computers, expand My

       Computer, and double-click DCOM Config.

    6 In the right pane, locate the program by using its friendly name.

    7 Right-click the program name, and then select Properties. 

    8 On the Security tab, in the Launch and Activation Permissions group

       box, select Customize, and then click Edit.

 

Or does this error really mean anything

 

this event error is followed by five W32Time errors Event IDs (29)

one error Server, Event ID (2504) and two more W32Time errors same ID (29).

 

I also noticed while looking in the registry for the key. that there are 18 other GIUD entries following the one in the Event log error, all with the first 7 characters the same and the 8th incrementing by 1. ALL WITH NOT OTHER KEYS - which is not like any other - CLSiD entry...

 

Can someone look at those registry keys to see what they have for subkeys

starting with -

\{BA126AD1-2166-11D1-B1D0-00805FC1270E}

to

\{BA126AE5-2166-11D1-B1D0-00805FC1270E}


Viewing all articles
Browse latest Browse all 69891

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>