Event ID 1015 Source MsiInstaller
| Event ID | 1015 |
| Source | MsiInstaller |
| Type | Warning |
| Description | Failed to connect to server. Error: <error code> |
| English, please! | Request a translation of the event description in plain English. |
| Concepts to understand | What is the role of MsiInstaller? |
| Comments |
Vince
(Last update 10/15/2007): I had these same issues and tried the fixes mentioned here and none of them worked. I eventually found a program that helped with this problem. It is called Dial-a-fix. See the link below to download it. I ran several diagnostics but I think the one that solved the problem was the Repair Permissions tool. Things are back to normal now. Sven Berend (Last update 6/13/2007): In my case, going under "HKLM\Software\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs" and removing any entries for "dll" files solved the problem. There was only one entry: "C:\WINNT\NiAMH.dll" (NetInstall). W. Cox (Last update 12/17/2006): In our case, we have a Windows XP SP2 box on which we could not install or uninstall any application. We also had difficulties changing power options / display options in the Control Panel even though my domain user account was set as a local administrator on the PC. In addition, when I went to disjoin & rejoin from the domain, it kept saying access is denied. I could not even join a Workgroup. Finally, I uninstalled and reinstalled Client for Microsoft Networks and everything is working fine again. Jan Mokken (Last update 1/31/2006): - Error code: 0x80080005 (Error code 0x80080005) - Check if the following register keys exist: [HKEY_CLASSES_ROOT\CLSID\{000C103E-0000-0000-C000-000000000046}] @="PSFactoryBuffer" [HKEY_CLASSES_ROOT\CLSID\{000C103E-0000-0000-C000-000000000046}\InProcServer32] @="C:\\WINNT\\system32\\msi.dll" "ThreadingModel"="Both" If not, try adding them and re-run a msi package. Mihai Andrei (Last update 1/11/2006): - Error code: 0x800401F0 (Error code 0x800401F0) - See M907341. - Error code: 0x80004001 (Error code 0x80004001) - See M911682. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! Ionut Marin (Last update 11/27/2005): - Error code: 0x800401F0 - See "Veritas Support Document ID: 264390" and "Veritas Support Document ID: 267742" for details on fixing this problem. - Error code: 0x80004005 (Error code 0x80004005) - See "Sophos Support Article ID: 3418" if you tried to install Sophos AutoUpdate component of Sophos Anti-Virus Small Business Edition (SBE). - Error code: 0x80070422 - Read McAfee Solution ID kb44710. Go to the McAfee Knowledge Search page and search for this solution to read it. M223300 provides information on how to enable Windows Installer logging. M555175 provides information on how to resolve common "Windows Installer" problems. Dmitriy Zavgorodniy (Last update 4/25/2005): - Error code: 0x800706BA (Error code 0x800706BA) - This problem occurred when I tried to Add/Remove options for Office 2003 SP1. Check the status of the service "DCOM Server Process Launcher", if it's disabled, change the mode to automatic, and start it. Steve (Last update 1/21/2005): - Error: 0x800401F0 – This error appeared in the event log when I was trying Veritas Backup Exec 9.1 push installations of Remote Agent for Windows Servers on Windows XP workstations. Backup Exec also reported Access Denied errors. Servers and Win2k workstations installed without a problem so it was obviously an XP issue, and it turned out to be related to Windows XP Service Pack 2. Veritas has the problem addressed in “Veritas Support Document ID: 270144”. It seams that only local installations are possible to Windows XP SP2. Read the article for more details on this issue. Anonymous (Last update 1/21/2005): I was getting the same message as contributor Steve when I was trying to push out BE 9.1 Remote Agent from a 2003 to a 2000 server. “Veritas Support Document ID: 265736” addresses this issue and provides information on how to do a manual/silent install of the Veritas Backup Exec 9.x Remote Agent for Windows Servers if the push install does not succeed. Read “Veritas Support Document ID: 272082” for additional information on this event. Arkady Karasin (Last update 9/21/2004): I received this event while trying to perform a remote installation of VERITAS Backup Exec Remote Agent to a Win2k3 DC. You can install Remote Agent by following this Veritas article: Veritas Support Document ID: 258982. Sysadmin (Last update 7/28/2004): I got event ID 1015 when trying to install Veritas Backup Exec 9.1 Premium on a Windows 2003 Small Business Server. The solution was extract the software image (downloaded from veritas.com) to a directory on the system disk, and run the install from there. Trying to install from any other location than the system disk (data partition, CD) failed. Rudy (Last update 4/13/2004): If “msiexec /regserver” fails, refer to M315346 method 2 which shows you how to reinstall the Windows Installer. This worked great for me. Bhasi (Last update 3/24/2004): Error code: 0x80080005 (Error code 0x80080005) - Just re-register the MSI installer with following command: Msiexec \regserver. This should fix the issue. Alejandro Guerrero (Last update 10/28/2003): In my case, this problem appeared when I was trying to install VERITAS Backup Exec 9.0 rev. 4454 on a WinNT server, some months after a Nimda Virus clean. In order to succeed with the install I had to add the SYSTEM and the INTERACTIVE account in dcomcnfg.exe for the default permissions. Then, installation worked like a charm. Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! R. Hop (Last update 8/31/2003): While adding a MSI-package to a group policy object you get the error: Add operation failed. Unable to extract deployment information from the package. Run validation on the package to ensure the package is correct. The GPO cannot be created In eventlog you find EventID 1015. Check if the MSI package you are trying to add to the GPO is on the server you are logged in to. If this is the case: log on to another server and try it again. See M324886. James MacMicking (Last update 8/31/2003): This problem can also occur when the System account is not given access to the system drive. When changing permissions from "Everyone" make sure you add System with Full Access. See M315346. Hannes Schmidt (Last update 4/29/2003): Error code: 0x80040154 (Error code 0x80040154) - My symptoms were that no program was associated with MSI files and some setup.exe reported that they couldn't connect to Windows Installer. Re-registering the msiexec service worked for me. Anonymous (Last update 4/24/2003): Error: 0x800401F0 - This issue has been addressed by Microsoft. See M294014. Eric W. Bowers Error: 0x80004001 = "The method is not implemented" - Accompanied by the following text in a message box entitled according to the software package in error(in this case "Network Associates GroupShield Exchange Installer"): Configuration file "" successfully created. Please run installer locally to complete installation. Network Associates' suggested fix for this issue does not resolve it. Prevents any new software from being installed on the machine because the installer thinks it is in the middle of an install. Rjagde Error code: 0x8007005 = "Access denied" - See Error code 0x8007005 for general information on this error. Thomas Wagenhauser Error: 0x80070422 I am getting this error quite often along with a 1001 error for "feature ProductNonBootFiles failed during request for component". Then my Win2k Terminal Services Server locks up. I believe it has to do with a faulty install of Office2k. Check M243400. Abel Error: 0x800401F0 = "CoInitialize() has not been called." From Microsoft: The error may mean CO_E_NOTINITIALIZED, indicating that CoInitialize() has not been called. From newsgroups: after installing Visio 2002 sr-1 on Windows 2000 or Windows XP, not necessarily located on a network, this event may rise everytime Visio 2002 is started or an object from it is opened or viewed in another application. Simon A. Frank In certain conditions, to fix this problem, re-register service: msiexec /unreg msiexec /regserver Why bother deciphering Event logs when GFI EventsManager can do everything for you? Free trial here! |
| Links | M223300, M243400, M294014, M315346, M324886, M555175, M907341, M911682, Error code 0x80004005, Error code 0x80004002, Error code 0x80040154, Error code 0x800401F0, Error code 0x80004001, Error code 0x800706BA, Error code 0x80080005, Veritas Support Document ID: 264390, Veritas Support Document ID: 258982, Veritas Support Document ID: 267742, Veritas Support Document ID: 270144, Veritas Support Document ID: 265736, Veritas Support Document ID: 272082, Sophos Support Article ID: 3418, McAfee Knowledge Search, Dial-A-Fix Download Page |
| Search | Google Web - Microsoft Support - Bing - EventID.Net Queue - More links... |
| Feedback | Send comments - Notify me when updated |
| Print version |