Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

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

Posted on 2010-11-12
10
Medium Priority
?
9,376 Views
Last Modified: 2012-05-10
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
Comment
Question by:Bidonet
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
  • 2
  • +1
10 Comments
 
LVL 24

Assisted Solution

by:Awinish
Awinish earned 1000 total points
ID: 34126319
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
 
LVL 66

Expert Comment

by:johnb6767
ID: 34126351
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
 
LVL 66

Assisted Solution

by:johnb6767
johnb6767 earned 1000 total points
ID: 34126355
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
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

 
LVL 5

Accepted Solution

by:
Bidonet earned 0 total points
ID: 34136698
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
 
LVL 24

Expert Comment

by:Awinish
ID: 34136728
Great Gesture Bidonet:
0
 
LVL 5

Author Comment

by:Bidonet
ID: 34136786
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
 
LVL 24

Expert Comment

by:Awinish
ID: 34136843
Let this question be like & this & you can ask for additional help by clicking on top right corner by Request Attention.
0
 
LVL 5

Author Closing Comment

by:Bidonet
ID: 34179144
I found the solution myself "googling" with hints from your comments.
0
 
LVL 4

Expert Comment

by:mcsallad
ID: 34851488
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
 
LVL 24

Expert Comment

by:Awinish
ID: 34851504
Nice to see, people are getting benefited..Kudos to Bidonet.
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Let's recap what we learned from yesterday's Skyport Systems webinar.
Microsoft Office 365 is a subscriptions based service which includes services like Exchange Online and Skype for business Online. These services integrate with Microsoft's online version of Active Directory called Azure Active Directory.
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…

610 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question