Couldn't generate 8dot3 name in particular folder on windows server
up vote
1
down vote
favorite
I was reported that our application can't generate 8.3 name in a particular folder.
The first thing pop up my mind is 8.3 creation setting probably is disabled.
Well, it was enabled. I modified the registry key and reboot too which didn't work either.
I found dir /x not able to show 8dot3 name in that path as well.
The weirdest thing I found is it only becomes invalid in this particular folder!
If I move to another folder in D: then the operation will work without problem. For instance, D:anotherfolderPML_18WW1PNL601.ini will be converted to
D:anotherfolderPML_18WW1P~1.INI correctly.
I wonder if it has something to do with permission but not sure where to start. I mean my account is admin already what else should I do?
I copy a new one as @barlop suggested. Surprisingly, it can generate 8.3 name successfully.
Furthermore, I found in D:. 8.3 creation only work on those folders and files created by me.
Still, don't know what's going on here.
windows-server-2012-r2
asked Mar 23 at 2:51
蕭為元
1065
add a comment |
up vote
1
down vote
favorite
I was reported that our application can't generate 8.3 name in a particular folder.
The first thing pop up my mind is 8.3 creation setting probably is disabled.
Well, it was enabled. I modified the registry key and reboot too which didn't work either.
I found dir /x not able to show 8dot3 name in that path as well.
The weirdest thing I found is it only becomes invalid in this particular folder!
If I move to another folder in D: then the operation will work without problem. For instance, D:anotherfolderPML_18WW1PNL601.ini will be converted to
D:anotherfolderPML_18WW1P~1.INI correctly.
I wonder if it has something to do with permission but not sure where to start. I mean my account is admin already what else should I do?
I copy a new one as @barlop suggested. Surprisingly, it can generate 8.3 name successfully.
Furthermore, I found in D:. 8.3 creation only work on those folders and files created by me.
Still, don't know what's going on here.
windows-server-2012-r2
asked Mar 23 at 2:51
蕭為元
1065
1
It looks like you have an issue that some directories support 8.3 names while other directories on the same disk do not. Please edit your question to focus on the behavior ofdir /xand deemphasize the programming interface aspect.
– Scott
Mar 23 at 3:24
no idea but what if now that you have enabled the 8.3 thing, if youcopy 18WW1PNL601.ini 28WW1PNL601.inithen do dir /x will the new file show as 8.3 or not?
– barlop
Mar 23 at 4:35
another thing to check is if you have any other folders where this is happening
– barlop
Mar 23 at 4:36
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I was reported that our application can't generate 8.3 name in a particular folder.
The first thing pop up my mind is 8.3 creation setting probably is disabled.
Well, it was enabled. I modified the registry key and reboot too which didn't work either.
I found dir /x not able to show 8dot3 name in that path as well.
The weirdest thing I found is it only becomes invalid in this particular folder!
If I move to another folder in D: then the operation will work without problem. For instance, D:anotherfolderPML_18WW1PNL601.ini will be converted to
D:anotherfolderPML_18WW1P~1.INI correctly.
I wonder if it has something to do with permission but not sure where to start. I mean my account is admin already what else should I do?
I copy a new one as @barlop suggested. Surprisingly, it can generate 8.3 name successfully.
Furthermore, I found in D:. 8.3 creation only work on those folders and files created by me.
Still, don't know what's going on here.
windows-server-2012-r2
asked Mar 23 at 2:51
蕭為元
1065
I was reported that our application can't generate 8.3 name in a particular folder.
The first thing pop up my mind is 8.3 creation setting probably is disabled.
Well, it was enabled. I modified the registry key and reboot too which didn't work either.
I found dir /x not able to show 8dot3 name in that path as well.
The weirdest thing I found is it only becomes invalid in this particular folder!
If I move to another folder in D: then the operation will work without problem. For instance, D:anotherfolderPML_18WW1PNL601.ini will be converted to
D:anotherfolderPML_18WW1P~1.INI correctly.
I wonder if it has something to do with permission but not sure where to start. I mean my account is admin already what else should I do?
I copy a new one as @barlop suggested. Surprisingly, it can generate 8.3 name successfully.
Furthermore, I found in D:. 8.3 creation only work on those folders and files created by me.
Still, don't know what's going on here.
windows-server-2012-r2
windows-server-2012-r2
asked Mar 23 at 2:51
蕭為元
1065
asked Mar 23 at 2:51
蕭為元
1065
edited Mar 23 at 6:48
asked Mar 23 at 2:51
蕭為元
1065
asked Mar 23 at 2:51
蕭為元
1065
asked Mar 23 at 2:51
蕭為元
1065
1065
1
It looks like you have an issue that some directories support 8.3 names while other directories on the same disk do not. Please edit your question to focus on the behavior ofdir /xand deemphasize the programming interface aspect.
– Scott
Mar 23 at 3:24
no idea but what if now that you have enabled the 8.3 thing, if youcopy 18WW1PNL601.ini 28WW1PNL601.inithen do dir /x will the new file show as 8.3 or not?
– barlop
Mar 23 at 4:35
another thing to check is if you have any other folders where this is happening
– barlop
Mar 23 at 4:36
add a comment |
1
It looks like you have an issue that some directories support 8.3 names while other directories on the same disk do not. Please edit your question to focus on the behavior ofdir /xand deemphasize the programming interface aspect.
– Scott
Mar 23 at 3:24
no idea but what if now that you have enabled the 8.3 thing, if youcopy 18WW1PNL601.ini 28WW1PNL601.inithen do dir /x will the new file show as 8.3 or not?
– barlop
Mar 23 at 4:35
another thing to check is if you have any other folders where this is happening
– barlop
Mar 23 at 4:36
1
1
It looks like you have an issue that some directories support 8.3 names while other directories on the same disk do not. Please edit your question to focus on the behavior of
dir /x and deemphasize the programming interface aspect.– Scott
Mar 23 at 3:24
It looks like you have an issue that some directories support 8.3 names while other directories on the same disk do not. Please edit your question to focus on the behavior of
dir /x and deemphasize the programming interface aspect.– Scott
Mar 23 at 3:24
no idea but what if now that you have enabled the 8.3 thing, if you
copy 18WW1PNL601.ini 28WW1PNL601.ini then do dir /x will the new file show as 8.3 or not?– barlop
Mar 23 at 4:35
no idea but what if now that you have enabled the 8.3 thing, if you
copy 18WW1PNL601.ini 28WW1PNL601.ini then do dir /x will the new file show as 8.3 or not?– barlop
Mar 23 at 4:35
another thing to check is if you have any other folders where this is happening
– barlop
Mar 23 at 4:36
another thing to check is if you have any other folders where this is happening
– barlop
Mar 23 at 4:36
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
The reason for 8dot3names creation for particular folders is because these folders were created when the 8dot3name setting was enabled on the volume these folders exist in.
You can try this experiment by enabling this setting, then create a folder and try to obtain its short name.
You can read more about this from here:
NTFS 8.3 short names
As I've already been through this problem.
answered Nov 26 at 6:44
Jeries Philip Abedrabbo
1
New contributor
Jeries Philip Abedrabbo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
The reason for 8dot3names creation for particular folders is because these folders were created when the 8dot3name setting was enabled on the volume these folders exist in.
You can try this experiment by enabling this setting, then create a folder and try to obtain its short name.
You can read more about this from here:
NTFS 8.3 short names
As I've already been through this problem.
answered Nov 26 at 6:44
Jeries Philip Abedrabbo
1
New contributor
Jeries Philip Abedrabbo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
The reason for 8dot3names creation for particular folders is because these folders were created when the 8dot3name setting was enabled on the volume these folders exist in.
You can try this experiment by enabling this setting, then create a folder and try to obtain its short name.
You can read more about this from here:
NTFS 8.3 short names
As I've already been through this problem.
answered Nov 26 at 6:44
Jeries Philip Abedrabbo
1
New contributor
Jeries Philip Abedrabbo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
up vote
0
down vote
The reason for 8dot3names creation for particular folders is because these folders were created when the 8dot3name setting was enabled on the volume these folders exist in.
You can try this experiment by enabling this setting, then create a folder and try to obtain its short name.
You can read more about this from here:
NTFS 8.3 short names
As I've already been through this problem.
answered Nov 26 at 6:44
Jeries Philip Abedrabbo
1
New contributor
Jeries Philip Abedrabbo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
The reason for 8dot3names creation for particular folders is because these folders were created when the 8dot3name setting was enabled on the volume these folders exist in.
You can try this experiment by enabling this setting, then create a folder and try to obtain its short name.
You can read more about this from here:
NTFS 8.3 short names
As I've already been through this problem.
answered Nov 26 at 6:44
Jeries Philip Abedrabbo
1
New contributor
Jeries Philip Abedrabbo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 26 at 6:44
Jeries Philip Abedrabbo
1
New contributor
Jeries Philip Abedrabbo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 26 at 6:44
Jeries Philip Abedrabbo
1
answered Nov 26 at 6:44
Jeries Philip Abedrabbo
1
1
New contributor
Jeries Philip Abedrabbo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jeries Philip Abedrabbo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Jeries Philip Abedrabbo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1307010%2fcouldnt-generate-8dot3-name-in-particular-folder-on-windows-server%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
It looks like you have an issue that some directories support 8.3 names while other directories on the same disk do not. Please edit your question to focus on the behavior of
dir /xand deemphasize the programming interface aspect.– Scott
Mar 23 at 3:24
no idea but what if now that you have enabled the 8.3 thing, if you
copy 18WW1PNL601.ini 28WW1PNL601.inithen do dir /x will the new file show as 8.3 or not?– barlop
Mar 23 at 4:35
another thing to check is if you have any other folders where this is happening
– barlop
Mar 23 at 4:36