I've created an ASP.NET application and want to deploy it on an XP Pro. machine so it will be available from other computers in the same local network.
What is the right configuration to achieve that?
I've tried to create the application on IIS 7 in Win 7 machine (at home, before going to the customer), but wasn't able to load it from other machine on the network.
Same problem when deploying the site on XP Pro. machine in a virtual machine and trying lo load it from the host machine.
I've canceled an ASP.NET problem by putting a simple html file in the application directory and trying to reach it.
Can you direct me to some check list about deploying a website?
Thank you in advance.
Follow this guide: http://www.wikihow.com/Configure-IIS-for-Windows-XP-Pro
Although I've searched before asking, I've searched again now.
Found this: Can't connect to Default Web Site in IIS 6.0
Disable windows firewall and everything is working....
I fill stupid...
Should this post be moved to serverfault.com? It seems to be a configuration/deployment issue not a programming problem.
Related
I have a question regarding IIS (version 7.5) and ASP.NET (.NET Framework 4) . I am trying to debug ASP.NET web application which is stored on IIS. Now, I have done this in past and everytime it worked perfectly.
But now when I try to do same, **Visual Studio 2010** always gives me error, **"unable to start debugging on the web server. the iis worker process for the launched URL is not currently running" ...** even the application I had created in past (& stored in IIS) can't debug using Visual Studio. But all applications (new & old) can be accessed if I type their path in Browser, and they work fine too.
I did search on internet about my problem and I found many posts, but almost every post talks about activating **Windows Authentication** in IIS for the application in question. But, I am using Windows 7 home premium and the IIS shipped with this version doesn't support option for Windows Authentication. Also, if this is the only reason then why my old applications were working just fine till now without this Authentication method?? I found MSDN help about this error but it is not much helpful to me. I also checked APPLICATION POOL selection in IIS and my Application (both are using V.4.XX.XXX)... I have also checked **BINDING** , which is *:80 to Default Website, that means all requests to port 80 will be directed to default website (where my all applications reside)
As a side note, I have SharePoint Server 2010 installed. Which has its own website (which I have disabled while debugging) ...
I think there is something is changed in my IIS configuration, but I cant figure out what it is. And I am sure that it has something to do with SharePoint installation (may be because of more than one website on IIS for same port ??). Because I am using IIS for first time after installing SharePoint and I am having this error.
I will really appreciate if any one has answer ...
Thanks,
Jack
UPDATE: As I suspected ... having more than one site in IIS was root cause of trouble, Once I uninstalled Sharepoint Server 2010 and its web sites from IIS, my Visual Studio 2010 debugger was able to "Auto-Attach" w3wp.exe process while debugging any application ... ( I really don't see any reason that even after disabling all other websites why still it was giving me error at first place ?? )
I know its not a solution, because I have to remove Sharepoint Server ... but at present its more important for me to work on that application then Sharepoint Server.
But I am still open for any suggestions which might help me to run both together ....
Thanks,
Jack
Check the Bug fix for this issue in the Microsoft's Connect site.
.
Is it with .NET 3.5 in Visual Studio 2010 , if yes , then check http://www.ginktage.com/2010/08/fix-for-visual-studio-2010-hangs-when-debugging-asp-net-3-5-web-application/ for information
I have accidently deleted the default-website on an "experimental" machine.
It is a standard-installation of "Windows Web Server 2008" with II7 running.
I have already tried to create a custom website on my own, but this always fails when I try to access the website in the browser (remote and locally). There is an endless number of permission- and setting - errors.
Could you please show me a link to a tutorial on what to do in my case?
Or possibly any suggestions what common pitfalls are in such situations?
Thank you!
Daniel Lang
Make sure your site points to %systemdrive%\inetpub\wwwroot, and then it has little difference from the default one.
Learning about how to back up IIS settings on IIS is a must for beginners,
http://mvolo.com/blogs/serverside/archive/2007/03/18/Most-Important-AppCmd-Commands_3A00_-Backing-up-and-restoring-IIS7-configuration.aspx
Save your custom code (virtual directories) and reinstall IIS? Probably cleanest.
I have an ASP.NET app that works fine on my windows XP dev machine but doesn't work when deployed to a Windows 2008 with IIS7. The app uses SmtpDeliveryMethod.PickupDirectoryFromIis and gives an error when I try to send an email from the app on IIS7 (an SmtpException with the message "cannot get iis pickup directory"). I use the same settings on both the dev machine and the server.
Any help would be really appreciated ...
It turned out to be a permissions problem but not with the pickup directory, actually with the metabase (SMTP settings are still saved in the metabase in IIS7)
I came across this forum thread, Cannot get IIS pickup directory. NEED HELP, on IIS.net forums website then followed what was mentioned in the posts, downloaded and installed the metabase explorer tool (you have to download IIS6 resource kit to get it) then gave read permissions to my custom user (as indicated in one of the posts) on the LS, SMTPSvc and SMTPSvc/1 keys and it worked. For some unknown reason if you only give permissions to the smptSvc key it doesn't work.
I think the problem could be with trust levels.
Because in medium trust you can only write to your application's directory (or any directory below that). And if the PickUp folder which you specified is not in your application's directory AND the application is running under medium trust (not full trust), then you can't write to the PickUp folder.
You may send directly to the SMTP server without using a pickup directory.
You need to specify the Pickup directory first. Here's a guide on how to do it.
Also it's not a good idea to compare your IIS 5.1 on an XP box against the one on your Windows Server 2008 (IIS 7), since besides the obvious version difference a lot of features have changed a lot. Specially the smtp server, for instance there's no such feature in Vista.
I am currently using Visual Studio 2008 on XP Pro SP3.
Developing against http://localhost/ everything including debugging works fine.
I need a second website on my machine. IIS 5.1 only allows one website at a time so I used the JetStat XP Pro IIS Admin tool to create a second website. This runs by stopping the Default website and starting the other.
I have added the new website name into the Hosts file and mapped to 127.0.0.1.
Websites can be accessed via this address http://NewHostname/VirtualDirectoryName
Projects can be started without debugging (Web Applications & Websites).
However, when I try to debug I get an error: "Unable to start debugging on the web server. An authentication error occurred while communicating with the web server."
Integrated Authentication is enabled in IIS.
I have seen a lot of documentation with many fixes for "unable to start debugging on the web server" errors but they all seem like huge overkill for my problem, after all, debugging works fine provided I'm not doing it on this different hostname. They talk about doing things that I would do if debugging did not work at all even with http://localhost/.
Is there a place where I can just add this new hostname so that VS debugging is allowed? Do I need to change permissions somewhere? I feel like there should be a really simple solution that I'm just overlooking.
Here's a description of the problem: http://blogs.msdn.com/webdevtools/archive/2008/08/13/debugging-a-website-with-a-host-header.aspx
And here's the recommended registry workaround: http://support.microsoft.com/kb/896861
Do yourself a favour and download IIS Admin .NET.
This handy little tool allows you to switch between your websites at a snip - each one will become localhost when activated, and crucially, get you out of this debug debacle.
http://www.codeplex.com/iisadmin
You do have to add the hostname to a value within the registry.. but I can't remember where.
Since you can only have one website running at a time, why don't you just have them all running as 'localhost'? This way you don't have to change any annoying registry settings but you still have your applications running in individual IIS Websites.
I have a XP Pro and Vista machine setup on a workgroup LAN, normal case
with NAT router/adsl modem. Latop is wireless.
The XP Pro laptop has IIS on it and I have written an ASP.NET app.
When I try to access the app from browser on the Vista PC I get an error
saying can't connect to site.
I have tried the following:
Can ping the XP Pro PC from Vista PC.
Turned on Web access from windows firewall.
Rebooted.
When I telnet to it I get http 400 bad request.
Any thing I am not doing please?
Malcolm
Are you debugging your project using the ASP.net development server? I believe that server does not accept external connections.
If you've allowed access through the firewall, I'd suggest looking at your IIS settings for the website. Is anonymous access allowed? What sort of authentication are you requiring if not? Is the website actually running in the url you're requesting?
Lots of different problems occur because of IIS settings. Play with each possible cause, one at a time, until you find out what it is the real cause, if you still can't find it, play with two at a time.
When you finally find the problem, REMEMBER it, because problems with IIS tend to be forgotten and then you have to go through everything AGAIN. Sadly, I know this from experience.