Error 2755.server Returned Unexpected Error
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sun, 09 Oct 2016 16:29:58 GMT by s_ac4 (squid/3.5.20)
Windows Installer (MSI) Windows Installer (MSI) Error Messages Help with MSI (Microsoft Installer) error 2755: Server returned unexpected error [2] attempting to install package [3]. 0 Comments [ + ] Show Comments Comments Please log in
Error 2755 Server Returned Unexpected Error 1639
to comment Rating comments in this legacy AppDeploy message board thread won't reorder them,so
Error 2755 Server Returned Unexpected Error 1624
that the conversation will remain readable. Answers 0 Where 2 is the error and 3 is the setup trying to install. The the authentication server returned an unexpected error error (2) is most often reported as 1632 ("The Temp folder is either full or inaccessible. Verify that the Temp folder exists and that you can write to it.") This error may occur if there are insufficient http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/error-message-error-2755-server-returned/adba2ba5-e905-40d5-8cd9-3b7a7c241303 privileges on the %windir%\Installer folder, or the inability of the Windows Installer service to create the %windir%\Installer folder. NOTE: This behavior can also occur if you have only Read permissions to the Winnt folder. This condition prevents the Installer folder from being created by Setup. If installing from a mapped drive letter in a terminal services session: "Windows 2000 and earlier operating systems do not support passing mapped drive letter information between terminal server http://www.itninja.com/question/help-with-msi-2755 sessions. Since Windows Installer service runs as a service in the console session, mapped drive letters established in remote sessions are not visible to Windows Installer service, resulting in this error. This only applies when running the service in Application Server mode, not Remote Admin mode." Note that this limitation no longer exists in Windows XP and later operating systems. For "Internal Error 2755: Please contact product support for assistance" see Microsoft knowledge base article 251274 for a solution/hotfix. One member offers, "I ran across this when attempting to install using an MSI which had been encrypted using EFS. I'm guessing msiexec uses an account which cannot access my encrypted files. Decrypting the file resolved this error." Answered 03/07/2004 by: AppDeploy.com Please log in to comment Please log in to comment Answer this question or Comment on this question for clarity AnswerSubmit Don't be a Stranger! Sign up today to participate, stay informed, earn points and establish a reputation for yourself! Sign up! or login Share Related Questions Anyone using K1000 for Windows 10 Anniversary Update? Can anyone identify why this script would fail to work properly? VBScript to add New Feature in MSI Table Jetbrains dotpeek 2015.2.2 packaging issue setup.ini options i need to deploy application in command prompt as a admin using psexec Windows Logo Testing warnin
CD! Parham04-17-2005, 03:38 AMHello, I have an installtion and no problem with installing from hard disk, But when https://community.flexerasoftware.com/archive/index.php?t-146975.html i copy the entire DISK1 folder to a CD and install from it,this error occurs after ready to install: Internal Error 2755.1639,D:\My Application - Alpha.msi here http://www.symantec.com/connect/forums/error-installing-sep-110-windows-server-2008-ent-edition-64-bit is the log: Action ended 13:15:03: SetupProgress. Return value 1. Action start 13:15:03: ExecuteAction. Info 1639.Invalid command line argument. Consult the Windows Installer SDK for detailed unexpected error command line help. PERSYS_SERVER_A" DEBUG: Error 2755: Server returned unexpected error 1639 attempting to install package D:\PERSYS Server - Alpha.msi. Internal Error 2755. 1639, D:\PERSYS Server - Alpha.msi MSI (c) (9C:94): Product: PERSYS Server - Alpha -- Internal Error 2755. 1639, D:\PERSYS Server - Alpha.msi Action ended 13:15:08: ExecuteAction. Return value 3. Action returned unexpected error start 13:15:08: SetupCompleteError. Action 13:15:08: SetupCompleteError. Dialog created Action ended 13:15:09: SetupCompleteError. Return value 2. Action ended 13:15:09: INSTALL. Return value 3. Why? anitabs04-19-2005, 04:50 AMError 2755 is a generic or system-specific error. This error occurs on some systems triggered by the combination of how the setup is run on certain machines and how the machines are configured internally. Following is a list of common causes of this error: 1.There is a corrupted version of Windows Installer engine on the machine. 2.The installation does not have access to the Temp directory or if the default Temp directory of the machine is not clean or does not have enough space to run the setup. 3.The installation is being run over a terminal Server via a mapped network drive. 4.The installation is unable to create or write to the Installer directory in a Windows NT system environment. 5.The installation has some custom actions that are not configured prope