Error while starting: Cannot start service TCXXXXXXXXXXXXXXX on computer '.'.

[elite90]

One of our boxes is displaying this error when anyone tries to start a service. Error while starting: Cannot start service TCXXXXXXXXXXXXXXX on computer '.'.

 

Restarting the box fixes this problem, but it comes back shortly after.

 

This error is displayed when trying to start the service from services.msc:

 

If anyone knows anything about this, please share! I think that it could have something to do with service limits or desktop heap size... but I don't know how to fix it.

 

Thank you

[elite90]

The services seem to start when they are set to run under the Local System account.

[elite90]

Got it... "Failed to create a desktop due to desktop heap exhaustion."

 

Now, does anyone know what I should put the heap settings to?

 

Thanks

[dimitrifrom31]

http://blogs.msdn.com/ntdebugging/archive/2007/01/04/desktop-heap-overview.aspx

 

something to start from

[elite90]

Luis suggested trying this: http://clients.tcadmin.com/knowledgebase.php?action=displayarticle&catid=2&id=9

 

Just need to wait until 4 AM on Wednesday to restart the box.

[Karkey]

Just out of curiosity what OS you running and how many services do you have installed on the box ?

[elite90]

2003 64-bit

 

These boxes have about 70 TCAdmin services each, but they're monsters.

 

Edit: I believe that you work for a company that also uses monster sized boxes? Have you run into this problem yet?

[Karkey]

Hi

Most definitely, as the reason i asked.

wether your box has 8 CPU's to 32 CPU's and tonnes of RAM it will not make a difference

Windows has issues with services over 50 i have tested this multiple times on OS 2003 64bit

 

The reg edit will not work, your windows services will crap out and mess up for other clients

I have not tried it on 2008 as no box is spare at any given one time.

 

Its not a TCA problem its a winblows problem on its limits.

This was tested with mumble, giving it away free to all clients or non clients 40 sign ups in one day alone, then the whole thing went kerupt and the box had to be rebooted and needed to keep rebooting to stop the problems

[elite90]

If anyone else runs into this problem...

 

SharedSection=1024,40960 did fix it, but then I was still having a weird network issue that was previously happening. I installed 2008 and everything is nice and dandy now. I also like the fact that I can postpone the Windows update restart reminder for 4 hours...

[Derek]

We have machines that have 50+ services on windows 08 64 bit with no issues.

[Karkey]

Hi

Well we really do not use 08 servers as i said i really could not comment on winblows 2008

 

The SharedSection=1024,40960 i also tried on 2003 64bit with the same problems or more problems.

I'm guessing 08 is the way to go with massively installed services however be a shame if the box died and you was left with 50 odd clients with no services.

 

just something to consider before mass installing services to a box

 

glad you fixed your issue.

[Derek]

No different then big vps nodes which have alot more services then 50.