Help with MSI 1325
Help with MSI (Microsoft Installer) error 1325: ''[2]'' is not a valid short file name.
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
AppDeploy.com
20 years ago
Aside from a short file name issue, this error may also simply indicate an inability to locate a file.
Also see:
OFFXP: Error 1325 After You Reinstall Office to a New Drive, "This issue may occur if you have reinstalled Office XP on a new drive after you moved or removed the drive in which Office XP was originally installed."
If your installation is corrupted and Add/Remove Programs does not work for you, you may need to make use of the Windows Installer CleanUp Utilty
MSI Error 1325 can occur as a red herring if a 2303 happens before it. Your log might look something like this:
MSI (s) (70:2C): Note: 1: 2303 2: 5 3: B:\
MSI (s) (70:2C): Note: 1: 1325 2: AspenTech Error 1325.AspenTech is not a valid short file name. MSI (s) (70:2C): Product: Aspen Icarus 2004 -- Error 1325.AspenTech is not a valid short file name.
In this case, look to error 2303.
Also see:
OFFXP: Error 1325 After You Reinstall Office to a New Drive, "This issue may occur if you have reinstalled Office XP on a new drive after you moved or removed the drive in which Office XP was originally installed."
If your installation is corrupted and Add/Remove Programs does not work for you, you may need to make use of the Windows Installer CleanUp Utilty
MSI Error 1325 can occur as a red herring if a 2303 happens before it. Your log might look something like this:
MSI (s) (70:2C): Note: 1: 2303 2: 5 3: B:\
MSI (s) (70:2C): Note: 1: 1325 2: AspenTech Error 1325.AspenTech is not a valid short file name. MSI (s) (70:2C): Product: Aspen Icarus 2004 -- Error 1325.AspenTech is not a valid short file name.
In this case, look to error 2303.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.