I am using the datastax-community-64bit_1.2.5.msi for installing on Windows VM. I am using the silent install command
msiexec /i
C:\ddapplications\cassandra\datastax-community-64bit_1.2.5.msi /quiet
/qn /le C:\ddapplications\cassandra\installlog.txt
If I run the installation command from the command line it installs as expected. No issues.
If I run the command from a Windows Service that runs as LocalSystem, I get the following error.
Is this a known issue? Is there a workaround? I also manually tried creating a group named WORKGROUP and adding the SYSTEM user to that group.
The SYSTEM user exists in the VM.
=== Logging started: 6/7/2013 23:52:23 === Error 1609. An error occurred while applying security settings. WORKGROUP\SYSTEM is not a
valid user or group. This could be a problem with the package, or a
problem connecting to a domain controller on the network. Check your
network connection and click Retry, or Cancel to end the install.
Unable to locate the user's SID, system error 1332
=== Logging stopped: 6/7/2013 23:52:25 ===
Is your VM in a domain? What is the service that you are using to trigger the installer running as?
A possible workaround may be to make that service run as Administrator.
Related
I am periodically getting the below error when running docker build . for a windows container. Only thing i've found that can fix it is a complete system reboot. Hoping there's some other way to fix this. Any ideas?
CreateComputeSystem 194bb656d998902d6a1cacabc8f6213df878a70bf9644bb5726a5339b5644f1e: Logon failure: the user has not been granted the requested logon type at this computer.
(extra info: {"SystemType":"Container","Name":"194bb656d998902d6a1cacabc8f6213df878a70bf9644bb5726a5339b5644f1e","Owner":"docker","IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\\ProgramData\\Docker\\windowsfilter\\194bb656d998902d6a1cacabc8f6213df878a70bf9644bb5726a5339b5644f1e","Layers":[{"ID":"0d961d17-3e59-57ec-b577-e2fa46e415f7","Path":"C:\\ProgramData\\Docker\\windowsfilter\\a80dd368b3b7cbd9ca1d9ee09f13abda58f99ee3eae3bb608d6c56807739b931"},{"ID":"3d9a0621-57cb-56d8-a59d-98c748f857b3","Path":"C:\\ProgramData\\Docker\\windowsfilter\\b5b087f9597cb06979e26e9fc1a4439001d72a4f9ab728e3c0fae6bb6ca1f386"},{"ID":"2928a4c9-75fe-5800-920a-c63965ccb3e3","Path":"C:\\ProgramData\\Docker\\windowsfilter\\d43421924da6b091e73c586c0635a8a12acacc34ea69a158d1050120c9b4224b"},{"ID":"b8d1ec89-66da-5527-a5f1-15717cd70b32","Path":"C:\\ProgramData\\Docker\\windowsfilter\\7c34e9529e612efe1d517ee3cbb6ca41ca98192b10bb0013aa168bd15b9df836"},{"ID":"5cf70ece-e2bd-5203-942a-75ce472653b2","Path":"C:\\ProgramData\\Docker\\windowsfilter\\e3112b599c90232a36498cd01af8208bdda3c0ae3f28a37eaaf810d75534f753"}],"HostName":"07b2112c2753","HvPartition":true,"EndpointList":["3af7ee72-3894-48ce-9259-fdc853db87da"],"HvRuntime":{"ImagePath":"C:\\ProgramData\\Docker\\windowsfilter\\e3112b599c90232a36498cd01af8208bdda3c0ae3f28a37eaaf810d75534f753\\UtilityVM"},"AllowUnqualifiedDNSQuery":true})
Try running gpupdate /force i've found this works instead of a system restart or vm restart. This command will reapply all group policy settings, see docs for more info.
I'm trying to install PostgreSQL 9.0.1 on Windows Server 2008, but every time, there will be such error message
"Problem running post-install step. Installation may not complete
correctly. Failed to start the database server"
in the installation log, it is due to a failure in initdb.exe, error is
"The program postgres is needed by initdb, but was not found in the
same directory as D:\PostgreSQL\9.0\bin\initdb.exe, Check your
installation."
I searched such error in internet and tried the solution in this page "Installing PostgreSQL on Windows Server 2008", but no help.
After reading code of initdb, I know it is caused by the window api CreateProcess in the function pipe_read_line. the calling of CreateProcess returned -5 (access denied). it is because initdb was executed in a subprocess invoked in the functiion CreateRestrictedProcess.
I know it is due to privilege setting, I ran gpedit.msc to add users group (even everyone) into almost all privilege policy, but the error was still there.
I also assigned full control rights of the install target folder to everyone, no help!
I also tried postgresql 9.6.2, the error was still there :-)
from the code, I know if there is the environment variable PG_RESTRICT_EXEC with value 1, initdb will not executed in a restricted process. so before run initdb.exe, I set an environment PG_RESTRICT_EXEC=1 in command prompt, then run initdb.exe. this time such error was gone!!
So I wonder how to change the os settings to allow the installation running without error!
I am trying to install Jenkins slave service after starting the slave via web start.
I get the following error when it tries to install on windows 10 and windows 8.1.
[JenkinsWorkDirectory]$ c:\JenkinsWorkDirectory\jenkins-slave.exe install
WMI.WmiException:AccessDenied
at WMI.WmiRoot.ClassHandler.Invoke(Object proxy, MethodInfo method, Object[] args)
at WMI.Win32ServicesProxy.Create(String, String, String, ServiceType, ErrorControl, StartMode, Boolean, String, String, String[])
at winsw.WrapperService.Run(String[]_args,ServiceDescriptor descriptor)
at winsw.WrapperService.Main(String[]args).
I can install the slave service without any issue on win 7.
Any idea why is this happening or is it some limitation of Jenkins or am i missing some dependency?
My jenkins version is 1.655 and using chrome browser when installing. Jenkins master is running on windows 7.
Thanks,
Daniel
I found another way to get the slave to install.
Open a command window with "Run as Administrator".
Change directory to the place where you saved the slave-agent.jnlp file.
at the prompt run "slave-agent.jnlp"
Now with the running slave click the menu item to "Install as Service".
The trick is to do it while running as an administrator. This installs the service running under localsystem.
Additionally, if you're like me and you need your jenkins routines to hit another machine, you'll need to change the service to run as a user with permission (network or otherwise) to do the task you want done.
Open a command window with "Run as Administrator".
Just in case, You may have trouble with the .jnlp in "Steve Brownell" instructions, then, run the first line of your error message, shown below.
c:\JenkinsWorkDirectory\jenkins-slave.exe install
goto your downloaded jenkins-slave.exe Application file.
goto properties -> compatibility -.> check run as administrator.
Now try installing it as service again. It will work.
"C:\Program Files (x86)\Java\jre1.8.0_161\bin\javaws.exe" slave-agent.jnlp just run this from command prompt my issue got resolved from this as an administrator
I am stuck in a problem trying to install appx with Powershell -ExecutionPolicy Unrestricted add-appxpackage <path to appx> using the Powershell plugin in Jenkins and the below errors are logged:
add-appxpackage : Deployment failed with HRESULT: 0x80073CF9, Install failed.
Please contact your software vendor. (Exception from HRESULT: 0x80073CF9)
Deployment Add operation rejected on package
<path to appx> install request because the Local
System account is not allowed to perform this operation.
NOTE: For additional information, look for [ActivityId].
As I understand, this problem is mainly because Jenkins service on Windows gets installed as NT Authority\System. (If I use psexec.exe to open a command prompt that runs as Authority\System, I run into the same issue.) I then tried adding net localgroup "Administrators" NT Authority\System /add hoping the group might get added as Administrator and would let me install the appx, so I can run the tests, but with no success. Now I am stuck and I am not sure if there is really a way to install an appx via Jenkins or not OR if there is a way to invoke the Powershell script as an administrator via Jenkins. I have been through couple of SO links already, but none of them seems to fix the issue I am facing. Any pointers would be appreciated.
DO NOT try to add System to the Administrators group, it's a limited account for a reason and does not require administrative privileges.
Instead change the Jenkins service to run as a user that has the right permissions for what you're trying to do. That might mean you need to create an account specifically for the Jenkins service.
There are a few ways to change the service account, this answer gives the following as a solution:
sc.exe config "Service Name" obj= "DOMAIN\User" password= "password"
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.