I am trying setup Release Management with TFS 2013 using build template "ReleaseTfvcTemplate.12.xaml" but when I set up to carry out the release occurs the following error:
"ERROR: The account running the TFS build service (Domain\User) needs to be added to the system user in the Release Management Server."
The RM is installed on isolated server from the server that is configured Build Controller, however, the machines are within the same domain, and each server has its own user with administator permission to perform the services.
The build server user was added among users of services in RM, and the error continues to occur.
Anyone have any idea how to solve this problem?
Thanks.
One possible cause is that the Release Management client needs to be installed on the machine(s) running the build agent. This gem is hidden away on p26 of the current RM user guide. This won't be a problem for anyone with everything on one server but will need addressing where components are distributed.
Related
When installing Jenkins (LTS) on windows 10 via the installer, after choosing the JDK folder - an error pops when the service is trying to start.
The error reads: "Jenkins failed to start - Verify that you have sufficient privileges to start system services"
Let me make it clear that I DO have sufficient privileges, yet something is not working.
I tried many different suggestions to fix this issue, and read many posts but none helped.
Also, a lot of these posts are getting old and I'm not sure how relevant they are these days.
I found a way to fix this issue, and I'll post it as a suggested answer. This could also work for other installers, but it was only tested with the Jenkins installer.
However, if anyone knows a better way to fix this - please share it with us.
Hope this method will help many people!
Important: If you retried the installation too many times, skip down to "Option 2". The local user account that runs Jenkins may be locked. You will need to unlock that account before attempting either fix below.
This is how I fixed the problem.
Option 1: Re-enter credentials for jenkins user
Please read it all before executing and follow the steps in order:
Delete any Jenkins installation leftovers you currently have
Start the installation process, input your credentials when asked, and continue with the on-screen instructions (including choosing the JDK folder) up until the point where the error is raised.
When the error is raised, >>> DO NOT DO ANYTHING! <<< leave it as it is shown in my question
Now (and only now), open "Services"
Search for the "Jenkins" service. It should be set to "Automatic", but it might be "Disabled"
Open the "Jenkins" properties, and go to the "Log On" tab
Make sure you choose the "This account" radio button, delete the account name and password fields, and enter them AGAIN
Click "Apply"
Go back to the installer and click "Retry"
If everything is according to plan - The installation will now continue without a problem.
This method was tested on a local and VM / AWS computer and worked!
If you still encounter a problem, try changing the startup in step 5 to "Automatic" and make sure you only open "Services" on step 4. "Services" will not update while it is open.
Option 2: Unlock jenkins user account and manually start service
If you encounter the "Service 'Jenkins' failed to start" error too many times, the account on your computer that should run Jenkins will become locked. You will need to unlock that local account first. Keep the Jenkins installation window open with the error message, and then perform the following steps:
Open the "Local Users and Groups" application.
Go into the "Users" folder.
Right-click on the user who will run the Jenkins service, and click "Properties".
Uncheck "Account is locked out". And while you are at it, make sure "Account is disabled" is unchecked as well.
Click OK.
Open the "Services" app on your computer.
Make sure the Jenkins service is set to start automatically.
Right-click the Jenkins service and click "Start". The service should start successfully.
Switch back to the Jenkins installation window with the "insufficient privileges" message still showing.
Click the "Retry" button in the "insufficient privileges" message box. The installer should recognize that the Jenkins service has started.
You should be able to finish the installation.
It didn't work for me until I installed Java Runtime Environment (JRE) 11.
For me wasn't working because java installed was jre-8u301-windows-x64.exe
I installed x86, jdk-8u301-windows-i586.exe and it worked
I had the same issue, I have both jre8, jdk 8 and jdk 11 corretto, I think there are some compatibility issues using these versions of java. I was able to fix it by installing jre mentioned above by #maksym which is this.
The Jenkins versions that I am trying to install are 2.332.2 LTS and 2.345. I am able to successfully install 2.332.2 LTS
I fix it with:
Uninstall all thing what linked with jenkins: foldert where i try to install and installer
Download again the jenkins installer
When i started reinstall next time, i had another issue with not correct jdk version, i downloaded 17.0.4.1 version
After that steps i didn't have previous error (Jenkins failed to start) again
Open cmd prompt as admin
Run
net user administrator
If the property value of Active in the response is No then Run
net user administrator /active:yes
This fixed the issue for me
I am confused by Oracle documentation on how to setup the (ATG) Web Commerce available on the edelivery website.
I would like to get to the step where I have properly set up the admin console.
Running the bin files on a server seems not work for various reasons:
either installation finishes but nothing is working
OR
the installation endlessly asks for arbitrary input.
Also, I want to know if it is possible to setup the server in docker and/or an Amazon Linux EC2 instance.
There are quite a number of steps involved in getting the ATG Admin Server up and running. These start with installing a JDK, Application Server and provisioning a database. Once you have gone through the Installer (which you downloaded from the edelivery site) you need to go through a basic setup process using the CIM tool. The installation process (for ATG 11.3.1) is documented here, while the steps to setup a basic application is documented here.
Working through the steps in the CIM tool, you will end up with a deployable .ear file that you can copy to your application server. Once your application server is started, you will be able to access the Dynamo Admin server.
As of version 11.3.1 ATG is officially supported on Docker. Considering that you compile your own .ear file and it can be deployed to an Application Server (such as Weblogic), Docker support won't necessarily provide you with an ATG Image. It will simply allow you to run your compiled artefact on a Docker container. You are more likely wanting to get hold of a Weblogic Docker Image and deploy your ATG artefact there.
I've been digging for hours and i haven't been able to find what i would think is a pretty common scenario.
I am attempting to deploy a Web Deploy Package to my existing Web Site\Web App via a TFS Release. The location of my existing Web Apps is mapped to a different drive. My source code on my web server is not in C:\inetpub lets say its in D:\MyFiles.
I'm open to using any TFS task to do this. It seems like my two options are:
Run Batch Script - point to myApp.deploy.cmd
WinRm IIS Web App Deployment
I've seen lots of examples of overriding the computer name via the setParamater file but I have not seen one example of how to set the target path for the package?
Again, i want to deploy a web package via a TFS release to D:\MyFiles. I've created the package and it deploys locally to c:inetpub, I would assume if I can get it to deploy to a specified Target location locally then when I run that same. CMD file from TFS release it will use that location on the deploy to server.
UPDATE:
So... this just started working. I'm not sure what the issue was but the WinRm Task didn't do the deploy on Friday but did the deploy on Monday. I'm thinking it may have been related to a FQDN for the server path? Honestly I'm not sure what fixed it or what to do with this post? The answer below by #Andy may help someone so I won't delete it. That link is a good one and it showed me how to perform IIS configuration with Web Deploy.
Thanks in advance,
Greg
Seems you are trying to change the physical path of an IIS site/app using MSDeploy.
Just try adding an additional command (appcmd) to the MSDeploy package manifest to change the physical path of the IIS site during the deployment:
<runcommand path="%windir%\system32\inetsrv\appcmd set app /app.name:"Default Web Site/app12" /[path='/'].physicalPath:C:\temp\app12" waitInterval="5000"/>
Refer to this article for details:
WebDeploy/MSDeploy Quick TIP: Change IIS Site/APP Physical Path with MSDeploy
I am using MS Release management with agent based release templates for my releases.
The releases are getting failed with the following error message and which is randomly happening for different actions in the deployment sequence.
"Communication with the deployer was lost during the deployment. Please make sure (1) the deployer machine has not rebooted during installation and (2) the component timeout is sufficient to copy the files from the drop location to the deployer machine and install the package."
Please note:
1) Deployer machine was not rebooted during the deployment
2) I have created custom components for all actions and made the components' time out to 60 mins
When I restarts the release, it succeeded with out any error. What could be the reason of this error, what is the solution.
Experts please share your views on this.
I think you must have a Encrypted field in your deployment component, just re-enter the value for that encrypted field.
You could refer to this: https://lajak.wordpress.com/2015/12/14/release-management-communication-with-the-deployer-was-lost-during-the-deployment-the-parameter-is-incorrect/
I am trying to setup a build agent to build my Win8 app, which I'm told I should be able to do on a Server 2012 machine.
Everything was going well, until the step told me to stop the build service and run it in 'interactive mode'.
What this appears to do, it make the service run with a command prompt saying "I'm running in interactive mode, press escape when done" (When I pressed escape the build service stopped).
My question is this, if I need to run the build service in interactive mode for win8 builds, how will I cope for the inevitable situation when the server restarts, or some admin logs the user out? presumably the build service will stop.
Is there a better way to handle this?
unless there is a specific reason why you need to run in interactive mode, i was building win8 apps all last year on a 2012 server running with out interactive mode and it ran fine. try it without and see what happens