The installer is made in Visual Studio 2010 (setup project). It is random which dll that it fails on.
Error writing to file: filename.dll. Verify that you have access to that directory.
It works on Windows 7 (x64) sometimes, if I rebuild it it might not work.
This error appears in Windows XP x86 install.
The log did not make more sense to me:
MSI (s) (B0:0C) [14:03:19:342]: Note: 1: 1304 2: filename.dll
MSI (s) (B0:0C) [14:03:19:342]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (54:50) [14:03:19:342]: Note: 1: 2262 2: Error 3: -2147287038
DEBUG: Error 2835: The control ErrorIcon was not found on dialog ErrorDialog
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2835. The arguments are: ErrorIcon, ErrorDialog,
Here is a list of Error Codes:
http://desktopengineer.com/msierrors
Your error code 2835 translates to The control [2] was not found on dialog [3].
Related
I have a console application running on .NET Framework 4.7.1 in Visual Studio 2019 with a Microsoft Visual Studio Installer Project (MSI Installer).
After migrating from packages.config to PackageReference, the .msi installer returns the following error once it collects all installer inputs and begins the install.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2727.
.msi installer created before the migration works fine. The executable and project work fine after the migration. The problem is only with the installer. The problem can be reproduced when installing from the VS 2019 project and from the generated .msi file.
There is an error in the Windows Event Viewer and the installer log:
Event Viewer on remote machine
Product: XXXXX -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2727. The arguments are: _0024F16DE39F4B7D9BF184AC802A7310, ,
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="MsiInstaller" />
<EventID Qualifiers="0">10005</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2021-10-21T19:14:41.779642800Z" />
<EventRecordID>18270804</EventRecordID>
<Channel>Application</Channel>
<Computer>XXXXXX.com</Computer>
<Security UserID="S-1-5-21-3296303954-3414968290-1573956784-1136" />
</System>
- <EventData>
<Data>Product: XXXXXX -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2727. The arguments are: _0024F16DE39F4B7D9BF184AC802A7310, ,</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data>(NULL)</Data>
<Data />
<Binary>7B41433031463831372D434435302D343530332D423239342D3844334438453538323844417D</Binary>
</EventData>
</Event>
MSI Installer Log on local machine
MSI (c) (4C:5C) [16:58:07:070]: PROPERTY CHANGE: Adding INSTALLLEVEL property. Its value is '1'.
MSI (c) (4C:5C) [16:58:07:070]: Note: 1: 2727 2: _7F06229DCDB74690AC0D18DBD0357B3B
DEBUG: Error 2727: The directory entry '_7F06229DCDB74690AC0D18DBD0357B3B' does not exist in the Directory table
DEBUG: Error 2835: The control ErrorIcon was not found on dialog ErrorDialog
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2835. The arguments are: ErrorIcon, ErrorDialog,
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2727. The arguments are: _7F06229DCDB74690AC0D18DBD0357B3B, ,
MSI (c) (4C:5C) [16:58:08:457]: Product: XXXXX -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2727. The arguments are: _7F06229DCDB74690AC0D18DBD0357B3B, ,
Nothing else in the log has the value _7F06229DCDB74690AC0D18DBD0357B3B. This value is the same between installs. This is not the ProductCode or the UpgradeCode in the installer properties.
Setup
Visual Studio 2019 Enterprise
Windows console project (runs as a service)
.NET Framework 4.7.1
Microsoft Visual Studio Installer Project 1.0.0 extension
Installer runs on Windows 10 Pro and Windows Server 2016
What I tried:
Clean and rebuild everything
Manually create all directories the installer is supposed to create
Removed unused dependencies (dlls) from the installer - they were highlighted in red.
Added <SatelliteResourceLanguages>en</SatelliteResourceLanguages> to *.csproj file as suggested by another SO answer
All code is backed up so I can go back to package.config but would prefer not to do so unless no solution could be found.
Note: for whatever reason, the .msi after the migration is almost twice as large as the .msi before migration.
Update
The installer fails right before the Select Installation Folder dialog (which is not shown when the failure occurs).
This is the screen before which the installer fails.
I also tried to revert the branch to before the migration but the revert is not working as the migration changes remain and prevent the installer from working. I had to delete all files and restore them from Git to finally remove the migrated packages and get the installer working.
The solution ended up being to delete the old installer project, migrate to PackageReference, and create a new installer project.
Based on Git, the only differences ended up being the references in the .vdproj file. The new installer was larger than the first but everything else was the same.
Problem
Installer stops working after After migrating from packages.config to PackageReference.
Solution
Delete the installer project (make sure you have a backup).
Do the migration.
Create a new installer project.
Cause
Auto-migration does not update the .dll references in the Installer project.
#eglease did most of the work here as I also would say this happened right after a ProjectReferences conversion.
But I found that I could clear the output and re-add it rather than deleting the whole project that I was also able to clear the error.
Delete these (or maybe just the primary output)
Re-add them:
That cleared the error for me.
installation of VS 2015 Update 3 reported an error installing Windows SDK 10.0.14393.
i found some forum entries about that issue, tipping for separat installation of the SDK. i did so. result:
Blockquote
Installation did not complete successfully.
Log-File shows that the rollback started after
CAQuietExec: Creating UnionWinMD using mdmerge tool
CAQuietExec: MDMerge failed. Please check See MDMerge tool logs at C:\Users\Lothar\AppData\Local\Temp\UnionWinmdWorkingFolder\Logs\27555-MDMerge.log and C:\Users\Lothar\AppData\Local\Temp\UnionWinmdWorkingFolder\Logs\27555-MDMerge.err
CAQuietExec: Error 0x80070002: Command line returned an error.
CAQuietExec: Error 0x80070002: CAQuietExec Failed
CustomAction GenUnionWinMD returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (74:50) [11:34:03:800]: Note: 1: 2265 2: 3: -2147287035
Any suggestions?
My instance of your problem included problems with the KB3165756 Update to Visual Studio 2015, lo these last 2 days. Though I've cleared that (downloaded the VS2015 .iso AND ran it OFFLINE <-- that was key), the 10.0.14393 Windows SDK installer now simply terminates without doing anything. Like you, the 10586 SDK installer went in smoothly.
For the version 10.0.14393.33 this helped me: https://github.com/PowerShell/PowerShell/issues/2571#issuecomment-259671943
You have to download the entire installer package via web-install of SDK. Then go to the folder with downloaded data and edit UserExperienceManifest.xml the described way.
I have a setup which chains 2 MSI files:
Either an x86/x64 MSI file that installs my product.
An x86 MSI file which deploys a third-party toolkit
I wanted the second MSI file to use the same install directory so MSI file 1 stores the user's selected directory in the registry which MSI file 2 then reads and uses as its target.
Fine and dandy - if I install MSI file 1 to C:\Test\ no problem - MSI file 2 picks this up and throws the tool kits into that folder.
When I install to C:\Program Files however... then MSI file 2 gets a bit to clever and decides I must have meant C:\Program Files (x86) and puts the tools in there - a bit messy.
It logs this when it does it:
Action start 16:53:59: AppSearch.
MSI (c) (2C:44) [16:53:59:521]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (c) (2C:44) [16:53:59:521]: WIN64DUALFOLDERS: 'C:\Program Files (x86)\' will substitute 17 characters in 'C:\Program Files\Manufacturer\Product' folder path. (mask argument = 0, the folder pair's iSwapAttrib member = 0).
MSI (c) (2C:44) [16:53:59:521]: PROPERTY CHANGE: Adding INSTALLDIRECTORY property. Its value is 'C:\Program Files (x86)\Manufacturer\Product'.
Action ended 16:53:59: AppSearch. Return value 1.
I am hoping to avoid bloating my setup too much with an x64 version of MSI file 2 (it is in the region of 20 MB), so my question is:
Is there a way I can avoid/disable this behaviour and get my x86 MSI file to trust me and write to "Program Files", not "Program Files (x86)"?
No, it can't be disabled. MSI enforces its rule that a 32-bit package cannot write to 64-bit portions of the file system (and registry).
I have downloaded Visual Studio Community 2013 Update 4 iso file from visualstudio.com to install VS on Windows 8.1 x64 and I have verfied SHA1 checksum of the iso file and the result was correct.
The problem was that setup stops at Applying: Visual Studio Core features and then fail and finalize with
-Error icon and "Visual Studio Core Features -ENU Fatal error during installation"
-Warning icons on three messages which were : "Microsoft Visual C++ 2013 32bit Compilers - ENU Resource Package failed", "Microsoft Visual C++ 2013 Compilers - ENU Resource Package failed" and "Microsoft Visual C++ 2013 x64 Native Compilers - ENU Resource Package failed"
Until now I have done the following :-
1) Disabled Antivirus,Firewall and Anti-Malware before installation and run installation as Administartor.
2) Cleaned %temp%,C:\ProgramData\Package Cache and AppData\Local\Temp folders before installation.
3) Verified all installed .Net frameworks using .Net Framewrok setup verfication utility.
4) Used the system file checker tool to repair missing or corrupted system files as descriped in https://support.microsoft.com/KB/929833 and the result was "Windows Resource Protection did not find any integrity violations".
And found these errors in logs (ERROR is coming from vs_professionalcore.msi) :-
AppData\Local\Temp\dd_vs_community_20141221193705.log
[0B88:12C4][2014-12-21T19:45:57]i000: MUX: Installation size in bytes for package: vs_professionalcore MaxAppDrive: 0 MaxSysDrive: 1821361272 AppDrive: 0 SysDrive: 1335334008
[0B88:12C4][2014-12-21T19:45:57]i000: MUX: Return Code:0x0 Msi Messages:0 Result Detail:RollbackCleanup Restart:None
[0B88:12C4][2014-12-21T19:45:57]i000: MUX: Reset execution Result
[0B88:12C4][2014-12-21T19:45:57]i000: MUX: Reset Result
[0B88:12C4][2014-12-21T19:45:57]i319: Applied execute package: vs_professionalcore, result: 0x0, restart: None
[0E44:1184][2014-12-21T19:45:57]i325: Registering dependency: {96a8b90c-0a91-4e76-ab34-730c23923d11} on package provider: Microsoft.VS.professionalcore,v12, package: vs_professionalcore
[0B88:12C4][2014-12-21T19:45:57]i000: MUX: ExecutePackageBegin PackageId: vs_professionalcoreres
[0E44:1184][2014-12-21T19:45:57]i301: Applying execute package: vs_professionalcoreres, action: Install, path: C:\ProgramData\Package Cache\{E9674444-9491-3961-873C-017D8912185E}v12.0.21005\packages\professionallp\vs_professionalcoreres.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" VSEXTUI="1" INSTALLINGBUNDLE="community" PATCH="C:\ProgramData\Package Cache\{9BA8E822-8889-4826-82CF-41DFE04129EA}\packages\kb2829760\kb2829760-enu.msp;C:\ProgramData\Package Cache\{B7C61168-6AE1-4AF3-BA3D-48D7369C41F2}\packages\kb2829760\kb2829760v2-enu.msp;C:\ProgramData\Package Cache\{ABEF08E8-5C61-42C4-AD64-FC5412586B89}\packages\kb2829760\kb2829760v3-enu.msp"'
[0B88:12C4][2014-12-21T19:47:56]i000: MUX: ExecuteError: Package (vs_professionalcoreres) failed: Error Message Id: 2902 ErrorMessage: The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2902.
[0E44:1184][2014-12-21T19:48:47]e000: Error 0x80070643: Failed to install MSI package.
[0E44:1184][2014-12-21T19:48:47]e000: Error 0x80070643: Failed to execute MSI package.
[0B88:12C4][2014-12-21T19:48:47]e000: Error 0x80070643: Failed to configure per-machine MSI package.
[0B88:12C4][2014-12-21T19:48:47]i000: MUX: Installation size in bytes for package: vs_professionalcoreres MaxAppDrive: 0 MaxSysDrive: 686784512 AppDrive: 0 SysDrive: 31719424
[0B88:12C4][2014-12-21T19:48:47]i000: MUX: Return Code:0x80070643 Msi Messages:2902 Result Detail:0 Restart:None
[0B88:12C4][2014-12-21T19:48:47]i000: MUX: Set Result: Return Code=-2147023293 (0x80070643), Error Message=2902, Result Detail=, Vital=True, Package Action=Install, Package Id=vs_professionalcoreres
[0B88:12C4][2014-12-21T19:48:47]i319: Applied execute package: vs_professionalcoreres, result: 0x80070643, restart: None
[0B88:12C4][2014-12-21T19:48:47]e000: Error 0x80070643: Failed to execute MSI package.
[0B88:12C4][2014-12-21T19:48:47]i000: MUX: ExecutePackageBegin PackageId: vs_professionalcoreres
[0E44:1184][2014-12-21T19:48:47]i318: Skipped rollback of package: vs_professionalcoreres, action: Uninstall, already: Absent
[0B88:12C4][2014-12-21T19:48:47]i000: MUX: Installation size in bytes for package: vs_professionalcoreres MaxAppDrive: 0 MaxSysDrive: 0 AppDrive: 0 SysDrive: 0
[0B88:12C4][2014-12-21T19:48:47]i000: MUX: Return Code:0x0 Msi Messages:2902 Result Detail:0 Restart:None
[0B88:12C4][2014-12-21T19:48:47]i000: MUX: Reset execution Result
[0B88:12C4][2014-12-21T19:48:47]i000: MUX: Reset Result
And this log also in AppData\Local\Temp\dd_vs_community_20141221193705_101_vs_professionalcoreres.log
MSI (s) (54:F0) [19:47:58:111]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (54:F0) [19:47:58:112]: User policy value 'DisableRollback' is 0
MSI (s) (54:F0) [19:47:58:112]: Machine policy value 'DisableRollback' is 0
Action ended 19:47:58: InstallFinalize. Return value 3.
And I have also found these in the same file
MSI (s) (54:F0) [19:48:46:815]: Note: 1: 2318 2:
MSI (s) (54:F0) [19:48:46:820]: No System Restore sequence number for this installation.
MSI (s) (54:F0) [19:48:46:821]: Unlocking Server
MSI (s) (54:F0) [19:48:46:873]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.
Action ended 19:48:46: INSTALL. Return value 3.
What is causing this problem? and how to solve it?,from the logs the error is ERROR 2902 I have googled about it and I didn't find any solutions.
My first guess for the solution of this issue is to set user access control to the lowest value.I found it worked for me.
Probably the issue arises from updates occurences after installation.
You could try to check the
kb2829760 installation in your
C:\ProgramData\Package Cache directory (look at http://support.microsoft.com/en-us/kb/2829760).
In my system I found C:\ProgramData\Package Cache\07D2D6FD53E7EDE1FB612619A11BBCD5530A3E56\packages\vsupdate_kb2829760\vsupdate_kb2829760.exe that I ran with /Uninstall /Force flags (my issue was cleaning up orphaned components of Visual Studio already removed via appwiz.cpl and not displayed in the updates list).
Anyway I suggest to take a deep check at C:\ProgramData\Package Cache. For example, if you look for vs (dir /s /b *vs*)
you could check all GUIDs and paths that sound like probable candidates to cleanup.
UPDATE :-
I have found these in AppData\Local\ dd_vs_community_20141222103227_097_vc_compilercore86res.log
MSI (s) (EC:D0) [10:33:13:227]: Executing op: ActionStart(Name=CreateShortcuts,Description=Creating shortcuts,Template=Shortcut: [1])
MSI (s) (EC:D0) [10:33:13:227]: Executing op: SetTargetFolder(Folder=C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\Shortcuts\)
MSI (s) (EC:D0) [10:33:13:228]: Executing op: ShortcutCreate(Name=kqcv3hvy.win|VS2013 x86 Native Tools Command Prompt,,,FileName=%comspec%,Arguments=/k ""C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\vcvarsall.bat"" x86,WorkingDir=C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\,,,,ShowCmd=1,Description=Open Visual Studio 2013 x86 Native Tools Command Prompt,,,,)
MSI (s) (EC:D0) [10:33:14:309]: Note: 1: 2105 2: -2147024809 3: VS2013 x86 Native Tools Command Prompt.lnk
MSI (s) (EC:D0) [10:33:14:310]: Executing op: ShortcutPropertyCreate(ShortcutName=kqcv3hvy.win|VS2013 x86 Native Tools Command Prompt,PropertyKey=System.AppUserModel.ExcludeFromShowInNewInstall,PropVariantValue=1)
Warning 1909.Could not create Shortcut VS2013 x86 Native Tools Command Prompt.lnk. Verify that the destination folder exists and that you can access it.
DEBUG: Error 2902: Operation ixoShortcutPropertyCreate called out of sequence.
MSI (s) (EC:D0) [10:33:14:315]: Product: Microsoft Visual C++ 2013 32bit Compilers - ENU Resources -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2902. The arguments are: ixoShortcutPropertyCreate, ,
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2902. The arguments are: ixoShortcutPropertyCreate, ,
MSI (s) (EC:D0) [10:33:14:327]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (EC:D0) [10:33:14:328]: User policy value 'DisableRollback' is 0
MSI (s) (EC:D0) [10:33:14:328]: Machine policy value 'DisableRollback' is 0
Action ended 10:33:14: InstallFinalize. Return value 3.
Solution :-
Firstly I give the current user full control over C:\Program Files (x86)\Microsoft Visual Studio 12.0. By clicking right click over the folder properties then security then make sure SYSTEM,Administrators and Users have Full Control and added the current user profile and gave it full control but that didn't solve the problem.
After that I have Found that ComSpec System Variable in Environment Variables value is : %SystemRoot%\system32\cmd.exe;C:\wamp\bin\php\php5.5.12;.Changing the value to %SystemRoot%\system32\cmd.exe; solved the problem.
EDIT :-
Adding the current user profile to C:\Program Files (x86)\Microsoft Visual Studio 12.0. folder caused Error 1316.The specified account already exists when I have tried to uninstall VS 2013 so I deleted that profile then I could uninstall VS 2013 Successfully.
I solved this problem in this way: Firstly, I deactivated the Windows firewall, and then using a free program: Revo Unistaller Pro (http://www.revouninstaller.com/revo_uninstaller_free_download.html), I cleared out the old installation of Visual Studio.
Afterwards, I used CCleaner to manually delete all the components that depend on Visual Studio:
and
Afterwards, from the command line (as administrator) I used this
name like 'microsoft visual%'" call uninstall /nointeractive
to delete the other packages.
note: Repeat for SQL etc by replacing visual% in above command with sql.
Then restart the pc and try to install now Visual Studio.
Best regards
I have implemented an Outlook add in visual studio 2010 using Outlook Add in template and VSTO, I created an install for it using MSI installer (created in visual studio 2010).. I am able to install it on all the machines (x86 and x64).
Recently I tried to install the same exact installer on a machine which has Office 2013 installed on it and getting the following error:
I should emphasize that I haven't changed anything in the system configuration and just installed Office 2013 in addition to what was installed there.
I ran the MSI in "Lv" mode (logging with verbose) and log file doesn't give me helpful information. All it contains is :
=== Logging stopped: 15/02/2013 14:22:04 ===
MSI (c) (20:24) [14:22:04:626]: Note: 1: 1708
MSI (c) (20:24) [14:22:04:626]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (20:24) [14:22:04:626]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (20:24) [14:22:04:626]: Product: Outlook AddIn -- Installation failed.
MSI (c) (20:24) [14:22:04:626]: Windows Installer installed the product. Product Name: Outlook AddIn. Product Version: 1.7.0. Product Language: 1033. Manufacturer: "Company". Installation success or error status: 1603.
MSI (c) (20:24) [14:22:04:626]: Grabbed execution mutex.
MSI (c) (20:24) [14:22:04:626]: Cleaning up uninstalled install packages, if any exist
MSI (c) (20:24) [14:22:04:641]: MainEngineThread is returning 1603
=== Verbose logging stopped: 15/02/2013 14:22:04 ===
Thanks for help in advance...
Usually add-in installers also package PIA prerequisites, to install when missing. That is why the message says to run "setup.exe" instead of the MSI directly.
The prerequisites install before the main package, i.e. the MSI, and this is handled only by the "setup.exe" file.
If the project is configured for Office 2013 too than VS should have included the appropriate prerequisites in the package and running setup.exe should install them. Try that and see how it goes.