Logo




Subscribe:
RSS 2.0 | Atom 1.0
Categories:

Sign In


[Giagnocavo]Michael::Write()

 Saturday, February 26, 2005
Visual Studio 2005 Install Errors (1304)

Well, I'm upgrading from Beta 1 to the December CTP, since my friend (who works on VS) insists that it's 150% better than the Beta. We've run into some issues, and I hope that December CTP will solve them (since no Beta2 was released today, as far as I know :)).

I was getting an error: 1304 Access denied on SdmCompile.dll. It tells me to check the path, but doesn't provide a path. Searching the whole system didn't find it. So, I went into the DVD and tried to install the .NET 2.0 Framework by itself - aha! It said “A previous product is installed....”. Even though I had already uninstalled everything.

All help pointed to a tool called MSIINV.EXE. Well, that's not public, and I didn't feel like calling PSS (why it's such a dangerous tool is beyond me, since MSIZAP is available). Reading some blog posts, I see that the suggestion is to find the .NET Framework, J# redist, etc. etc. for .NET 2 using msiinv.exe, and then msiexec /x or msizap TWA them.

Well, as far as I can tell, it just looks at HKEY_CLASSES_ROOT\Installer\Products. Maybe I'm wrong. But that worked for me. Regedit, goto HKCR\Installer\Products, and then search for anything related to the 2.0 Framework and friend. Find the product code, then run MSIZAP TWA {XXXXXXXXX-XXXX-XXXX-XXXX-...}. The format is important! If you just copy from the registry, and don't do 8-4-4-4-rest, it won't work.

After I've cleaned everything, I think installing the .NET Framework 2.0 and the J# redist (arrrg) separately from the VS install helps.

Just my few bits on getting VS working. A lot of others have posted too, so doing this plus what everyone else suggests might work :).

Misc. Technology
Saturday, February 26, 2005 2:46:16 AM UTC  #    Comments [2]  |  Trackback Tracked by:
"http://valwgki.biz/john-hagee-ministries.html" (http://valwgki.biz/john-hagee-m... [Pingback]


Saturday, February 26, 2005 5:14:54 AM UTC
Michael - I could bitch for a week about the hell I've went through every time I try to install new bits of VS.NET. You have to uninstall all the old stuff - but since it's such a risky proposition you don't want to kill your only copy. So I've resorted to doing everything on Virtual Machine - which is cool except that the RAM consumtpion is through the f***ing roof .... which makes me want to ask - WHY DON'T THEY HAVE VM Images available for Betas? For the MVP academy - they have a VM image for instance w/ Biztalk complete with BTS2004, Windows 2003 Server, VS.NET, SQL Server - everything you need. Just attach and go. The same would be REALLY nice for the beta stuff as long as it's so brutal to install.
Saturday, February 26, 2005 5:27:31 AM UTC
Well, see, I work with VS2005 in production each day, and well, the December CTP is much nicer, with my few minutes of experience. I see some things are unfinished (like icons disappearing and stuff), but it's a much better product. Who wants to work in a VM? ugg :\

My only guess as to why they don't do VM images for betas is because that'd limit the amount of feedback they'd get. They'd only get reports for a specific system, that's always configured the same way. At least this way, when we go thru hell, that gets reported back, and they can fix it.

Betas are made to get feedback, not to work perfectly ;).
Name
E-mail
Home page

Comment (HTML not allowed)  

Enter the code shown (prevents robots):

Live Comment Preview