Last week I changed the server of my ASP.net Application. Everything is fine except none of the web services seem to work. Nothing happens when the web service is being called from browser. I think there is problem with the IIS configuration or server settings.
I searched a lot in Google for this and did intensive debugging for weeks, yet with no solution. No web services work in my project since we changed server.
Is there any configuration that disables all web services? How can I debug this problem?
At last I got it from here..
Deploying ASMX webservice on iis 7.5
Thanks a lot #Frank.
Thank you Mr Joachim Isaksson For your comments
Related
I finally got my ASP.NET MVC application hosted on my local Windows/IIS server. I went to the login page but when I try to log in it says,
Error:
An error occurred while processing your request
This is fairly non-descript...
My gut feeling is that when I did the web deploy, I didn't deploy the localdb(?) where the users' credentials are stored. Before I try to re-deploy the entire app, I'd like to see if anyone can offer some guidance. Am I on the right track? Are there other possible causes/solutions I should investigate?
I'm using the default registration/login system that is in the project to start with, and it woks just fine in VS. I did a regular web deploy to my IIS server, and the site works just fine until you go to log in.
Fixed: This issue was caused (as suspected) by the inaccessibility of the LocalDB where all the users' credentials are stored. VS uses this light DB instead of making you install SQL Express or another alternative (much like IIS Express works better for debugging than full IIS). When I push my application to IIS from VS, the database wasn't connecting. I eventually found this other SO question, and the top answer fixed my issue.
How to deploy ASP.NET MVC 4 application using localDB to local IIS on Windows 7?
This will solve the issue, but there is a lot of conflict on the web as to whether or not it is ok to use LocalDB in production, so if you have a lot riding on your project you might want to take a look at that. For my purpose, LocalDB is just fine, so this solved the issue. Thank you to all who responded to my (admittedly) broad question. I'm sure this will be a useful thread for others with the same issue.
I know there are lots of questions about 404 error of /signalr/hubs folder and i read all of them but none of it is relevant with my problem.
Because normally my code is working on local machine and test server; but same code is not working on production server. This will make me crazy, i tried to recycle app pool, restart IIS or w3svc service but didn't help.
My web site is a secure web site and i think this may cause problem but i couldn't find any thing about running SignalR with SSL.
My project is ASP.Net Web Forms (Web site) and running on IIS 7 on Windows Server Version 6.0 (Build 6002, SP2). App pool is configured to run with .Net Framework version 4.0.30319
P.S: I had another https site which runs signalr without any problems. So i am very confused.
Edit: I had created another web site at same server and copied working codes from working server and tried; result was same. There is something (maybe configuration) about server or IIS.
Solution:
This solution solved my problem too. Actually i had tried this but i got 500 Internal Server Error and gave up. Whatever this is this solution, so i want to change my question what is purpose of this code? Why my site works at another server without this modification?
Ensure that where you're hosting your site is where your signalr/hubs is pointing to. A common issue is that people will host their site like so:
www.abcd.com/mysite/index.html
Now in this example SignalR is hosted at www.abcd.com/mysite/signalr however a lot of people will put /signalr/hubs in their index.html which is wrong. It should be ~/signalr/hubs because the hubs file isn't hosted at www.abcd.com/signalr/hubs it's at www.abcd.com/mysite/signalr/hubs.
Hope this helps!
Use <script src="<%: ResolveUrl("~/signalr/hubs") %>"></script>and that will resolve the problem
I have an Azure application that works perfectly on every one of my colleagues machines. On mine, the web application works, but not the azure project, which runs on the local development fabric.
I'm getting a 403 error, which causes a blank page in Chrome. The application_start method gets fired and sets up the routes, but the actual MVC controller never gets called. Again, this works perfect if I run the web application directly. If I use that same azure project and deploy it online, it also works fine.
I've tried repairing visual studio, reinstalling Azure, rebooting, re-fetching source, you name it.
I'm desperate for ideas! What would cause a 403?
Here is the answer. Looks like I wasn't the first to be victimized by this:
http://scottdensmore.typepad.com/blog/2010/05/how-a-checkbox-saved-paving-my-machine.html
What's interesting is that I wasn't even using IIS.
You need IIS for dev fabric. Cloud service projects do not run on the asp.net web server inbuilt in visual studio. Refer this.
So any configuration issues in IIS will affect you.
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
Is it possible to debug (with VS 2008) a site at my host? I have no particular control of the server, I'm only allowed to upload my website files to the server. I can however upload .pdb files etc.
The reason for me wanting this is because the site works fine on my dev machine, but refuses to show even the first page when deployed on the server (404-error).
Maybe a long-shot, but in my experience the "works-on-my-machine-but-returns-404-on-the-server" problem is often a consequence of that the WebServer Extension "ASP.NET v2.0.50727" is prohibited.
As Ganesh R points out, it may sound like your application never gets startet.
As for the debugging part, I don't think you would be able to pull that off...
Debugging requires that certain debugging components are installed and enabled on the server. This is highly unlikely to be the case on any production hosting platform.
Contact your hosting provider - they will usually be quite willing to help you diagnose the problem you are encountering.