Specified path is too long

[Swan]

We have some customers using a .msi produced by Advanced Installer 4.8.1 that are running into an "Installer Information" alert which states:
"The specified path is too long: C:\ProgramData\Documents\Neon Software".

The problem seems to occur when running the installer on a Vista machine that has been upgraded from an XP machine. It may have something to do with the folders in question being symlinked but that's just a theory.

I do see a forum message discussing a similar problem that occurs as the result of a substituted drive, but I don't belive the conditions are the same as we are encountering:
http://www.advancedinstaller.com/forums ... +path+long

Is there some explanation or workaround for this problem or perhaps more information we can provide that will help diagnose the problem?

Michael Swan
Neon Software, Inc.

Here is a snippet from the installer log file where the problem occurs:

1: {81F9D463-3B8B-40F2-BC9D-9F301532336F} 2: {EE276E83-0167-48B8-9CBF-794B34FAAD9D} 3: C:\ProgramData\Documents\Neon Software\LANsurveyor\Recovered Files\
Action 18:46:29: RemoveODBC. Removing ODBC components
Action 18:46:29: CreateFolders. Creating folders
CreateFolders: Folder: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\LANsurveyor\
CreateFolders: Folder: C:\Program Files\LANsurveyor\Neon Responder Updaters\
CreateFolders: Folder: C:\ProgramData\Documents\Neon Software\LANsurveyor\
Error 1320. The specified path is too long: C:\ProgramData\Documents\Neon Software
MSI (s) (5C:00) [18:46:34:698]: Product: LANsurveyor -- Error 1320. The specified path is too long: C:\ProgramData\Documents\Neon Software

Are you sure you want to cancel?
Error 1320. The specified path is too long: C:\ProgramData\Documents\Neon Software
MSI (s) (5C:00) [18:46:37:219]: Product: LANsurveyor -- Error 1320. The specified path is too long: C:\ProgramData\Documents\Neon Software

Are you sure you want to cancel?
Action ended 18:46:38: InstallFinalize. Return value 2.
Action 18:46:38: Rollback. Rolling back action:

[gigi]

Hi,

The error 1320 usually occurs when using the DOS SUBST command to substitute a drive. This is because Windows Installer doesn't support drive substitution.

If this is not the case then move the package to other folder with the path smaller than 150 chars and run it from there. Error 1320 is described here:
http://www.appdeploy.com/msierrors/detail.asp?id=83

Also please try to reproduce this behavior on other computer to see if you get the same behavior.

Let us know if the problem persist.

Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com

[Swan]

Hi Gigi,

Thanks for your reply.

Is there anything within the installer that would cause the DOS SUBST command to be executed or would SUBST have to be explicitly executed by the user separate from the installation that would affect the installation?

I don't believe the 1320 error has to do with the path length as the installer log clearly shows the path as "C:\ProgramData\Documents\Neon Software" which is clearly shorter than the 150 char limit of the Windows Installer. Could it be that a portion of the displayed path is a symlink to some longer path? For example, could "C:\ProgramData" be a symlink to some unexpectedly long path that doesn't get displayed by the alert?

Michael Swan
Neon Software, Inc.

[gigi]

Hi Michael,

The SUBST command can be used to associate a path with a drive letter (you cannot install in a substituted drive).

I'm not sure if this is the case. Have you tried to reproduce this behavior on other computer?

Best Regards,
Gigi
______________
Gheorghe Rada
Advanced Installer Team
http://www.advancedinstaller.com

[Swan]

Hello,

After talking with the customer, it appears the root path in question, "C:\ProgramData\Documents\" was damaged somehow on his Vista OEM installation. Even when logged in as Administrator, he was not able to change to that folder. So, it looks like the Error 1320 diagnosis of "path too long" was a little misleading to everyone. In any case, it looks to be a user problem, rather than an installer problem. Thanks for your help.

Michael Swan
Neon Software, Inc.

[wtbaxter]

We have had several users complain of the exact same thing. We would like to understand if this is really an isolated instance or if there is something about the way that path is created, which would cause this problem.

Please advise.

Thanks, Bill.

[gigi]

Hi Bill,

In order to investigate this problem please send the AIP file (if doesn't contain any confidential informations) or a small similar test case reproducing this behavior.

Regards,
Gigi