Cannot Start the UPS Service

View products that this article applies to.

This article was previously published under Q310437

Expand all | Collapse all

SYMPTOMS

You are unable to configure an uninterruptible power supply (UPS). The UPS service does not start and you may receive a Dr. Watson access violation or application error message in Ups.exe.

Back to the top

CAUSE

This issue can occur in the following situation:

You upgrade a Microsoft Windows 98-based computer to Microsoft Windows 2000.
You upgrade that Windows 2000-based computer to Microsoft Windows XP.

Back to the top

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

322389 (http://support.microsoft.com/kb/322389/EN-US/ ) How to Obtain the Latest Windows XP Service Pack

This update is available on the Microsoft Windows Update Web site.

Collapse this imageExpand this image

Download the UPS Update now (http://windowsupdate.microsoft.com/)

Release Date: October 25, 2001

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 (http://support.microsoft.com/kb/119591/EN-US/ ) How to Obtain Microsoft Support Files from Online Services

Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file. The English-language version of this fix should have the following file attributes or later:

   Date         Time   Version      Size    File name  Platform
   ------------------------------------------------------------------
   12-Oct-2001  16:38  5.1.2600.15  16,384  Ups.exe    i386
   12-Oct-2001  16:38  5.1.2600.15  50,176  Ups.exe    Itanium 64-bit

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows XP Service Pack 1.

Back to the top