Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"error 1325 : <filename> is not a valid short filename"

Status
Not open for further replies.

Leozack

MIS
Oct 25, 2002
867
0
0
GB
Hi all - I'm getting this error when deploying some software via GPO that deployed fine to XP 32bit but not to win7 64bit and I don't know why. I found that if I literally make every folder in the install path 8 letters or less the error doens't happen, but on the software I did that with I then had corrupted results in some of the config files and such where folder paths had folders over 8 letters they wer ereplaced with random 8 character strings :( what's stranger is not only does it deploy fine to XP 32bit, but even on this win7 64bit if I run the install manually it works - it only fails when it's deployed to clients from GPO and installed at startup. I'm not getting much help from software vendors and I'm finding very little online that doesnt' refer to office 97 or something old and suggesting using msi cleanup util or whatever. Nearest thing I've found it this but I don't have enough time onsite to keep testing so I'm really hoping anyone can shed some light on this?


_________________________________
Leozack
Code:
MakeUniverse($infinity,1,42);
 
I've found some further information but it's not overly helpful suggestions like changing your username or using a different account or disabling offline files!




_________________________________
Leozack
Code:
MakeUniverse($infinity,1,42);
 
I wonder if this might work, or give you a few clues, in Windows 7? Fsutil.exe is available in Windows 7 with the "8dot3name 8dot3name management" command. I must admit I also wonder if it is relevant to your problem too?


How to Disable the 8.3 Name Creation on NTFS Partitions



Does including full paths in quotes make any difference?
 
I'm not in a hurry to change the way the system works with 8.3 since only some packages are having this problem and I know by disabled 8.3 to "speed up for XP pc" in old tips I actually found certain software failed to run because it relied on it (you can't help people writing crao sofware I guess - age old problem!)

I'm not giving paths in quotes or otherwise - I'm making a GPO and setting an MSI to deploy with it. Some work fine, but particular ones fail with this message. But if you run them while logged in they work fine - they also deploy fine (while not logged in) as they always did on 32bit XP.

So I dunno if it's a problem with 64bit, or win7, or permissions (works when logged in, not as system during startup as deployed msi via gpo) but I dont' really have resources to test it (already lost a whole day trying to get it going and eventually managed it by making all folders in path 8 chars - which then corrupts/fails parts of the program containing long folders even though it installs ok!)

:/

_________________________________
Leozack
Code:
MakeUniverse($infinity,1,42);
 
Incase anyone wants to know I eventually found the answer to this! Believe it or not it actually came down to NTFS permissions (relevant to filename/folder length how??)

The problem was on the ROOT of the share being used, someone hsd stripped back NTFS permissions to certain users. eg

\\servers\apps\programname

"programname is not a valid short filename" etc, and you check all the permissions in that folder and so on and wonder why it works fine on XP 32bit but not win7 64bit.

The reality is up at the apps level, you need to give either users or auth users read permissions - I found 2 different shares using different tickboxes under advanced permissions but the end result was equivilent I think to basic reading capacity.

Anyway once we did that, we found we cuold install said software. There were plenty of other solutions offered by people but none of them worked or were relevant. This one was a TOTAL waste of many hours of work mainly due to the completely red herring nature of what little information you are given. Another lesson learnt was always be aware of what permissions people have set on your share roots!

Anyway hope this helps someone somewhere

_________________________________
Leozack
Code:
MakeUniverse($infinity,1,42);
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top