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 / April 2005

Tip: Looking for answers? Try searching our database.

Visual Studio 2005 Beta 2 Install Error

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Brendan Green - 18 Apr 2005 10:25 GMT
Hi all,

I've downloaded the Visual Studio Team Suite Beta 2 from MSDN Subscriber
downloads, and when installing, I'm getting the following error message
(it's most of the way through the installation of Visual Studio 2005):

Error 1310.Error writing to file:
Microsoft.VisualStudio.QualityTools.Resource.dll. Verify that you have
access to that directory.

Now, I definitely have access to everything on the machine (I've tried both
logged on through a domain account that has admin rights to the local
machine, and as the local machine administrator account), and I've also
tried this: http://support.microsoft.com/?scid=kb;en-us;330733.

Unfortunately, the only options presented when this error occurs is to Retry
or Cancel.

Does anyone have any other ideas?  I am really keen on getting this
installed and running.

Thanks,
Brendan Green.
Tim Macaulay[MSFT] - 19 Apr 2005 21:57 GMT
Brendan,

We create some log files, and place them in the temporary directory.  Can
you navigate there and send me the text files that are in there?

Start > Run and type %temp% and then click Ok.
Locate Text file, Compress and Send.

Another idea, would be to generate a filemon and/or regmon log and look for
ACCESS DENIED.

How to use Filemon and Regmon

1.    Please navigate to and download the tools listed:
    a.    FILEMON: http://www.sysinternals.com/ntw2k/source/filemon.shtml
    b.    REGMON: http://www.sysinternals.com/ntw2k/source/regmon.shtml
2.    Unzip the tools to there respective directories.
    a.    Close all applications down that you possibly can (so the log does
clutter to much).
    b.    Launch the Filemon executable.
    c.    Note the button that looks like a magnifying glass.  (This is the
Capture On/Off button)
    d.    Launch the troubled installation
    e.    When the problem occurs please go to the Filemon tool.
    f.    Hit the Capture button to stop the logging process. (Now we have
captured the problem happening.)
    g.    From the File menu there is a save as option.  (save the log as a txt
file)
    h.    Reboot the computer and repeat the above steps with Regmon. (run them
separately so we don't record the two tools processes.)

Cheers,
Tim Macaulay
Microsoft Corp.
This posting is provided "AS IS" with no warranties, and confers no rights
Brendan Green - 20 Apr 2005 01:21 GMT
Hey Tim,

Thanks for the reply!

I actually got the thing working already, but the resources you mention
below will definitely come in handy at some point.

Cheers,
Brendan.

> Brendan,
>
[quoted text clipped - 32 lines]
> Microsoft Corp.
> This posting is provided "AS IS" with no warranties, and confers no rights
mikechidsey@gmail.com - 20 Apr 2005 21:52 GMT
How did you fix it?  I'm having the same problem.  It's a clean machine
(Virtual PC, windows XP w/SP2).

-Mike

> Hey Tim,
>
[quoted text clipped - 42 lines]
> > Microsoft Corp.
> > This posting is provided "AS IS" with no warranties, and confers no rights
Simon Chalfont - 20 Apr 2005 22:30 GMT
Hi... Same problem here with Virtual PC & clean Windows 2000 Pro. Any
solutions?
chid - 21 Apr 2005 19:41 GMT
I fixed it by copying the DVD contents to the hard drive and installing
from there.  I also stopped most of the services that aren't needed.

-Mike
Brendan Green - 22 Apr 2005 00:00 GMT
Yes - this is what I also had to do.

To re-iterate, I extracted the contents of the ISO to the hard disk, and
then ran the installation from there - worked without a hitch.

I didn't bother about stopping any services, but that is not to say that you
should/should not do that as well.

Cheers,
Brendan.

>I fixed it by copying the DVD contents to the hard drive and installing
> from there.  I also stopped most of the services that aren't needed.
>
> -Mike
mattw - 22 Apr 2005 00:53 GMT
I found I was getting an error on that file, so I tried to manually
copy it from the "virtualized" iso (via the Microsoft CDRom tool) on to
the desktop and I got a file I/O error.

I don't know whether this is an error in the CDRom tool or the iso
image, but I was able to pull it all off of the image and put it into a
directory on hard drive, which I then shared with the virtual PC and
then installed just from that and it worked fine.

annoying little issue there.

-mattt
mattw - 22 Apr 2005 01:20 GMT
I found I was getting an error on that file, so I tried to manually
copy it from the "virtualized" iso (via the Microsoft CDRom tool) on to
the desktop and I got a file I/O error.

I don't know whether this is an error in the CDRom tool or the iso
image, but I was able to pull it all off of the image and put it into a
directory on hard drive, which I then shared with the virtual PC and
then installed just from that and it worked fine.

annoying little issue there.

-mattt
mattw - 21 Apr 2005 16:14 GMT
What did you do to get around this error?  Thanks?

> Hi all,
>
[quoted text clipped - 19 lines]
> Thanks,
> Brendan Green.

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.