'The installer was interrupted before [project name] could be installed. You need to restart the installer to try again.'
I just moved to Win7, and I cannot get the .msi files to install from my Web Setup Projects that are built on that machine. The same projects build and work fine on my other Windows XP, IIS6, VS 2008 SP1 machine. I'm not sure if this is a IIS7 or Win7 issue, but I've done the following:
I have all the IIS/ASP.net compatibility settings checked.
I am an administrator, and I have UAC turned off.
I get the following error when I even try install the .msi file on the Win7 machine and on our existing development server (windows 2003 with IIS6).
I've restarted the windows installer service, and I've added logging for the installer but there is nothing that is showing me what the problem is. Any help would be MUCH appreciated.
I'm running Visual Studio 2005 and had the same problem as you described when moving to Windows 7.
After trying my Web Setup Project .msi file on another computer also running Windows 7 I found that it worked.
When I looked in the "Windows Features" dialog on the working computer I noticed that the IIS had IIS 6 compatibility features turned on. I enabled the same feature on my computer and after that I could install my setup project.
Open up "Control Panel > Programs > Turn Windows features on or off" in Windows 7 and in the "Windows Features" dialog go to "Internet Information Services > Web Management Tools > IIS 6 Management Compatibility" and check the feature "IIS Metabase and IIS 6 configuration compatibility".
Run the installer with full verbose logging:
msiexec /i /lv installLog.txt
Then search the installLog.txt file for "Return Value 3"
This will indicate the exact problem.
Additionally this may help:
http://blog.dragonsoft.us/2009/01/02/visual-studio-2008-and-iis-7/
I solved this by running 'regsvr32.exe actxprxy.dll'
It resolved the following:
Not able to create valid .msi web project in VS 2008.
Start Page in VS2008 was not displaying rss feed in the main window.
IE was not opening up shorted url links to a new tab (in twitter for example).
I suspect this was because of redirects, but I'm not sure. I'm guessing this was a bug in the install process, so I hope this helps others.
Related
I am trying to run an asp .net website in Visual Studio 2015 that is using windows authentication in IIS7. Although I installed IIS in my PC, while trying to add "windows authentication" from
Control Panel-> Turn Windows features on or off-> Internet Information
Services -> World Wide Web Services -> Security
it seems that this feature is missing from the list.
Have a look at the picture.
What other options do I have in order to run the project via windows authentication?
Windows 10 Home edition doesn't include Windows Authentication (and a bunch of other IIS security features). However, the package with these features is sitting right there in your OS and you can manually install it.
All you need to do is open an elevated command prompt and run:
dism /online /norestart /add-package:%SystemRoot%\servicing\Packages\Microsoft-Windows-IIS-WebServer-AddOn-2-Package~31bf3856ad364e35~amd64~~10.0.16299.15.mum
Filename above may be slightly different since it's based on system bitness and version
Then just make your way back to:
Turn Windows features on or off > Internet Information Services > World Wide Web Services > Security
All the "pro" options under Security will be available. Simply check "Windows Authentication" and reboot.
Windows 10 Home edition does not support windows authentication in IIS. Once you upgrade to Windows 10 Pro, you will see several additional features in IIS, including windows authentication.
Check if this feature is deployed:
At appwiz.cpl, select 'Turn Windows Features on or off', verify if
Internet Information Services -> World Wide Web Services -> Security -> Windows Authentication is selected.
Just rightclick on IIS and click open as 'Adminstrator'. Retry the same. It should work
To enable “Windows Authentication” either you need to upgrade the OS to Pro version or you can run this command to enable it.
C:\WINDOWS\system32>dism /online /norestart /add-package:%SystemRoot%\servicing\Packages\Microsoft-Windows-IIS-WebServer-AddOn-2-Package~31bf3856ad364e35~amd64~~10.0.17134.1.mum
The file name will be different based on windows updates. So please update if requires.
I have downloaded the IIS Powershell snapin IISPowershellSnapin.26IISPowershellSnapin.exe
Unfortunately installing on a windows 2012 Remote desktop doesn't succeed.
The error is:
Microsoft Webinstaller couldn't find the product you tried to install.
Either the link you clicked is incorrect or you may be overwriting
your feed with different feed.
I have downloaded it from the site:
http://www.iis.net/downloads/microsoft/powershell
The manual gives the following Prerequisites:
The IIS PowerShell Snap-in requires the following prerequisites:
•Windows Server 2008, Windows Server 2008 R2, Windows Vista Service
Pack 1, or Windows 7 •Microsoft PowerShell 1.0 or 2.0
So nothing is said about Windows Server 2012.
Is there another executable for Windows Server 2012 or is there another problem.
http://www.iis.net/learn/manage/powershell/installing-the-iis-powershell-snap-in
I have allready checked whether the IIS Management Console is installed and it is installed.
Maybe this executable needs internet connection to install?
On our RDP we have no internet connection so this could be the cause as well.
Simply don't. PSSnapIns are obsolete; everything runs on modules now. The IIS Snap-In has been superseded by the WebAdministration module, which provides a superset of functionality.
Install the module on a >2008R2 server with the following PS:
Add-WindowsFeature Web-Scripting-Tools
This will not cause a service interruption. If it needs a reboot, it will tell you so. You might need to restart your PowerShell console, although this is unnecessary in my experience. After installation, run the cmdlet:
Import-Module WebAdministration
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
I am trying to remote debug my application in VMware workstation 7 and Visual studio 2010 ultimate. I habe several images (win 7 ultimate,vista,etc).
I am following this tutorial: http://kristofmattei.be/2010/01/20/debugging-applications-in-virtual-machines-with-vmware-workstation-7-and-visual-studio-2008-sp1-2/
Whenever I try to start msvsmon.exe on the remote computer it will say :
"The visual studio remote debugger does not support this edition of windows"
tried it with win 7 ultimate, vista premium and xp home, same situation.
Could someone help me out here?
Thanks!
The error message "The visual studio remote debugger does not support this edition of windows" appears because the remote debugger tries to use Windows Authentication by default, and this is only supported in the "Pro" versions of Windows, and up.
However, the remote debugger does work with the "Home" versions of Windows, you just have to tell it not to use authentication via the command line.
(Why it doesn't let you do this after launching it without any arguments, why the error message is so misleading (and contradicts the official list of supported OS), and why there is so little info about this on the web, I don't know. :))
To launch it, run this:
msvsmon.exe /noauth /nosecuritywarn
Of course, this launches it in the lowest security mode, so you'd only want to do this on a secure network. (But that's usually the mode one ends up using msvcmon in anyway, as the other mode is an even bigger PITA to set up than it is normally. Very useful tool, but really could use some streamlining.)
No need to use VMWare features.
Inside the guest VM run the version of msvsmon that came with your copy of visual studio 2010 (A setup package for just the remote deubgging stuff can be found on the disc/image) (use x86 if debugging a 32-bit process or x64 if debugging 64-bit one ,Itanium if you need to laugh).
through the msvsmon GUI disable authentication and select allow any user to connect.
disable the firewall in the VM.
on the host machine you should be running visual studio 2010, under the debug dropdown select "attach to process..." and then on the window that pops up select remote from the dropdown that should say local or something initially, enter the IP address (should be private network IP i.e. 10.1.?.?) of the guest VM, alternatively use the server name displayed by the msvsmon GUI. You should get the process list for the guest and should only attach to any process that matches the version of msvsmon you ran (x86 or 64 ...or Itanium laugh).
NOTE: These are basic instructions to show you it definitely works but these instructions will only work for native code since managed requires a secure connection.
If you are debugging a .NET app using the VMWare VS Plugin and are getting a "file not found" type of error...make sure you have the .NET runtime installed! :)
Like a moron, I set up a fresh XP VM and forgot to install the .NET runtime and wasted a good day trying to get the VMWare VS Plug-In to work!
VSID is not supported by visual studio2010 http://communities.vmware.com/thread/282407
I have a tool that I want to install on my main development box (Windows Server 2008). The installer tells me that it requires Vista. Of course I'm not saying Server 2008 is Vista, but I figure something that installs on Vista should be able to install on Server 2008.
Is there some way (perhaps via a temporary registry change) to get a server 2008 system to appear as Vista for the purpose of installing software?
Thanks!
Win2008Workstation has an example guide of how to use Orca to patch an MSI file.
Have you tried the emulator for running the install, when right clicking and going in to the properties of the installer?
right click > properties > compatiblity > and change the compatibility mode to Windows XP or Windows Server 2003
A few ideas:
If it's an MSI installer, download orca and delete the custom action that does the check
Use a tool such as process monitor to watch what registry keys the installer reads and tweak them to match vista's.