My legacy FSFD driver is not being loaded on a Windows 2003 Server.
Last time this happened it was because the customer was running inside a
Virtuozzo container, but this is the first time I am seeing this on a
physical machine.
All the files and registry entries seem to be in-place. I even write a log
entry as the first order of business in DriverEntry, but nothing is showing
up in the event log.
When I try to start it with OSRLoader, I get the message: "The service
cannot be started, either because it is disabled or because it has no
enabled devices associated with it. "
Any idea what to look at?
Thanks.
Unresolved runtime linkage?
“Neil Weicher” wrote in message news:xxxxx@ntfsd…
> My legacy FSFD driver is not being loaded on a Windows 2003 Server.
>
> Last time this happened it was because the customer was running inside a
> Virtuozzo container, but this is the first time I am seeing this on a
> physical machine.
>
> All the files and registry entries seem to be in-place. I even write a log
> entry as the first order of business in DriverEntry, but nothing is
> showing up in the event log.
>
> When I try to start it with OSRLoader, I get the message: "The service
> cannot be started, either because it is disabled or because it has no
> enabled devices associated with it. "
>
> Any idea what to look at?
>
> Thanks.
>
>
>
>
>
Interesting suggestion, but I am not linking to anything out of the
ordinary. However, how would I determine that?
“Lyndon J Clarke” wrote in message
news:xxxxx@ntfsd…
> Unresolved runtime linkage?
>
> “Neil Weicher” wrote in message news:xxxxx@ntfsd…
>> My legacy FSFD driver is not being loaded on a Windows 2003 Server.
>>
>> Last time this happened it was because the customer was running inside a
>> Virtuozzo container, but this is the first time I am seeing this on a
>> physical machine.
>>
>> All the files and registry entries seem to be in-place. I even write a
>> log entry as the first order of business in DriverEntry, but nothing is
>> showing up in the event log.
>>
>> When I try to start it with OSRLoader, I get the message: "The service
>> cannot be started, either because it is disabled or because it has no
>> enabled devices associated with it. "
>>
>> Any idea what to look at?
>>
>> Thanks.
>>
>>
>>
>>
>>
>
>
>
What’s depends say?
? S
-----Original Message-----
From: Neil Weicher
Sent: Wednesday, January 07, 2009 10:26
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Legacy Filter Driver won’t start in Windows 2003
Interesting suggestion, but I am not linking to anything out of the
ordinary. However, how would I determine that?
“Lyndon J Clarke” wrote in message
news:xxxxx@ntfsd…
> Unresolved runtime linkage?
>
> “Neil Weicher” wrote in message news:xxxxx@ntfsd…
>> My legacy FSFD driver is not being loaded on a Windows 2003 Server.
>>
>> Last time this happened it was because the customer was running inside a
>> Virtuozzo container, but this is the first time I am seeing this on a
>> physical machine.
>>
>> All the files and registry entries seem to be in-place. I even write a
>> log entry as the first order of business in DriverEntry, but nothing is
>> showing up in the event log.
>>
>> When I try to start it with OSRLoader, I get the message: "The service
>> cannot be started, either because it is disabled or because it has no
>> enabled devices associated with it. "
>>
>> Any idea what to look at?
>>
>> Thanks.
>>
>>
>>
>>
>>
>
>
>
—
NTFSD is sponsored by OSR
For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
You are currently subscribed to ntfsd as: xxxxx@valhallalegends.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Doh! Sorry - silly question. There are no dependencies.
“Skywing” wrote in message news:xxxxx@ntfsd…
What’s depends say?
– S
-----Original Message-----
From: Neil Weicher
Sent: Wednesday, January 07, 2009 10:26
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Legacy Filter Driver won’t start in Windows 2003
Interesting suggestion, but I am not linking to anything out of the
ordinary. However, how would I determine that?
“Lyndon J Clarke” wrote in message
news:xxxxx@ntfsd…
> Unresolved runtime linkage?
>
> “Neil Weicher” wrote in message news:xxxxx@ntfsd…
>> My legacy FSFD driver is not being loaded on a Windows 2003 Server.
>>
>> Last time this happened it was because the customer was running inside a
>> Virtuozzo container, but this is the first time I am seeing this on a
>> physical machine.
>>
>> All the files and registry entries seem to be in-place. I even write a
>> log entry as the first order of business in DriverEntry, but nothing is
>> showing up in the event log.
>>
>> When I try to start it with OSRLoader, I get the message: "The service
>> cannot be started, either because it is disabled or because it has no
>> enabled devices associated with it. "
>>
>> Any idea what to look at?
>>
>> Thanks.
>>
>>
>>
>>
>>
>
>
>
—
NTFSD is sponsored by OSR
For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
You are currently subscribed to ntfsd as: xxxxx@valhallalegends.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
There are no dependencies. This is really a very simple, straighforward
legacy FSFD. Thanks.
“Lyndon J Clarke” wrote in message
news:xxxxx@ntfsd…
> Unresolved runtime linkage?
>
> “Neil Weicher” wrote in message news:xxxxx@ntfsd…
>> My legacy FSFD driver is not being loaded on a Windows 2003 Server.
>>
>> Last time this happened it was because the customer was running inside a
>> Virtuozzo container, but this is the first time I am seeing this on a
>> physical machine.
>>
>> All the files and registry entries seem to be in-place. I even write a
>> log entry as the first order of business in DriverEntry, but nothing is
>> showing up in the event log.
>>
>> When I try to start it with OSRLoader, I get the message: "The service
>> cannot be started, either because it is disabled or because it has no
>> enabled devices associated with it. "
>>
>> Any idea what to look at?
>>
>> Thanks.
>>
>>
>>
>>
>>
>
>
>
> There are no dependencies. This is really a very simple, straighforward
legacy FSFD. Thanks.
What build env is used to build? what is the OS where issue occurs?
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
Yes, exactly the thoughts … and, I’ll come clean, been there, done that.
“Maxim S. Shatskih” wrote in message
news:xxxxx@ntfsd…
> There are no dependencies. This is really a very simple, straighforward
> legacy FSFD. Thanks.
What build env is used to build? what is the OS where issue occurs?
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
Well, how about dumpbin/imports on your driver, and dumpbin/exports on
anything on which driver depends (such as, whatever ‘ntoskrnl’ is on the
machine)? Neil, it’s just a long shot, but I’ve had the experience before.
“Neil Weicher” wrote in message news:xxxxx@ntfsd…
> Interesting suggestion, but I am not linking to anything out of the
> ordinary. However, how would I determine that?
>
> “Lyndon J Clarke” wrote in message
> news:xxxxx@ntfsd…
>> Unresolved runtime linkage?
>>
>> “Neil Weicher” wrote in message news:xxxxx@ntfsd…
>>> My legacy FSFD driver is not being loaded on a Windows 2003 Server.
>>>
>>> Last time this happened it was because the customer was running inside a
>>> Virtuozzo container, but this is the first time I am seeing this on a
>>> physical machine.
>>>
>>> All the files and registry entries seem to be in-place. I even write a
>>> log entry as the first order of business in DriverEntry, but nothing is
>>> showing up in the event log.
>>>
>>> When I try to start it with OSRLoader, I get the message: "The service
>>> cannot be started, either because it is disabled or because it has no
>>> enabled devices associated with it. "
>>>
>>> Any idea what to look at?
>>>
>>> Thanks.
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
Depends shows static linked dllimports, i.e. any DDIs that you are calling. You won’t be even registering as a filesystem if you call no imported functions.
? S
-----Original Message-----
From: Neil Weicher
Sent: Wednesday, January 07, 2009 13:03
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Re:Legacy Filter Driver won’t start in Windows 2003
Doh! Sorry - silly question. There are no dependencies.
“Skywing” wrote in message news:xxxxx@ntfsd…
What’s depends say?
? S
-----Original Message-----
From: Neil Weicher
Sent: Wednesday, January 07, 2009 10:26
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Legacy Filter Driver won’t start in Windows 2003
Interesting suggestion, but I am not linking to anything out of the
ordinary. However, how would I determine that?
“Lyndon J Clarke” wrote in message
news:xxxxx@ntfsd…
> Unresolved runtime linkage?
>
> “Neil Weicher” wrote in message news:xxxxx@ntfsd…
>> My legacy FSFD driver is not being loaded on a Windows 2003 Server.
>>
>> Last time this happened it was because the customer was running inside a
>> Virtuozzo container, but this is the first time I am seeing this on a
>> physical machine.
>>
>> All the files and registry entries seem to be in-place. I even write a
>> log entry as the first order of business in DriverEntry, but nothing is
>> showing up in the event log.
>>
>> When I try to start it with OSRLoader, I get the message: "The service
>> cannot be started, either because it is disabled or because it has no
>> enabled devices associated with it. "
>>
>> Any idea what to look at?
>>
>> Thanks.
>>
>>
>>
>>
>>
>
>
>
—
NTFSD is sponsored by OSR
For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
You are currently subscribed to ntfsd as: xxxxx@valhallalegends.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
NTFSD is sponsored by OSR
For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
You are currently subscribed to ntfsd as: xxxxx@valhallalegends.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Nit pick: I’ll bet Neil’s filter driver isnt registering as a file system
Well., you’re point is right, it isnt like the driver will get to be a
file system filter without calling some imported functions … and
IofCallDriver seems inevitable somewhere here for example.
“Skywing” wrote in message news:xxxxx@ntfsd…
Depends shows static linked dllimports, i.e. any DDIs that you are calling.
You won’t be even registering as a filesystem if you call no imported
functions.
– S
-----Original Message-----
From: Neil Weicher
Sent: Wednesday, January 07, 2009 13:03
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Re:Legacy Filter Driver won’t start in Windows 2003
Doh! Sorry - silly question. There are no dependencies.
“Skywing” wrote in message news:xxxxx@ntfsd…
What’s depends say?
– S
-----Original Message-----
From: Neil Weicher
Sent: Wednesday, January 07, 2009 10:26
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Legacy Filter Driver won’t start in Windows 2003
Interesting suggestion, but I am not linking to anything out of the
ordinary. However, how would I determine that?
“Lyndon J Clarke” wrote in message
news:xxxxx@ntfsd…
> Unresolved runtime linkage?
>
> “Neil Weicher” wrote in message news:xxxxx@ntfsd…
>> My legacy FSFD driver is not being loaded on a Windows 2003 Server.
>>
>> Last time this happened it was because the customer was running inside a
>> Virtuozzo container, but this is the first time I am seeing this on a
>> physical machine.
>>
>> All the files and registry entries seem to be in-place. I even write a
>> log entry as the first order of business in DriverEntry, but nothing is
>> showing up in the event log.
>>
>> When I try to start it with OSRLoader, I get the message: "The service
>> cannot be started, either because it is disabled or because it has no
>> enabled devices associated with it. "
>>
>> Any idea what to look at?
>>
>> Thanks.
>>
>>
>>
>>
>>
>
>
>
—
NTFSD is sponsored by OSR
For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
You are currently subscribed to ntfsd as: xxxxx@valhallalegends.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
—
NTFSD is sponsored by OSR
For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
You are currently subscribed to ntfsd as: xxxxx@valhallalegends.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Hi Max,
It is happening on Windows 2003 Server. This is the first time I have ever
seen this on a phyiscal machine. It is running on plenty of real and virtual
2003 boxes.
One curious thing I see with the box - they have uninstalled (not just
disabled) the “Help and Support” Service.
Thanks for any light you can shed on this mystery.
Neil
“Maxim S. Shatskih” wrote in message
news:xxxxx@ntfsd…
> There are no dependencies. This is really a very simple, straighforward
> legacy FSFD. Thanks.
What build env is used to build? what is the OS where issue occurs?
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
Hi Lyndon - I will definitely take a look. I would have thought that without
ntoskrnl, a whole lot of other things would fail as well. - Neil
“Lyndon J Clarke” wrote in message
news:xxxxx@ntfsd…
> Well, how about dumpbin/imports on your driver, and dumpbin/exports on
> anything on which driver depends (such as, whatever ‘ntoskrnl’ is on the
> machine)? Neil, it’s just a long shot, but I’ve had the experience before.
>
> “Neil Weicher” wrote in message news:xxxxx@ntfsd…
>> Interesting suggestion, but I am not linking to anything out of the
>> ordinary. However, how would I determine that?
>>
>> “Lyndon J Clarke” wrote in message
>> news:xxxxx@ntfsd…
>>> Unresolved runtime linkage?
>>>
>>> “Neil Weicher” wrote in message news:xxxxx@ntfsd…
>>>> My legacy FSFD driver is not being loaded on a Windows 2003 Server.
>>>>
>>>> Last time this happened it was because the customer was running inside
>>>> a
>>>> Virtuozzo container, but this is the first time I am seeing this on a
>>>> physical machine.
>>>>
>>>> All the files and registry entries seem to be in-place. I even write a
>>>> log entry as the first order of business in DriverEntry, but nothing is
>>>> showing up in the event log.
>>>>
>>>> When I try to start it with OSRLoader, I get the message: "The service
>>>> cannot be started, either because it is disabled or because it has no
>>>> enabled devices associated with it. "
>>>>
>>>> Any idea what to look at?
>>>>
>>>> Thanks.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
Neil - Nice I guess point is that, maybe the particular ‘ntoskrnl’ (or
hal.dll) on this machine does not export something which your driver
imports. I only mention it in the first place, because I had a similar
experience. Good luck - Lyndon
“Neil Weicher” wrote in message news:xxxxx@ntfsd…
> Hi Lyndon - I will definitely take a look. I would have thought that
> without ntoskrnl, a whole lot of other things would fail as well. - Neil
>
> “Lyndon J Clarke” wrote in message
> news:xxxxx@ntfsd…
>> Well, how about dumpbin/imports on your driver, and dumpbin/exports on
>> anything on which driver depends (such as, whatever ‘ntoskrnl’ is on the
>> machine)? Neil, it’s just a long shot, but I’ve had the experience
>> before.
>>
>> “Neil Weicher” wrote in message news:xxxxx@ntfsd…
>>> Interesting suggestion, but I am not linking to anything out of the
>>> ordinary. However, how would I determine that?
>>>
>>> “Lyndon J Clarke” wrote in message
>>> news:xxxxx@ntfsd…
>>>> Unresolved runtime linkage?
>>>>
>>>> “Neil Weicher” wrote in message news:xxxxx@ntfsd…
>>>>> My legacy FSFD driver is not being loaded on a Windows 2003 Server.
>>>>>
>>>>> Last time this happened it was because the customer was running inside
>>>>> a
>>>>> Virtuozzo container, but this is the first time I am seeing this on a
>>>>> physical machine.
>>>>>
>>>>> All the files and registry entries seem to be in-place. I even write a
>>>>> log entry as the first order of business in DriverEntry, but nothing
>>>>> is showing up in the event log.
>>>>>
>>>>> When I try to start it with OSRLoader, I get the message: "The service
>>>>> cannot be started, either because it is disabled or because it has no
>>>>> enabled devices associated with it. "
>>>>>
>>>>> Any idea what to look at?
>>>>>
>>>>> Thanks.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
I am sharing my experience, please do not ask reason as I still have to figure them out.
I got something exactly similar few months back on few machine with one driver (not a filter driver neither a FSD)
Initially NtLoadDriver was giving same error,
"The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. "
I tried some registry manipulation and it worked. I deleted the Enum key inside the driver key, tried to load it and this NtLoadDriver returned success.
Same jack worked on 2-3 machines.
How!!! please read the first line…
Thanks
Aditya
Depends.exe is, again, probably the easiest to figure out if this is the problem, and if it is, the cause (symbol(s) that are missing).
? S
-----Original Message-----
From: Lyndon J Clarke
Sent: Thursday, January 08, 2009 00:10
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] Legacy Filter Driver won’t start in Windows 2003
Neil - Nice I guess point is that, maybe the particular ‘ntoskrnl’ (or
hal.dll) on this machine does not export something which your driver
imports. I only mention it in the first place, because I had a similar
experience. Good luck - Lyndon
“Neil Weicher” wrote in message news:xxxxx@ntfsd…
> Hi Lyndon - I will definitely take a look. I would have thought that
> without ntoskrnl, a whole lot of other things would fail as well. - Neil
>
> “Lyndon J Clarke” wrote in message
> news:xxxxx@ntfsd…
>> Well, how about dumpbin/imports on your driver, and dumpbin/exports on
>> anything on which driver depends (such as, whatever ‘ntoskrnl’ is on the
>> machine)? Neil, it’s just a long shot, but I’ve had the experience
>> before.
>>
>> “Neil Weicher” wrote in message news:xxxxx@ntfsd…
>>> Interesting suggestion, but I am not linking to anything out of the
>>> ordinary. However, how would I determine that?
>>>
>>> “Lyndon J Clarke” wrote in message
>>> news:xxxxx@ntfsd…
>>>> Unresolved runtime linkage?
>>>>
>>>> “Neil Weicher” wrote in message news:xxxxx@ntfsd…
>>>>> My legacy FSFD driver is not being loaded on a Windows 2003 Server.
>>>>>
>>>>> Last time this happened it was because the customer was running inside
>>>>> a
>>>>> Virtuozzo container, but this is the first time I am seeing this on a
>>>>> physical machine.
>>>>>
>>>>> All the files and registry entries seem to be in-place. I even write a
>>>>> log entry as the first order of business in DriverEntry, but nothing
>>>>> is showing up in the event log.
>>>>>
>>>>> When I try to start it with OSRLoader, I get the message: "The service
>>>>> cannot be started, either because it is disabled or because it has no
>>>>> enabled devices associated with it. "
>>>>>
>>>>> Any idea what to look at?
>>>>>
>>>>> Thanks.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
—
NTFSD is sponsored by OSR
For our schedule debugging and file system seminars
(including our new fs mini-filter seminar) visit:
http://www.osr.com/seminars
You are currently subscribed to ntfsd as: xxxxx@valhallalegends.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Another reason I have seen in the past (although it seems unlikely in
this scenario) is that if you try to load a boot time driver from a FAT
file system volume, the driver’s file name must be 8.3 compatible.
Otherwise, the bootstrap loader cannot access the file. I have not
tried to use the image path mechanism to specify an 8.3 name - I just
made the driver name be less than 9 characters.
It’s certainly unlikely these days, but it does cause this behavior.
Tony
OSR
> It is happening on Windows 2003 Server. This is the first time I have ever
seen this on a phyiscal machine. It is running on plenty of real and virtual
2003 boxes.
And what is the build env used?
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com
Thanks to all for the suggestions. We’re caught in the famous “hurry up and
wait” situation that most here have experienced with customers.
“Lyndon J Clarke” wrote in message
news:xxxxx@ntfsd…
> Well, how about dumpbin/imports on your driver, and dumpbin/exports on
> anything on which driver depends (such as, whatever ‘ntoskrnl’ is on the
> machine)? Neil, it’s just a long shot, but I’ve had the experience before.
>
> “Neil Weicher” wrote in message news:xxxxx@ntfsd…
>> Interesting suggestion, but I am not linking to anything out of the
>> ordinary. However, how would I determine that?
>>
>> “Lyndon J Clarke” wrote in message
>> news:xxxxx@ntfsd…
>>> Unresolved runtime linkage?
>>>
>>> “Neil Weicher” wrote in message news:xxxxx@ntfsd…
>>>> My legacy FSFD driver is not being loaded on a Windows 2003 Server.
>>>>
>>>> Last time this happened it was because the customer was running inside
>>>> a
>>>> Virtuozzo container, but this is the first time I am seeing this on a
>>>> physical machine.
>>>>
>>>> All the files and registry entries seem to be in-place. I even write a
>>>> log entry as the first order of business in DriverEntry, but nothing is
>>>> showing up in the event log.
>>>>
>>>> When I try to start it with OSRLoader, I get the message: "The service
>>>> cannot be started, either because it is disabled or because it has no
>>>> enabled devices associated with it. "
>>>>
>>>> Any idea what to look at?
>>>>
>>>> Thanks.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>