• 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.

Back to the top

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

Back to the top

Method 2: Manually remove leftover files

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.

Back to the top

Method 3: Install from Setup.hta

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.

Back to the top

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

Use the ACComplusVerify tool to fix the errors

Repair the COM+ catalog

Back to the top

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

• 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}

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.

Back to the top

Method 6: Additional error in Ac_setup.log

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

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

• Msxml3.dll
• Msxml3a.dll
• Msxml3r.dll

Back to the top

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

• 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"

Back to the top