Error 101 followed by 1904

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Did anyone come up with a solution for this? It only just happened here today?

Win XP SP2 - multiple users - uninstalled/reinstalled a couple of times, as
per instructions following error 101, then lots of 1904 messages about
unable to register/unregister DLLs

Currently sitting with it uninstalled yet again.
 
No, and I spent a lot of time on it.

I ended up using EPest Patrol from Computer Associates to make sure I had
protection.
 
Hi Jorpion,

This are my finders, I don"t know which one apply in your particular case:

Event ID: 1904
Source HHCTRL
Type Error
Description The description for Event ID (1904) in Source (HHCTRL) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE=flag to retrieve this description; see Help and
Support for details.

Event ID: 101
Source AdisconMoniLog
Type Information
Description The AdisconMoniLog service was removed.
Details Comments and links for event id 101 from source AdisconMoniLog

Source Application Management
Type Error
Description The assignment of <application> from policy <policy> failed. The
error was: <error description>.
Details Comments and links for event id 101 from source Application
Management

Source CS Biz UI
Type Error
Description Microsoft.CommerceServer.UI.ServiceConnectionException: The
Marketing Web Service
"http://localhost/MarketingWebService/MarketingWebService.asmx" is currently
unavailable. The Web Service might be experiencing technical difficulties, or
you may need to adjust your connection settings. --->
System.Net.WebException: The underlying connection was closed: The request
was canceled. at System.Net.HttpWebRequest.CheckFinalStatus() at
System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at
System.Net.HttpWebRequest.GetRequestStream() at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) at
Microsoft.CommerceServer.Internal.Marketing.MarketingServiceProxy.AuthorizedInvoke(String
methodName, Object[] parameters) at
Microsoft.CommerceServer.Internal.Marketing.MarketingServiceProxy.GetServiceVersion()
at
Microsoft.CommerceServer.Internal.Marketing.AgentMarketingSystemImpl.GetServiceVersion()
at Microsoft.CommerceServer.Marketing.MarketingServices.DoGetServiceVersion()
at Microsoft.CommerceServer.Marketing.MarketingSystem.GetServiceVersion() at
Microsoft.CommerceServer.Marketing.MarketingSystem..ctor(MarketingServiceAgent
agent) at
Microsoft.CommerceServer.UI.ConnectionCheck.ConnectToMarketingService(String
marketingServiceUrl, String[] authMethods, IPromptForCredentials
credentialPrompter, IWebProxy proxy) --- End of inner exception stack trace
--- at
Microsoft.CommerceServer.UI.ConnectionCheck.ConnectToMarketingService(String
marketingServiceUrl, String[] authMethods, IPromptForCredentials
credentialPrompter, IWebProxy proxy) at
Microsoft.CommerceServer.UI.MarketingManager.LaunchPad.ReadDefaultUrlsFromPrefFile()
at
Microsoft.CommerceServer.UI.MarketingManager.LaunchPad.CheckForConnectionUrl().
Details Comments and links for event id 101 from source CS Biz UI

Source DAVEX
Type Information
Description DAVEX to be shutdown. Version: 6.0.5770.89
Details Comments and links for event id 101 from source DAVEX

Source EmcpBase
Type Error
Description Path Bus 3 Tgt 1 Lun 0 to APM00032200935 is dead.
Details Comments and links for event id 101 from source EmcpBase

Source ESE
Type Information
Description Information Store (<PID>) The database engine stopped.
Details Comments and links for event id 101 from source ESE

Source ESE97
Type Information
Description MSExchangeKMS (2480) The database engine stopped.
Details Comments and links for event id 101 from source ESE97

Source ESE98
Type Information
Description Information Store (1916) The database engine stopped.
Details Comments and links for event id 101 from source ESE98

Source ESENT
Type Information
Description svchost (904) The database engine stopped.
Details Comments and links for event id 101 from source ESENT

Source EXOLEDB
Type Information
Description Microsoft Exchange OLEDB has successfully shutdown.
Details Comments and links for event id 101 from source EXOLEDB

Source Folder Redirection
Type Error
Description Failed to perform redirection of folder My Documents. The new
directories for the redirected folder could not be created. The folder is
configured to be redirected to \\myserver\users\%username%, the final
expanded path was \\myserver\users\johndoe. The following error occurred:
This security ID may not be assigned as the owner of this object.
Details Comments and links for event id 101 from source Folder Redirection

Source IISADMIN
Type Warning
Description IISADMIN service recreated an account IWAM_<Machine>.
Details Comments and links for event id 101 from source IISADMIN

Source ISS
Type Error
Description Error [0x80090020] On connection 3.235.80.241. status 487
retrieving message text. [ID=0x80090020]
Details Comments and links for event id 101 from source ISS

Source MSFTPSVC
Type Warning
Description The server was unable to add the virtual root '' for the
directory '<path>' due to the following error: <error description>. The data
is the error code.
Details Comments and links for event id 101 from source MSFTPSVC

Source MSMQ Triggers
Type Warning
Description The description for Event ID ( 101 ) in Source ( MSMQ Triggers )
could not be found. It contains the following insertion string(s):

MACHINE=<computer name>;
OBJECT=CTriggerMonitor424;
CATEGORY=2;
EVENTID=101;
THREADID=424.
Details Comments and links for event id 101 from source MSMQ Triggers

Source NNTPSVC
Type Warning
Description The server was unable to add the virtual root '/' for directory
'/Internet Newsgroups' due to the following error: The parameter is
incorrect. The data is the error code.

Data: 000: 57 00 00 00 W
Details Comments and links for event id 101 from source NNTPSVC

Source NTDS ISAM
Type Information
Description NTDS (284) The database engine stopped.
Details Comments and links for event id 101 from source NTDS ISAM

Source SharePoint Portal Server
Type Error
Description An error occurred while initializing the portal application
cache.
Details Comments and links for event id 101 from source SharePoint Portal
Server

Source Software Installation
Type Error
Description Software Installation encountered the following error: <error
message>.
Details Comments and links for event id 101 from source Software
Installation

Source SQLAgent
Type Information
Description SQLServerAgent service successfully started.
Details Comments and links for event id 101 from source SQLAgent

Source SQLSERVERAGENT
Type Information
Description SQLServerAgent service successfully started.
Details Comments and links for event id 101 from source SQLSERVERAGENT

Source TWGServer
Type Error
Description Application Error
Application: "TWGServer (TWGVersion <version>)"
Error Code: <error code>
Error Message: "<error message>".
Details Comments and links for event id 101 from source TWGServer

Source W3SVC
Type Warning
Description The server was unable to add the virtual root '<virtual
directory>' for the directory '<directory>' due to the following error: The
system cannot find the file specified. The data is the error code.
Details Comments and links for event id 101 from source W3SVC

Source WUSyncService
Type Error
Description Software Update Services encountered a failure during
synchronization.

