I am using VS2010 on Windows 7 (64 bits). When trying to install "Nuget Package Manager" from VS's "Extension Manager" it fails. The download works, but then I am stuck at the installing progress bar. When looking in Windows' task manager yo can see that the installer keeps on starting up new instances of the "vsixinstaller.exe" process. It goes on and on until the computer ultimately crashes.
The same behaviour occurrs when starting the file "NuGet.Tools.vsix" directly.
I have searched the net for the solution but haven't been able to find anything useful.
I received the same behavior today so I decided to open Process Monitor to investigate.
Guess what...Process Monitor gives the same behavior. Then the light bulb went off... :)
Answer: I previously had administrator privileges on my laptop, but those were removed at the beginning of the new year. For some reason, when these programs use credentials that are not in the administrator group, they recursively call themselves instead of failing, timing out or reporting access denied, etc.
Please ensure that your attempting to update after launching VS as an Administrator.
I will be providing this feedback to the nuget support thread as well.
Fixed by installing Nuget with admin right under SP1.
I found a solution at NuGet Docs Known Issues. Installing the hotfix they recommend even though I have SP1. It includes KB2581019.
Related
Attempting to launch the SQL Server Management Studio set-up exe leads to an icon briefly appearing in the taskbar, before disappearing without any further screen showing up. The task manager does not show any running instance for the installer either.
I have tried various versions of the SSMS installer executables posted on Microsoft's official documentation for SSMS, including version 18.8, 18.7.1, and 17.9.1.
Also tried updating the .NET framework, as suggested here (Why the SSMS-setup-ENU for version 17.8.1 isn't running?), but the latest version is already showed as having been installed.
I did a soft and hard reboot both, without success.
Confused as to how to proceed and install the software now. Any help would be appreciated.
I have VS Community 2015 installed on a Windows 7 machine.
Few days ago new Xamarin version, the 4.1.1.3 one, has been released.
I have tried to install it (upgrading from 4.1.0.350) many times but every time I receive message about Build Tools requirement, even if the Build Tools 2013 and 2015 are correctly installed on the machine.
I have tried to reinstall Build Tools, repair VS and actual Xamarin installation without any success.
What may I check to be able to upgrade?
Thanks in advance for any help I will receive.
Am not sure if you were lucky enough to find a solution yet.
I faced a similar issue and was able to overcome it by :
1)First running the VS as Administrator.
2)Then Follow the normal update process Via Tools -> Options -> Xamarin -> Other
You will be asked to close VS during installation which is OK.
I guess that means the update process needs to access some files which require Admin rights? anyway it worked for me and I hope it works for you as well.
All the best!.
Br,
Khalid
I get the following error:
This operation returned because the timeout period expired.
Any solutions?
I've tried searching, but nothing useful.
Thanks in advance.
I'm running Windows 8.1.
Try: Cancel Hyper-V instances of the Emulator (Virtual Machines) already running and possibly in a corrupt state.
Close Visual Studio.
Open up Hyper-V Manager; stop and remove any instances of VMs that are present.
Try: Remove/Disable third party drivers or software that may be interfering with virtual networking
For Details check the link
http://social.msdn.microsoft.com/Forums/wpapps/en-us/b06cc9f2-aa5e-4cb3-9df1-0c273e1dfd68/wp8-emulator-xde-troubleshooting-tips
Try downloading vs_ultimate_download.exe from here. Run it and it'll download all the files (this can take a while).
Then run vs_ultimate.exe.
We have an installer package authored with InstallShield 2009, targeting Windows Installer 3.1.
Recently, we started to notice that sometime, when installing on some Windows 2003 R2 x86 based hosts, the installation fails, and the installer log report a 1603 error code (which by the way, doesn't really help much, as it means ERROR_INSTALL_FAILURE, that is a very generic "A fatal error occurred during installation.").
As the installation is still working on some other hosts on that very same platform, after further investigation we found out it was happening on hosts where Sql Server 2008 R2 was already installed, which leaded us to find out the issue is really with Windows Installer 4.5.
Whenever Windows Installer 4.5 was installed by an installer package, our installer package is failing with 1603. So far, we found as a work around: if we manually uninstall Windows Installer 4.5 (running something like "C:\WINDOWS\$NtUninstallKB942288-v4$\spuninst\spuninst.exe"), we can then run our installer package successfully, but this has various drawbacks:
the user who uninstall Windows Installer 4.5 is prompted with a dialog listing all the various software products installed using that, and effectively the link between those products and Windows Installer 4.5 is lost after uninstalling that, even if we reinstall it after successfully installing our application;
as Microsoft released various version of Windows Installer 4.5, the location of the utility to uninstall that is not strictly the one given above;
It is awkward to ask customers to perform such a work around.
I suppose upgrading the installer package to target Windows Installer 5 may solve the issue, but if possibile I would like to avoid it, and continuing to use InstallShield 2009 to author this specific package.
I have scoured the Microsoft and Flexera Knowledge Bases (and I am continuing my investigation), with no avail so far.
Does anyone knows if Microsoft or Flexera, or any other third party, have published an hotfix, or some further info, about this issue?
Some info about the 1603 error code failure
We got verbose logs for this issue, from at least 3 different servers, and we have investigated that in depth, to not avail so far. Most actions return 1, some 0 (specifically IsolateComponents, MigrateFeatureStates, IsolateComponents, SetODBCFolders, MigrateFeatureStates, UnpublishComponents, UnregisterComPlus, UnregisterTypeLibraries, UnregisterMIMEInfo, RemoveShortcuts, RemoveFiles, CreateShortcuts, RegisterMIMEInfo, InstallODBC, RegisterTypeLibraries, RegisterComPlus and PublishComponents, but nothing has yet came out investigating those), the installer package seems actually to be almost able to install (perform all the sequence down to "INSTALL. Return value 1.", it even prints "Product: [Our Product] -- Installation operation completed successfully."), only then it starts to rollback everything, and as there are various errors on the rollback, I think some of those will cause the 1603 (probably some 1607 returned by MsiProvideAssembly on ISChainPackagesCleanup), but the point is that it shouldn't rollback, and with Windows Installer 3.1 (or 5.x for that matter) it doesn't, it does rollback only when there is Windows Installer 4.5 installed on a Windows 2003 x86 environment.
Most likely your package has an action which fails, either custom or standard. Try creating a verbose log of the installation which fails (it's very important to be verbose). After the failure, open the log with a text editor and search for the error code (1603) to see what triggers it.
As a side note, don't try to blame Windows Installer. There's nothing wrong with version 4.5 and there are no hotfixes or something like that. The problem is in your package. It does something which is either incorrect or unsupported.
EDIT:
From your post update it looks like a failed chained installation. No errors are shown in the log because the error occurs in a different installer process.
If you are not using chained packages, try looking for errors in the Event Viewer.
If you are using chained packages, you can try enabling the Windows Installer logging policy and check for logs generated by them. Most likely one of the packages is encountering a problem.
I have a VB6 app that loads initially (for a small prompt to enter a license key, only on the first time). It works fine on my machine (windows 7).
I had complaints of it crashing on someone else's machine (both xp and 7), so I made a Windows XP virtual machine. I installed it on the virtual machine, it crashed. I wanted to see where it crashed so I installed Visual Studio on the virtual machine so that I would get a debug prompt. When I ran the program again, it worked.
I am more familiar with C++ and had these kinds of problems, so I figured it was some sort of runtime issue.
I found this VB6 SP6 Redistributable Runtime:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=24417
I installed that, and it still wouldn't run.
Any ideas where to go from here?
Edit:
I have tried depends.exe, it only shows MSJava, which I've heard I can ignore. Does depends.exe also show things like .ocx (Active X controllers?) that are required?
Also, from the cmd prompt, %errorlevel% doesn't seem to get populated. Is that a VB6 things, or does that indicate that this is truely a crash and not a user exit?
Open the Visual Basic project and check both "References" and "Components" under the "Project" menu.
Since it is crashing with the VB runtime installed it is likely a component that you have referenced in the project that either does not exist (or is not registered) on the client under test.
This should be a simple fix.
I had the same problem on my windows 7 computer.
I have uninstalled everything, changed my windows theme to Windows Classic.
I changed following properties of VB setup file.
Right click on setup.exe and go to properties and in compatibility tab change the compatibility mode to windows XP SP2. And in settings uncheck the following check boxes.
Disable Visual themes
Disable Desktop composition
Disable display scaling on high DPI settings.
Run this program as an administrator
And have completed installation.
Followed by installing VB 6 service pack 6 from here.
http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=24417
Hope it helps.
It may require something else other than just the runtime, have you tried viewing it with dependency walker http://www.dependencywalker.com/ on the machine that it crashes on?
It should quickly point out any missing references.
Maybe try again, create a new VM, but install the remote debugger instead of the full VS.
You should create an installer for your application. There may be more dependencies than just the VB6 runtime. A good installation tool will detect at least some of necessary dependencies for you. Have a look at this question or this question