Hi folks,
Is there a registry value I can change to stop this annoying popup I'm getting every time I boot into Win2003, Web Edition? The popup reads as follows:

Service Control Manager: At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.

Of course I checked the Event Viewer, but all it tells me is:
Event ID 26 - Application popup: Service Control Manager : At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.

It's one of those typical windows merry-go-rounds.
I wouldn't have to bother you people here today if it would at least tell me which driver or service is at fault. But of course it doesn't do that. So to cut a long story short, I'd rather edit the registry and nip this thing in the butt. It's the only way to treat windows, right?
Anyway, I tried the following without success:

Hive: HKEY_LOCAL_MACHINE
Key: SYSTEM\CurrentControlSet\Control\Windows
Name: ErrorMode
Type: REG_DWORD
Value: 0 Errors are serialized and wait for a response
Value: 1 If the error does not come from the system, then the system continues in normal operating mode. If the error comes from the system, then it is written to the system log; no user intervention is required and dialog boxes are not displayed.
Value: 2 The error is written to the system log; the dialog box is not displayed.

alas, no joy.
Does anybody know of a different one?
I would really appreciate some help with this, because this boot popup is driving me 'round the bend.
Thanks.

You need to do what it says...heh. Take a look at the event log and find out what service didn't load. Then find out why it didn't load, and determine if you need the service. If you don't, then diable the service from startup or remove it through the registry. Simple. The event log is there for a reason

Thanks for taking the time to reply.
It's exactly what I did, checking the Event (system) log.
Like I already said, apart from 'Application Popup' (Event ID 26) there's nothing else that would indicate which service or driver is responsible for the Service Control Manager popup at bootup. And that is why I'm looking to get rid of it by way of a registry hack.

I can see where this is going.
It's very probable, nobody here knows what I'm talking about.
That's ok, thanks anyway.

dude something did not start - look at your services, look at all the ones marked as auto, are they ALL listed as started?

Maybe this will help you http://www.eventid.net/display.asp?eventid...20Popup&phase=1

can you post the whole event you get in the event viewer?

thanx

First up, thanks to everyone who's showing an interest in my problem.
@Eversurf...
below is an extract of the...

Event Viewer (System log) at bootup:

EventID 6009
Microsoft ® Windows ® 5.02. 3790 Uniprocessor Free.

EventID 6005:
The Event log service was started.

EventID 14533:
DFS has finished building all namespaces.

EventID 14531:
DFS server has finished initializing.

EventID 26 (I take it, this is the one responsible for the popup at boot time):
Application popup: Service Control Manager : At least one service or driver failed during system startup. Use Event Viewer to examine the event log for details.

EventID 4295:
The IPSec Driver is starting in Bypass mode. No IPSec security is being applied while this computer starts up. IPSec policies, if they have been assigned, will be applied to this computer after the IPSec services start.

EventID 4294:
The IPSec driver has entered Secure mode. IPSec policies, if they have been configured, are now being applied to this computer.

EventID 10005:
DCOM got error "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. " attempting to start the service appmgr with arguments "-Service" in order to run the server:

EventID 7000:
The V7 service failed to start due to the following error:
The specified driver is invalid.

The rest are just Service Control Manager confirmations of services that were successfully initiated, eg. Network Connections, Telephony, Remote Access Connection Manager, etc.

@BudMan...
As far as the windows services are concerned, I admit, I always disable the ones I consider aren't needed, eg. Automatic updates, Clipbook, Volume Shadow Copy, etc.
Then again, I can't understand why I'm getting a DCOM error. 'COM+ Event System' & 'COM+ System Application' are set to manual startup mode. The same goes for all the COM+ associated services, File replication, System Event Notification, and Remote Procedure Call (RPC), a service I would never mess around with.
One question though, what is the V7 service? That's a new one to me.

JCAP...thanks for the link. Will take a look later.

never heard of a V7 service. check its properties and see where the .exe resides.

@primortal...
Found it.
V7.SYS...location: %systemroot%\system32\drivers
Apparently it's a system file. I'm still googleing to find out what it's for.
Any of you folks have the file on your system?
Maybe I'll make a backup of it, encrypt the original and I suppose I soon find out what it's meant to do.
I just checked my other partition (WinXP Pro), same file, same location.
I'm gonna alter the ErrorMode value in the registry for the V7 service
(HKLM\System\CurrentControlSet\Services\V7) and see what happens.

just disable the service or set it to manual. If you right-click on that file (v7.sys) and select properties and then the version tab it will tell you some info about the file.

Problems solved. (EventID 26 (V7 service) & DCOM Errors).
First up the V7 service, although listed in the registry it is not listed under windows services. Don't know why that is. I have to research this somewhat more.

However, I solved the V7 service error by replacing the V7.SYS file in Win2003 with the one from WinXP Pro on my other partition. That took care of the Event ID26 (Application popup at boot time).
It's gone , and it's just as well, because I was gonna have a fit very soon.
Still need to find out though what exactly the V7 driver does, or what purpose it serves.

@primortal...
Properties of V7.SYS driver:
version: 1.3.0.0 , Copyright © IBM Corporation 1997-1999

The DCOM errors, well, that's down to me. I was in a bit of a rush when I last set up the server and accidentally disabled one to many services (Remote Administration Service)

Anyway, thanks again to everyone who took the time and looked into this.
Much obliged. Later.

V7.SYS seems to be IBM's DVD decoding driver.