I have project with SignalR + MVC, this not working on Server win server 2019 with IIS.
I Got errors:
signalr/negotiate?clientProtocol=2.1&connectionData=%5B%7B"name"%3A"feedbackhub"%7D%5D&_=1646730379815
Can anybody help me?
This all my Code:
https://github.com/duc14s/SignalRFeedbackSample
Have you enabled websockets on the server?
On the taskbar, click Server Manager.
In Server Manager, click the Manage menu, and then click Add Roles and Features.
In the Add Roles and Features wizard, click Next. …
On the Server Roles page, expand Web Server (IIS), expand Web Server, expand - Application Development, and then select WebSocket Protocol.
Related
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?
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 1 web application 1 web service and 1 windows application and I am calling a web service method from web application and in that method i am calling windows application exe. I have put windows application exe on server machine and also host that web service on server machine. If I the web service is hosted on local iis then its working and if it is on server IIS then it gives me Time Out error
Web service executes in the context of the ASP.NET worker process on the Web server. If you use the Process.Start method in an ASP.NET Web page or server control, the new process executes on the Web server with restricted permissions.
Give permission for ASP.NET worker process account to interact with desktop or allow ASP.NET worker process to run in SYSTEM account.
Open Control Panel and follow these steps: For Windows NT: click Services. For Windows 2000, Windows XP, and .NET Server: click Administrative Tools, and then click Services.
Double-click IIS Admin Service.
On the Log On tab, select the Allow Service to Interact with Desktop check box. Remember to run IIS Admin Service as a local system.
Stop and restart the IIS Admin Service.
I have a .NET 1.1 solution where all projects have been upgraded to .NET 4.0 (VS2010, Windows 7). To get past my "Unable to start debugging on the web server" problem, I switched my web application property to use VS Development Server instead of IIS.
When debugging the web application, it launches OK. But I get the above error when I hit a line where I call a web service that's local on my machine. I've seen stuff about adding useUnsafeHeaderParsing=false, but my web.config doesn't have a sytem.net section.
Is it not able to server the web service as well as the web application simultaneously on the application development server? Do I need to get it configured correctly to use IIS7? As a longtime IIS6 user, just looking at it makes my head spin... although, I do have the site and webservices set up within it, and I am fairly certain it worked at one time. Gotta love that.
This worked for me: Text below is comming from This CodePlex Post
This error usually occurs when you have set up Visual Studio to debug
an existing web application running in IIS rather than the built in
ASP.NET debug web server. IIS by default listens for web requests on
port 80. In this case, another application is already listening for
requests on port 80. Typically, the offending application is Skype,
which by default takes over listening on ports 80 and 443 when
installed. Skype is already occupy the port 80. So IIS is unable to
start.
To resolve the issue follow the steps:
- Skype -> Tools -> Options -> Advanced -> Connection:
- Uncheck "Use port 80 and 443 as alternatives for incoming connections".
Its due to Skype has taken default Port 80 or 443 and Default website is stopped.
to solve this issue, close Skype, [Start] Default Website from IIS, (and start skype again if you want.)
you might also try doing an IIS reset
I have a webApp in my IIS 7.5 on windows server 2008 now I need to move this particular web app (not all of them) to another IIS 7.5 on the new windows server 2008 R2.
Can anyone please suggest?
thanks
Web Deploy is probably the best, it can do it server to server (ie live sync/migration) as well as allow you to generate a package that can then be installed in the other server:
http://www.iis.net/download/WebDeploy
It includes GUI (extends IIS Manager) as well as command line options, can do it over HTTPS or directly using the IIS configuration APIs. It supports moving configuration, content, GAC, DLLs, Database, Certificates, SSL settings and more.