STATUS_OBJECT_PATH_NOT_FOUND 0xC000003a win2k?

NTFSD
1

Hi all,

I’m getting a STATUS_OBJECT_PATH_NOT_FOUND failure on win2k when forwarding
a CREATE irp synchronously to NTFS. The path name is of the format
"\some\path\name", and I can find nothing wrong with the UNICODE_STRING in
the file object that I’m forwarding with the IRP. This same exact code path
works just fine on winXP, win2k3 server. Does anyone know of any reason
that I would get this failure code on a create IRP on win2k, and not the
others? Has the behavior of NTFS with respect to this changed any? The
directory definitely exists, because I’ve seen a file being opened in the
directory previously.

Finally, would/could there be any other reason for this return code other
than a messed up pathname, such as sharing problems or access control
problems? Just looking for ideas…

Thanks for any help,
Matt

2

> I’m getting a STATUS_OBJECT_PATH_NOT_FOUND failure on win2k when

forwarding
a CREATE irp synchronously to NTFS. The path name is of the format

Well, sorry for kinda stupid question, but isn’t the problem
just what the status code says, so “The path has not been found” ?

L.

3

Case sensitivity?

----- Original Message -----
From: “Matthew N. White”
To: “Windows File Systems Devs Interest List”
Sent: Wednesday, January 25, 2006 1:08 PM
Subject: [ntfsd] STATUS_OBJECT_PATH_NOT_FOUND 0xC000003a win2k?

> Hi all,
>
> I’m getting a STATUS_OBJECT_PATH_NOT_FOUND failure on win2k when
> forwarding
> a CREATE irp synchronously to NTFS. The path name is of the format
> "\some\path\name", and I can find nothing wrong with the UNICODE_STRING
> in
> the file object that I’m forwarding with the IRP. This same exact code
> path
> works just fine on winXP, win2k3 server. Does anyone know of any reason
> that I would get this failure code on a create IRP on win2k, and not the
> others? Has the behavior of NTFS with respect to this changed any? The
> directory definitely exists, because I’ve seen a file being opened in the
> directory previously.
>
> Finally, would/could there be any other reason for this return code other
> than a messed up pathname, such as sharing problems or access control
> problems? Just looking for ideas…
>
> Thanks for any help,
> Matt
>
>
>
>
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@privtek.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

4

No, the path definitely exists, b/c as I said, I opened a file that is in
the directory successfully.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Ladislav Zezula
Sent: Wednesday, January 25, 2006 4:32 PM
To: Windows File Systems Devs Interest List
Subject: Re: [ntfsd] STATUS_OBJECT_PATH_NOT_FOUND 0xC000003a win2k?

I’m getting a STATUS_OBJECT_PATH_NOT_FOUND failure on win2k when
forwarding a CREATE irp synchronously to NTFS. The path name is of
the format

Well, sorry for kinda stupid question, but isn’t the problem just what the
status code says, so “The path has not been found” ?

L.

Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@bitarmor.com To unsubscribe
send a blank email to xxxxx@lists.osr.com

5

Is that a guess, or are you saying that win2k is case sensitive and the
others are not?

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Dan Kyler
Sent: Wednesday, January 25, 2006 6:39 PM
To: Windows File Systems Devs Interest List
Subject: Re: [ntfsd] STATUS_OBJECT_PATH_NOT_FOUND 0xC000003a win2k?

Case sensitivity?

----- Original Message -----
From: “Matthew N. White”
To: “Windows File Systems Devs Interest List”
Sent: Wednesday, January 25, 2006 1:08 PM
Subject: [ntfsd] STATUS_OBJECT_PATH_NOT_FOUND 0xC000003a win2k?

> Hi all,
>
> I’m getting a STATUS_OBJECT_PATH_NOT_FOUND failure on win2k when
> forwarding
> a CREATE irp synchronously to NTFS. The path name is of the format
> "\some\path\name", and I can find nothing wrong with the UNICODE_STRING
> in
> the file object that I’m forwarding with the IRP. This same exact code
> path
> works just fine on winXP, win2k3 server. Does anyone know of any reason
> that I would get this failure code on a create IRP on win2k, and not the
> others? Has the behavior of NTFS with respect to this changed any? The
> directory definitely exists, because I’ve seen a file being opened in the
> directory previously.
>
> Finally, would/could there be any other reason for this return code other
> than a messed up pathname, such as sharing problems or access control
> problems? Just looking for ideas…
>
> Thanks for any help,
> Matt
>
>
>
>
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@privtek.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@bitarmor.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

6

Yes, it’s a guess, as I have seen neither your code, nor a directory listing
from your system.

Yes, by default, W2K is case sensitive, and WXP and W2K3 are not. The
behavior is controlled with the registry key …\Control\Session
Manager\kernel\obcaseinsensitive, which is 1 by default on the newer OSes
and absent on W2K.

If the case of the path you are opening does not exactly match the on-disk
case of the actual path, and the open does not specify case insensitivity,
that is most likely the problem.

  • Dan.

----- Original Message -----
From: “Matthew N. White”
To: “Windows File Systems Devs Interest List”
Sent: Thursday, January 26, 2006 7:46 AM
Subject: RE: [ntfsd] STATUS_OBJECT_PATH_NOT_FOUND 0xC000003a win2k?

