I've set up a Mercurial server on a Windows 2003 / IIS 6 machine and when I try to pull the repository I get the following sequence
requesting all changes
adding changesets
adding manifests
adding file changes
transaction abort!
rollback completed
abort: premature EOF reading chunk (got 91303 bytes, expected 1542634)
I've tried pretty much everything I can think of, but with no success. I followed the steps of Jeremy Skinners guide on doing it for IIS7, but on an IIS6 server.
I found a post where the author was experiencing the same issue, but was unable to find a solution.
So far it looks like the solution is to migrate to Apache or upgrade to Windows 2008/II7 .. but if someone knows how to solve this, please let me know
I'll answer this one myself.
The problem turned out to be that there is a CGI script timeout of 5 minutes in IIS 6 (and below, not sure about 7) and this was what kept being hit. To change the timeout value you have to have the IIS 6 Resource Kit installed.
Once installed, start the MetaBase Explorer utility and navigate to \LM\W3SVC and locate the CGITimeout entry and change the value from the default 300 (5 minutes) to a higher value (I ended up using 20 minutes).
After changing the value I restarted IIS to make sure it was used by the server. Once this has been done, everything worked like a charm!
Cross posted on my blog
I haven't tried it yet, but there's this: Running Mercurial on Windows
If you scroll down to the "Windows Server 2003/XP" section, I think that should cover you for IIS 6.
Have you checked out Joel's tutorial? Maybe you'll find the answer there.
Related
I hope this is the right place to ask. I was thinking serverfault might not be correct, since the computer in question is not a server. Feel free to migrate if StackOverflow is not right.
I usually install IIS on servers but have installed it on Workstations before. I actually had the same problem with another machine of the same model a few weeks ago but can't remember how I resolved it. I must have installed additional features or run some powershell-command that did not resolve the issue on this machine.
I installed IIS the correct way using the Windows Features, as described in the answers to this question. I've actually removed and reinstalled it since then, but it hasn't resolved my problem.
The WWW publishing service is running and I can open the IIS Manager, but it's completely empty, unlike here where the IIS Manager at least shows the local computer
When I type localhost into a browser I don't see the IIS Startpage, I get the error ERR_CONNECTION_REFUSED
You can see that all the required checkboxes are checked:
And the service seems to be running.
I've since tried installing IIS using
DISM:
Powershell:
And I checked the status using the iisreset command which was mentioned in the comments here (second linked question upstairs):
It restarts without any error and says everything is working fine.
Has anyone ever encountered this before or might know what I could try to get IIS actually working?
Edit:
I just noticed, while trying to uninstall IIS, that I can not uninstall it. I used Windows-Features and confirmed to reboot when prompted, but while rebooting Windows does a rollback and IIS is still available. So I can't even uninstall it.
Also just found this similar quesion on SuperUser. I'm still trying some suggestions there. So far to no avail.
Thanks for the comments.
I was on vacation, but a colleague was able to fix the problem.
Unfortunately, the solution was to reset Windows 11. He was then able to install IIS through Windows Features and it worked.
No idea why it didn't work in the first place, or why it got to this unrecoverable state. But now everything is fine.
I'm setting up an asp.net server for school and I am getting ERROR_USER_UNAUTHORIZED.
I have looked over the internet and everyone says that it has to do with not being administrator or not having access to the site. I am just getting confused. I added the user to the local administrator group. added him to iis manager permissions and to IIS manager users in like 3 different ways (same user different type of name, with server/name, name, iis manager user name).
Man I am just trying to publish to this server and I've been at it for like 5 hours (not that much but still I havent gotten any further at all).
To give some more detail:
I setup a publish profile in visual studio, correct host, username,password,site name and I think correct url (we have no dns setup yet so its just the ip of the server). INTERESTING PART HERE (I Think) when I click validate connection it works correctly (in edit) but when I publish it gives the error stated above. Also when I change https to http in the url it makes the error ERROR_USER_NOT_ADMIN, which the user is... .
To summarize, I have no clue what I am doing please help me god.
Take as long as you want to, I just want to get this done.
Check if you open VS with administrative right?
I forgot to mark this as solved and post the solution.
Apparently the solution was that I didn't mark the folder(inside the site in iis manager) as an application.
Solution is simply, open iis, select the server, select the site, right click the main folder with all your stuff, click mark as application.
I couldn't find this anywhere on the internet or on the help page it shows but it solved the problem. (litterally just started to turn insane a bit after trying stuff for 5 hours so stopped and went at it again next day and solved it in 5 minutes).
I've recently had a name change to my PC and rebooted. Before this change, I could run my MVC3 project from VS2010 using IIS 7. After the name change I getting:
Http Error 403 Forbidden Version Information: ASP.NET Development Server 10.0.0.0
I realise this could be a number of things so I'll try, in detail, to describe what's going on.
IIS
My IIS reverted back to v6 so I loaded 7 and set my DefaultAppPool to use .NET v4.0.
Security has all permissions for my account.
Request Filtering has 'Allow unlisted file name extensions checked (another answer on SO)
I'm using FireFox 24.0
VS2010 hasn't changed as far as I'm aware.
I'm not very familiar with IIS which, seems to me, is my problem so please bear this in mind if you decide to help. I'll gladly provide more information if needed.
thanks,
Paul
Do you actually have IIS7 installed or are you using IIS Express or Cassini?
I'm pretty sure that you'll be able to get things going again if you use the aspnet_regiis command.
Navigate to your .Net folder and run the following command aspnet_regiis -i
This isn't the answer but rather a different question. The problem wasn't IIS, the problem is with FireFox. I changed the default browser to Chrome and my app runs as it should.
Simple answer - I changed windows authentication password which wasn't updated in firefox. I changed the password to be in sync and it solved the issue.
I am having below mentioned issue when I am running Asp.Net MVC 2 project on windows Azure emulator (dev environment)
I have installed Windows Azure SDK for .NET - October 2012 version and I am using cache feature on my system.
With above error Below one is also comming.
How to get rid of this ?
Maybe I have an stupid solution, but that works with me.
When I begin to recieve the message "CacheInstaller.exe has stopped working", I do the following:
1) Stop the execution.
2) Go to the Role I'm using in the Azure project and open the corresponding Properties page.
3) Go to the "Caching" section and there I uncheck the "Enable Caching" checkbox. After that I checked again.
4) Save*, Run de application and never the warning appear again.
Is weird because nothing should change if you uncheck and check it again an option without save in the middle, but in this case when you do that the file changes (I can see it in the red icon that said something change there, :P)
I hope this helps. Cheers.
Do you have any error messages in the event log that may give more hint.
It could be an issue with missing dlls, do you have the windows server appFabric installed as well on this machine, which may be leading to a conflict with the dlls?
A procmon log might help you see what file paths its looking for.
"http://technet.microsoft.com/en-us/sysinternals/bb896645"
I banged my head against the wall on this one as well. I finally figured out the problem after digging deep into the crash-dump logs located within: C:\Users\{YOU}\AppData\Local\dftmp\Resources\{GUID}\directory\DiagnosticStore\AzureCaching\
AzureCaching does not allow UNC paths.
As my primary .net dev is from a vm, my documents/projects drive is mapped to my native drive located at: \\psf\Home\Documents\... Once I moved the project to the vm c:/ drive, CacheInstaller worked as intended.
Might as well post my experience as I was unable to locate anything on this specific problem.
I found today that if my system time was more than about 10 minutes wrong then CacheInstaller.exe bailed out on starting the emulator.
That includes the combination of system time and timezone being wrong, presumably as it results in an inability to calculate the correct UTC time at which Azure operates. Fixing the system clock resolved the issue in my case.
Just fired up a fresh Windows Server 2008 instance on Amazon EC2 to begin messing around with the ColdFusion 10 beta and ran into an interesting issue.
This WORKS and properly renders the default index.cfm in the root:
mydomain.com/
This however DOES NOT work:
mydomain.com/index.cfm
Any .cfm file referenced directly within the url doesn't load but if referenced as the default document in a given directory does work.
Like I said, this is a fresh install with nothing outside of the ColdFusion 10 public beta installed along side IIS 7. Ideas?
This is a connector issue from within IIS. The IIS CFM Handler Mappings should have been taken care of during the installation process but apparently that didn't happen in this case. It's possible IIS is missing a feature (like ISAPI support) that the connector needs in order to function.
You can try re-installing (and thus re-running the connection process) or you may be able to use wsconfig directly to re-install just the connector bit:
ColdFusion10\config\wsconfig
... whatever is easiest for you.
Jordan is correct, this is a connector issue with CF10/IIS.
This question is similar to:
Coldfusion 10 on Windows 2k8 - .com/ loads OK but .com/index.cfm gives a 404
I posted an answer to that question that may be useful to others who find this question.
I had the same problem but the "Web Server Configuration Tool" (i.e. wsconfig) did not work for me. My answer to this other question provides info on how to manually install the connector in IIS 7.x.