I have an application already deployed on a couple of customers utilizing signalr for communication. It works on windows 2003 server with IIS 6.0 with the mappings configuration, also works on win 7 and iis express. But for windows 2008 R2 with IIS 7.5 the hubs file although it's served, the signalr.hub with the list of server methods is NOT included in the script therefore clients can't connect to the hub.
Help is appreciated!!!
Ok, so here is what I found. We have a setup project that installs our product. I haven't looked into the process in detail but what it does is: creates a website under iis default, then assigns an app-pool that runs with Frw 4.0 and I think it also registers the framework at some point of the process. So, for some reason the javascript hub file was being generated without the actual definition of the hub. After so many teaks I decided to remove the website from iis and added it back manually and it got fixed. So, I don't know what setting was impeding signalr to initiate the hub but that was how I solved it.
Thanks
Related
Im using IIS 8.5 on Windows Server 2012 R2 so I add my Web Api but when I try to view the site it stays in a loading state like this:
Do not show any message or error just stays loading, I think that i miss some configuration or feature in my IIS but I don't know which one.
Edit: I use .Net framework, it is a REST .net web api like this reference, the IIS have installed .Net versions 3.5 and 4.5, it's IIS not the express and the default IIS website runs fine.
I would really appreciate any help.
Try to reduce the timeout settings to a minimum level, say 10 seconds.
See if it throws a Timeout error.
Without much information from your side its hard to judge.
Perhaps it could be an external service you are trying to access(Web service) or a DB connection?
Please check if the application pool you assigned to your solutions runs under the correct version of .net framework and in integrated mode. I had similar issues when trying to run an mvc app in classic mode. Check this out.
EDIT 1 - Reconfiguring IIS
If problems persists then try the ASP.NET IIS Registration tool. Execute the followig command as administrator:
aspnet_regiis -i
At the end of this post the different locations for aspnet_regiis are described. You should select a .NET Framework version corresponding to that of your project, run aspnet_regiis and assign the proper application pool to your app.
Hi iam making an app for which i have already completed the UI part and is currently a asp.net MVC project. for which i use the local IIS to debug. A part of the project that we are using uses signalr for device that connect to the system running the app.
Local IIS on windows 10 PRO limits the max connection to 10. Which is not something we can do away with.
The solution that seems promising is to make a signalR self host.
as the link states here
https://github.com/aspnet/KestrelHttpServer/issues/435
if the app is not using any part of the inbuilt IIS then there is no limit of the maximum connection.
The problem that im facing is that there is not help available anywhere related to it. and i want to be sure before getting to start with signalR self host about the maximum connections that it will be able to hold on a system running windows 10 Home / Pro.
Run it in IIS Express.
Right click your web project and go to properties.
On the Web tab, note the Project Url with port (http://localhost:12345)
That is the url it will be running in IIS Express.
Then start your site to fire it up in IIS Express. I right click the web and select View, but you could also start debugging.
Once it is running in IIS Express you can see the icon in the taskbar by the clock and manage all sites running in IIS Express there.
So without the available help. I converted my application to SignalR Self Host and tested it. ANd seems there is no Connection Limit even on Windows 10 Home version. So the system is working fine.
#Lex Li i think you should test again with windows 10.
So the conclusion is that IIS is actually the culprit for the max connection limit.
so after .net core 1.0 got published I started a new console project and imported the code from a small prototype that is supposed to run without IIS. Besides having to use net46 in my project.json due the not-yet updated MongoDB.Driver, that worked fine. When I build the app in Visual Studio a small App.exe with a lot of dll is build and can be run fine locally without IIS.
I then noticed the option to build for IIS Express and thought that I can use the IIS on our server (IIS 6.2, Windows Server 2012 R2) too. It publishes fine with WebDeploy, but nothing happens after that. I was following this official guide. I installed the .NET core Windows Server Hosting bundle and everything appears to be in order, but when I browse to the url, I get a ERR_NAME_NOT_RESOLVED. Theapp.exedoes not appear in the Task Manager and I can't find any log file, although it is enabled in theweb.config. I can execute the app manually, but then it only listens on the defaultlocalhost:5000` address.
If I understood it correctly, the IIS is supposed to act as a reverse-proxy to the dotnet tool which starts a dll, but in my case it's already a compiled exe that works standalone. But I can't figure out how to build a dll from this app..
What am I doing wrong?
If you target full .NET Framework the application will be .exe and not .dll and it is fine. ERR_NAME_NOT_RESOLVED indicates that the url you provided in your browser could not be resolved and the request to the application was not made. AspNet Core Module starts the application on the first request and because the host could not be resolved the request was not made and the application was not started. Once you figure out why the name could not be resolved and you still have issues with making your application work with IIS take a look at my post which explains how things work and how to troubleshoot issues. This, however, only applies after the request can reach your application.
I've just got a new server setup on Windows 2008 Web edition. I'm trying to set the first asp.net 4 application up on it but am having nothing but problems.
The latest is that I'm getting the 404.17 error, which says "the requested content appears to be script and will not be served by the static file handler.".
I've done a lot of research on google but most suggestions seem to be to run aspnet_regiis -i to install asp.net 4. I've done this several times both on the Framework and Framework64 folders, but with no success.
I tried changing from the default application pool to a .net4 application pool, which appeared to work at first and I instead got a server error to do with permissions. I fixed that, and immediately the 404.17 error returned.
Other suggestions I've read say to go into the "turn windows features on and off" and make sure .net 4 is selected there under IIS. However on this server clicking "turn windows features on and off" takes me to the standard windows 2008 server manager. I click "add features" there, and only ".NET Framework 3.0 Features (Installed)" is listed and selected. .NET 4 isn't shown there, yet it is selectable through the application pools.
What else can I try to get the website running as I'm at a complete loss now. Its annoying because my old server was easy to manage - I did it all through the server itself without a control panel (Windows 2003), now on my new server I have to manage most of it through Plesk because there is no dns.
Any help would be much appreciated.
I too had the same problem but solved it with simple solution. My program was in framework 4.0 but in application pool was mapped to framework 2.0.
Just changed the frame work in application pool to 4.0.
It worked.
I've finally figured out the problem, and it was to do with Plesk itself.
After delving through some of the thousands of links throughout the plesk control panel I found a page for "Website Scripting and Security". Under there it was set to .NET 2.0. However, even though I'd installed .NET 4 on the server, Plesk didn't know about it. Although the application pool I'd set the website to run under through IIS was .NET 4, it still wouldn't work for some reason.
I then found another page under "tools and settings" for server components, and on that page is a refresh button. Hit that and it suddenly realised that .NET 4 was installed, went back to the website scripting and security page, selected .NET 4, and hey presto, I got a server error (never have I been so glad to see a server error).
I then just had to give the application pool identity read access to the web folder, and the website worked.
I wish I'd paid an extra £15 per month for Windows 2008 Standard edition now so I could manage it all manually without Plesk.
Ensure that you are running this application under a Virtual Directory, also ensure that your IIS has ASP, ASP.Net, ISAPI Extensions And Filters, Static Content installed.
Change the .net framework from 'plesk' panel:
go to Domains
select then domain
Go to 'Domain and Websites & Domains'
Hide Advanced Operations
Go to 'Asp.net Settings'
Go to 'Change Version'
select 4.0
If you don't have the 4.0 option then you must install the framework on your server first.
I have a Win 2008 R2 Enterprise machine that is running fine several websites each one with its own app pool.
I have no troubles giving permissions (using windows GUI) to IIS AppPool\A, IIS AppPool\B, etc... But today I have created one more app pool "C" and I can't find it in the GUI nor using icacls command. I'm trying to give permissions in a folder to IIS AppPool\C but it says it can't find! I'm including built-in security principals in the search and if I type any of the existing app pool identities windows finds then Ok. The problem is just with this new one.
Does anyone knows what is going on?
I don't know if it is reladed but the only change made to this server was to enable .net 3.5 WCF Activation for http and non-http. After enabling this, I got error in all my .net 4 sites and fixed by running aspnet_regiis.exe /iru as described here http://devonenote.com/2010/06/could-not-load-type-system-servicemodel-activation-httpmodule .
Turns out you need to start the associated IIS application for the first time before you can see your application pool in the windows GUI!