We recently had to rebuild one of our servers that had PCo on it. After completing the installation of PCo 2.3, I defined about 12 identical agent instances that all pointed to the same source system (to Kepware, our OPC DA 3.0 server), tested out a couple of them to make sure they worked, then set all 12 of them to "Automatic (Delayed Start)" in the Windows Services dialog (not in the PCo Management Console), then restarted the server.
After the server restarted, I was unable to remote into it. Talked to our Windows server guys, and they said the server was running hot (using 100% of RAM). They rebooted the server in safe mode, set the newly created PCo services to manual, and then rebooted again. That fixed the problem, but I don't know what I did to cause this. This type of configuration didn't cause problems on our QA server or on the earlier incarnation of our PROD server.
Using PCo 2.3. Currently in demo mode; will re-register soon.
Has this happened to anyone else, and how do you avoid it?
Thanks,
Greg