So, I need to setup a delayed startup for eCenter or just manually start eCenter for now.
I always use REXX AutoStart:
http://www.7cities.net/~mckinnis/rxautost/index.htmlIt seems to be necessary when you have more than about 4 items in the startup folder. Unfortunately, it doesn't always help, if the startup conflict occurs before STARTUP.CMD gets executed (A startup conflict can actually cause STARTUP.CMD to fail to run).
I actually had that problem when I installed eCS 2.1 to one of my systems. Not loading eCenter allowed me to proceed, and get a few more programs installed, then it happened again. Putting eCenter back into the mix fixed it long enough to get more things installed. The final fix (actually a work around) was to use REXX AutoStart.
See eCS bug tracker incident 3072 for more details. Your symptoms may not be exactly the same, but I am pretty sure that it is the same cause.