Crikety Crick
Posts: 104
Joined: 9.May2004
From: Virginia Beach, VA
Status: offline
|
OK that did not work. I did find out that DCOM was the problem. I found the soulution in a round about way from eventfinder.net that sent me to the right area. The problem, while I still do not know why the account was not created, was with the LNSS USER account as I previously stated. The solution was to go to the DCOMCONFG.exe from the command line and then look into the registry using the error code from event user and locating the DCOM process. I found out that teh RegServer process was using a bad account and when I reset the REGserver account to my own domain account the problem of locking up with the filters was gone. Here is the write up that led me in the right direction I give Kudos to Leigh Dawson for this write up.
"I was getting this: ôDCOM got error "Overlapped I/O operation is in progress. " and was unable to logon <domain>\administrator in order to run the server: {ID}ö. I had changed the administrator password. I had to run ôdcomcnfgö and find the Dcom object that was referenced by the ID (just searched in the registry). Load up dcomcnfg then reset the administrator password.
|