COM+ error 4614

[Guest]

I am getting strange, intermittant errors. Sometimes when I enter my
password and click to log on, it immediately logs me off. So I enter my
password again and then I am logged in, but there are two identical events
posted at the exact same time in Event Viewer.


Event Type: Error
Event Source: EventSystem
Event Category: (50)
Event ID: 4614
User: N/A

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.


I can't find information on Event ID 4614 anywhere. I've run full
anti-virus scans with Ad-Aware and Defender, full Scandisk and Defrag, all
high priority updates from Windows Update. I don't know what else to do.
Any ideas?

XP Home SP2
1GB RAM
P4 3.0GHz
33GB free space

Thanks,
Scott

 

[Guest]

I would try creating a new profile ID

811151 - How to Copy User Data to a New User Profile:
http://support.microsoft.com/default.aspx?scid=kb;en-us;811151

 

[Guest]

I am also having this same identical problem. I have contacted MSFT and paid
for support. They are of the opinion that there was a bad drvier. I formatted
my HD and reloaded Windows XP SP2 Home Edition.
It appears(?) that when I turn on the Automatic updates, and get IE7 the
problem comes back. ( Or one of the IE7 Security Updates).
I have seen this error posted over the WEB as well.
Does MSFT monitor these forums?
I truly believe the problem is a result of some Fix that has been issued.
If I run without the automatic updates on and do not pull IE7, the error
message does not appear.
This all started about 2 months ago.
I tried all the recomended solutions about profiles, etc. and nothing will
remove the error unless I go back to a Pre Automatic Update version of XP.
Are other people seeing this error and not reporting it?
Does anyone have any other suggestions/solutions?
Thanks for any help you can provide.

 

[Guest]

I contacted Support as well and the first thing they said was:

"This kind of behavior can occur when some program has removed the
Wsaupdater.exe file from the computer. Wsaupdater.exe is spyware that changes
the Userinit.exe, to Wsaupdater.exe in the registry. Though Registry Clean
can remove that file, it cannot change the registry subkey back to
Userinit.exe." (I had previously ran thorough Ad-Aware and Windows Defender
scans as well as Error-Checking aka scandisk, and everything came up clean).

The solution was:

"Change the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Replace "wsaupdater.exe" with "userinit.exe," (make sure to include the
comma, as shown), and then click OK."



However, it already had that value. The next suggestion was to Re-register
es.dll (REGSVR32 es.dll). Then boot into what he referred to as Clean Mode.



"1. Click "Start", go to "Run", and type "msconfig" (without the quotation
marks) in the open box to start the System Configuration Utility.

2. Click the "Services" tab, check the "Hide All Microsoft Services" box and
click "Disable All" (if it is not gray).

3. Click the "Startup" tab, click "Disable All" and click "OK".

4. Click "OK" to restart your computer to Selective Startup environment.

Please let me know if the issue persists in Clean Boot Mode. Since the
logoff issue does not occur every time we logon, please try several times to
confirm if the issue does or does not occur in Clean Boot Mode. It may take
us some time to perform the steps. If the issue does not occur, the problem
can be caused by third party programs.

If the issue persists in Clean Boot Mode, please assist me in collecting the
System Information in Clean Boot Mode and send to me. The System Information
can provide us with more information about the current status of the system.
I would like to check it for you. Please send it to me using the following
steps:

How to collect System Information:

==========================

1. Click Start, go to "Run", type in "MSINFO32" (without quotation marks)
and press Enter to start System Information.

2. On the popup window, on the menu bar, click "File", and click "Save";
save it as an NFO file, such as "system.nfo" to your local Desktop.

3. Find the file, right-click on this file, click "Send To", and click
"Compressed (zipped) Folder".

4. Please send it as an attachment to ********

Note: Since most System Information which is not compressed will corrupt
when arriving, please do not forget to zip it (step 3) before sending."



I have not done any of these steps after and including the registering of
es.dll. My solution was to install XP Pro on a new hard drive (my school has
a MS Academic program and I got my copy free; this solution may not be the
best if you have to pay for it). The issue has not reappeared.

I hope this helps.

 

[Guest]

Thanks so much for the info. Please elaborate on how to Re-Register es.dll.
( My registry has only been modified by Live One Care and I did have the
correct process name in place also.)

I have XP Home edition. Been running this since 12/25/06. Problem started in
July of 07.

I have reformatted and reloaded 5 different times. But as soon as I get the
updates, there she blows.

I am fairly confident I can get the error again and will gather the
information that Microsoft requested of you. I will then send the
documentation to them based on my incident number.

Again...Thanks for the info.

 

[Guest]

I found the KB article about using rebsvr32 for the reregister of es.dll.

I will now try to create the error with Clean Boot Mode.

I will post back with my results.

Thanks again !!

 