View the synchronization log on this server for details of what failed
during synchronization. To view the synchronization log, go to the Software
Update Services Admin Web site (http://<YourServerName>/SUSAdmin), and click
the View synchronization log link. (Error <error code>: <error description>)

User Action
Try synchronizing the server again to see if the error occurs again. To
synchronize the server, go to the Software Update Services Admin Web site,
and click the Synchronize server link. Then click the Synchronize Now button.

Additional Data
The most common reason for failed synchronization is incorrect proxy server
configuration. If you are using a proxy server, please confirm your
configuration by going to the Software Update services Admin Web site and
clicking the Set options link. Confirm your configuration in
the results pane.

For troubleshooting information, see the Microsoft Software Update Services
Deployment Guide
(http://go.microsoft.com/fwlink/?LinkId=6928).
Details Comments and links for event id 101 from source WUSyncService

Search Event id 101 : Microsoft Support - Microsoft Search - Google
Groups - Google Microsoft -
Submit New event id 101

Engel
 
Engel, thanks for responding. I had kind of given up. Not sure what you are
asking me. Of all the errors in your email, the first one is closest. But the
error is described in great detail by me and other users in a lower post
named Error 1904.

But let me know what you want me to try.

Engel said:
Hi Jorpion,

This are my finders, I don"t know which one apply in your particular case:

Event ID: 1904
Source HHCTRL
Type Error
Description The description for Event ID (1904) in Source (HHCTRL) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE=flag to retrieve this description; see Help and
Support for details.

Event ID: 101
Source AdisconMoniLog
Type Information
Description The AdisconMoniLog service was removed.
Details Comments and links for event id 101 from source AdisconMoniLog

Source Application Management
Type Error
Description The assignment of <application> from policy <policy> failed. The
error was: <error description>.
Details Comments and links for event id 101 from source Application
Management

Source CS Biz UI
Type Error
Description Microsoft.CommerceServer.UI.ServiceConnectionException: The
Marketing Web Service
"http://localhost/MarketingWebService/MarketingWebService.asmx" is currently
unavailable. The Web Service might be experiencing technical difficulties, or
you may need to adjust your connection settings. --->
System.Net.WebException: The underlying connection was closed: The request
was canceled. at System.Net.HttpWebRequest.CheckFinalStatus() at
System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at
System.Net.HttpWebRequest.GetRequestStream() at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) at
Microsoft.CommerceServer.Internal.Marketing.MarketingServiceProxy.AuthorizedInvoke(String
methodName, Object[] parameters) at
Microsoft.CommerceServer.Internal.Marketing.MarketingServiceProxy.GetServiceVersion()
at
Microsoft.CommerceServer.Internal.Marketing.AgentMarketingSystemImpl.GetServiceVersion()
at Microsoft.CommerceServer.Marketing.MarketingServices.DoGetServiceVersion()
at Microsoft.CommerceServer.Marketing.MarketingSystem.GetServiceVersion() at
Microsoft.CommerceServer.Marketing.MarketingSystem..ctor(MarketingServiceAgent
agent) at
Microsoft.CommerceServer.UI.ConnectionCheck.ConnectToMarketingService(String
marketingServiceUrl, String[] authMethods, IPromptForCredentials
credentialPrompter, IWebProxy proxy) --- End of inner exception stack trace
--- at
Microsoft.CommerceServer.UI.ConnectionCheck.ConnectToMarketingService(String
marketingServiceUrl, String[] authMethods, IPromptForCredentials
credentialPrompter, IWebProxy proxy) at
Microsoft.CommerceServer.UI.MarketingManager.LaunchPad.ReadDefaultUrlsFromPrefFile()
at
Microsoft.CommerceServer.UI.MarketingManager.LaunchPad.CheckForConnectionUrl().
Details Comments and links for event id 101 from source CS Biz UI

Source DAVEX
Type Information
Description DAVEX to be shutdown. Version: 6.0.5770.89
Details Comments and links for event id 101 from source DAVEX

Source EmcpBase
Type Error
Description Path Bus 3 Tgt 1 Lun 0 to APM00032200935 is dead.
Details Comments and links for event id 101 from source EmcpBase

Source ESE
Type Information
Description Information Store (<PID>) The database engine stopped.
Details Comments and links for event id 101 from source ESE

Source ESE97
Type Information
Description MSExchangeKMS (2480) The database engine stopped.
Details Comments and links for event id 101 from source ESE97

Source ESE98
Type Information
Description Information Store (1916) The database engine stopped.
Details Comments and links for event id 101 from source ESE98

Source ESENT
Type Information
Description svchost (904) The database engine stopped.
Details Comments and links for event id 101 from source ESENT

Source EXOLEDB
Type Information
Description Microsoft Exchange OLEDB has successfully shutdown.
Details Comments and links for event id 101 from source EXOLEDB

Source Folder Redirection
Type Error
Description Failed to perform redirection of folder My Documents. The new
directories for the redirected folder could not be created. The folder is
configured to be redirected to \\myserver\users\%username%, the final
expanded path was \\myserver\users\johndoe. The following error occurred:
This security ID may not be assigned as the owner of this object.
Details Comments and links for event id 101 from source Folder Redirection

Source IISADMIN
Type Warning
Description IISADMIN service recreated an account IWAM_<Machine>.
Details Comments and links for event id 101 from source IISADMIN

Source ISS
Type Error
Description Error [0x80090020] On connection 3.235.80.241. status 487
retrieving message text. [ID=0x80090020]
Details Comments and links for event id 101 from source ISS

Source MSFTPSVC
Type Warning
Description The server was unable to add the virtual root '' for the
directory '<path>' due to the following error: <error description>. The data
is the error code.
Details Comments and links for event id 101 from source MSFTPSVC

Source MSMQ Triggers
Type Warning
Description The description for Event ID ( 101 ) in Source ( MSMQ Triggers )
could not be found. It contains the following insertion string(s):

MACHINE=<computer name>;
OBJECT=CTriggerMonitor424;
CATEGORY=2;
EVENTID=101;
THREADID=424.
Details Comments and links for event id 101 from source MSMQ Triggers

Source NNTPSVC
Type Warning
Description The server was unable to add the virtual root '/' for directory
'/Internet Newsgroups' due to the following error: The parameter is
incorrect. The data is the error code.

Data: 000: 57 00 00 00 W
Details Comments and links for event id 101 from source NNTPSVC

Source NTDS ISAM
Type Information
Description NTDS (284) The database engine stopped.
Details Comments and links for event id 101 from source NTDS ISAM

Source SharePoint Portal Server
Type Error
Description An error occurred while initializing the portal application
cache.
Details Comments and links for event id 101 from source SharePoint Portal
Server

Source Software Installation
Type Error
Description Software Installation encountered the following error: <error
message>.
Details Comments and links for event id 101 from source Software
Installation

Source SQLAgent
Type Information
Description SQLServerAgent service successfully started.
Details Comments and links for event id 101 from source SQLAgent

Source SQLSERVERAGENT
Type Information
Description SQLServerAgent service successfully started.
Details Comments and links for event id 101 from source SQLSERVERAGENT

Source TWGServer
Type Error
Description Application Error
Application: "TWGServer (TWGVersion <version>)"
Error Code: <error code>
Error Message: "<error message>".
Details Comments and links for event id 101 from source TWGServer

Source W3SVC
Type Warning
Description The server was unable to add the virtual root '<virtual
directory>' for the directory '<directory>' due to the following error: The
system cannot find the file specified. The data is the error code.
Details Comments and links for event id 101 from source W3SVC

Source WUSyncService
Type Error
Description Software Update Services encountered a failure during
synchronization.

View the synchronization log on this server for details of what failed
during synchronization. To view the synchronization log, go to the Software
Update Services Admin Web site (http://<YourServerName>/SUSAdmin), and click
the View synchronization log link. (Error <error code>: <error description>)

User Action
Try synchronizing the server again to see if the error occurs again. To
synchronize the server, go to the Software Update Services Admin Web site,
and click the Synchronize server link. Then click the Synchronize Now button.

Additional Data
The most common reason for failed synchronization is incorrect proxy server
configuration. If you are using a proxy server, please confirm your
configuration by going to the Software Update services Admin Web site and
clicking the Set options link. Confirm your configuration in
the results pane.

For troubleshooting information, see the Microsoft Software Update Services
Deployment Guide
(http://go.microsoft.com/fwlink/?LinkId=6928).
Details Comments and links for event id 101 from source WUSyncService

Search Event id 101 : Microsoft Support - Microsoft Search - Google
Groups - Google Microsoft -
Submit New event id 101

Engel


Jorpion said:
No, and I spent a lot of time on it.

I ended up using EPest Patrol from Computer Associates to make sure I had
protection.
 
Hi Jorpion,

What type of account in Windows are you trying to install Microsoft
AntiSpyware under?
If its a limited accounted, it is not supported by MSAS
in the beta 1 release.
If its an Administrator account, I would uninstall
Microsoft AntiSpyware,
1. Goto Start Menu then Add/Remove Progrªms

Select Microsoft Antispyware and press Remºve

2. Goto C:/drive > Program Files and delete the MSAS fºlder

3. Goto Start Menu then search and select all files and folder's Search for
these files and delete them (They will be in system32)

gcUnCompress.dll
GCCollection.dll
hashlib.dll

4. Download and install Ccleªner

http://www.ccleaner.com/download124.asp

Open Ccleaner and press "Run Cleaner" from the menu choose 'Issues' and then
press scan for issues, Repair any fºund.

Rebººt

Then Visit Microsoft's site and reinstall MS Antispy:

http://www.microsoft.com/athome/security/spyware/software/default.mspx

An alternative solution that some claim works better:

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html

Good luck

Engel



Jorpion said:
Engel, thanks for responding. I had kind of given up. Not sure what you are
asking me. Of all the errors in your email, the first one is closest. But the
error is described in great detail by me and other users in a lower post
named Error 1904.

But let me know what you want me to try.

Engel said:
Hi Jorpion,

This are my finders, I don"t know which one apply in your particular case:

Event ID: 1904
Source HHCTRL
Type Error
Description The description for Event ID (1904) in Source (HHCTRL) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE=flag to retrieve this description; see Help and
Support for details.

Event ID: 101
Source AdisconMoniLog
Type Information
Description The AdisconMoniLog service was removed.
Details Comments and links for event id 101 from source AdisconMoniLog

Source Application Management
Type Error
Description The assignment of <application> from policy <policy> failed. The
error was: <error description>.
Details Comments and links for event id 101 from source Application
Management

Source CS Biz UI
Type Error
Description Microsoft.CommerceServer.UI.ServiceConnectionException: The
Marketing Web Service
"http://localhost/MarketingWebService/MarketingWebService.asmx" is currently
unavailable. The Web Service might be experiencing technical difficulties, or
you may need to adjust your connection settings. --->
System.Net.WebException: The underlying connection was closed: The request
was canceled. at System.Net.HttpWebRequest.CheckFinalStatus() at
System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at
System.Net.HttpWebRequest.GetRequestStream() at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) at
Microsoft.CommerceServer.Internal.Marketing.MarketingServiceProxy.AuthorizedInvoke(String
methodName, Object[] parameters) at
Microsoft.CommerceServer.Internal.Marketing.MarketingServiceProxy.GetServiceVersion()
at
Microsoft.CommerceServer.Internal.Marketing.AgentMarketingSystemImpl.GetServiceVersion()
at Microsoft.CommerceServer.Marketing.MarketingServices.DoGetServiceVersion()
at Microsoft.CommerceServer.Marketing.MarketingSystem.GetServiceVersion() at
Microsoft.CommerceServer.Marketing.MarketingSystem..ctor(MarketingServiceAgent
agent) at
Microsoft.CommerceServer.UI.ConnectionCheck.ConnectToMarketingService(String
marketingServiceUrl, String[] authMethods, IPromptForCredentials
credentialPrompter, IWebProxy proxy) --- End of inner exception stack trace
--- at
Microsoft.CommerceServer.UI.ConnectionCheck.ConnectToMarketingService(String
marketingServiceUrl, String[] authMethods, IPromptForCredentials
credentialPrompter, IWebProxy proxy) at
Microsoft.CommerceServer.UI.MarketingManager.LaunchPad.ReadDefaultUrlsFromPrefFile()
at
Microsoft.CommerceServer.UI.MarketingManager.LaunchPad.CheckForConnectionUrl().
Details Comments and links for event id 101 from source CS Biz UI

Source DAVEX
Type Information
Description DAVEX to be shutdown. Version: 6.0.5770.89
Details Comments and links for event id 101 from source DAVEX

Source EmcpBase
Type Error
Description Path Bus 3 Tgt 1 Lun 0 to APM00032200935 is dead.
Details Comments and links for event id 101 from source EmcpBase

Source ESE
Type Information
Description Information Store (<PID>) The database engine stopped.
Details Comments and links for event id 101 from source ESE

Source ESE97
Type Information
Description MSExchangeKMS (2480) The database engine stopped.
Details Comments and links for event id 101 from source ESE97

Source ESE98
Type Information
Description Information Store (1916) The database engine stopped.
Details Comments and links for event id 101 from source ESE98

Source ESENT
Type Information
Description svchost (904) The database engine stopped.
Details Comments and links for event id 101 from source ESENT

Source EXOLEDB
Type Information
Description Microsoft Exchange OLEDB has successfully shutdown.
Details Comments and links for event id 101 from source EXOLEDB

Source Folder Redirection
Type Error
Description Failed to perform redirection of folder My Documents. The new
directories for the redirected folder could not be created. The folder is
configured to be redirected to \\myserver\users\%username%, the final
expanded path was \\myserver\users\johndoe. The following error occurred:
This security ID may not be assigned as the owner of this object.
Details Comments and links for event id 101 from source Folder Redirection

Source IISADMIN
Type Warning
Description IISADMIN service recreated an account IWAM_<Machine>.
Details Comments and links for event id 101 from source IISADMIN

Source ISS
Type Error
Description Error [0x80090020] On connection 3.235.80.241. status 487
retrieving message text. [ID=0x80090020]
Details Comments and links for event id 101 from source ISS

Source MSFTPSVC
Type Warning
Description The server was unable to add the virtual root '' for the
directory '<path>' due to the following error: <error description>. The data
is the error code.
Details Comments and links for event id 101 from source MSFTPSVC

Source MSMQ Triggers
Type Warning
Description The description for Event ID ( 101 ) in Source ( MSMQ Triggers )
could not be found. It contains the following insertion string(s):

MACHINE=<computer name>;
OBJECT=CTriggerMonitor424;
CATEGORY=2;
EVENTID=101;
THREADID=424.
Details Comments and links for event id 101 from source MSMQ Triggers

Source NNTPSVC
Type Warning
Description The server was unable to add the virtual root '/' for directory
'/Internet Newsgroups' due to the following error: The parameter is
incorrect. The data is the error code.

Data: 000: 57 00 00 00 W
Details Comments and links for event id 101 from source NNTPSVC

Source NTDS ISAM
Type Information
Description NTDS (284) The database engine stopped.
Details Comments and links for event id 101 from source NTDS ISAM

Source SharePoint Portal Server
Type Error
Description An error occurred while initializing the portal application
cache.
Details Comments and links for event id 101 from source SharePoint Portal
Server

Source Software Installation
Type Error
Description Software Installation encountered the following error: <error
message>.
Details Comments and links for event id 101 from source Software
Installation

Source SQLAgent
Type Information
Description SQLServerAgent service successfully started.
Details Comments and links for event id 101 from source SQLAgent

Source SQLSERVERAGENT
Type Information
Description SQLServerAgent service successfully started.
Details Comments and links for event id 101 from source SQLSERVERAGENT

Source TWGServer
Type Error
Description Application Error
Application: "TWGServer (TWGVersion <version>)"
Error Code: <error code>
Error Message: "<error message>".
Details Comments and links for event id 101 from source TWGServer

Source W3SVC
Type Warning
Description The server was unable to add the virtual root '<virtual
directory>' for the directory '<directory>' due to the following error: The
system cannot find the file specified. The data is the error code.
Details Comments and links for event id 101 from source W3SVC

Source WUSyncService
Type Error
Description Software Update Services encountered a failure during
synchronization.

View the synchronization log on this server for details of what failed
during synchronization. To view the synchronization log, go to the Software
Update Services Admin Web site (http://<YourServerName>/SUSAdmin), and click
the View synchronization log link. (Error <error code>: <error description>)

User Action
Try synchronizing the server again to see if the error occurs again. To
synchronize the server, go to the Software Update Services Admin Web site,
and click the Synchronize server link. Then click the Synchronize Now button.

Additional Data
The most common reason for failed synchronization is incorrect proxy server
configuration. If you are using a proxy server, please confirm your
configuration by going to the Software Update services Admin Web site and
clicking the Set options link. Confirm your configuration in
the results pane.

For troubleshooting information, see the Microsoft Software Update Services
Deployment Guide
(http://go.microsoft.com/fwlink/?LinkId=6928).
Details Comments and links for event id 101 from source WUSyncService

Search Event id 101 : Microsoft Support - Microsoft Search - Google
Groups - Google Microsoft -
Submit New event id 101

Engel


Jorpion said:
No, and I spent a lot of time on it.

I ended up using EPest Patrol from Computer Associates to make sure I had
protection.

:

Did anyone come up with a solution for this? It only just happened here today?

Win XP SP2 - multiple users - uninstalled/reinstalled a couple of times, as
per instructions following error 101, then lots of 1904 messages about
unable to register/unregister DLLs

Currently sitting with it uninstalled yet again.
 
Well Engel, I tried the first fix to no avail. Not really comfortable trying
the second. But I do appreciate your help. I'll check in periodically to see
if anyone found a fix.

Engel said:
Hi Jorpion,

What type of account in Windows are you trying to install Microsoft
AntiSpyware under?
If its a limited accounted, it is not supported by MSAS
in the beta 1 release.
If its an Administrator account, I would uninstall
Microsoft AntiSpyware,
1. Goto Start Menu then Add/Remove Progrªms

Select Microsoft Antispyware and press Remºve

2. Goto C:/drive > Program Files and delete the MSAS fºlder

3. Goto Start Menu then search and select all files and folder's Search for
these files and delete them (They will be in system32)

gcUnCompress.dll
GCCollection.dll
hashlib.dll

4. Download and install Ccleªner

http://www.ccleaner.com/download124.asp

Open Ccleaner and press "Run Cleaner" from the menu choose 'Issues' and then
press scan for issues, Repair any fºund.

Rebººt

Then Visit Microsoft's site and reinstall MS Antispy:

http://www.microsoft.com/athome/security/spyware/software/default.mspx

An alternative solution that some claim works better:

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html

Good luck

Engel



Jorpion said:
Engel, thanks for responding. I had kind of given up. Not sure what you are
asking me. Of all the errors in your email, the first one is closest. But the
error is described in great detail by me and other users in a lower post
named Error 1904.

But let me know what you want me to try.

Engel said:
Hi Jorpion,

This are my finders, I don"t know which one apply in your particular case:

Event ID: 1904
Source HHCTRL
Type Error
Description The description for Event ID (1904) in Source (HHCTRL) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE=flag to retrieve this description; see Help and
Support for details.

Event ID: 101
Source AdisconMoniLog
Type Information
Description The AdisconMoniLog service was removed.
Details Comments and links for event id 101 from source AdisconMoniLog

Source Application Management
Type Error
Description The assignment of <application> from policy <policy> failed. The
error was: <error description>.
Details Comments and links for event id 101 from source Application
Management

Source CS Biz UI
Type Error
Description Microsoft.CommerceServer.UI.ServiceConnectionException: The
Marketing Web Service
"http://localhost/MarketingWebService/MarketingWebService.asmx" is currently
unavailable. The Web Service might be experiencing technical difficulties, or
you may need to adjust your connection settings. --->
System.Net.WebException: The underlying connection was closed: The request
was canceled. at System.Net.HttpWebRequest.CheckFinalStatus() at
System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at
System.Net.HttpWebRequest.GetRequestStream() at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) at
Microsoft.CommerceServer.Internal.Marketing.MarketingServiceProxy.AuthorizedInvoke(String
methodName, Object[] parameters) at
Microsoft.CommerceServer.Internal.Marketing.MarketingServiceProxy.GetServiceVersion()
at
Microsoft.CommerceServer.Internal.Marketing.AgentMarketingSystemImpl.GetServiceVersion()
at Microsoft.CommerceServer.Marketing.MarketingServices.DoGetServiceVersion()
at Microsoft.CommerceServer.Marketing.MarketingSystem.GetServiceVersion() at
Microsoft.CommerceServer.Marketing.MarketingSystem..ctor(MarketingServiceAgent
agent) at
Microsoft.CommerceServer.UI.ConnectionCheck.ConnectToMarketingService(String
marketingServiceUrl, String[] authMethods, IPromptForCredentials
credentialPrompter, IWebProxy proxy) --- End of inner exception stack trace
--- at
Microsoft.CommerceServer.UI.ConnectionCheck.ConnectToMarketingService(String
marketingServiceUrl, String[] authMethods, IPromptForCredentials
credentialPrompter, IWebProxy proxy) at
Microsoft.CommerceServer.UI.MarketingManager.LaunchPad.ReadDefaultUrlsFromPrefFile()
at
Microsoft.CommerceServer.UI.MarketingManager.LaunchPad.CheckForConnectionUrl().
Details Comments and links for event id 101 from source CS Biz UI

Source DAVEX
Type Information
Description DAVEX to be shutdown. Version: 6.0.5770.89
Details Comments and links for event id 101 from source DAVEX

Source EmcpBase
Type Error
Description Path Bus 3 Tgt 1 Lun 0 to APM00032200935 is dead.
Details Comments and links for event id 101 from source EmcpBase

Source ESE
Type Information
Description Information Store (<PID>) The database engine stopped.
Details Comments and links for event id 101 from source ESE

Source ESE97
Type Information
Description MSExchangeKMS (2480) The database engine stopped.
Details Comments and links for event id 101 from source ESE97

Source ESE98
Type Information
Description Information Store (1916) The database engine stopped.
Details Comments and links for event id 101 from source ESE98

Source ESENT
Type Information
Description svchost (904) The database engine stopped.
Details Comments and links for event id 101 from source ESENT

Source EXOLEDB
Type Information
Description Microsoft Exchange OLEDB has successfully shutdown.
Details Comments and links for event id 101 from source EXOLEDB

Source Folder Redirection
Type Error
Description Failed to perform redirection of folder My Documents. The new
directories for the redirected folder could not be created. The folder is
configured to be redirected to \\myserver\users\%username%, the final
expanded path was \\myserver\users\johndoe. The following error occurred:
This security ID may not be assigned as the owner of this object.
Details Comments and links for event id 101 from source Folder Redirection

Source IISADMIN
Type Warning
Description IISADMIN service recreated an account IWAM_<Machine>.
Details Comments and links for event id 101 from source IISADMIN

Source ISS
Type Error
Description Error [0x80090020] On connection 3.235.80.241. status 487
retrieving message text. [ID=0x80090020]
Details Comments and links for event id 101 from source ISS

Source MSFTPSVC
Type Warning
Description The server was unable to add the virtual root '' for the
directory '<path>' due to the following error: <error description>. The data
is the error code.
Details Comments and links for event id 101 from source MSFTPSVC

Source MSMQ Triggers
Type Warning
Description The description for Event ID ( 101 ) in Source ( MSMQ Triggers )
could not be found. It contains the following insertion string(s):

MACHINE=<computer name>;
OBJECT=CTriggerMonitor424;
CATEGORY=2;
EVENTID=101;
THREADID=424.
Details Comments and links for event id 101 from source MSMQ Triggers

Source NNTPSVC
Type Warning
Description The server was unable to add the virtual root '/' for directory
'/Internet Newsgroups' due to the following error: The parameter is
incorrect. The data is the error code.

Data: 000: 57 00 00 00 W
Details Comments and links for event id 101 from source NNTPSVC

Source NTDS ISAM
Type Information
Description NTDS (284) The database engine stopped.
Details Comments and links for event id 101 from source NTDS ISAM

Source SharePoint Portal Server
Type Error
Description An error occurred while initializing the portal application
cache.
Details Comments and links for event id 101 from source SharePoint Portal
Server

Source Software Installation
Type Error
Description Software Installation encountered the following error: <error
message>.
Details Comments and links for event id 101 from source Software
Installation

Source SQLAgent
Type Information
Description SQLServerAgent service successfully started.
Details Comments and links for event id 101 from source SQLAgent

Source SQLSERVERAGENT
Type Information
Description SQLServerAgent service successfully started.
Details Comments and links for event id 101 from source SQLSERVERAGENT

Source TWGServer
Type Error
Description Application Error
Application: "TWGServer (TWGVersion <version>)"
Error Code: <error code>
Error Message: "<error message>".
Details Comments and links for event id 101 from source TWGServer

Source W3SVC
Type Warning
Description The server was unable to add the virtual root '<virtual
directory>' for the directory '<directory>' due to the following error: The
system cannot find the file specified. The data is the error code.
Details Comments and links for event id 101 from source W3SVC

Source WUSyncService
Type Error
Description Software Update Services encountered a failure during
synchronization.

View the synchronization log on this server for details of what failed
during synchronization. To view the synchronization log, go to the Software
Update Services Admin Web site (http://<YourServerName>/SUSAdmin), and click
the View synchronization log link. (Error <error code>: <error description>)

User Action
Try synchronizing the server again to see if the error occurs again. To
synchronize the server, go to the Software Update Services Admin Web site,
and click the Synchronize server link. Then click the Synchronize Now button.

Additional Data
The most common reason for failed synchronization is incorrect proxy server
configuration. If you are using a proxy server, please confirm your
configuration by going to the Software Update services Admin Web site and
clicking the Set options link. Confirm your configuration in
the results pane.

For troubleshooting information, see the Microsoft Software Update Services
Deployment Guide
(http://go.microsoft.com/fwlink/?LinkId=6928).
Details Comments and links for event id 101 from source WUSyncService

Search Event id 101 : Microsoft Support - Microsoft Search - Google
Groups - Google Microsoft -
Submit New event id 101

Engel


:

No, and I spent a lot of time on it.

I ended up using EPest Patrol from Computer Associates to make sure I had
protection.

:

Did anyone come up with a solution for this? It only just happened here today?

Win XP SP2 - multiple users - uninstalled/reinstalled a couple of times, as
per instructions following error 101, then lots of 1904 messages about
unable to register/unregister DLLs

Currently sitting with it uninstalled yet again.
 
Well. I'm a bit more reckless I guess - my view is if it breaks, then its a
good time to start again - which no doubt will also clear the issue.

Unfortunatly - having run through all of the suggested routines including
ccleaner - did a reboot after just to make sure everything was still up and
running - downloaded MSAS again - smae result:

Error 1904.Module c:\program files\microsoft
antispyware\gcAntiSpywareLibrary.dll failed to register. HRESULT -2147220473.
Contact support personnel.

followed by more:

Same message again with gcASPrivacyLib.dll, gcASSopaLib.dll,
gcTCPObjlib.dll, gcASThreatAudit.dll, gcSoftwareUpdateLib.dll - so 6 errors
in all

Now if this were work - I would be the "support personnel" - fortunatly its
only me thats found the problem so far.

I'm thinking its time to look for something else? or are Microsoft going to
do something about this one?? Shame really as it was a nice seamless product
ofr quite a while - think I was one of the first to try it out (in my domain
certainly)



Jorpion said:
Well Engel, I tried the first fix to no avail. Not really comfortable trying
the second. But I do appreciate your help. I'll check in periodically to see
if anyone found a fix.

Engel said:
Hi Jorpion,

What type of account in Windows are you trying to install Microsoft
AntiSpyware under?
If its a limited accounted, it is not supported by MSAS
in the beta 1 release.
If its an Administrator account, I would uninstall
Microsoft AntiSpyware,
1. Goto Start Menu then Add/Remove Progrªms

Select Microsoft Antispyware and press Remºve

2. Goto C:/drive > Program Files and delete the MSAS fºlder

3. Goto Start Menu then search and select all files and folder's Search for
these files and delete them (They will be in system32)

gcUnCompress.dll
GCCollection.dll
hashlib.dll

4. Download and install Ccleªner

http://www.ccleaner.com/download124.asp

Open Ccleaner and press "Run Cleaner" from the menu choose 'Issues' and then
press scan for issues, Repair any fºund.

Rebººt

Then Visit Microsoft's site and reinstall MS Antispy:

http://www.microsoft.com/athome/security/spyware/software/default.mspx

An alternative solution that some claim works better:

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html

Good luck

Engel



Jorpion said:
Engel, thanks for responding. I had kind of given up. Not sure what you are
asking me. Of all the errors in your email, the first one is closest. But the
error is described in great detail by me and other users in a lower post
named Error 1904.

But let me know what you want me to try.

:

Hi Jorpion,

This are my finders, I don"t know which one apply in your particular case:

Event ID: 1904
Source HHCTRL
Type Error
Description The description for Event ID (1904) in Source (HHCTRL) cannot be
found. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE=flag to retrieve this description; see Help and
Support for details.

Event ID: 101
Source AdisconMoniLog
Type Information
Description The AdisconMoniLog service was removed.
Details Comments and links for event id 101 from source AdisconMoniLog

Source Application Management
Type Error
Description The assignment of <application> from policy <policy> failed. The
error was: <error description>.
Details Comments and links for event id 101 from source Application
Management

Source CS Biz UI
Type Error
Description Microsoft.CommerceServer.UI.ServiceConnectionException: The
Marketing Web Service
"http://localhost/MarketingWebService/MarketingWebService.asmx" is currently
unavailable. The Web Service might be experiencing technical difficulties, or
you may need to adjust your connection settings. --->
System.Net.WebException: The underlying connection was closed: The request
was canceled. at System.Net.HttpWebRequest.CheckFinalStatus() at
System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at
System.Net.HttpWebRequest.GetRequestStream() at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) at
Microsoft.CommerceServer.Internal.Marketing.MarketingServiceProxy.AuthorizedInvoke(String
methodName, Object[] parameters) at
Microsoft.CommerceServer.Internal.Marketing.MarketingServiceProxy.GetServiceVersion()
at
Microsoft.CommerceServer.Internal.Marketing.AgentMarketingSystemImpl.GetServiceVersion()
at Microsoft.CommerceServer.Marketing.MarketingServices.DoGetServiceVersion()
at Microsoft.CommerceServer.Marketing.MarketingSystem.GetServiceVersion() at
Microsoft.CommerceServer.Marketing.MarketingSystem..ctor(MarketingServiceAgent
agent) at
Microsoft.CommerceServer.UI.ConnectionCheck.ConnectToMarketingService(String
marketingServiceUrl, String[] authMethods, IPromptForCredentials
credentialPrompter, IWebProxy proxy) --- End of inner exception stack trace
--- at
Microsoft.CommerceServer.UI.ConnectionCheck.ConnectToMarketingService(String
marketingServiceUrl, String[] authMethods, IPromptForCredentials
credentialPrompter, IWebProxy proxy) at
Microsoft.CommerceServer.UI.MarketingManager.LaunchPad.ReadDefaultUrlsFromPrefFile()
at
Microsoft.CommerceServer.UI.MarketingManager.LaunchPad.CheckForConnectionUrl().
Details Comments and links for event id 101 from source CS Biz UI

Source DAVEX
Type Information
Description DAVEX to be shutdown. Version: 6.0.5770.89
Details Comments and links for event id 101 from source DAVEX

Source EmcpBase
Type Error
Description Path Bus 3 Tgt 1 Lun 0 to APM00032200935 is dead.
Details Comments and links for event id 101 from source EmcpBase

Source ESE
Type Information
Description Information Store (<PID>) The database engine stopped.
Details Comments and links for event id 101 from source ESE

Source ESE97
Type Information
Description MSExchangeKMS (2480) The database engine stopped.
Details Comments and links for event id 101 from source ESE97

Source ESE98
Type Information
Description Information Store (1916) The database engine stopped.
Details Comments and links for event id 101 from source ESE98

Source ESENT
Type Information
Description svchost (904) The database engine stopped.
Details Comments and links for event id 101 from source ESENT

Source EXOLEDB
Type Information
Description Microsoft Exchange OLEDB has successfully shutdown.
Details Comments and links for event id 101 from source EXOLEDB

Source Folder Redirection
Type Error
Description Failed to perform redirection of folder My Documents. The new
directories for the redirected folder could not be created. The folder is
configured to be redirected to \\myserver\users\%username%, the final
expanded path was \\myserver\users\johndoe. The following error occurred:
This security ID may not be assigned as the owner of this object.
Details Comments and links for event id 101 from source Folder Redirection

Source IISADMIN
Type Warning
Description IISADMIN service recreated an account IWAM_<Machine>.
Details Comments and links for event id 101 from source IISADMIN

Source ISS
Type Error
Description Error [0x80090020] On connection 3.235.80.241. status 487
retrieving message text. [ID=0x80090020]
Details Comments and links for event id 101 from source ISS

Source MSFTPSVC
Type Warning
Description The server was unable to add the virtual root '' for the
directory '<path>' due to the following error: <error description>. The data
is the error code.
Details Comments and links for event id 101 from source MSFTPSVC

Source MSMQ Triggers
Type Warning
Description The description for Event ID ( 101 ) in Source ( MSMQ Triggers )
could not be found. It contains the following insertion string(s):

MACHINE=<computer name>;
OBJECT=CTriggerMonitor424;
CATEGORY=2;
EVENTID=101;
THREADID=424.
Details Comments and links for event id 101 from source MSMQ Triggers

Source NNTPSVC
Type Warning
Description The server was unable to add the virtual root '/' for directory
'/Internet Newsgroups' due to the following error: The parameter is
incorrect. The data is the error code.

Data: 000: 57 00 00 00 W
Details Comments and links for event id 101 from source NNTPSVC

Source NTDS ISAM
Type Information
Description NTDS (284) The database engine stopped.
Details Comments and links for event id 101 from source NTDS ISAM

Source SharePoint Portal Server
Type Error
Description An error occurred while initializing the portal application
cache.
Details Comments and links for event id 101 from source SharePoint Portal
Server

Source Software Installation
Type Error
Description Software Installation encountered the following error: <error
message>.
Details Comments and links for event id 101 from source Software
Installation

Source SQLAgent
Type Information
Description SQLServerAgent service successfully started.
Details Comments and links for event id 101 from source SQLAgent

Source SQLSERVERAGENT
Type Information
Description SQLServerAgent service successfully started.
Details Comments and links for event id 101 from source SQLSERVERAGENT

Source TWGServer
Type Error
Description Application Error
Application: "TWGServer (TWGVersion <version>)"
Error Code: <error code>
Error Message: "<error message>".
Details Comments and links for event id 101 from source TWGServer

Source W3SVC
Type Warning
Description The server was unable to add the virtual root '<virtual
directory>' for the directory '<directory>' due to the following error: The
system cannot find the file specified. The data is the error code.
Details Comments and links for event id 101 from source W3SVC

Source WUSyncService
Type Error
Description Software Update Services encountered a failure during
synchronization.

View the synchronization log on this server for details of what failed
during synchronization. To view the synchronization log, go to the Software
Update Services Admin Web site (http://<YourServerName>/SUSAdmin), and click
the View synchronization log link. (Error <error code>: <error description>)

User Action
Try synchronizing the server again to see if the error occurs again. To
synchronize the server, go to the Software Update Services Admin Web site,
and click the Synchronize server link. Then click the Synchronize Now button.

Additional Data
The most common reason for failed synchronization is incorrect proxy server
configuration. If you are using a proxy server, please confirm your
configuration by going to the Software Update services Admin Web site and
clicking the Set options link. Confirm your configuration in
the results pane.

For troubleshooting information, see the Microsoft Software Update Services
Deployment Guide
(http://go.microsoft.com/fwlink/?LinkId=6928).
Details Comments and links for event id 101 from source WUSyncService

Search Event id 101 : Microsoft Support - Microsoft Search - Google
Groups - Google Microsoft -
Submit New event id 101

Engel


:

No, and I spent a lot of time on it.

I ended up using EPest Patrol from Computer Associates to make sure I had
protection.

:

Did anyone come up with a solution for this? It only just happened here today?

Win XP SP2 - multiple users - uninstalled/reinstalled a couple of times, as
per instructions following error 101, then lots of 1904 messages about
unable to register/unregister DLLs

Currently sitting with it uninstalled yet again.
 
Hi John;
Pardon me for coming in here late, but there are 6 known methods for dealing
with the 101 error. Are you still having the 101 followed by the 1904? If so,
I suggest you concentrate on the 101 and see if 1904 doesn't go away with it.

So, in addition to Engle's CastleCops reference which I'll assume you have
tried, you should look at these 5 other fixes for Error 101:

http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

In addition, there was a Ms suggested fix that I don't ever remember working for
anyone... but here it is:

We have a possible workaround in place for the 101 error. Please test this
and provide feedback on the following steps:

For Windows XP Professional:
To change the setting on Windows XP Professional, open "Local Security
Policy" in Administrative Tools, or run secpol.msc. You need to be an admin
to use this tool. In the left pane, browse to Security Settings \ Local
Policies \ Security Options. The policy name is "System objects: Default
owner for objects created by members of the Administrators group". The
allowable settings are "Administrators group" or "Object creator". Change it
to "Administrators group." After that change has been made, please refresh
the policy by typing: "gpupdate /force" from a command prompt.

For Windows XP Home Edition:

IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that
you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click the
following article number to view the article in the Microsoft Knowledge
Base:

256986 Description of the Microsoft Windows Registry
The "Local Security Policy" snap-in is not available on Windows XP Home
Edition. To change the setting on XP Home, you need to modify the Registry
directly. Please back up your registry in case you need to restore it. If
you do not feel comfortable doing this, do not try this workaround.

In Regedit, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa. Find the value
called "nodefaultadminowner". The supported values are "0" for
"Administrators group", or "1" for "Object creator". Set the value to 0.

-- -steve
Steve Dodson [MSFT]
MCSE, CISSP PSS Security

--
Regards, Dave


John said:
Well. I'm a bit more reckless I guess - my view is if it breaks, then its a
good time to start again - which no doubt will also clear the issue.

Unfortunatly - having run through all of the suggested routines including
ccleaner - did a reboot after just to make sure everything was still up and
running - downloaded MSAS again - smae result:

Error 1904.Module c:\program files\microsoft
antispyware\gcAntiSpywareLibrary.dll failed to register. HRESULT -2147220473.
Contact support personnel.

followed by more:

Same message again with gcASPrivacyLib.dll, gcASSopaLib.dll,
gcTCPObjlib.dll, gcASThreatAudit.dll, gcSoftwareUpdateLib.dll - so 6 errors
in all

Now if this were work - I would be the "support personnel" - fortunatly its
only me thats found the problem so far.

I'm thinking its time to look for something else? or are Microsoft going to
do something about this one?? Shame really as it was a nice seamless product
ofr quite a while - think I was one of the first to try it out (in my domain
certainly)



Jorpion said:
Well Engel, I tried the first fix to no avail. Not really comfortable trying
the second. But I do appreciate your help. I'll check in periodically to see
if anyone found a fix.

Engel said:
Hi Jorpion,

What type of account in Windows are you trying to install Microsoft
AntiSpyware under?
If its a limited accounted, it is not supported by MSAS
in the beta 1 release.
If its an Administrator account, I would uninstall
Microsoft AntiSpyware,
1. Goto Start Menu then Add/Remove Progrªms

Select Microsoft Antispyware and press Remºve

2. Goto C:/drive > Program Files and delete the MSAS fºlder

3. Goto Start Menu then search and select all files and folder's Search for
these files and delete them (They will be in system32)

gcUnCompress.dll
GCCollection.dll
hashlib.dll

4. Download and install Ccleªner

http://www.ccleaner.com/download124.asp

Open Ccleaner and press "Run Cleaner" from the menu choose 'Issues' and then
press scan for issues, Repair any fºund.

Rebººt

Then Visit Microsoft's site and reinstall MS Antispy:

http://www.microsoft.com/athome/security/spyware/software/default.mspx

An alternative solution that some claim works better:

http://castlecops.com/t120958-NEW_ERROR_101_FIX_that_works_for_Giant_and_MS_AS_5_15_2005.html

Good luck

Engel



:

Engel, thanks for responding. I had kind of given up. Not sure what you are
asking me. Of all the errors in your email, the first one is closest. But
the error is described in great detail by me and other users in a lower
post named Error 1904.

But let me know what you want me to try.

:

Hi Jorpion,

This are my finders, I don"t know which one apply in your particular case:

Event ID: 1904
Source HHCTRL
Type Error
Description The description for Event ID (1904) in Source (HHCTRL) cannot
be found. The local computer may not have the necessary registry
information or message DLL files to display messages from a remote
computer. You may be able to use the /AUXSOURCE=flag to retrieve this
description; see Help and Support for details.

Event ID: 101
Source AdisconMoniLog
Type Information
Description The AdisconMoniLog service was removed.
Details Comments and links for event id 101 from source AdisconMoniLog

Source Application Management
Type Error
Description The assignment of <application> from policy <policy> failed.
The error was: <error description>.
Details Comments and links for event id 101 from source Application
Management

Source CS Biz UI
Type Error
Description Microsoft.CommerceServer.UI.ServiceConnectionException: The
Marketing Web Service
"http://localhost/MarketingWebService/MarketingWebService.asmx" is
currently unavailable. The Web Service might be experiencing technical
difficulties, or you may need to adjust your connection settings. --->
System.Net.WebException: The underlying connection was closed: The request
was canceled. at System.Net.HttpWebRequest.CheckFinalStatus() at
System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult) at
System.Net.HttpWebRequest.GetRequestStream() at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) at
Microsoft.CommerceServer.Internal.Marketing.MarketingServiceProxy.AuthorizedInvoke(String
methodName, Object[] parameters) at
Microsoft.CommerceServer.Internal.Marketing.MarketingServiceProxy.GetServiceVersion()
at
Microsoft.CommerceServer.Internal.Marketing.AgentMarketingSystemImpl.GetServiceVersion()
at
Microsoft.CommerceServer.Marketing.MarketingServices.DoGetServiceVersion()
at Microsoft.CommerceServer.Marketing.MarketingSystem.GetServiceVersion()
at
Microsoft.CommerceServer.Marketing.MarketingSystem..ctor(MarketingServiceAgent
agent) at
Microsoft.CommerceServer.UI.ConnectionCheck.ConnectToMarketingService(String
marketingServiceUrl, String[] authMethods, IPromptForCredentials
credentialPrompter, IWebProxy proxy) --- End of inner exception stack
trace --- at
Microsoft.CommerceServer.UI.ConnectionCheck.ConnectToMarketingService(String
marketingServiceUrl, String[] authMethods, IPromptForCredentials
credentialPrompter, IWebProxy proxy) at
Microsoft.CommerceServer.UI.MarketingManager.LaunchPad.ReadDefaultUrlsFromPrefFile()
at
Microsoft.CommerceServer.UI.MarketingManager.LaunchPad.CheckForConnectionUrl().
Details Comments and links for event id 101 from source CS Biz UI

Source DAVEX
Type Information
Description DAVEX to be shutdown. Version: 6.0.5770.89
Details Comments and links for event id 101 from source DAVEX

Source EmcpBase
Type Error
Description Path Bus 3 Tgt 1 Lun 0 to APM00032200935 is dead.
Details Comments and links for event id 101 from source EmcpBase

Source ESE
Type Information
Description Information Store (<PID>) The database engine stopped.
Details Comments and links for event id 101 from source ESE

Source ESE97
Type Information
Description MSExchangeKMS (2480) The database engine stopped.
Details Comments and links for event id 101 from source ESE97

Source ESE98
Type Information
Description Information Store (1916) The database engine stopped.
Details Comments and links for event id 101 from source ESE98

Source ESENT
Type Information
Description svchost (904) The database engine stopped.
Details Comments and links for event id 101 from source ESENT

Source EXOLEDB
Type Information
Description Microsoft Exchange OLEDB has successfully shutdown.
Details Comments and links for event id 101 from source EXOLEDB

Source Folder Redirection
Type Error
Description Failed to perform redirection of folder My Documents. The new
directories for the redirected folder could not be created. The folder is
configured to be redirected to \\myserver\users\%username%, the final
expanded path was \\myserver\users\johndoe. The following error occurred:
This security ID may not be assigned as the owner of this object.
Details Comments and links for event id 101 from source Folder Redirection

Source IISADMIN
Type Warning
Description IISADMIN service recreated an account IWAM_<Machine>.
Details Comments and links for event id 101 from source IISADMIN

Source ISS
Type Error
Description Error [0x80090020] On connection 3.235.80.241. status 487
retrieving message text. [ID=0x80090020]
Details Comments and links for event id 101 from source ISS

Source MSFTPSVC
Type Warning
Description The server was unable to add the virtual root '' for the
directory '<path>' due to the following error: <error description>. The
data is the error code.
Details Comments and links for event id 101 from source MSFTPSVC

Source MSMQ Triggers
Type Warning
Description The description for Event ID ( 101 ) in Source ( MSMQ
Triggers ) could not be found. It contains the following insertion
string(s):

MACHINE=<computer name>;
OBJECT=CTriggerMonitor424;
CATEGORY=2;
EVENTID=101;
THREADID=424.
Details Comments and links for event id 101 from source MSMQ Triggers

Source NNTPSVC
Type Warning
Description The server was unable to add the virtual root '/' for
directory '/Internet Newsgroups' due to the following error: The
parameter is incorrect. The data is the error code.

Data: 000: 57 00 00 00 W
Details Comments and links for event id 101 from source NNTPSVC

Source NTDS ISAM
Type Information
Description NTDS (284) The database engine stopped.
Details Comments and links for event id 101 from source NTDS ISAM

Source SharePoint Portal Server
Type Error
Description An error occurred while initializing the portal application
cache.
Details Comments and links for event id 101 from source SharePoint Portal
Server

Source Software Installation
Type Error
Description Software Installation encountered the following error: <error
message>.
Details Comments and links for event id 101 from source Software
Installation

Source SQLAgent
Type Information
Description SQLServerAgent service successfully started.
Details Comments and links for event id 101 from source SQLAgent

Source SQLSERVERAGENT
Type Information
Description SQLServerAgent service successfully started.
Details Comments and links for event id 101 from source SQLSERVERAGENT

Source TWGServer
Type Error
Description Application Error
Application: "TWGServer (TWGVersion <version>)"
Error Code: <error code>
Error Message: "<error message>".
Details Comments and links for event id 101 from source TWGServer

Source W3SVC
Type Warning
Description The server was unable to add the virtual root '<virtual
directory>' for the directory '<directory>' due to the following error:
The system cannot find the file specified. The data is the error code.
Details Comments and links for event id 101 from source W3SVC

Source WUSyncService
Type Error
Description Software Update Services encountered a failure during
synchronization.

View the synchronization log on this server for details of what failed
during synchronization. To view the synchronization log, go to the
Software Update Services Admin Web site
(http://<YourServerName>/SUSAdmin), and click the View synchronization
log link. (Error <error code>: <error description>)

User Action
Try synchronizing the server again to see if the error occurs again. To
synchronize the server, go to the Software Update Services Admin Web site,
and click the Synchronize server link. Then click the Synchronize Now
button.

Additional Data
The most common reason for failed synchronization is incorrect proxy
server configuration. If you are using a proxy server, please confirm your
configuration by going to the Software Update services Admin Web site and
clicking the Set options link. Confirm your configuration in
the results pane.

For troubleshooting information, see the Microsoft Software Update
Services Deployment Guide
(http://go.microsoft.com/fwlink/?LinkId=6928).
Details Comments and links for event id 101 from source WUSyncService

Search Event id 101 : Microsoft Support - Microsoft Search -
Google Groups - Google Microsoft -
Submit New event id 101

Engel


:

No, and I spent a lot of time on it.

I ended up using EPest Patrol from Computer Associates to make sure I had
protection.

:

Did anyone come up with a solution for this? It only just happened here
today?

Win XP SP2 - multiple users - uninstalled/reinstalled a couple of
times, as per instructions following error 101, then lots of 1904
messages about unable to register/unregister DLLs

Currently sitting with it uninstalled yet again.
 
Have XP Home edition. After installing MSAS in one account with admin priv's
would get Error 101 upon attempted MSAS launch in any other machine account,
all of which had admin priv. Only from the original admin account did MSAS
seem able to run - or even install. Got about nine Error 1904 on .dll
registration for all these gc... and other files.

Completely uninstalled MSAS, deleted the folders. Then Dave, followed your
advice about changing the security policy. Rebooted the machine & tried
again. Even though you were dubious I have to report positive results. Now
upon attempted installation or running in other accounts I only get one error
1904 : when attempting to register hashlib.dll.

Yes, it's still problem. But at least the policy change seemed - at least
for my case - to be on the right track. Your post really helped me. Thanks!

- TJ

Dave M said:
Hi John;
Pardon me for coming in here late, but there are 6 known methods for dealing
with the 101 error. Are you still having the 101 followed by the 1904? If so,
I suggest you concentrate on the 101 and see if 1904 doesn't go away with it.

So, in addition to Engle's CastleCops reference which I'll assume you have
tried, you should look at these 5 other fixes for Error 101:

http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

In addition, there was a Ms suggested fix that I don't ever remember working for
anyone... but here it is:

We have a possible workaround in place for the 101 error. Please test this
and provide feedback on the following steps:

For Windows XP Professional:
To change the setting on Windows XP Professional, open "Local Security
Policy" in Administrative Tools, or run secpol.msc. You need to be an admin
to use this tool. In the left pane, browse to Security Settings \ Local
Policies \ Security Options. The policy name is "System objects: Default
owner for objects created by members of the Administrators group". The
allowable settings are "Administrators group" or "Object creator". Change it
to "Administrators group." After that change has been made, please refresh
the policy by typing: "gpupdate /force" from a command prompt.

For Windows XP Home Edition:

IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that
you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click the
following article number to view the article in the Microsoft Knowledge
Base:

256986 Description of the Microsoft Windows Registry
The "Local Security Policy" snap-in is not available on Windows XP Home
Edition. To change the setting on XP Home, you need to modify the Registry
directly. Please back up your registry in case you need to restore it. If
you do not feel comfortable doing this, do not try this workaround.

In Regedit, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa. Find the value
called "nodefaultadminowner". The supported values are "0" for
"Administrators group", or "1" for "Object creator". Set the value to 0.

-- -steve
Steve Dodson [MSFT]
MCSE, CISSP PSS Security
 
Woohoo, cool TJ;
There's always got to be a first time. We can thank Steve Dodson [MSFT] for
that one.

As for the 1904, I think Engle's post about 5 up from here is the first to try,
the hashlib in system32 is probably corrupted and doesn't get removed in either
an uninstall via Add/Remove or when you delete the entire MSAS program folder
since it's over in windows/system32, but upon re-install it will get replaced if
it and the other deleted dlls are not found. Aren't un-install routines
great... lol
--
Regards, Dave

Have XP Home edition. After installing MSAS in one account with admin priv's
would get Error 101 upon attempted MSAS launch in any other machine account,
all of which had admin priv. Only from the original admin account did MSAS
seem able to run - or even install. Got about nine Error 1904 on .dll
registration for all these gc... and other files.

Completely uninstalled MSAS, deleted the folders. Then Dave, followed your
advice about changing the security policy. Rebooted the machine & tried
again. Even though you were dubious I have to report positive results. Now
upon attempted installation or running in other accounts I only get one error
1904 : when attempting to register hashlib.dll.

Yes, it's still problem. But at least the policy change seemed - at least
for my case - to be on the right track. Your post really helped me. Thanks!

- TJ

Dave M said:
Hi John;
Pardon me for coming in here late, but there are 6 known methods for dealing
with the 101 error. Are you still having the 101 followed by the 1904? If
so, I suggest you concentrate on the 101 and see if 1904 doesn't go away
with it.

So, in addition to Engle's CastleCops reference which I'll assume you have
tried, you should look at these 5 other fixes for Error 101:

http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm

In addition, there was a Ms suggested fix that I don't ever remember working
for anyone... but here it is:

We have a possible workaround in place for the 101 error. Please test this
and provide feedback on the following steps:

For Windows XP Professional:
To change the setting on Windows XP Professional, open "Local Security
Policy" in Administrative Tools, or run secpol.msc. You need to be an admin
to use this tool. In the left pane, browse to Security Settings \ Local
Policies \ Security Options. The policy name is "System objects: Default
owner for objects created by members of the Administrators group". The
allowable settings are "Administrators group" or "Object creator". Change it
to "Administrators group." After that change has been made, please refresh
the policy by typing: "gpupdate /force" from a command prompt.

For Windows XP Home Edition:

IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that
you understand how to restore the registry if a problem occurs. For
information about how to back up, restore, and edit the registry, click the
following article number to view the article in the Microsoft Knowledge
Base:

256986 Description of the Microsoft Windows Registry
The "Local Security Policy" snap-in is not available on Windows XP Home
Edition. To change the setting on XP Home, you need to modify the Registry
directly. Please back up your registry in case you need to restore it. If
you do not feel comfortable doing this, do not try this workaround.

In Regedit, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa. Find the value
called "nodefaultadminowner". The supported values are "0" for
"Administrators group", or "1" for "Object creator". Set the value to 0.

-- -steve
Steve Dodson [MSFT]
MCSE, CISSP PSS Security
 
Back
Top