MSI Error 1335 - Disk1.cab cannot be found

[afluffehbunneh]

Hello forums,

 

​It has been a while​ since I posted here, but this is the forum that got me interested in doing a lot of tech work. I had a problem a while back that this forum helped me solve, and was super helpful with. Here I am asking for help, yet again. I have helped some people on this forum with my old account, hopefully I can get an answer.

 

Issue:

​

I have created an .MSI package installation using Advanced Installer to help my company install Microsoft Dynamics Great Plains on their computers. We have decided to try an eliminate a receiver in the company as it caused issues, and so we have tried to make local installations for the users. I am attempting to get this .MSI package to expedite the​ process of an entire Great Plains installation, because as some of you know, this can be lengthy. I made the install and everything seemed fantastic. It ran flawlessly on 3 test computers I setup, and then on two User computers.

 

Problem:

After the 5th computer my .MSI package, which I had been installing through the network the whole time, started running into an error. the error is as follows:
​

"Error 1335. The cabinet file 'disk1.cab' 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."

 

I fo​und the error message identification number from within the logs output by the installation itself. The file itself is not from a CD, so it is not a CD-ROM problem. I have rebuilt the package 8 times, so I believe it is not an issue with the package. Our network is running perfect without any problems from other installations that are prebuilt from other places.

 

This is where it gets​ interesting. Sometimes when I get the error I can press the "Retry" button several times and it will go through. Almost like it is a Network issue. So, I sat down and thought through it and decided I would put the installation file on a flash drive and build it completely offline. After eliminating the Network I STILL RAN INTO THE ISSUE!! I hunted down the disk1.cab file it was referring to (which is supposed to be inside the database of the .MSI file) made sure it was properly located, and still the issue persists. The error seems to occur during the Copying new files... part of the installation.

 

A colleague o​f mine brought up an interesting point that I should try to use another program to build the package instead of Advanced Installer. From what I have seen however, Advanced Installer is a well-known/used program. If others were having this issue, I am sure they would have released a patch of sorts to fix it.

 

I am running out​ options, and mental capacity to understand the issue. Any help would be appreciated. I will attach a Log File from the MSI error that I receive when I manage to get the error again. Other than that I am not sure what other information I can give. Please ask if you would like anything to further understand this issue.

 

I will be working diligently, and if I come up with an answer miraculously I will post the answer on this forum. It seems like several others have had this issue as well.

​

Sorry for the length,

Fluffeh

​​

P.S. The install works on my machine every time and virtual machines located on my machine. Perhaps there is a directory that I am forgetting to share or...something? Not sure what this would be. I would think building it on a flash drive would of remedied this though.​ I just got it to work on the machine it kept failing on, and then it didn't work after uninstalling and trying again. Same installation file...interesting.

 

Edit: Changed media1.cab to say disk1.cab because of a transcribing error pointed out by Venomz1337

[Venomz1337]

I'm confused.

The error says media1.cab yet you think disk1.cab is the issue.

Am I missing something here?

[0x1e]

I have no idea about this but as a simple user, could it be an anti-virus problem, or is someone else accessing the same file?

 

Just throwing out some random thoughts.

[afluffehbunneh]

My fault on that I transcribed that message incorrectly. here are the log files for personal viewing. Media1.cab should be replaced with disk1.cab.

 

The log file was 8 mb so I will attach a snippet of it. I made sure to include the error and a good part of the before and after in the log.Log.txt

 

 

 

 

 

[afluffehbunneh]

The file is shared on the network, but I have tried again making sure there was nothing accessing the file as you stated. No dice. Still get the error. The computer next to me (correctly named Testbed-PC) does not have antivirus on it for that purpose. It is for testing installs/programs. I know antivirus causes issues sometimes, so it is one of the only unprotected PC's in the company.

 

Good thoughts though. ​That is why I am here. Put our heads together we might come up with something.

[afluffehbunneh]

Quick update here. If I ignore the error that I get from the disk1.cab during the installation, I get another error saying "FDI server error" from the "Installer Information" window. I dont know if this helps at all, but it seems like some other people reported this issue as well. I am doing some research into this.

[afluffehbunneh]

For those who appreciate eye-candy:

 

[afluffehbunneh]

Turns out after uninstalling the program on my main machine, I am now getting the disk1.cab issue from the flashdrive environment, but not from the Network installation...more interesting things...

 

Maybe a corruption issue on the flash drive, or just a coincidence? Testing the installation on the problematic machine.

-Disk1.cab error on the problematic machine, even though it just worked on my machine.........sooooo strange.

[afluffehbunneh]

Tried the installation on the workstation administrative account. It went through once. I uninstalled to make sure it wasn't just a fluke. After trying to reinstall the program I received the same error. It worked, and then it didn't.

[afluffehbunneh]

Upon further investigation I found this in the error logs:

 

Logerror.txt

[afluffehbunneh]

Continued to try to fix this when in the office today. I went ahead and deployed the package to all the computers. Turns out it works on all of them after trying to deploy it 3-4 times to failed computers. Before hand it replies with an MSI Error 1603, which directs via the log to the above error. Not sure what this problem is...but the work around is to constantly redeploy so far...interesting

[afluffehbunneh]

This issue still has not been solved. I have been working diligently nonetheless.

 

Anybody with networking experience that can shed some light on the situation? I have been trying to deploy several different fixes/patches/programs to computers on the network that result in this same issue where the disk1.cab (or whatever .cab file is storing the installation files) is unreachable/corrupted. 

 

Would really like to figure out where this problem originates to possibly fix it.