- Failed to start apc pbe agent service. install#
- Failed to start apc pbe agent service. software#
- Failed to start apc pbe agent service. plus#
The syntax, when executing a remote shutdown command for instance is the following: cfg/php/e nduser/std _adp.php?p _faqid=178 4&p_cr eated=1010 390400& p_sid=W2m 3KsWh& p_lva=& p_sp=cF9z cmNoPTEmcF 9zb3J0X2J5 PSZwX2dyaW Rzb3J0PSZw X3Jvd19jbn Q9MjgxJnBf cHJvZHM9MC ZwX2NhdHM9 JnBfcHY9Jn BfY3Y9JnBf c2VhcmNoX3 R5cGU9YW5z d2Vycy5zZW FyY2hfbmwm cF9wYWdlPT EmcF9zZWFy Y2hfdGV4dD 1tYW51YWxs eSB1bmluc3 RhbGwgcG93 ZXJjaHV0ZQ**&p_li=&p_topview=1Ģ) Make sure the extention of your script file and syntax within are correct.
Failed to start apc pbe agent service. plus#
PowerChute Plus for Windows NT/2000/XP is not executing a command file - Answer ID: 1784 APC actually has a decent article on this at the following location: I finally got this working using a combination of methods mentioned above.so to consolidate what everyone was talking about:ġ) Make sure that the services for the Agent and Server are bound to an authorized administrator that can run commands on the remote servers. RE: APC shutdown sequence pthomass (TechnicalUser) 23 Aug 05 08:35 I have to fix a crashed server that's very far (I'm in Canada and the server is in Africa). I'll give it a try when I get back from my trip.
Failed to start apc pbe agent service. software#
I've been too busy with half a dozen ongoing projects and trying to joggle everything ! There's another thread in this forum about an open license software that works with remote servers. The port expander is already screwed into the server rack but haven't connected the comm cables to each server yet. 1) I got separate UPSes for each server and 2) I bought a port expander for my other "larger" UPS to control up to 7 servers. Then in PowerChute, I configured it to execute the batch file I created when the battery ran low. When I manually ran the batch file, it would properly shutdown the other servers that were NOT attached to the UPS via the comm cable. But basically what I tried is create a batch file with the commands like tsshutdown (from windows) or psshutdown (from Winternals) with switches that remotely shutdown the servers. BTW, I have the PowerChute Business Edition 5 Nodes that comes with the APC Smart-UPS 1000Īny ideas ? Or do I have to absolutely buy a port expander or put a single UPS per server ?Īnthony RE: APC shutdown sequence jstreich (Programmer) 10 Feb 05 14:27 I even tried calling a batch file that resides on the remote server from the script and it still doesn't work. I'm wondering if the APC software somehow detects you are trying to shutdown a remote system without using a port expander and blocks it. It won't work when you run it from the computer connected to the UPS even through command line. With nltest and shutdown, they seem to only work locally (must be run from the remote system). With tsshutdn, you see a message appear on the screen indicating the server will shutdown but after the time elapses, nothing happens, the server keeps on running. However, when the UPS calls the script then it doesn't work. Using psshutdown and tsshutdn works fine when executed within a. Now I've tried the following tools to remotely shutdown my other server : psshutdown (from PSTools), nltest.exe (comes with Windows 2000 Server), tsshutdn (usable if you have terminal services running) and shutdown.exe (comes with PowerChute). I know that you can buy the port expander so that there are multiple communication cables going to each server but I don't want to use that option. The script is placed in the Shutdown Sequence menu. When there's a power failure, you can program a little script so that certain operations can be performed before the UPS shuts down the server that is connected to it (via the communication cable). I have the ups connected to one of the servers. Your second option is to manually grant the Log on as a service right using Group Policy.Have any of you successfully used the shutdown sequence to turn off remote servers within the same lan ? Currently I have 1 UPS with 1 communication port and 2 servers. Windows will automatically grant the Log on as a service right to your account. Your first option is to do everything from the Services window. Those packages cannot be used by the Network Service account so I configure my service based agents to run under a user account.
Failed to start apc pbe agent service. install#
I needed to run my service as a user account because package management systems like NPM install packages per user. Therefore, any accounts used as the service identity must have the right to log on as a service. Windows services begin to run as soon as Windows boots regardless if anyone logs into the machines or not. Make sure the account has the “Log on as a service” right.Īfter configuring my agent with the following command my agent failed to start.\config.cmd -url -auth PAT -token -pool default -runasservice -windowslogonaccount -password -work _work -agent When I try and install my agent as a service with a user account it fails to start.Įven if I try to start it from services window it fails.