[Guest]

You're welcome, I know how frustrating this error is. It's usually easy to
find an answer in the KB. By the way I forgot to mention this problem seemed
to start some time after I installed IE 7 too. I don't know how long after
but I'm almost 100% sure I was not getting these errors prior. Of course I
always keep up to date with Automatic Updates so it wasn't a problem of
outdated versions.

 

[Guest]

Thanks again. I totally agree with everything you have stated. IE7 appears to
have introduced the error. I also stay current on Maintenance and use only
Microsoft add-ons. Windefend and Live One Care update my system.

 

[brettlarson]

I think I found the culprit, now I need a fix...

Ok, so I have been battling this same issue that you all are having for quite some time now. After installing IE7, reboot, try to log in and it appears to log in and then goes to saving user settings and back to the log in screen. It doesnt happen all the time, totally random... I have reloaded and applied every security patch and windows update except for IE7, and the problem does not occur. BUT, there is more to the story. I am curious to know what kind of video card you all have? It may sound crazy, but I am convinced their is a conflict between ATI cards and\orleast their catalyst drivers and software and Internet Explorer 7. I have 10 computers, and this problem persists on exactly 3 of them, always the same three, even though they are all loaded identically. The three that the problem exists on all have ATI Radeon AGP graphics cards, the other 7 just use the integrated video card.

Please let me know if this theory seems to be in line with the rest of you. I dont know what I am going to do yet, I did go way back to an old ATI driver (5.11 with the old style control panel and not the horrible CCC) and am testing that, I will see if that resolves the issue. I would like to be able to use IE7 obviously for functionality and security, so I am not sure who is at fault here, MS or ATI.

 

[Guest]

Just thought I would update this entry. Yesterday the error occurred twice. I
was running Clean Boot Mode. Sent the info off to MSFT. Now wait to hear back.

 

[Guest]

Hi again.
After getting really annoyed with MSFT phone support, I decided to use my 36
years of IBM Mainframe System Programmer skills back in motion. Yes..I wrote,
debugged code and tuned IBM Mainframes for 36 years. Retired in March of 2007
to see the Counrty. Anyway...After reading what MSFT had you do, I went
looking for a FIX that had a more current vversion of ES.DLL. I found one. It
is the COM+ Rollup Hotfix 14. I have NOT seen the error again since I applied
it to my XP Home Edition yesterday. This rollup is also for XP Professional
as well. Here is the link so you can request the Hotfix from MSFT.

http://support.microsoft.com/kb/922668

The new ES.DLL should have a date of 07/10/2006.

I will post back in one week with my final report.

Thanks for your previous help.

 

[Unknown]

Were you an IBM employee or did you work for an IBM customer?

 

[Guest]

I worked for a IBM customer. A large Mutual Insurance company that has its
Home Office in Minnesota. Started in 1971 sorting IBM Cards. Finished as a
Senior System Programmer, specializing in Z Series, CICS and Communications.

And you ??

 

[Unknown]

I fixed and then later designed the systems you programmed.

 

[Guest]

So..I assume you were(?) an IBMer? Where abouts are you located?
Why are you known as "unknown" ?

 

[Unknown]

Chicago area. (now) Chose this ID for newsgroups. Eliminates unwanted
e-mail.

 

[Guest]

Is anyone from Microsoft reviewing this thread? The annoying error has not
gone away. It appears(?) to be associated with IE7 and/or KB929969. Could
someone from MSFT please reply to this problem. There are many groups on the
Web reporting this same problem.

Thanks for your response.

 

[Ken Blake, MVP]

Is anyone from Microsoft reviewing this thread? The annoying error has not
gone away. It appears(?) to be associated with IE7 and/or KB929969. Could
someone from MSFT please reply to this problem. There are many groups on the
Web reporting this same problem.

If you want to contact Microsoft, you're in the wrong place.

This is a peer support newsgroup. We are all just Windows XP users
here, helping each other if and when we can. We are not Microsoft
employees (not even those of us with "Microsoft MVP" behind our names;
that's an honorary title for having provided consistently helpful
advice) except for an occasional employee who posts here unofficially
on his own time.

 

[Guest]

Thanks for the info Ken. It is really a shame that MSFT would not view their
newsgroups for problems. I read that they do this. That is why each thread
should only contain one problem. MSFT has been useless in resolving this
issue with anyone that has reported it.( Through the PAY support line.) The
other user in this thread finally installed XP Professional. I have seen
ithis issue from other users in XP Professional as well. I am very
disappointed in MSFT Support, after having used IBM support services for 36
years.

Regards,
Bruce Bentley

 

[Guest]

Scottshell - Are you still viewing this thread? I have a question for you.
Did you have an ATI Grapics Driver installed when you were getting this error?

Thanks for the info.

Bruce