I have to update our build-system from the old "XML-System" to the newer vNext.
Now I have the problem, that in a build progress, I'm getting errormessages from ligther.exe:
[error]light.exe(0,0): Error LGHT0217: Error executing ICE action 'ICE01'. ...
up to ICE07.
And at the end:
[error]light.exe(0,0): Error LGHT0216: An unexpected Win32 exception with error code 0x643 occurred: Action - 'ICE09' Fatal error during installation
When I make the same build with the "old" XML-Version it works without any problems, any ideas?
Thanks a lot.
Kriz
According to the error prompting message: An unexpected Win32 exception with error code 0x643 occurred: Action - 'ICE09' Fatal error during installation
It's probably a permissions problem with validation. You could try to give the build service account more privileges such as local administrator permission on the build agent.
Besides, there are no tools to convert XAML build definition to vNext directly, so please double check you have manually created fully in a accord.
I saw this issue only on the build machine, where the build task has no admin rights.
I didn't saw this on my developer machine, where I have admin rights. This error is written by the light.exe, which is the Windows Installer XML linker contained in the Wix Toolset.
In order to solve this I suppressed validation of the light.exe. This can be done in two different ways:
On the commandline of light.exe
-sval
On the commandline, when using WixSharp
Compiler.LightOptions = "-sval";
Related
Using Visual Studio 2019 to publish an update to an existing windows store application. This worked a week ago.
Our solution builds without error. When I go to create the setup package I get an error "Failed to sign 'D:\dev\MeyerMusic\MeyerTablet\TabletDistribution\bin\AnyCPU\Release\MeyerMusicTabletSetup_2.6.6.0_AnyCPU.msix'."
We are distributing the application as a Microsoft Store app under the existing app name.
Last week on this same development computer I built version 2.6.5 as well as many packages before that.
The error number is blank or missing. I do not have a reason for the failure. I only see one fact in the error message and that points to line 4574 in the file: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets
That line is this:
<SignAppxPackage Condition="'$(AppxPackageSigningEnabled)' == 'true'"
AppxPackageToSign="$(AppxMainPackageOutput)"
CertificateThumbprint="$(PackageCertificateThumbprint)"
CertificateFile="$(PackageCertificateKeyFile)"
CertificatePassword="$(PackageCertificatePassword)"
HashAlgorithmId="$(AppxHashAlgorithmId)"
EnableSigningChecks="$(EnableSigningChecks)"
SignAppxPackageExeFullPath="$(SignAppxPackageExeFullPath)"
TempCertificateFilePath="$(TempCertificateFilePath)"
VsTelemetrySession="$(VsTelemetrySession)"
SigningTimestampServerUrl="$(AppxPackageSigningTimestampServerUrl)"
SigningTimestampDigestAlgorithm="$(AppxPackageSigningTimestampDigestAlgorithm)"
/>
Troubleshooting steps:
Attempted to build a side load package. Results in same error
Successfully built a side load package that was not signed
I have restarted Visual Studio
I have rebooted the machine
I have deleted OBJ, BIN for the entire solution
I have looked for errors in the event log but none have been found so far.
After uninstalling KB4535996 the problem was resolved.
I found this via a tip from the following post: https://developercommunity.visualstudio.com/content/problem/934967/uwp-error-failed-to-sign.html
I am trying to run an incremental migration using the VSS Upgrade tool. I'm migrating through the command prompt.
I have in the past successfully migrated all our projects and history to TFS, I have also checked in incremental migrations. However, now that I'm doing it for a 3rd time I get an error.
As far as I know nothing has changed. Any general tips in how I could go about debugging this would be helpful.
The error I get when running the vssupgrade migrate settings.xml command.
ERROR: Retrieving the COM class factory for component with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E)
Looking into the log file created by the analyze tool the error looks like this:
[VSS, Error, 3, 2019/03/20 11:23:56.676] Exception: System.IO.FileNotFoundException
Message: Retrieving the COM class factory for component with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E).
Stack Trace: at Microsoft.TeamFoundation.Admin.VssMigration.VssConverter.OpenVss(String sourceRepository, String passwd)
at Microsoft.TeamFoundation.Admin.VssMigration.VssConverter.Initialize(ExecutionMode executionMode, MigrationSession migrationSession)
at Microsoft.TeamFoundation.Admin.VssMigration.Api.MigrationSession.PrepareForProcessing(ExecutionMode executionMode, Boolean requireUserMapFile)
at Microsoft.TeamFoundation.Admin.VssMigration.Api.MigrationSession.Migrate()
at Microsoft.TeamFoundation.Admin.VssMigration.CommandLine.VSSUpgradeCommand.MainThread()
Help Link:
BaseExceptionMessage: Retrieving the COM class factory for component with CLSID {783CD4E4-9D54-11CF-B8EE-00608CC9A71F} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E).
COM interop fails when the convertor runs under x64, the trick that may work is to start the conversion from a forced 32-bit command prompt, which you can start through:
c:\windows\SysWOW64\cmd.exe
That should give you a forced 32-bit context:
Another alternative is to change the corflags to force the convertor to x86 at all time:
corflags /32bit+ vssupgrade.exe
My solution was to repair Visual Source Safe Upgrade Tool for Team Foundation Server. I re-downloaded the application link from Microsoft's website
And then run and Repair the application. That fixed my issues.
In Team Foundation Server 2015 Build (on-premise), I'm having issues running simple command line commands. All Command Line tasks simply fail with the following error: "File not found: ".
Take for example the following build definition:
This is executed using an on-premise Build Agent and will fail with the following exception in the logs:
BUILD FAILED
2016-01-20T12:04:47.5127709Z ##[warning]Filename doesn't indicate a full path to a executable file.
2016-01-20T12:04:47.5127709Z Executing the following commandline. (workingFolder = D:\_work\2\s)
2016-01-20T12:04:47.5127709Z date
2016-01-20T12:04:47.5127709Z Error message highlight pattern:
2016-01-20T12:04:47.5127709Z Warning message highlight pattern:
2016-01-20T12:04:47.5439748Z ##[error]File not found: date
Of course this is a simplified example where I simply want to output the current date using the date /t command. But the same problem occurs with all general command line commands which I've tried, such as dir, time, path etc. The MSDN does not provide any troubleshooting info on it, other than that the tool executed must reside in the PATH variable.
The issue is not specific to one build definition or repo; it can be reproduced on others as well.
The builds run as the built-in svc_tfsbuild account.
I'm perhaps thinking this is either a simple setting, or - wildly guessing - an issue related to rights, but cannot find any documentation where to look or what to check. Any help would be appreciated.
It appears this is a known issue on MS Connect as well.
In short a MSFT mentions the following:
Commands that are built-in to command prompt don't work. Anything resolvable based on your PATH/PATHEXT will work.
In the comment from 27 Oct, 2015 it is stated that this will be fixed in the next sprint. The mentioned workaround for now is simply executing cmd.exe first and provide the rest as arguments.
Using the example from the original question this would lead to:
Tool: cmd.exe
Arguments: /c "date /t"
And I can indeed confirm this works.
I just downloaded and installed Xamarin and selected the ASP.NET MVC template. I haven't touched anything. When I build the solution I get the following error:
Could not add packages.
"The specified task executable "Csc.exe" could not be run. Access is denied (MSB6003)".
This is at the end of messages displayed on the Package Console:
Added file 'packages.config'.
An exception was thrown while dispatching a method call in the UI thread.
I'm running Windows 8.1 and Visual Studio Community 2015.
Any ideas?
when i run Msbuild web.csproj i get the following error:
AfterBuild target> -> C:..\web\obj\debug\csautoparameterize\original\web.config
: error ASPconfig: an error occurred
loading a configuration file:
Directory C:..\web\obj\debug\csautoparameterize\original\Configs'
does not exist. Fail to start
monitoring file changes.
if i open visual studio (2010)..clean solution and rebuild, its fine. if i try to do publish via visual studio, this error returns and i cant build again (until i clean solution).
any ideas?
thanks
Is that a network drive? I was getting a similar error when I had my SVN working copy on a network drive, apparently the folder monitoring service for the test server completely freaks out when it's not a physical drive.