Home Dashboard Directory Help
Search

Visual Studio Update 3 Install took the PATH variable over 2048 characters by Jamie748


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 794164
Opened: 7/16/2013 2:00:21 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

Given that this value causes everything to break it should properly have a warning in most of the microsoft products when this occurs as it's a pain in the bum to find out the cause.

To be fair Microsoft SQL Server is the worst culprit on upgrades!
Details
Sign in to post a comment.
Posted by Microsoft on 7/24/2013 at 11:52 PM
Hi, given that we have not heard back from you in these days. We will go ahead and close this Connect Issue. If you get a chance to review and provide the information requested earlier, you can go ahead and reactivate this iss
Posted by Microsoft on 7/21/2013 at 10:11 PM
I am currently standing by for an update from you and would like to know how things are going on your end. If you could get back to me at your earliest convenience with information I request, we will be able to make headway towards a resolution. I look forward to hearing from you.
Posted by Microsoft on 7/16/2013 at 11:16 PM
Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

It may help if you provide us with:
a setup log file

You can get the log files with the following steps:
1) Download collect.exe from the link below. http://go.microsoft.com/?LinkId=8967043
2) You may choose to save the tool for later use, or to run directly.
3) The utility creates a compressed cabinet of all the VS and .NET logs to %TEMP%\vslogs.cab.

You can get more details about how to get the log files here:
http://blogs.msdn.com/heaths/archive/2008/05/09/visual-studio-and-net-log-collection-utility.aspx

Thanks again for your efforts and we look forward to hearing from you.
Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 7/16/2013 at 2:52 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.