I have a simple setup based on the example code of signalR.
Client is a .net core console app.
Server is a.net core web app with signalR published to local IIS website.
Everything works fine in general.
if i stop/start the server using the IIS manager, 'reconnecting', 'reconnected' events do fire.
However if i re-publish the server ( asp.net app), via the visual studio- publish menu.. events are not fired on the client..and its not able to reconnect either. not even 'closed ' event. just sits there doing nothing.
i need to explicitly need to 'restart' the IIS website to get things going again.
Any ideas anyone what could be going on under the hood?
Related
I have an application that his a .Net Core API.
Everything works locally, and by that means,
Client App --> hits an .Net Core API successfully.
Howevever we have pushed the app to IIS Server, and we are not able to successfuly hit the API.
I know this is extremely vague, but what is something that I should be looking at to diagnose address this. I pulled the code from the published branch, and it works like a charm on local, but does not work on Server.
I do not get any Server Side exceptions.
Is there network connectivity? Log into the server and open a browser and put in the URL to the API. Any HTTP error is good. It means you can reach the API. If it times out, that's bad and that's your problem.
How do you know there are no exceptions? Are you logging all exceptions? Are you sure no exceptions are hidden in try blocks that end up ignoring the exception?
Assuming it's a Windows server, check the Event Viewer for warnings or errors.
I have an ASP.Net web application running on Windows Server 2008 R2 with IIS 7. A few weeks ago, something happened to the server, and I believe some Windows logins had been flushed from the system.
After getting the server back online, all our files and SQL Server databases were still intact. Some of the functionality of the web application is working properly--the users are able to log into the application (the login data is stored in an SQL Server database). Browsing to some pages, however will show a white page showing "HTTP Error 503: The service is unavailable."
The pages causing the 503 errors appear to be ones using special ASP controls, such as DataGrids.
The web project was compiled using .Net Framework 3.5. The IIS application pool on the server uses .Net Framework v2.0 with an Integrated pipeline.
Any thoughts on what I can look at to get this site back up to full functionality?
I figured out what was going on: the folder in my web site causing the 503 error was called Reports, which was causing a conflict with SQL Server Reporting Services on Port 80.
We don't run the SSRS, but it was tied to Port 80.
https://seankilleen.com/2012/11/how-to-stop-sql-server-reporting-services-from-using-port-80-on-your-server-field-notes/
I started SSRS and followed the link above to change the SSRS port to 81. After making that change, I was able to access the Reports application on my web application.
I have a .NET framework 1.1 application that uses two web services, one handles security and the other business functionality. Both were working fine. I made a change to the service responsible for business functionality, as well as the main application, and reinstalled both the web service and the main application. I have done this at least twice before, but this time, after logging in (which shows that the security web service is working), any access to the biz web service fails with "Server Application Unavailable. The web application you are attempting to access on this web server is currently unavailable."
There is no error logged in the event application log.
It works fine on my development laptop (in the Visual Studio .NET 2003 dev environment), this error only occurs when I install it on the server (Windows Server 2003 Standard).
I'm really stumped because all I changed was some code affecting functionality, and I built the application in exactly the same was as the last time.
I have an n-tier application which I have added SignalR functionality to. When I now compile my business layer I have to do a iisreset before the website can load again. It simply just keeps loading, and doesn't get anywhere. Even a kill on the w3wp process doesn't help this out.
I have tried and removed SignalR and then it works fine when compiling the backend. My guess is that a connection is made from SignalR to the server, and it is broken when the backend is compiled, which haults the site from doing a complete load.
Anything I might be able to do about this?
Are you developing on windows 7? If you are then don't as it only allows 10 concurrent connections. Use IIS express instead.
I am doing an simple Siverlight app talk to server using WCF.When I run the app in visual studio,it works fine .However,when I hosted unders IIS,the data from the server will never returned.
Can anyone shine some light on this and how can I debug silverlight app with WCF?
you can try fiddler.
or enable wcf logging on a website that hosts your service, which will give you even more information. Read more here.
Are you receiving any kind of response from the server at all? Are your silverlight applications configured to reference the correct web services (not the visual studio web server)? Can you browse to your WCF services in the browser and get a response?
www.example.com/myservice.svc
Just a few ideas...
Use Attach to process. Remember Silverlight is running on the client so you can open the app in IE and then attach visual studio to it.
You may also want to look at Fiddler to check the traffic is going to the right place.