I have a Exe program which run fines and update the log when I run it manually or create a batch script run the .bat file (By double click/call from CMD prompt).
When I am trying to automate this process by creating scheduled task/ creating a service it don't work.
In Windows 2012 Srvany.exe also dont work so i am not able to create a service , even though I create a service using SC Create command the service fails to run in windows 2012.
I got the answer- This was happening as My Program was not running at Interactive mode,As per Microsoft a task runs at Interactive mode when "Run when User logged on" option is chosen, if we choose other option the program will not run at interactive mode.
https://technet.microsoft.com/en-us/library/cc722152.aspx
Related
I need one batch to open a .exe file with admin privileges and in high priority/realtime,without asking for an admin password.
Also, I need to call this batch file from a desktop shortcut.
I have tried:
start "%app_name%" /high "%app_name%.exe"
Thanks in advance!
I made an installer using Inno setup, the installer made an elevated desktop shortcut to a batch file that started the process in high priority.
I have AEM instance setup on a AWS Ubuntu machine. Not sure why stop command not working for publish instance. It is working fine for author instance. We have configured it on changed port(5054). Can anyone suggest if I am missing anything? Here is the screen shot showing the error message while running the stop command:
You cannot stop an AEM instance with the stop script if you did not start it with the start script.
If you look at the scripts you'll see that:
start script creates a file conf/cq.pid that has the java PID
stop script looks for that file and tries to stop the instance then deletes the file.
Thus, if you did not start with start script, you cannot stop with stop script.
I needed to run x2goclient desktop session on background. I found out that x2goclient cannot create new session, but user should use x2goclient GUI to create some sessions, then you can use command to use already created sessions. Found another CLI, called pyhoca-cli, which has a lot of advantages and it can create new sessions. But the problem is when it creates session, instead of showing x2goclient desktop windows, it shows x2goclient ssh terminal. I am using the commands like this:
pyhoca-cli --new --server=some_ip --port=some_port --username=some_username
I successfully installed Maximo 7.5 on Windows Server 2008 R2 64-bit with the defaults (WebSphere 7, DB2, Tivoli Directory). I'm trying to install the 7.5.0.7 fix pack but get this error after I ran install_win64.bat (Run as Administrator). This error occurs a few steps after "Database is ready for upgrade" checkbox.
CTGIN2076E: Exception Running WASThingClient method for task runConfigurationStep.
The CCMD_install.log said:
FndUpgradePanelActionshandleInstall: Getting a WAS thin client config task object
FndUpgradePanelActionshandleInstall: Running WAS thin client config task
FndUpgradePanelActionshandleInstall: Returned from running WAS thin client config task
FndUpgradePanelActionshandleInstall: Got task result from task return.
Completion message :CTGIN2076E: Exception Running WASThinClient method
for task runConfigurationStep.
FndUpgradePanelActionshandleInstall: verifyInputs method,
rc=-1 cmpMessage=CTGIN2076E: Exception Running WASThinClient
method for task runConfigurationStep. stderr=CTGIN2286E:
An error occurred while configuring the WebSphere Application
Server thin client. The error message is CTGIN2283E: Exception
caught while connecting to the remote server. Exception
com.ibm.tivoli.ccmdb.install.common.util.rxa.RemoteSystemException:
com.ibm.tivoli.ccmdb.install.common.util.rxa.RemoteSystemException:
Remote system cannot be reached using Supported RXA Protocols... stdout=
FndUpgradePanelActionshandleInstall:
Configuration of WAS thin client was not successful
Make sure MXServer on the application server is stopped first.
Extract the fix pack to c:\temp\ to run the installer.
From a command prompt, run:
C:\temp>set skipwasvalidation=yes (this will create a set variable
to skip websphere application server validation)
On the same command prompt window run the install.exe (or
install_win64.exe for x86-64).
When you run install.exe, the Run
Configuration Step panel will offer the some options:
Check on Copy files now, but perform the installation configuration step later
Deploy application files manually later
Defer the Update of the Maximo Database
This will complete the install, deferring all automated actions.
At a command prompt, change to the c:\ibm\smp\scripts folder and run:
taskrunner.bat CONTINUE STOPONERROR
Run updatedb.bat from c:\ibm\smp\maximo\tools\maximo
Build and deploy the maximo.ear (c:\ibm\smp\maximo\deployments\buildmaximoear.cmd)
Source: CTGIN2233E: The WebSphere NodeAgent is not running
I want to change the Server Collation of SQL Server 2008 R2
As all opinions says (including MSDN) the following command should be executed:
E:\setup.exe /q /ACTION=RebuildDatabase /INSTANCENAME=MSSQLSERVER /SAPWD=”**″ /SQLSYSADMINACCOUNTS=”HEREISMYPROBLEM” /SqlCollation=SQL_Latin1_General_CP1_CI_AS
As I Pointed, my problem is with the SYSADMINACCOUNT paremeter because the error that I get is:
The Windows account ”blablabla” does not exist and cannot be provisioned as a SQL Server system administrator.
I tried all possible windows accounts that may be, but It's not working.
Please can you guide me how to know my correct windows account.
The MSDN link that shows this problem is
here
This page describes the switches and says to use "DOMAIN\User" format, for example:
BUILTIN\Administrators MyDomain\MyUser
For anyone else that gets stuck with this problem and cant find an answer. The commands work you just need to run cmd as an administrator for it to work.
Use this batch file for change collation on SQL Server 2008
But you need edit batch file for set you instance and target collation.
Stop SQL Server Service when you run this file
File need Run as administrator
If don't work well (maybe access problem), you can use cmd (Run as admin) and run batch file steps on cmd