Installshield error 1309.Error reading from file

I have a Basic MSI Project.

I have three discs I am going to span the content on for the release. I have three features I am using for this, each with their own individual content. I use the project assistant->Application Files tab to select each feature and add content to them. When I drop-down the "All Application Data: tab, I drop down the items therein, and it looks great...

I then use the release wizard to begin creating my three discs. So I use custom disc spanning, and create three CDs with the default value for the names ("DISC?" which is equivalent to the current disc it is.. ex: DISC1). I then put each feature under each disc. One feature per disc... total: three discs and three features... It output those folders labeled as "DISC1", "DISC2", and "DISC3". I then proceeded t开发者_如何转开发o burn each folder onto each disc as such: "DISC1" folder copied and burned to disc with the disc labeled as "DISK1".

It seemed like a dream come true.. everything was going so smoothly, until...

I launched the install on the first disc... and when it prompted to insert the next disc, I did so, then it gave the error: "Error 1309.Error reading from file"

It recognizes that it should continue to the next disc to continue the install, and then when I insert the next disc, it gives the error that it cannot locate the data from disc 2 because it is looking in the filepath for disc 1 (ie "E:\DISK1\data.txt")

Any thoughts? Thanks!

Windows Installer has a bug / feature limitation. When you burn your disc, your CD volume label has to match excactly what MSI is expecting the label to be. So if your Media table says DISK1, DISK2, DISK3 that's how your CD's have to be burned.

Ok, let's take another angle. Have you confirmed the burned CD's are good? Perform MD5 hashes of all the files? What happens if you create an INSTALL folder on your harddrive and consolidate all of the files into a single structure and run it there. Does it succeed?

Also, are you comperessing into CAB's or are you doing uncompressed? If uncompressed, have you tried compressed? Also are you doing uncompressed are you consuming any merge modules? Have you run Validation on the MSI to identify any issues?

Also checkout: Additional Causes for 1308 and 1309 Error Messages