Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Setup / January 2006

Tip: Looking for answers? Try searching our database.

VS2005 Team Suite Setup Error

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
mixfix - 04 Nov 2005 09:37 GMT
I downloaded the ISO image from MSDN Subscribers.
I computed the hash and it's correct, so the ISO image is good.
I expanded it with Winrar on HDD (c:\VS2005 so it's a short path) and began
installing it.
The PC is a Win2K3 on which no beta has ever been installed.
On the same machine there are working VS6 and VS2003 installations, platform
sdk, ddk and variouos developer tools.

I tried also the full install but setup always fails with this error:
Error 1335.The cabinet file '_14310_VC80_PDB_WINSXS_CRT_x86.msm' 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.

Followed by:
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2350.

That file is not present in the ISO image at all (but the image is good).
I tried to expand the ISO image with another tool but the total size (and
numbers) of the expanded files are the same.

Since that msm file contains PDBs, I suppose there is an install condition
in the MSI file that triggers the installation of the msm. I looked into it
with Orca with no luck in understanding that condition.

Any ideas?

Signature

mf

Rhett Gong [MSFT] - 07 Nov 2005 02:42 GMT
Hello mixfix <mixfix@newsgroups.nospam>,
Error 1335 indicates component corruption or a copying error in the installation. I have not tried winrar to extract iso before, but
personally, I prefer using Daemon Tools (downloaded from following page) to mount the iso image, and use the virtual disc to
install vs2005.
http://www.daemon-tools.cc/dtcc/download.php
So far, it works fine for me, and I would like to recommend you to give Daemon Tools a try.

Please let me know if Daemon tools helps you solve this problem. If there is any more I can assist, please feel free to let me
know.

[3RD Disclaimer]
This response contains a reference to a third-party World Wide Web site. Microsoft is providing this information as a
convenience to you. Microsoft does not control these sites and has not tested any software or information found on these
sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or
information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions
you to make sure that you completely understand the risk before retrieving any software from the Internet.

Thanks,
Rhett Gong [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp&SD=msdn

This posting is provided "AS IS" with no warranties and confers no rights.
mixfix - 07 Nov 2005 11:14 GMT
> Error 1335 indicates component corruption or a copying error in the
> installation. I have not tried winrar to extract iso before, but
[quoted text clipped - 7 lines]
> Please let me know if Daemon tools helps you solve this problem. If
> there is any more I can assist, please feel free to let me know.

Hi Rhett,
thanks, it worked.

But I have a question for you. After mounting the volume, I looked for the
missing msm, and it's still missing!
Now, is it possible to know what's triggering the installation (i.e. the
setup confition) of that msm file?
As I said before I found that msm filename in the msi file (using Orca) so
it should not be a corruption problem.

I just want to understand. Thanks again.

Signature

mf

Rhett Gong [MSFT] - 08 Nov 2005 06:17 GMT
Thank for your feedback, I am glad to know it works for you.

msm is the MSI merging module, it seems that winrar also extracts it from msi package, and later installer can't find the module in the builtin "path". I don't have further
knowledge on MSI, so I am not sure what cause the problem exactly.

Best regards,
Rhett Gong [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp&SD=msdn

This posting is provided "AS IS" with no warranties and confers no rights.
bradb - 21 Jan 2006 05:57 GMT
> Error 1335.  The cabinet file _14310_VC80_PDB_WINSXS_CRT_x86.msm ... is
corrupt.

I had the identical problem as mixfix when installing Visual Studio 2005,
Standard Edition, Part No.x31 45579.   I am installing from a newly purchased
distribution CD.  I get the same error if I copy everything to a hard drive.  
I don't have an ISO image.

I do not see the file on the CD.  Any suggestions on how to get a copy, and
where it belongs?

                                                              --Brad

> I downloaded the ISO image from MSDN Subscribers.
> I computed the hash and it's correct, so the ISO image is good.
[quoted text clipped - 23 lines]
>
> Any ideas?

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.