technomonkey

I have found nothing yet...

Thanks for the advice on microsoft.public.vstudio.general - I will check
there soon.

Do you think reinstalling Vista solve the problem?

Thanks

Andrew McLaren

"technomonkey" <technomonkey@discussions.microsoft.com> wrote ...
>I have found nothing yet...
> Thanks for the advice on microsoft.public.vstudio.general - I will check
> there soon.
> Do you think reinstalling Vista solve the problem?

Run msiexec with an additonal "x" parameter, lik ethis:

C:\TEMP\extract2>msiexec /i vcredist.msi /l*xv vcredist.log

The "x" will put additional debugging information into the log. This might
make it more obvious what is failing.

If you just need to get Visual Studio up and running then reinstalling Vista
could be a crude-but-effective, brute force approach to the problem. If you
go down that path, make sure that Visual Studio is the first application you
re-install; the problem might be caused by a conflict with some other app
you have installed (a SxS conflict or similar).

I'm not necessarily recommending you re-install Vista - as a solution, it
lacks finesse and elegance. But it might get you up and running in a short
time. If you do go down that route you should save your existing,
unsuccessful log file. Create a log file as you make the new installation of
Visual Studio, on the re-installed Vista. Then when you have finished, you
can compare the unsuccessful log file with the successful log file. This may
help you to understand what was failing, in your current installation
attempt. You'll be the local expert in your team, for interpreting MSI log
files! :-)

Good luck.

--
Andrew McLaren
amclar (at) optusnet dot com dot au

Andrew McLaren

"technomonkey" <technomonkey@discussions.microsoft.com> wrote ...
>I have found nothing yet...
> Thanks for the advice on microsoft.public.vstudio.general - I will check
> there soon.
> Do you think reinstalling Vista solve the problem?

Run msiexec with an additonal "x" parameter, lik ethis:

C:\TEMP\extract2>msiexec /i vcredist.msi /l*xv vcredist.log

The "x" will put additional debugging information into the log. This might
make it more obvious what is failing.

If you just need to get Visual Studio up and running then reinstalling Vista
could be a crude-but-effective, brute force approach to the problem. If you
go down that path, make sure that Visual Studio is the first application you
re-install; the problem might be caused by a conflict with some other app
you have installed (a SxS conflict or similar).

I'm not necessarily recommending you re-install Vista - as a solution, it
lacks finesse and elegance. But it might get you up and running in a short
time. If you do go down that route you should save your existing,
unsuccessful log file. Create a log file as you make the new installation of
Visual Studio, on the re-installed Vista. Then when you have finished, you
can compare the unsuccessful log file with the successful log file. This may
help you to understand what was failing, in your current installation
attempt. You'll be the local expert in your team, for interpreting MSI log
files! :-)

Good luck.

--
Andrew McLaren
amclar (at) optusnet dot com dot au

Andrew McLaren

"technomonkey" <technomonkey@discussions.microsoft.com> wrote ...
>I have found nothing yet...
> Thanks for the advice on microsoft.public.vstudio.general - I will check
> there soon.
> Do you think reinstalling Vista solve the problem?

Run msiexec with an additonal "x" parameter, lik ethis:

C:\TEMP\extract2>msiexec /i vcredist.msi /l*xv vcredist.log

The "x" will put additional debugging information into the log. This might
make it more obvious what is failing.

If you just need to get Visual Studio up and running then reinstalling Vista
could be a crude-but-effective, brute force approach to the problem. If you
go down that path, make sure that Visual Studio is the first application you
re-install; the problem might be caused by a conflict with some other app
you have installed (a SxS conflict or similar).

I'm not necessarily recommending you re-install Vista - as a solution, it
lacks finesse and elegance. But it might get you up and running in a short
time. If you do go down that route you should save your existing,
unsuccessful log file. Create a log file as you make the new installation of
Visual Studio, on the re-installed Vista. Then when you have finished, you
can compare the unsuccessful log file with the successful log file. This may
help you to understand what was failing, in your current installation
attempt. You'll be the local expert in your team, for interpreting MSI log
files! :-)

Good luck.

--
Andrew McLaren
amclar (at) optusnet dot com dot au

technomonkey

Hi all,

Just to let you know that I am going away for the next couple of days, so I
will not be able to reply during that time. I will however return soon and be
ready to continue.

Thanks

technomonkey

Hi all,

Just to let you know that I am going away for the next couple of days, so I
will not be able to reply during that time. I will however return soon and be
ready to continue.

Thanks

technomonkey

Hi all,

The new log seems to suggest that setup is examining my setup, there is info
about my system such as username and screen resolution. The final line is;

Property(C): ACTION = INSTALL

This is after all the system info. Could there be a problem with my system?
I find this unlikely because my system is only about a week old! Just in case
here is my spec;

AMD Athlon 64 4000+ Live!
2 GB RAM
320 GB HDD
ATI Radeon X1300

Is there anything that could be causing a problem?

I have just realised that I am trying to install C++ Redistributable rather
than the development tool, would the error codes mean the same or is this the
wrong thread?

Thanks
Michael

technomonkey

Hi all,

The new log seems to suggest that setup is examining my setup, there is info
about my system such as username and screen resolution. The final line is;

Property(C): ACTION = INSTALL

This is after all the system info. Could there be a problem with my system?
I find this unlikely because my system is only about a week old! Just in case
here is my spec;

AMD Athlon 64 4000+ Live!
2 GB RAM
320 GB HDD
ATI Radeon X1300

Is there anything that could be causing a problem?

I have just realised that I am trying to install C++ Redistributable rather
than the development tool, would the error codes mean the same or is this the
wrong thread?

Thanks
Michael

Andrew McLaren

"technomonkey" <technomonkey@discussions.microsoft.com> wrote ...
> I have just realised that I am trying to install C++ Redistributable
> rather
> than the development tool, would the error codes mean the same or is this
> the

I regret to say, I have compassion-fatigue. You don't know what product you
are trying to install. I have tried to help; but I suspect you just need to
sit down, think carefully, and work out what the hell you are doing, before
you continue wasting people's time. I regret sounding a bit harsh, but ...
geez!! At this rate, we could spend years on this issue and still get
nowhere.

> This is after all the system info. Could there be a problem with my
> system?
> I find this unlikely because my system is only about a week old! Just in
> case

Yes, there is a problem with your system - you cannot install the VC Redist.
I don't think the problem you're seeing is intrinsic to Vista.

Make sure that you are installing the latest redistributable package:
http://www.microsoft.com/downloads/d...displaylang=en
(or x64 version, if appropriate).

If that doesn't work, try asking over on microsoft.public.vstudio.general.
Good luck.
--
Andrew McLaren
amclar (at) optusnet dot com dot au

technomonkey

I apologise for any of your time that I have wasted, I will continue to try
and find a solution on my own.

Thank you very much for your help.