Member Avatar for Hamrick

I wrote a windows service in .NET 2.0, but when I try to uninstall it, I get an exception. The full text for the message from my event viewer is this.

The description for Event ID ( 11001 ) in Source ( MsiInstaller ) 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. The following information is part of the event: Product: SQL Task Scheduler Service -- Error 1001. An exception occurred while uninstalling. This exception will be ignored and the uninstall will continue. However, the application might not be fully uninstalled after the uninstall is complete. --> Cannot find Log STS Service on computer '.'., (NULL), (NULL), (NULL).

I've tried everything down to manually removing all of the registry keys for the service and cleaning my registry with RegSeeker. I can't fix any problems in the service until I know what the problem is. :( Does anybody know where I can look to troubleshoot this exception?

  • 2 Contributors
  • 1 Reply
  • 507 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by nakul.bhagat

Dani AI

Generated

The MSI Event 1001 reported by is the Windows Installer surfacing an exception thrown by a custom action (the Installer class) during uninstall. The "Cannot find ... on computer '.'" text means the uninstall code attempted to locate or control the service and failed. That narrows the investigation to two places that are often missed: the ProjectInstaller/service metadata, and any custom uninstall code.

Check list (do these in order):

  • Verify the actual service key name (HKLM\SYSTEM\CurrentControlSet\Services\<ServiceName>) matches the installer property ServiceInstaller.ServiceName. A common mistake is using the display name where the service short name is required.
  • Inspect any overridden Uninstall or other installer methods for unhandled exceptions (EventLog writes, ServiceController calls, file I/O). Wrap cleanup code in try/catch and log details instead of letting exceptions bubble up.
  • Capture the real failure: enable verbose MSI logging and check the Application log for the .NET stack trace. Example commands to try:
sc query "YourServiceShortName"
sc delete "YourServiceShortName"

"C:\Windows\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exe" /u "C:\path\YourService.exe"

msiexec /x {PRODUCT-CODE-GUID} /L*V "C:\msilog.txt"

Notes and cautions:

  • If the service was manually removed earlier (registry edits, RegSeeker), orphaned EventLog sources or mismatched installer state often cause the custom action to fail. As observed, restoring the expected installer state with InstallUtil, then running the MSI uninstall, can clear the error — but always back up the registry before manual edits.
  • If Uninstall must run additional cleanup, catch exceptions and write a diagnostic file or event entry so MSI sees a clean exit.
Member Avatar for nakul.bhagat

hey!

I faced the same issue when I uninstalled the windows service by mistake while still it was running. To resolve this type of issue all I did is this :
a. First uninstalled the dll using the installutil.exe and then
b. Install the .exe using the installutil.exe.
c. The again I uninstalled the msi using the control panel.

After all this I was able to successfully install the windows service and made it it up n running. :)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.