• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 9864
  • Last Modified:

Error 1325. <username> is not a valid short file name

Hi,

I have a strange problem here in the organization.
- We are running Active Directory and user's home folders (P: Drive) were moved from a windows 2003 server to a windows 2008 server.
- On clients (Windows XP), Favorites are redirected to their home folders in the registry:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders]
Both Values to "\\SERVER\Share$\username\Favorites"

Since this move, when installing/updating softwares in MSI format, this kind of error appears:

Error 1325. <username> is not a valid short file name.

Sometimes, the error number is not there.

Example of softwares getting the error:
- Adobe Acrobat Standard and Reader
- VMWare Workstation and Player
- Others that I cannot remember

I have managed to fix the error by setting the drive letter instead of the UNC in the registry: "P:\Favorites".

1. What does the Favorites path has to do with msi installations?
2. Is there something different with Windows Server 2008 that can cause this error because we did not get this error before?

Thanks for your help.
0
Bidonet
Asked:
Bidonet
  • 4
  • 3
  • 2
  • +1
3 Solutions
 
AwinishCommented:
The reason could be incorrect registry value as XP uses profile path as

c:\documents and settings\username & Win7/2008 uses C:\Users\username

So the registry path is not correctly modified mapped in windows 7.
Below link might solve your problem.

http://help.wugnet.com/vista/Unable-install-msi-packages-error-1325-ftopict130110.html
http://forums.techarena.in/active-directory/1110526.htm
http://www.eggheadcafe.com/software/aspnet/30523812/error-1325username-is-not-a-valid-short-file-name.aspx
0
 
johnb6767Commented:
Username should be %username%...

The way you have it is expecting to find a folder called "username". Should be able to change that in the policy and have it propagate down
0
 
johnb6767Commented:
Oh, and to answer the other part....

MSI packages enumerate the currently logged in user's Shell folders, User shell folders and the local machine Shell/User shell folders to make surE it can resolve the paths.. Standard behavior...
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
BidonetAuthor Commented:
Thanks for your replies.

I finally found the source of the problem.

This has nothing to do with the move from server 2003 to 2008.

The only change is that before, the homeshare was
- \\ServerName\Username$
Now it is:
- \\ServerName\Share$\Division\Username

- The permissions on "Username" is full acces for the user but the permission on "Share$" has no read access.  Even if the user can successuflly access the full UNC, MSI install files need "read" access on "Share$".
- It also appears that if the username is no longer than 8 characters, it is working fine even if user has no "read" access on "Share$"

So the fix would be to:
- Give READ access on "Share$" to the users or everyone
OR
- Conform user account to an 8 charaters or less format.

0
 
AwinishCommented:
Great Gesture Bidonet:
0
 
BidonetAuthor Commented:
For my part, I have given "read" access to the "Share$" to everyone so my problem is fixed bu I would be interested to know why this only affects user accounts longer than 8 characters.

Should I start another question or this could be answered in this one?
0
 
AwinishCommented:
Let this question be like & this & you can ask for additional help by clicking on top right corner by Request Attention.
0
 
BidonetAuthor Commented:
I found the solution myself "googling" with hints from your comments.
0
 
mcsalladCommented:
Ive solved this issue like bidonet did. My customer had a unc path for folder redirections to \\ServerName\Share\Division\Username. But no read on "Share" but fullaccess on rest, so i just added the read and everything was OK!

Thx for the solution!
0
 
AwinishCommented:
Nice to see, people are getting benefited..Kudos to Bidonet.
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 4
  • 3
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now