Iis 5.1 Unexpected Error 0x8ffe2740 Occurred
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies unexpected error 0x8ffe2740 ftp of this site About Us Learn more about Stack Overflow the company unexpected error occurred Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users unexpected error -50 mac Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a
Dep0001 Unexpected Error
minute: Sign up Unexpected error 0x8ffe2740 occurred in IIS up vote 1 down vote favorite I have installed IIS in my system (WINDOWS-XP). While i am seeing IIS window, the Default web site is in stop mode. when i am ready to start IIS. It shows "Unexpected error 0x8ffe2740 occurred" Finally, I discovered that its caused by Skype. It listens to port tcpview 80 for incoming call. Now, most of the time IIS starts before Skype starts. So IIS works but if you restart IIS or try to start IIS after Skype is started then you will get this error message. For this, I changed my Skype settings Skype File-> Options -> Connection Uncheck Use Port 80 as an alternative for incoming connections. But even though i am unable to start my IIS. Please help me some one.. Thanks. asp.net iis share|improve this question asked Sep 22 '12 at 15:19 user1622824 356 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote I had a similar problem and I solve it using a firewall not allowing skype to do anything else more than open the ports to talk or chat. Restart IIS after this or restart computer. Additionally you can check for other programs like teamViewer, that also try to use port 80. May be a little bit hard to check ports on windows xp, xampp has a program to check ports that is very handy for this kind of things.
code for quite awhile and haven't had the need to open any ASP.NET projects, but this morning had to trouble shoot one. Visual Studio complained it couldn't open the URL. I went to the IIS snap-in and noted that the default web site was stopped. When I'd try to start it, I'd instantly get "Unexpected Error 0x8ffe2740 Occurred". OK. Well. Googling around for this, it's universally said that this error is IIS's way of saying, "some other process is using port 80 and I http://stackoverflow.com/questions/12545032/unexpected-error-0x8ffe2740-occurred-in-iis can't get at it". (Aside: then why in the name of all that's holy doesn't it simply SAY that? Nevermind). The solution is to find the offending process or app and either get rid of it, or get it to use another port. Skype is an often-mentioned culprit; it's default configuration uses port 80 if available. But I don't use Skype, and have http://bobondevelopment.com/2007/10/17/unexpected-error-0x8ffe2740-occurred-in-iis-51/ never had it installed. Microsoft's KB article on this issue recommends installing something like TCPView to figure out what's using what ports, so I installed TCPView but it revealed nothing using port 80. Sometimes a process like SvcHost will host other processes within itself, which TCPView can't see. So it just became a game: shut down app after app, try to restart IIS after each shutdown, no joy. Then I started shutting things down in my system tray. Finally, I found the culprit: JungleDisk, an open source program that maps a Windows drive letter to an Amazon S3 storage bucket. I use it for online backups. When I get a breather I'll submit this to JungleDisk, but thought this might help someone else in the meantime. { 2 comments… read them below or add one } darryl March 9, 2008 at 4:02 pm Thanks for the post! I had the same problem and went through the same routine, not finding anything using port 80. I tried to think what I had installed recently, and on a whim, closed Jungle Disk. It worked, and then I re-Googl
Trouble Shooting (10) How To Guides (53) IIS-Aid News (100) Interviews (2) Site Updates (5) My Word (41) Performance Testing (8) Reviews (2) Email (5) FastCGI (4) IIS (54) Monitoring (1) MySQL (7) PHP (40) Security (2) URL Rewrite (9) Windows http://www.iis-aid.com/articles/trouble_shooting/unexpected_error_0x8ffe2740_occurred (11) Unexpected Error 0x8ffe2740 Occurred Submitted by Dominic Ryan on Wed, 2007-10-17 23:01. Categories: Trouble Shooting IIS If you are using IIS 5.1 on XP and are being presented with an "Unexpected Error 0x8ffe2740 Occurred" error message when trying to start your website from the IIS Admin panel, then it is likely that you have a port conflict on your system. That's the easy part, now what do you do to track this conflict down unexpected error and fix it? Well, that actually isn't that hard either. By default IIS will try and bind itself to TCP port 80, so the first thing to do is track down which process is binding itself to this port. This could be anything from another webserver (such as Apache), or in my case Skype. To do this, open a command prompt window and type in the following; netstat -anop TCP|find ":80 " This will give unexpected error 0x8ffe2740 you some details of what process is using TCP port 80, and unless you have a multihomed system you should only get one result here. The only information that you really need to be concerned about is the number that is display on the far right hand side. This is the PID (Process Identifier) which is a unique number given to a process by the system when it is initiated. The next step is to match this PID with an actual process that you can identify. There are several ways you can do this, but probably the easiest way is to go back to your command prompt window and type this in (where the number 1234 is the PID number from the previous step); tasklist /SVC /FI "PID eq 1234" What this will do is associate the PID number you enter with a process name which will be displayed on the far left, and on the far right will be the name(s) of any related services.This should give you a pretty clear picture of what software is binding itself to TCP port 80, and from there it is a matter of either reconfiguring that software to use a different port number or disabling it while IIS is in use. Of course on the flip side you could always reconfigure IIS to use a differen