Vista - Boot up: Failed to start up the COM client

Hi,

I have a problem with the COM client not starting up at boot time on a
Windows 2003 Server, web edition, with service pack 1. It always "hung" on
start up with event ID error of 7022, which is: The service hung on starting.
In Microsoft's Windows Server 2003: Managing System Services document, the
cause was stated as follows: "The service is experiencing an internal error.
The error means that the service took more than 80 seconds plus its
dwWaitHint ( ...) either to change its state or update its dwCheckPoint
(...)."

I have tried to do a registry edit to make the service start at the end by
adding the following dependencies to the COM Client: DependOnGroup-> Network
SpoolerGroup, DependOnService -> RPCSS SENS. But the COM Client still fail to
startup at boot-up. (So I know my registry edit failed to make the COM Client
start near the end of the startup cycle)

The reasons that I want to make the COM client start up "LAST", are as
follows:
1. The COM Client is the only service that fail with EVENT ID: 7022
2. All other services was able to load successfully.
3. When I log into the window 2003 server and do a "manual" startup of the
COM Client service, it starts up successfully.

So, is there an option that will allow me to make my com client service
start up last, after everything has been loaded. That is, is there a special
attribute that I can add to the com client (whether by a registry edit or
some other method) to make sc.exe start the service at the end of the boot-up
cycle. I know the lists that sc.exe creates is dynamic, but there must be a
way to tell sc.exe that this service has to be start at the end.

Any help or suggestions that you can provide will be greatly appreciated.

Sincerely,
Thomas