I have set Mercurial 1.51 up on a Hyper-V server running Windows 2008R2 and am trying to use IIS7 to serve the repositories. I followed these instructions which I had previously used when evaluating mercurial with success. All was going well I could see the repositories from with a browser but when I tried to clone the repository from the server I receive the following error:
requesting all changes
abort: HTTP Error 502: Bad Gateway
I am not sure if this is an issue with IIS or Hyper-V or Mercurial? Any suggestion much appreciated
I noticed that tutorial did not instruct you to add the python IIS Handler Mapping. Take a look at this tutorial, specifically #3 under the IIS 7 section. That may help.
Vampire Basic: Running Mercurial on Windows (web.archive.org mirror).
I was getting the same error, in my case the workaround was to check the use uncompressed transfer option in the clone dialog.
Related
I am trying to publish a website from my computer to an IIS web server via web deploy.
I have 3 servers. All servers have installed the same things (Webdeploy etc.) and the services are started (Web Deployment Agent Service and Web Management Service).
On the first server I have no problems on connecting. But the other two servers give me some error when I "Validate Connection" in Visual Studio to the IIS. When I look at the logs on the IIS server, there are my accesses listet with html code 200 (ok).
An error ocurred when the request was processed on the remote computer. Filename: MACHINE/WEBROOT
Error: The configuration section 'system.webServer/management/delegation' cannot be read because it is missing schema
I really have no idea what could solve this problem and hope you are able to help me.
I had the exact same problem, it turned out I had installed Web Deploy 3.6 on top of 3.5. Remove Web Deploy 3.6 and reinstall 3.5 and see if it solves your issue.
You can also try #james-wilkins comment below: "In my case I installed Web Deploy BEFORE installing the management service..."
Uninstall and then re-install Web Deploy.
This fixed the problem for me -- the 'repair' option in the installer did not.
In my case, I installed Web Deploy BEFORE installing the management service. I tried to do a "change" on the install to include the management service (or you can add the feature from add/remove windows features), but that didn't help (got the error on this post). In the end, a simple uninstall and reinstall of 3.6 was what worked for me. Seems it needs the Web Management Service to be installed FIRST. Typical MS instructions don't even mention this at all.
I am trying desperately to get a nuget gallery hosted on Apache with mono. I have mono and apache configured and a new empty .net 4 web app with nuget.server created and copied to the linux server. I got as far as getting the site up and running so the Default.aspx is displayed when browsing to the site. However I can't get anything beyond that to work. If I try to view available packages via the link on the main page (I copied some nupkg files into the Packages directory), I get the following error:
Description: HTTP 404.The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Details: Requested URL: /nuget/Packages
On IIS, the routemagic.dll seems to be the key in making the /nuget path work. However that simply isn't happening in Mono. I have no idea if this is simply not a supported service on mono or if I'm doing something wrong.
All permissions are correct. I am calling mod-mono-server4 since the nuget.server was built with .NET 4.
Any help or direction would be most helpful.
If you need it i made a little nuget server with php. It works on apache with mod_rewrite or IIS: http://www.kendar.org/?p=/dotnet/phpnuget :)
It supports security, push, odata queries, gallery and Nuget Package Explorer (https://npe.codeplex.com/) with 5 (five) minutes setup on Apache.
Actually it works on text file db and i'm doing the verifications for the MySql implementation.
I have installed Web Deploy 3.5 on Windows Server 2008 R2 and tried to run remote publish web application through visual studio 2012. However, I got the error - Destination Not Reachable.
I read some post and checked below and still got no luck.
Firewall was off
Both Web Management Service and Web Deployment Agent Service were restarted and running
Tried to open https://[server]:8172/msDeploy.axd in a browser and it is reachable. (Use default 8172)
Tried to use http://[server]/MsDeployAgentService and it is working with Admin username/password.
Did I miss anything? Thanks.
Maybe same issue as in https://stackoverflow.com/questions/16708021/msdeploy-wmsvc-not-working ?
It appears you have to activate the web management service first and
then install web deploy and i'd done it the other way round. I
uninstalled WebDeploy and re-installed it, restarted the server and
its working
I also met the same problem. When installing WebDeploy, do not choose classic installation, but choose complete installation.
If you messed with SSL certificates this could be one of the causes as well:
https://serverfault.com/questions/613634/could-not-connect-to-remote-computer-web-deploy-error-destination-not-reachable#answer-812712
In Visual Studio 2012 RC when I try to validate a Web Deploy connection I get this error message:
ERROR_DESTINATION_NOT_REACHABLE
The required Web Management Service is started on the server and Web Deploy 3.0 RC is installed.
Then using Remote Desktop Connection I log on the server and go check IIS logs located at C:\inetpub\logs\LogFiles\W3SVC1. There I can see my attempts to validate the connection because they contain my IP address:
2012-07-13 20:58:49 185.201.117.17 HEAD /msdeploy.axd site=Default%20Web%20Site 8172 - 189.10.32.194 - 404 0 2 78
It's giving me a 404.
After trying to get this working for almost 6 hours now (reading a lot of material including this great Troubleshooting guide by IIS team titled Troubleshooting Web Deploy problems with Visual Studio and this related question Visual Studio 2010 Web deployment task failed) I decided to ask for help here and see if anyone has a clue about what can be the problem... Do you know what's causing this 404 error?
If you need any more info, just ask me and I'll provide it... :)
Edit 1
Yesterday I also tried the following msdeploy command on my local machine to list the the contents of a folder called test on the server [ and it worked as expected ]:
C:\Program Files\IIS\Microsoft Web Deploy V3>msdeploy -verb:dump -source:content
path=c:\test,computerName=xxxxxxxxxx.publiccloud.com.br,username=User,password=Password
Info: Using ID 'a246a13c-7777-4226-964c-fe9934c60b77' for connections to the rem
ote server.
MSDeploy.contentPath
c:\test
c:\test
c:\test\test.txt
Edit 2
After a lot of install/reinstall operations I finally got to a point where Windows Server 2008 is returning a 503 HTTP error when I try to publish the web site using VS 2012 RC or even msdeploy in the command line.
Looks like the best thing to do now is to do a clean install of Windows Server 2008 since I got a messed up VM server image to work with. Hope it'll do the trick.
Just for the record, this is the msdeploy command VS 2012 tries to execute. I did a copy/paste and tried it with msdeploy in the command line:
C:\Program Files (x86)\IIS\Microsoft Web Deploy V3\msdeploy.exe -source:manifest='E:\SISPEC\SISPEC\obj\Release\Package\SISPEC.SourceManifest.xml' -dest:auto,ComputerName="https://xxxxxxxxxx.publiccloud.com.br:8172/msdeploy.axd?site=Default%20Web%20Site",UserName='UserName',Password='Password',IncludeAcls='False',AuthType='Basic' -verb:sync -enableRule:DoNotDeleteRule -disableLink:AppPoolExtension -disableLink:ContentExtension -disableLink:CertificateExtension -setParamFile:"E:\SISPEC\SISPEC\obj\Release\Package\SISPEC.Publish.Parameters.xml" -retryAttempts=2
just to get the same 503 Server Unavailable message.
Edit 3
This question was cross-posted at the IIS Web Deployment Tool (MS Deploy) forum here.
Fyi - I too was getting the 404 errors. It turned out that I had to download the full package and install everything.
http://www.iis.net/downloads/microsoft/web-deploy#additionalDownloads
I had this same error (ERROR_DESTINATION_NOT_REACHABLE). I was able to fix the issue by opening port 8172.
I then ran into the error: ERR_COULD_NOT_CONNECT_TO_REMOVESVC which I was able to resolve by installing every component of Web Deploy 3.0. It was trying to hit /MSDEPLOYAGENTSERVICE which by default isn't installed by the Web Deploy 3.0 installer.
I had to manually add the Deployment Handler. In IIS Manager, with the server selected, choose "IIS|Handler Mappings|Add Managed Handler...".
Request path: msdeploy.axd
Type: Microsoft.Web.Deployment.DeploymentAgentHandler,..., Version=9...
Name: Web Deploy Whatever
In my case, the default certificate issued for WMSVC was not issued for the machine-name. My Solution was to:
Issue a certificate for the machine name from my domain CA. This could be self-signed if you're willing to trust the certificate.
Install that certificate under the Personal certificate store
stop the web management service
change the certificate to my properly issued certificate
restart the service.
Did you check your handlers? You can test this by creating an HTML page on the same folder and trying to access that HTML. If you can, then go check that your site has the necessary handlers. Also, make sure your DNS record are pointing to the correct IP address.
First I tried just Repair install of Web Deploy 3.0 and not worked. Removing and installing solved my issue.
In my case I had both Web Deploy 2.0 and 3.0 on server machine.
Removing both and installing just 3.0 solved my issue.
Ensure Web Management Service is started.
I deleted SSL certificate and the service stopped working.
If all previous indications fail, and if you are using an Azure virtual machine, where the endpoint for 8172 is open, I have solved it deleting the endpoint and opening it again. I believe the first time I have selected using Floating IP Enabled, and that did not work. Just create the endpoint again, select disable floating ip and done!
can I easily move my drupal installation from Apache to Microsoft server, or I do need to run the install.php script and reinstall all modules ?
I'm having troubles to connect it to the database, that's why I'm asking. (I get technical problems without specific error messages)
thanks
The technical differences you will encounter are the ones between Apache and IIS. For example, there is no mod_rewrite in IIS, you have to get ISAPIRewrite to play along. You also need the Windows Server to be running MySQL. You may also have .htaccess pathing issues.