Windows Installer 1335 error
I'm getting a Windows Installer 1335 error when I install my program on Windows 2000. No errors occur when it is installed on XP. I've confirmed that the probelm isn't a bad CD. Also, the install doesn't use any network resources and I tried updating the windows installer to version 3.0. Nothing has worked. Here is the error as it appears in the install log file. It is basically the same as the error you see during the installation.
Error 1335. The cabinet file '_D688138D484689C6C935433D08BFD983' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
MSI (s) (7C:14): Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (7C:14): Product: ********* -- Error 1335. The cabinet file '_D688138D484689C6C935433D08BFD983' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the C
D-ROM, or a problem with this package.
Any help would be much appreciated
Error 1335. The cabinet file '_D688138D484689C6C935433D08BFD983' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
MSI (s) (7C:14): Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (7C:14): Product: ********* -- Error 1335. The cabinet file '_D688138D484689C6C935433D08BFD983' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the C
D-ROM, or a problem with this package.
Any help would be much appreciated
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
brenthunter2005
19 years ago
If you are installing from the CDROM, try copying the entire CD down to a temporary folder on your C: drive and attempt to run it from that location.
I've had a similar issue in the past where local security policies prevented the installation of software from CDROM drives.
[8D] Keep cool. [8D]
I've had a similar issue in the past where local security policies prevented the installation of software from CDROM drives.
[8D] Keep cool. [8D]
Posted by:
WiseUser
19 years ago
Did you create the MSI?
Have you checked which files are supposed to be inside that particular cabinet file?
Otherwise, you could try creating an administrative image (/a) on a network share from your "good" XP machine. Then try installing the product on your 2000 PC from the admin image.
Have you checked which files are supposed to be inside that particular cabinet file?
Otherwise, you could try creating an administrative image (/a) on a network share from your "good" XP machine. Then try installing the product on your 2000 PC from the admin image.
Posted by:
Galen
19 years ago
Nope, copying it to the hard drive and then trying to install produces the same error message. Anymore ideas?
Posted by:
brenthunter2005
19 years ago
WOW, thats a strange one Galen. Have you had any other strange issues with that particular Windows 2000 computer?
Posted by:
Galen
19 years ago
I finally got it to install. I noticed in the log file that the installation failed at a particular file. The error was fixed by removing that dll file from the setup project and then adding it again (keeping the same properties). All this did (as far as I know) was change the sequence that the files are installed. It is still unclear what caused the error. Is this a bug in Windows Installer that only occurs in Windows 2000? The error had nothing to do with registering the dll so I still don't understand the error. So even though I fixed the problem it still isn't very satisfying to not know why the error was caused in the first place.
Posted by:
Galen
19 years ago
Making an administrative image on a good XP machine and then taking it to a Windows 2000 machine with a usb drive worked. Its at least a work around of the problem.
Thanks to everyone that helped
Thanks to everyone that helped
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.