Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

MBSA 2.0 The operating systems returned error code 1222

0 views
Skip to first unread message

alex

unread,
Aug 7, 2005, 9:01:21 PM8/7/05
to
Hi,

I have Microsoft Windows 2000 5.00.2195 Service Pack 4

2 problems:

1) MBSA 2.0 originally "recognizes" my standalone computer
(connected to Internet over Comcast Cable) but later comes to
an error:

"workgroup\<my computer name> (my IP address)
An unexpected error has occured .
The operating systems returned error code 1222."

I checked 1222 - it means - No Network Connection
(which is false )

Any idea how to fix it ?

2)Windows Genuine Advantage Validation Tool (KB892130)
fails to install:

"Updates were unabled to be successfully installed"
Review Your Installation Results
Windows Genuine Advantage Validation Tool (KB892130)

WindowsUpdate.log (tail of it)
...
2005-08-07 14:33:02 632 480 Agent WARNING: Failed
to evaluate Installed rule, updateId =
{ED300F67-421C-4C08-B3BA-F35C55F3B427}.100, error = 0x80041017
2005-08-07 14:33:21 632 480 Service WARNING:
GetUserTokenFromSessionId failed with hr 0x800706d3
2005-08-07 14:33:21 632 480 Agent * WARNING:
Exit code = 0x80240020
2005-08-07 14:33:21 632 480 Agent *********
2005-08-07 14:33:21 632 480 Agent ** END **
Agent: Installing updates [CallerId = MicrosoftUpdate]
2005-08-07 14:33:21 632 480 Agent *************
2005-08-07 14:33:21 632 480 Agent WARNING: WU
client failed installing updates with error 0x80240020
2005-08-07 14:33:21 712 174 COMAPI >>-- RESUMED
-- COMAPI: Install [ClientId = MicrosoftUpdate]
2005-08-07 14:33:21 712 174 COMAPI - Install call
failed
2005-08-07 14:33:21 712 174 COMAPI - Reboot
required = No
2005-08-07 14:33:21 712 174 COMAPI - WARNING:
Exit code = 0x80240FFF; Call error code = 0x80240020
2005-08-07 14:33:21 712 174 COMAPI ---------
2005-08-07 14:33:21 712 174 COMAPI -- END --
COMAPI: Install [ClientId = MicrosoftUpdate]
2005-08-07 14:33:21 712 174 COMAPI -------------
2005-08-07 14:33:23 712 100 COMAPI WARNING:
Operation failed due to earlier error, hr=80240020

Any take on this one (I am in communicado with Microsoft support on
this but so far without result ...)

Regards,
Alex

pauly [MSFT]

unread,
Aug 9, 2005, 6:52:11 PM8/9/05
to

Hi Alex,

Regarding the failure to install Genuine Advantage and other updates, you
most likely have a problem with Default AccessPermissions for DCOM.

How to test and possobly correct:

1. Check the following registry key to see if you have the
DefaultAccessPermissions value set:

HKLM\Software\Microsoft\OLE

2. If you have the value 'DefaultAccessPermissions' then we need to check
to see what the value translates to the UI for DCOM:

3. On Win2000 launch DCOMCNFG

4. Click on the Default Security Tab

5. Under Default Access Permissions click on Edit

If the list is not blank, then verify that Administrator is in the list.
Add it if necessary.

If the list is blank (the default is blank), then cancel DCOMCFG and remove
the DefaultAccessPermissions value from the registry key above.

Notes: By default on Windows 2000, the DefaultAccessPermissions value does
not exist in the Ole registry key refeenced above. Furthermore, by default
on Windows 2000, the list for DefaultAccessPermissions is blank in the
Dcomcnfg GUI. The owner should list Administrator by default.

What we see when this is broken: We see a blank list in the dcomcnfg GUI
but also see that the registry key value for DefaultAccessPermissions
exists.

Reason why this is a problem: If you have a blank list in dcomcfg GUI for
DefaultAccessPermissions - which by default is correct, but you have a
registry key value for this as well, that corresponds to a setting of
<null> which gives permissions to no account. Under such a setting DCOM is
broken and we see Windows Update failures.

The default on Windows 2000 and Windows Server 2003 is for there to be no
value present in the OLE registry key for DefaultAccessPermissions and for
the DefaultccessPermissions list to bel blak in the DComcnfg GUI.

After making the needed mofifications, reboot and test Windows Update again
.. all should be working correctly.

Let me know how this goes.

Paul Hayes, MCSE
Product Support Services
Microsoft Corporation
pa...@online.microsoft.com

=========

This posting is provided "AS IS" with no warranties, and confers no rights.

Windows XP Security Homepage:
http://www.microsoft.com/windowsxp/security/default.asp

Windows 2000 Security Homepage:
http://www.microsoft.com/windows2000/security/default.asp

Top 10 Windows Newsgroups Security Questions:
http://www.microsoft.com/technet/newsgroups/default.asp?url=/technet/newsgro
ups/nodepages/sectop10.asp

=========

Nelson Araujo [MSFT], CISSP, MCAD

unread,
Aug 16, 2005, 1:42:41 AM8/16/05
to
Alex, this is usually caused by either the Workstation or Server services
not running on the machine. Can you please verify that they are running?
--
Regards,

Nelson Araujo, CISSP, MCAD
Software Development Engineer
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

"alex" <pev...@juno.com> wrote in message
news:1123462881.5...@f14g2000cwb.googlegroups.com...

0 new messages