I am getting the following error while running a workflow in microsoft release management 2013 update 4:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.AggregateException: One or more errors occurred. ---> Microsoft.TeamFoundation.Release.Common.Helpers.OperationFailedException: System.AggregateException: Failed to install 'VisualStudioRemoteDeployerbd3a8a59-325a-45d0-89f5-86a548554a12' from service executable path VisualStudioRemoteDeployer.exe . Consult the logs below:
c:\Users\vmadmin\AppData\Local\Temp\mfurnl9w.0.cs(95) : ; expected
c:\Users\vmadmin\AppData\Local\Temp\mfurnl9w.0.cs(94) : IntPtr policyHandle = IntPtr.Zero;
c:\Users\vmadmin\AppData\Local\Temp\mfurnl9w.0.cs(95) : >>> var attributes = new LSA_OBJECT_ATTRIBUTES()
c:\Users\vmadmin\AppData\Local\Temp\mfurnl9w.0.cs(96) :
I am using a vNext Release Template. I have added an action "Deploy using PS/DSC" which is supposed to execute a powershell script on the machine.
All I get is the above error.
I have verified that remoting is setup as per here (on-premise section): https://www.visualstudio.com/en-us/get-started/deploy-no-agents-vs.aspx
I have also referenced this: http://roadtoalm.com/2015/02/04/start-with-visual-studio-release-management-vnextvs-rm-for-dummies/
but our error is slightly different as it doesn't complain about the account. Although i am assuming the account is ok... I did use a couple variations and when the account is incorrect i get an obvious failure.
any help would be appreciated.
I found this question because I had the same issue. In RoadToAlm article he is using Windows Server 2012 on his VM. My Azure VM was Windows Server 2008 SP2 and I resolved the issue by installing Windows Management Framework 3.0 (http://go.microsoft.com/?linkid=9811175) which includes a newer Powershell than was installed on my server. After this update the issue was resolved.
I was facing the same issue on a destination Windows Server 2008 R2. I just shift down the UAC level and it let the deployment tools be copied by the task into the c:\Windows\DtlDownloads folder (with VisualStudioRemoteDeployer.exe).
From the moment this file was available, the artifact copy had been successful.
Related
I'm using an 'Install MSI' task to install an msi file as part of a deployment. The task is throwing the error:
2022-02-22T06:42:35.0716371Z ActionData: Updating component registration
2022-02-22T06:42:35.0839323Z ##[error]Unable to process command '##vso[task.logdetail id=5c578bc6-8e75-4147-992e-fe8cd643eaa2;parentid=00000000-0000-0000-0000-000000000000;name=;type=release;order=1]Updating component registration' successfully. Please reference documentation (http://go.microsoft.com/fwlink/?LinkId=817296)
2022-02-22T06:42:35.0888633Z ##[error]Name is required for this new timeline record.
I'm using Azure DevOps on a local Team Foundation Server for the build and deploy process. From the error message I can see that the 'Name' parameter is missing. The deployment works fine when I'm installing to physical machines, but gives the above error when I'm installing to virtual machines.
There were apparently lots of people who had variants of this issue back in 2016, like this guy on social.msdn or this guy on github or this guy on SO. Apparently in 2016 it was possible to turn off "Record project details", however this option is not available in newer versions of Azure Devops.
Does anyone know how to fix this issue in newer versions of Azure DevOps?
Versions: Azure DevOps Server 2020 Update 1.1, Agent 2.153.1, Install MSI 0.1.20.
More a workaround than an answer, but I ended up switching the 'Install MSI' task to a regular 'Command line ' task.
Using the command line with the 'msiexec' command lets you install msi files just as easily as using the 'Install MSI' task.
We have just uninstalled Docker Community Edition and installed Enterprise Edition on a Windows Server 2016 System as per these steps.
On reaching the last step which is to test a hello-world container we are receiving the following error:
C:\Program Files\Docker\docker.exe: failed to register layer: re-exec
error: exit status 1: output: ProcessUtilityVMImage
\?\C:\ProgramData\Docker\windowsfilter\e345ad40cc8f7d073f62501b7445d42d677889c04b2c6fe0963ea6e092b52f95\UtilityVM:
The process cannot access the file because it is being used by another
process.
We are seeing lots of examples on SO related to other types of applications giving this error but not Docker.
How might we fix this?
This turned out to be an issue related to Symantec Endpoint Protection(SEP) clashing with Docker.
SEP needs to be upgraded to version 14 RU1 and several files need execution privileges.
Symantec posted a fix here: https://support.symantec.com/en_US/article.TECH246815.html which we have tried and worked.
I am trying to run a service stack application, it works fine on my dev machine when deployed on another box, I get System.PlatformNotSupported exception.
Stack trace below:
Unhandled Exception: System.PlatformNotSupportedException: Operation is not supported on this platform.
at System.Net.HttpListener..ctor()
at ServiceStack.Host.HttpListener.HttpListenerBase.Start(IEnumerable`1 urlBases, WaitCallback listenCallback)
at ServiceStack.Host.HttpListener.HttpListenerBase.Start(String urlBase)
at ExcaliburAppHost.Program.Main(String[] args)
I am trying to build a Restful app with self hosting (with no IIS support on the other box).
var listeningOn = args.Length == 0 ? "http://*:8090/" : args[0];
var appHost = new AppHost()
.Init()
.Start(listeningOn);
error occurs in AppHost().Start() method
If you have any unmanaged .dlls e.g. sqlite3.dll you may need to set the Platform Target of your project as x86.
You can also try running the Console App as Administrator / sudo in-case it's a permissions issue.
To whom facing with exception "System.PlatformNotSupportedException: ServiceController enables manipulating and accessing Windows services and it is not applicable for other operating systems." - in my case I had to add "System.ServiceProcess.ServiceController" NuGet package to my .net 5 Worker Service project and issue is gone.
For me, I was building a .NET 6 worker service in a Docker container on a Linux host, building a Windows service to run on Windows Server 2016. My csproj file has the following properties set, but I was receiving the same PlatformNotSupportedException as the OP:
<TargetFramework>net6.0</TargetFramework>
<Nullable>enable</Nullable>
<ImplicitUsings>enable</ImplicitUsings>
<OutputType>Exe</OutputType>
<InvariantGlobalization>true</InvariantGlobalization>
<PublishSingleFile>false</PublishSingleFile>
<SelfContained>true</SelfContained>
<RuntimeIdentifier>win-x86</RuntimeIdentifier>
<PublishReadyToRun>false</PublishReadyToRun>
I was able to resolve this by specifying the runtime option (-r win-x64) directly to the dotnet publish command in my Dockerfile.
Now the application builds from a Docker container running on a Linux host, but the resulting binaries run fine on the Windows Server 2016 platform.
I'm installing sonarqube on Windows Server 2012.
I have followed the following steps:
Downloaded sonarqube4.4 and extracted to C:\Sonarqube
Downloaded Java JDK 1.7.0_60 and jre 1.7.0_67 as well as jre7
Installed Windows SDK 7 and .NET Framework 4
Navigated to C:\sonar\bin\windows x86-64 and ran StartSonar.bat as an administrator, this ran ok with no output and Ihad to hot ctrl- Z to break
I then ran \windows-x86-64\InstallNTService.bat as an administrator and I am seeing the sonarQube services was launched, but failed to start.
Not sure what the problem is.
I believe you first ran \windows-x86-64\InstallNTService.bat successfully and then StartSonar.bat unsuccessfully (the inverse order of what you describe).
You probably have [this problem]: http://qualilogy.com/fr/wp-content/uploads/sites/2/2013/09/Sonar_ServiceLaunchError2.jpg
Windows could not start the Sonar service on Local Computer.
Error 1067: The process terminated unexpectedly.
In that case, the solution is to change the user/rights to launch the Sonar service: https://qualilogy.com/en/migrate-sonarqube-tomcat-to-windows-service/
Go to the Services window, find the Sonar service, and open the Properties windows to change the user it logs on as to one with sufficient permissions.
I was able to solve this problem by creating a new folder named “Temp” in C:\Windows\System32\config\systemprofile\AppData\Local\
The Log-File will show only
--> Wrapper Started as Service
Cleaning or creating >temp directory C:\Program Files (x86)\SonarQube\sonarqube\temp
<-- Wrapper Stopped
The SonarQube service was launched, but failed to start.
After a long search, I came up to this site http://zen-and-art-of-programming.blogspot.de/2013/03/installing-and-running-sonar-source.html.
Solution:
Navigate to C:\Windows\system32\config\systemprofile\AppData\Local\ and create the directory Temp
2: Set the user rights to full access
3: Run the StartNTService.bat
I have a Windows 2003 SP2 Virtual Box guest in which I'm trying to install Portal Express 7.
During the installation there's a prompt that said that the Server couldn't start and I have to that manually. When I try to start it using startServer.bat I get every time this message:
ADMU3011E: Server launched but failed initialization. startServer.log,SytemOut.log(or job log in zOS) and other log files under C:\IBM\WebSphere\AppServer/profiles\default\logs\server1 should contain failure information.
ADMU7704E: Failed while trying to start the Windows Service associated with server: WebSphere_Portal;probable error executing WASService.exe: com.ibm.ws.management.tools.ProblemInWASServiceException: ADMU7711E: Unexpected exception associated with WASService.exe: exitCode = -1 during processing of server with name: WebSphere_Portal
In the logs I only found java.lang.NoClassDefFoundError:com/ibm/ffdc/impl/EmptyProvider$EmptyFfdc and several verbosegc.txt files. Have anyone succeeded in installing IBM WP 7 on Windows 2003?
PS: My problem is very similar to this DeveloperWorks post.
If you can start it manually but not through Windows Service, perhaps something got corrupted into the service definition. No problem, you may very simply remove it (WASService.exe -remove servicename in AppServer/bin directory ), and then add it again
I use a syntax like this one
wasservice -add "Cluster1_server1" -serverName "Cluster1_server1" -profilePath "D:\IBM\WebSphere\AppServer\profiles\AppSrv01" -wasHome "D:\IBM\WebSphere\AppServer" -stopArgs " -username youradmin-password yourpassword" -encodeParams
or you may also insert username and password into soap.client.props, so you don't need to change it all the times.