> Is that a guess, or are you saying that win2k is case sensitive and the
> others are not?
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Dan Kyler
> Sent: Wednesday, January 25, 2006 6:39 PM
> To: Windows File Systems Devs Interest List
> Subject: Re: [ntfsd] STATUS_OBJECT_PATH_NOT_FOUND 0xC000003a win2k?
>
> Case sensitivity?
>
> ----- Original Message -----
> From: “Matthew N. White”
> To: “Windows File Systems Devs Interest List”
> Sent: Wednesday, January 25, 2006 1:08 PM
> Subject: [ntfsd] STATUS_OBJECT_PATH_NOT_FOUND 0xC000003a win2k?
>
>
>> Hi all,
>>
>> I’m getting a STATUS_OBJECT_PATH_NOT_FOUND failure on win2k when
>> forwarding
>> a CREATE irp synchronously to NTFS. The path name is of the format
>> "\some\path\name", and I can find nothing wrong with the UNICODE_STRING
>> in
>> the file object that I’m forwarding with the IRP. This same exact code
>> path
>> works just fine on winXP, win2k3 server. Does anyone know of any reason
>> that I would get this failure code on a create IRP on win2k, and not the
>> others? Has the behavior of NTFS with respect to this changed any? The
>> directory definitely exists, because I’ve seen a file being opened in the
>> directory previously.
>>
>> Finally, would/could there be any other reason for this return code other
>> than a messed up pathname, such as sharing problems or access control
>> problems? Just looking for ideas…
>>
>> Thanks for any help,
>> Matt
>>
>>
>>
>>
>>
>>
>> —
>> Questions? First check the IFS FAQ at
>> https://www.osronline.com/article.cfm?id=17
>>
>> You are currently subscribed to ntfsd as: xxxxx@privtek.com
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@bitarmor.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@privtek.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

7

Try using the OBJ_CASE_INSENSITIVE to override the default 2k behavior.
Look up the following URL for more details:
http://support.microsoft.com/default.aspx?scid=kb;en-us;817921

-Ilya.
-------------- Original message --------------
From: “Dan Kyler”

> Yes, it’s a guess, as I have seen neither your code, nor a directory listing
> from your system.
>
> Yes, by default, W2K is case sensitive, and WXP and W2K3 are not. The
> behavior is controlled with the registry key …\Control\Session
> Manager\kernel\obcaseinsensitive, which is 1 by default on the newer OSes
> and absent on W2K.
>
> If the case of the path you are opening does not exactly match the on-disk
> case of the actual path, and the open does not specify case insensitivity,
> that is most likely the problem.
>

8

Sweet. Thanks, I will look into this…

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Dan Kyler
Sent: Thursday, January 26, 2006 10:19 AM
To: Windows File Systems Devs Interest List
Subject: Re: [ntfsd] STATUS_OBJECT_PATH_NOT_FOUND 0xC000003a win2k?

Yes, it’s a guess, as I have seen neither your code, nor a directory listing
from your system.

Yes, by default, W2K is case sensitive, and WXP and W2K3 are not. The
behavior is controlled with the registry key …\Control\Session
Manager\kernel\obcaseinsensitive, which is 1 by default on the newer OSes
and absent on W2K.

If the case of the path you are opening does not exactly match the on-disk
case of the actual path, and the open does not specify case insensitivity,
that is most likely the problem.

  • Dan.

----- Original Message -----
From: “Matthew N. White”
To: “Windows File Systems Devs Interest List”
Sent: Thursday, January 26, 2006 7:46 AM
Subject: RE: [ntfsd] STATUS_OBJECT_PATH_NOT_FOUND 0xC000003a win2k?

> Is that a guess, or are you saying that win2k is case sensitive and the
> others are not?
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Dan Kyler
> Sent: Wednesday, January 25, 2006 6:39 PM
> To: Windows File Systems Devs Interest List
> Subject: Re: [ntfsd] STATUS_OBJECT_PATH_NOT_FOUND 0xC000003a win2k?
>
> Case sensitivity?
>
> ----- Original Message -----
> From: “Matthew N. White”
> To: “Windows File Systems Devs Interest List”
> Sent: Wednesday, January 25, 2006 1:08 PM
> Subject: [ntfsd] STATUS_OBJECT_PATH_NOT_FOUND 0xC000003a win2k?
>
>
>> Hi all,
>>
>> I’m getting a STATUS_OBJECT_PATH_NOT_FOUND failure on win2k when
>> forwarding
>> a CREATE irp synchronously to NTFS. The path name is of the format
>> "\some\path\name", and I can find nothing wrong with the UNICODE_STRING
>> in
>> the file object that I’m forwarding with the IRP. This same exact code
>> path
>> works just fine on winXP, win2k3 server. Does anyone know of any reason
>> that I would get this failure code on a create IRP on win2k, and not the
>> others? Has the behavior of NTFS with respect to this changed any? The
>> directory definitely exists, because I’ve seen a file being opened in the
>> directory previously.
>>
>> Finally, would/could there be any other reason for this return code other
>> than a messed up pathname, such as sharing problems or access control
>> problems? Just looking for ideas…
>>
>> Thanks for any help,
>> Matt
>>
>>
>>
>>
>>
>>
>> —
>> Questions? First check the IFS FAQ at
>> https://www.osronline.com/article.cfm?id=17
>>
>> You are currently subscribed to ntfsd as: xxxxx@privtek.com
>> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@bitarmor.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
>
> —
> Questions? First check the IFS FAQ at
> https://www.osronline.com/article.cfm?id=17
>
> You are currently subscribed to ntfsd as: xxxxx@privtek.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com

—
Questions? First check the IFS FAQ at
https://www.osronline.com/article.cfm?id=17

You are currently subscribed to ntfsd as: xxxxx@bitarmor.com
To unsubscribe send a blank email to xxxxx@lists.osr.com