SUA1500 SERIAL w/PCBEB on 1 non-networked computer "Could not connect. . ."

[Anonymous user]

h2. SYSTEM SPECIFICATIONS
* SUA1500 Serial on COM1
* SCSI PIII
* Windows XP Media Center Edition SP3 (fresh install, no internet connection established yet)
* Messenger Service STOPPED + DISABLED (and no, I WON'T enable it)
-----
{color:#0000ff}THE NIGHTMARE OF SETTING UP APC BUSINESS EDITION BASIC ON A STANDALONE COMPUTER{color}
Compelling this software to drive multiple computers is something APC is good at doing; but automating the agent for ONE LOUSY 9-Pin SERIAL PORT -- with a PERMANENT electrical connection to the motherboard (something USB will never have) -- is apparently beneath APC's technical ability. So I'm posting the Nightmare Install that is this software on a standalone computer before anyone else inadvertently tampers with their OS-installed Services as a direct result of APC's refusal to release a PCPE for their serial line . . . and then finds that they've screwed up the networking service defaults carefully placed there by the OS, with no easy way back. If it sounds like I'm angry, you're right: this is the second time this software has done this to me. I'm finally fed up enough to post a formal rant, and so thoroughly intimidated by this software that I'm showing up here to BEG SOMEONE TO HELP ME GET IT TO WORK SO I CAN USE MY 60-LB. UPS.

The last time this software was DOA with my SUA1500 I hunted down an upgraded version of PCBEB, thinking that would remedy the program's inability to drive a perfectly-functioning serial connection. The problem then was the same problem I'm having at this second futile attempt to enjoy the use of my UPS (detailed below); so before anyone says "get the upgraded version of~ (SNIP)" you can park that bull outside. The problem isn't the version of this software; the problem is how this software needlessly-interacts with my desktop just to drive one UPS connected to a sturdy, dedicated serial port. Convince me that the core programming model of this software can do anything beyond make my life a misery and then we can talk about upgrading it, fair enough? Been there done that; rant done; now help me please.

-----
{color:#ff0000}*CONSOLE ERROR*{color}
bq. APC BUSINESS EDITION BASIC 7.0.5.108 \\ Host 127.0.0.1 \\ {color:#ff0000}Could not connect to the APC PowerChute Business Edition Server. Make sure that the APC Business Edition Server software is running and that its host is connected to the network.{color}
-----
DEBUG.TXT
bq. Wed Oct 07 08:51:54 PDT 2009: [http://ServerConnectionManager.run()]- PCBE Error: Error accepting socket connection \\ Wed Oct 07 08:51:54 PDT 2009:Critical Exception class java.io.IOException:PCBE Error: Error accepting socket connection On Thread Ali Communications Listener Thread(1) Caught at ServerConnectionManager.run()[:|http://www.apc-forums.com/] \\ Wed Oct 07 08:51:54 PDT 2009: [http://ServerConnectionManager.getAgentVersion()]- \\ Wed Oct 07 08:51:54 PDT 2009:Critical Exception class com.apcc.m11.arch.CommunicationException: On Thread Ali Communications Listener Thread(1) Caught at ServerConnectionManager.getAgentVersion()[:|http://www.apc-forums.com/] \\ Wed Oct 07 08:51:54 PDT 2009: [http://ServerConnectionManager.getAgentVersion()]- Error getting agent version
-----
h2. {color:#ff0000}*HOW NOT TO GET THIS SOFTWARE TO WORK*{color}*, Condensed Version*
=====================================================================
DNS CLIENT
Changed Logon to "Local Computer" = NO EFFECT
=====================================================================
TCP/IP NetBIOS HELPER
Changed Logon to "Local Computer" = EFFECTIVELY *{color:#ff0000}DISABLED TCP/IP{color}*

TCP/IP Service preserved "Automatic" characteristic, but once changed to "Local Computer" the service STOPPED, LOCKED UP, and reported ERROR 1079: The account specified for this service is different from the account specified for other services.

Frantic to get XP Services back to their installed defaults, I RE-clicked the XP Logon, hoping it would restore the original "{color:#ff0000}NT AUTHORITY/LocalComputer{color}" password carefully put there by XP and . . . . the settings were GONE.

=====================================================================
UNINSTALLED ALL XP NETWORKING w/Install CD
=====================================================================
REBOOT
=====================================================================
REINSTALLED ALL XP NETWORKING w/Install CD
=====================================================================
REBOOT
=====================================================================
Successfully restarted TCP/IP, but {color:#ff0000}original Microsoft Logon password still gone{color}
=====================================================================
PCBE attempted = NO EFFECT
=====================================================================
Back to Services where I clicked "Allow service to interact with Desktop" on
bq. DNS CLIENT \\ TCP/IP NetBIOS HELPER
=====================================================================
PCBE attempted = NO EFFECT

WUp

[Erasmus_apc]

So just to get a few basics out of the way, to understand the issue...you ran through the agent, server, console install, and there were no errors, I assume? Once the server is installed the console is the only way to log onto it so that error came up after putting in a user/pass, and it looks like you specified the host field as "127.0.0.1"? That is technically fine...the alternative to that setting is localhost, or the IP of whatever other PC the server portion is installed on. If there were any more complications you haven't mentioned, or if you experienced this error somewhere else than when logging into the console after all 3 pieces of PCBE were installed, we need to know.

The next part is where I'm a little confused. You say you changed (again I assume via services.msc) the DNS Client service and TCP/IP service settings...and this is when your TCP/IP blew up. I don't see how PCBE had anything to do with this. The PCBE server process is entirely idle, other than communication to and from the agent(s) to maintain connection, and just sits and waits for a request on port 2260 to acknowledge a logon request from the PCBE Console. It does not integrate itself into the Windows TCP/IP service or any other networking services. It can certainly be rendered unusable by improper network configuration, internet security suites, and firewalls, but it has no active role with these items.

You said there was no internet connection set up on the PC. Is there an actual network adapter fully configured, but just not on a wireless/wired connection? Are all your network drivers installed? That statement leaves some guesswork. You are also getting some Java errors in that log. I would recommend making sure that your Java is fully updated to the most recent version, as PCBE is a Java app and heavily dependent on function calls and Java resources.

If you can, try accessing the agent portion once the agent is installed. You should be able to do that by using a web browser and typing in 127.0.0.1:3052 or localhost:3052. Does that bring up the web agent? Also, have you tried this on another PC? The OS you have listed is not tested for compatibility against PCBE 7.0.5, so we would not be able to verify if it is meant to work.

[Erasmus_apc]

Not a problem. The reason I ask so many questions and ask for clarification on your statements is because, in all honesty, we very rarely see PCBE installation failures.

WattsUp wrote:
No. This is a standalone computer and I only have dialup available for it.


I'm unclear what you're referring to. I just installed XP MCE up through SP3. You're now in the grey area that I
ventured into yesterday when I inadvertently fried my TCP/IP settings. This is precisely what I was trying to
tweak.

Ok, this might be where the problem lies. To use a localhost/loopback on a standalone system with no network, you need the Microsoft Loopback adapter installed. On a computer with a fully enabled, internet connected IPV4/IPV6 (::1 is the loopback in that case) connection, this is in nearly every case unecessary. The loopback adapter basically allows the computer direct access back to itself, no physical network adapter needed, and it's safe to use, according to MS. You can install it via the steps in this link:

http://www.windowsnetworking.com/articles_tutorials/Install-Microsoft-Loopback-adapter-Windows-XP.ht...


http://support.microsoft.com/kb/236869 (this link is for Windows 2000 so use it for educational purposes only)

Or in short:

Start->Settings->Control Panel-> Add/Remove New hardware -> Next-> Add or Troubleshoot a device-> select Add New Device->Next->Select No, I want to select the hardware from the list->Next->select Network Adapters-> Next-> Select the Manufacturer Microsoft -> Microsoft Loop back Adapter->next -> Finish

Frankly, it's been a long, long time since I've used dial-up, and some quick Google researching didn't really pull up a lot on the ability of dial-up modems/adapters to perform a loopback request. The MS loopback adapter should help for troubleshooting PCBE. In regards to the question about your network drivers, I asked that because a physically installed network device/modem doesn't necessarily mean it's going to work...your network drivers fully enable whatever device you have installed. Even if you try the MS loopback adapter I would want to know if your drivers are installed for your dial-up device.

WattsUp wrote:

Okay, Java . . . would be where? I mean, isn't this installed along with the OS? Is there a separate
"JAVA-Something" I need to download and install independent of the OS?

This is usually not installed along with Windows. Some retail PCs like Dells will come with it installed, but Java is a proprietary SDK/runtime environment/API made by Sun. Go to www.java.com and get the most recent version.

In regards to the OS compatibility...yes we are aware Windows XP MC is not worlds different than Home or Pro, just saying that it's not in our compatibility list which means it either was not tested (unlikely since we have a lot of other Service Pack and Windows versions listed), or it failed testing for some reason.

I would start with all the above steps, and whatever else I recommended in the previous response. I'm especially curious about installing the agent portion, and then accessing it in your web browser. You can try using the computer's own IP address, loopback, or localhost:

:3052
127.0.0.1:3052
or
localhost:3052

If none of those work, you will need to verify that the PBE/PCBE Agent service is running in services.msc. If it is...I suspect a network adapter/firewall/Network setting issue. If the agent can't loopback to itself, then the server process is almost assuredly not going to be able to.

[Anonymous user · Accepted solution]

h2. SYSTEM SPECIFICATIONS
* SUA1500 Serial on COM1
* SCSI PIII
* Windows XP Media Center Edition SP3 (fresh install, no internet connection established yet)
* Messenger Service STOPPED + DISABLED (and no, I WON'T enable it)
-----
{color:#0000ff}THE NIGHTMARE OF SETTING UP APC BUSINESS EDITION BASIC ON A STANDALONE COMPUTER{color}
Compelling this software to drive multiple computers is something APC is good at doing; but automating the agent for ONE LOUSY 9-Pin SERIAL PORT -- with a PERMANENT electrical connection to the motherboard (something USB will never have) -- is apparently beneath APC's technical ability. So I'm posting the Nightmare Install that is this software on a standalone computer before anyone else inadvertently tampers with their OS-installed Services as a direct result of APC's refusal to release a PCPE for their serial line . . . and then finds that they've screwed up the networking service defaults carefully placed there by the OS, with no easy way back. If it sounds like I'm angry, you're right: this is the second time this software has done this to me. I'm finally fed up enough to post a formal rant, and so thoroughly intimidated by this software that I'm showing up here to BEG SOMEONE TO HELP ME GET IT TO WORK SO I CAN USE MY 60-LB. UPS.

The last time this software was DOA with my SUA1500 I hunted down an upgraded version of PCBEB, thinking that would remedy the program's inability to drive a perfectly-functioning serial connection. The problem then was the same problem I'm having at this second futile attempt to enjoy the use of my UPS (detailed below); so before anyone says "get the upgraded version of~ (SNIP)" you can park that bull outside. The problem isn't the version of this software; the problem is how this software needlessly-interacts with my desktop just to drive one UPS connected to a sturdy, dedicated serial port. Convince me that the core programming model of this software can do anything beyond make my life a misery and then we can talk about upgrading it, fair enough? Been there done that; rant done; now help me please.

-----
{color:#ff0000}*CONSOLE ERROR*{color}
bq. APC BUSINESS EDITION BASIC 7.0.5.108 \\ Host 127.0.0.1 \\ {color:#ff0000}Could not connect to the APC PowerChute Business Edition Server. Make sure that the APC Business Edition Server software is running and that its host is connected to the network.{color}
-----
DEBUG.TXT
bq. Wed Oct 07 08:51:54 PDT 2009: [http://ServerConnectionManager.run()]- PCBE Error: Error accepting socket connection \\ Wed Oct 07 08:51:54 PDT 2009:Critical Exception class java.io.IOException:PCBE Error: Error accepting socket connection On Thread Ali Communications Listener Thread(1) Caught at ServerConnectionManager.run()[:|http://www.apc-forums.com/] \\ Wed Oct 07 08:51:54 PDT 2009: [http://ServerConnectionManager.getAgentVersion()]- \\ Wed Oct 07 08:51:54 PDT 2009:Critical Exception class com.apcc.m11.arch.CommunicationException: On Thread Ali Communications Listener Thread(1) Caught at ServerConnectionManager.getAgentVersion()[:|http://www.apc-forums.com/] \\ Wed Oct 07 08:51:54 PDT 2009: [http://ServerConnectionManager.getAgentVersion()]- Error getting agent version
-----
h2. {color:#ff0000}*HOW NOT TO GET THIS SOFTWARE TO WORK*{color}*, Condensed Version*
=====================================================================
DNS CLIENT
Changed Logon to "Local Computer" = NO EFFECT
=====================================================================
TCP/IP NetBIOS HELPER
Changed Logon to "Local Computer" = EFFECTIVELY *{color:#ff0000}DISABLED TCP/IP{color}*

TCP/IP Service preserved "Automatic" characteristic, but once changed to "Local Computer" the service STOPPED, LOCKED UP, and reported ERROR 1079: The account specified for this service is different from the account specified for other services.

Frantic to get XP Services back to their installed defaults, I RE-clicked the XP Logon, hoping it would restore the original "{color:#ff0000}NT AUTHORITY/LocalComputer{color}" password carefully put there by XP and . . . . the settings were GONE.

=====================================================================
UNINSTALLED ALL XP NETWORKING w/Install CD
=====================================================================
REBOOT
=====================================================================
REINSTALLED ALL XP NETWORKING w/Install CD
=====================================================================
REBOOT
=====================================================================
Successfully restarted TCP/IP, but {color:#ff0000}original Microsoft Logon password still gone{color}
=====================================================================
PCBE attempted = NO EFFECT
=====================================================================
Back to Services where I clicked "Allow service to interact with Desktop" on
bq. DNS CLIENT \\ TCP/IP NetBIOS HELPER
=====================================================================
PCBE attempted = NO EFFECT

WUp