How to troubleshoot the installation of Application Center 2000 (832325)

RESOLUTION

This section describes troubleshooting methods that you can use to resolve problems with the installation of Application Center 2000 SP2.

The method that you use depends on whether Application Center was previously installed:

• If you have previously installed Application Center 2000, start at "Method 1" and follow each method until the problems are resolved.
• If no version of Application Center 2000 was previously installed, start at "Method 3" and follow each method until the problems are resolved.

Method 1: Use the Acremover.exe tool to remove leftover files

To resolve this problem, use the Acremover.exe tool to remove the files, the folders, and the registry keys that are leftover from the previous installation. Microsoft recommends that you run this tool after each failed installation of Application Center 2000.

To use this tool, the .NET Framework must be installed.

For additional information about the Acremover.exe tool and how to use it, click the following article number to view the article in the Microsoft Knowledge Base:

Method 2: Manually remove leftover files

If the .NET Framework is not installed, you must manually remove the files, the folders, and the registry keys.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To make sure that the previous installation of Application Center 2000 is completely removed, follow these steps:

1. If the following services that are associated with Application Center 2000 are present on your computer, stop the services:
   • Application Center Administration Service
   • Application Center Cluster Service
   • Application Center Log Query Helper
   • Application Center Name Resolution Service
   • Application Center Synchronization Service
   • COM+ Component Load Balancing Service
   • SQLAgent$MSAC
2. Remove the following Application Center 2000 and Microsoft Application Center SQL Server Desktop Engine (MSDE) keys from the registry:
   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Application Center Server
   • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSAC
   • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQL$MSAC
   • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SQLAGENT$MSAC
   • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Acadmin
   • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Accluster
   • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Aclqhelper
   • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Acnameres
   • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Acsrepl
   • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ComLBSvc
3. Remove the following folder:

   C:\Program Files\Microsoft Application Center

   If you cannot remove the folder, run the following command at a command prompt, and then try to remove the folder again:

   msizap.exe T {20F95200-47D6-4CAC-92FF-5F6B29C78F88}

4. Remove the following folder:

   C:\Program Files\Microsoft SQL Server\MSSQL$MSAC

5. Use the Add/Remove programs item in Control Panel to remove Health Monitor.

Method 3: Install from Setup.hta

If the problem continues to occur after you have followed the previous steps to remove leftover files, follow these steps:

1. Start your installation from the Setup.hta installer file. The Setup.hta file generates a log file that is named Ac_setup.log and that indicates where the installation failed. By using the information in Ac_setup.log, you can continue to troubleshoot. (The Ac_setup.log file is typically saved in either the C:\WINNT folder or in the C:\Windows folder.)
   
   If you start your installation from the Setup.exe installer file, the log file is not generated and cannot give you troubleshooting information.
2. Open Ac_setup.log in a text editor such as Notepad and search for "Return value 3".
3. View the text that appears immediately before "Return value 3" for indications about error codes or error messages.

Method 4: Review the errors in the Ac_setup.log file

If the problem continues to occur after you have followed the previous steps, you can view the Ac_setup.log file for more information about where the installation failed.

Following are two of the errors that are frequently encountered:

Use the ACComplusVerify tool to fix the errors

If the Ac_setup.log file includes either error 1722 or error 2744, run the ACComplusVerify tool. If bad components are detected, remove them. For additional information about how to run this tool and about how to remove bad components, click the following article number to view the article in the Microsoft Knowledge Base:

Repair the COM+ catalog

If the problem continues to occur even after you run the ACComplusVerify tool, this behavior indicates that a COM+ catalog may be corrupted. For additional information about how to repair a corrupted COM+ catalog, click the following article numbers to view the articles in the Microsoft Knowledge Base: For more information about another error that may appear in the Ac_setup.log file and how to resolve the problem, see the "Method 6: Additional error in Ac_setup.log" section that appears later in this article.

Method 5: Determine whether a third-party program is at fault

Some third-party applications seem to cause problems during Application Center 2000 installation. For example, either of the following programs may cause the problem:

• ASPUpload: This program has the following registry key

  ClSID\HKEY_CLASSES_ROOT\CLSID\{12BCCB9B-A6B6-4a47-A643-1C141828415C}

  The REG_DWORD unnamed value of 2 for InprocServer32 causes the problem.
• ASPGrid: This program has the following registry key:

  HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{7100FA7E-2852-4fa5-B4B5-F422034CB1B5}

If the problem continues to occur even after you use the earlier methods, follow these steps:

1. Rename the InprocServer32 key with any other name, and then restart the server. For example, use the name DummyKey.
2. Install Application Center 2000.
3. Replace the dummy key name with the original name, InprocServer32, and then restart the server.

Method 6: Additional error in Ac_setup.log

The following error message may be listed in the Ac_setup.log file For additional information about this error and how to resolve the problem, click the following article numbers to view the articles in the Microsoft Knowledge Base:

The follow error message is displayed in the Ac_setup.log file: A dbmon trace shows the following:

00000250 182.87378513 [2208] 2260, AsaiRoot, acmetaobj.cpp, (699), [18:19:03] [0xC0140079] CAcMetaObj::WriteValues
00000251 182.87390553 [2208] 2260, AsaiRoot, appsrvobjimpl.cpp, (1063),[18:19:03] [0xC0140079] CAppSrvObjImpl::_Save 
00000252 182.87402971 [2208] 2260, AsaiRoot, acapplications.cpp, (600), [18:19:03] [0xC0140079] CAcApplications::CreateSiteApps - saving app
00000253 182.88563896 [2208] 2260, AsaiRoot, appsrvadm.cpp, (93), [18:19:03] [0xC0140079] init apps
00000254 182.88625524 [2208] 2260, AsaiRoot, appsrvadm.cpp, (165),[18:19:03] [0xC0140079] _tWinMain - Service

The problem is that a Web site on the server uses characters that are not valid in Application Center 2000. The following characters are not permitted:

• <
• >
• \
• "
• '
• +
• &
• %
• [
• ]

Rename the Web sites that include characters that are not valid, and then restart the Web service.

Method 7: Previous solutions do not work and you suspect MSDE

If none of the previous steps that are listed in this article resolve the problem, and if you suspect that the problem is because of the Microsoft SQL Server 2000 Desktop Engine installation (MSDE), consider the following:

• If an attempt to install MSDE appears before "Return value 3", the issue may be occurring during the installation of MSDE.
• Try to install Application Center 2000 without the Event and Performance Logging feature turned on. This logging feature tries to install MSDE. During Application Center 2000 installation, click the Custom install option, and then select the Event and Performance Logging check box.
• If the installation succeeds without the Event and Performance Logging feature turned on, the problem occurs during the MSDE installation. The problem may be caused by some of the bits of MSDE that are leftover from the previous removal of Application Center 2000. Remove the leftover files according to the steps that are listed at the beginning of the "Resolution" section.

Method 8: The "SetCLBIdentity" string appears just before "Return value 3"

This situation does not occur frequently. For additional information about what to do in this situation, click the following article number to view the article in the Microsoft Knowledge Base: