RE: The COM+ Event System detected an inconsistency in its internal state

Hello Alex,

Thank you for posting here.

According to your description, I understand that you need to log on XP
client twice and get error 4614. If I have misunderstood the problem,
please don't hesitate to let me know.

Based on my research, I suggest we try the following steps to see if we can
resolve this issue:

Step I: Logon with another Domain User Account.

Use another domain user account to logon this computer, if it works, then
maybe the profile of the user account which experience this issue was
corrupted. There is a workaround to repair the user account, but sometimes
this workaround may not work and it will change the user account into its
default settings. Please perform the following steps to repair the user
account:

Step II: Repair the User Account.

1. Log on into Windows XP with the account which can log on successfully.

Note: This account must have domain administrator permission.

2. Open My Computer, click Tools->Folder Options and select the View tab.

3. Under the "Hidden files and folders" item, clear the check box "Show
hidden files and folders".

4. Clear the check box "Hide extensions for known file types".

5. Copy the file NTUSER.DAT from C:\Documents and Settings\default user\ to
C:\Documents and Settings\xxxxx. Here xxxxx represents the user account
which experiences the issue. This action will overwrite the corrupted
NTUSER.DAT of the user account.

6. Log off and then use the original account to log on.

How to copy data from a corrupted user profile to a new profile
http://support.microsoft.com/default.aspx?scid=kb;en-us;811151

If logon with another domain user account failed, please perform following
steps to confirm weather this computer itself or a network related issue
caused this log on problem.

Step III: Logon with a Local User Account.

1. Start the computer.
2. When you are prompted to input logon username and password, type
"administrator" (without quotation marks) as the username, and type its
password, and then select "xxxx (this computer)" in the "Log on to" drop
down list ("xxxx" is your computer name), and then click OK.

Note: 1. The user "administrator" is a local user, and its password was
created during the installation of Windows XP Profession.
2. If you have other local user accounts in this computer, use them
to logon as well.

Does the administrator can logon normally? If it works, this issue may be
caused by some network connection problem, I suggest you to check if there
is anything wrong with the network connection of this computer.

Step IV: If you enable XP Fast Logon feature, please try to disable it for
test:

Description of the Windows XP Professional Fast Logon Optimization feature
http://support.microsoft.com/default.aspx?scid=kb;en-us;305293

Step V: To isolate the issue from 3rd-party software, please do clean boot
on client and SBS same time, then test this issue:

To clean boot the problematic computer, please use the steps below:
a. Click Start, click Run, and then in the Open box, type "MSCONFIG"
(without the quotation marks). Click OK.

b. In the System Configuration Utility (MSConfig) window, click to select
the Selective Startup button.

c. Click to clear the check mark from the "Load startup items" below
Selective Startup.

d. Click the Services tab, click to check the "Hide All Microsoft Services"
box, and remove all the check marks from the remained Non-Microsoft
Services. Please note that the Exchange services could be marked as
non-Microsoft. Please do not disable those services.

e. Click OK to close the MSConfig window. Click Yes when you are asked to
restart your computer in order to enable the changes.

f. After restarting, please check whether this issue will reoccur.

g. If there are no more problems, please use the above steps to enable
services and startup items one by one in order to figure out the root cause
of this issue.

If we can not resolve the issue after we perform the above steps, please
kindly help me collect some information for further investigation:

1. Does this issue happen on SBS?

2. Use the Networking MPS report to capture the SBS networking
configurations for further analysis:

a. Download MPSrepot_network from
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd9
15706/MPSRPT_NETWORK.EXE

b. Run MPSRPT_NETWORK.exe on the server box.

c. The tool will automatically collect the information. This procedure will
take 10~15 minutes.

d. Open Windows Explorer, navigate to the folder:
%SystemRoot%\MPSReports\Network\Reports\Cab\

e. Send the .cab file directly to me at v-terliu@xxxxxxxxxxxxxx

Hope these steps will give you some help.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

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

--------------------
| From: Alex <postings@xxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.sbs
| Subject: The COM+ Event System detected an inconsistency in its internal
state
| Date: 20 Apr 2007 05:35:30 -0700
| Organization: http://groups.google.com
| Lines: 42
| Message-ID: <1177072530.130682.116340@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
| NNTP-Posting-Host: 80.168.251.19
| Mime-Version: 1.0
| Content-Type: text/plain; charset="iso-8859-1"
| X-Trace: posting.google.com 1177072530 2765 127.0.0.1 (20 Apr 2007
12:35:30 GMT)
| X-Complaints-To: groups-abuse@xxxxxxxxxx
| NNTP-Posting-Date: Fri, 20 Apr 2007 12:35:30 +0000 (UTC)
| User-Agent: G2/1.0
| X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET
CLR 1.1.4322; .NET CLR 2.0.50727),gzip(gfe),gzip(gfe)
| X-HTTP-Via: 1.0 CLARENDON04
| Complaints-To: groups-abuse@xxxxxxxxxx
| Injection-Info: l77g2000hsb.googlegroups.com; posting-host=80.168.251.19;
| posting-account=bd-IXgwAAACbp4ozXlik9I7Q9REODQph
| Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!TK2MSFTFE
EDS01.phx.gbl!news-out.cwix.com!newsfeed.cwix.com!newscon02.news.prodigy.net
!prodigy.net!border1.nntp.dca.giganews.com!nntp.giganews.com!postnews.google
..com!l77g2000hsb.googlegroups.com!not-for-mail
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:31602
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hi
|
| I am getting behaviour whereby occasionally if somebody types in
| username/password into XP Pro to log in, presses enter, for about 1
| second it appears they are about to log in (you see the background
| colour), and then it bombs out back to the login prompt, immediatelyt.
| No message or nothing on the screeen. Second time they try this they
| get in no probs.
|
| When this happens the following message is logged in the event log:
|
| Event Type: Error
| Event Source: EventSystem
| Event Category: (50)
| Event ID: 4614
| Date: 20/04/2007
| Time: 13:08:40
| User: N/A
| Computer: MYPC
| Description:
| The COM+ Event System detected an inconsistency in its internal
| state. The assertion "GetLastError() == 122L" failed at line 201 of d:
| \qxp_slp\com\com1x\src\events\shared\sectools.cpp. Please contact
| Microsoft Product Support Services to report this error.
|
| This is happening on all our client PC's (they are not all the same, a
| lot have different hardware configurations). My environement is
| Windows 2003 SBS + Windows XP clients. Everything is patched up to the
| hilt with WSUS inc Windows Server 2003 SBS, although I haven't
| installed SP2 yet.
|
| So far I've consulted eventid.net and searched everywhere. Only advise
| given was to remove KB929969. This did not work.
|
| Also tried patching COM+ with http://support.microsoft.com/kb/912817.
| (Windows XP COM+ Hotfix Rollup Package 13). Whilst this speed up my
| clients somewhat (would you believe) it did not work either.
|
| Any ideas?
|
| Many thanks....
|
|

.

Loading