CrazyBuckaroo
IS-IT--Management
I used to have an older version of this software running just fine a while back so I am pretty familiar with how it works.
Recently though (after a 1 year hiatus from the software), I decided to set it up again on my W2K Server network. The servers have all the updates. I have the PowerChute agent running on 5 servers including the Server that is running the PowerChute Server module. The thing is, for some reason, the Server software keeps giving me the "Failed to Apply Configuration Profile" error message when attempting to add other devices on the network so I am only able to monitor the device that is on the PowerChute server and not any of the other servers.
Here is the APC link but I have tried every one of the options on the list with no resolution.
The other weird thing I notice (and I've tried it on 2 different servers) is that when the PowerChute Server is trying to update the profile and communicate to the agents on the other servers, the PowerChute server can not be pinged for about 25 seconds, completing temporarily removing it from the network for those 25 seconds. Very bizarre. I had read that some earlier versions of PowerChute had a similar problem where the CPU would tag at 100% causing all devices on the server to fail for roughly the same amount of time, but I don't think this is related, especially because that bug was supposed to be fixed.
Anyone else run into this weird issue? I have disabled all virus scanning software and used a port monitor which looks good except I do notice while port monitoring that some of the communications on some of the ports time out for reasons unknown. I can post the port scanning timeouts if it will help. Thanks
Recently though (after a 1 year hiatus from the software), I decided to set it up again on my W2K Server network. The servers have all the updates. I have the PowerChute agent running on 5 servers including the Server that is running the PowerChute Server module. The thing is, for some reason, the Server software keeps giving me the "Failed to Apply Configuration Profile" error message when attempting to add other devices on the network so I am only able to monitor the device that is on the PowerChute server and not any of the other servers.
Here is the APC link but I have tried every one of the options on the list with no resolution.
The other weird thing I notice (and I've tried it on 2 different servers) is that when the PowerChute Server is trying to update the profile and communicate to the agents on the other servers, the PowerChute server can not be pinged for about 25 seconds, completing temporarily removing it from the network for those 25 seconds. Very bizarre. I had read that some earlier versions of PowerChute had a similar problem where the CPU would tag at 100% causing all devices on the server to fail for roughly the same amount of time, but I don't think this is related, especially because that bug was supposed to be fixed.
Anyone else run into this weird issue? I have disabled all virus scanning software and used a port monitor which looks good except I do notice while port monitoring that some of the communications on some of the ports time out for reasons unknown. I can post the port scanning timeouts if it will help. Thanks