Morning All
I am hosting my website on IIS , the website was built using the react template. But I have ran into a problem. When using localhost my webapp worked a charm, i could interact with the database and life was good. But now ive moved it over to IIS Im no longer able to pull data in from the database or interact with the db.
I think the problem may be the fact that IIS is running on a different server to my local machine. I have the ASP Core runtime installed on my local machine but not on the server where IIS is situated.
Can someone just confirm to me that I do require ASP Core runtime to be installed on the IIS server also?
Im not able to test things out until tomorrow otherwise I would find out for my self. Apologies, im basically a beginner with IIS and ASP
Thanks
If you are facing troubles with the database connection and not with your API endpoints could be network/proxy/firewall stuff. But if you're not able to deploy your API to IIS maybe could be that you're missing the Net Core bundle. For more information check the link below:
https://dotnet.microsoft.com/download/dotnet-core/thank-you/runtime-aspnetcore-3.1.9-windows-hosting-bundle-installer
Yes, you are required to have the ASP.NET Core runtime installed if you plan on running asp.net-core applications on it.
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'm pretty new to apache web hosting as my experience has been mainly in writing ASP .Net hosted on Windows boxes. I'm starting a new project for a client soon and on their Fedora web server they already have 3 other websites running under the Django framework on Apache.
I'm looking to write this new application in ASP .Net and therefore am looking into installing mono on the server so I can run it. I've had a look through the mono documentation but I don't want to start installing it on their server in case it messes up the existing sites running on Django. Can anyone give me any advice on this?
I have an ASP.NET MVC solution with multiple project under it, it works fine locally after uploading the site on the server I get the System.Reflection.ReflectionTypeLoadException error
I am also trying to run the solution on IIS and the error I am getting is Not Found
The requested URL / was not found on this server.
I have also copied all the DLL to the output folder, what could be the issue is the problem most likely from a missing DLL, is it from the remote hosting security level or am I missing something else in the project please advise.
After calling the hostgator (where the site is hosted) and addressing the issue, I was told that custom DLL is not allowed in our hosting as you may see I have taken screenshots of the DLLs I wonder what are the customs DLL in my project as hostgator technician put it
I assume you're running v3 of ASP.NET MVC. In which case, have you set the Application Pool .NET Framework version in IIS to C# 4.0? Indeed, is ASP.NET MVC and .NET Framework 4.0 installed on your server?
Does your application rely on any external libraries which were not included in the deployed application?
Are you able to debug your application at all? Ie the Application_Start. It's possible that something is going awry during that which is causing this.
Basically, more information would help!
Howcome I deploy my intranet ASP.NET MVC project?
What I've got so far:
project itself;
several client machines connected in a workgroup and server;
IIS Express 7.5, SQL Server 2008 R2 Express installed on a server.
It should be mentioned that though it's odd and unusual but server is just a machine without (even) server OS installed. Please note that it's not mine idea and is the environment I've got at the moment
I've read the instruction http://msdn.microsoft.com/en-us/library/gg703322(VS.98).aspx but it describes situation when you have Web Developer installed on the same machine.
Please help!
And Thanks!
This is the 100% manual approach, you might be able to access the remote web server via VS if authorization/permissions is lined up properly (much simpler, basically you just hit deploy):
Install IIS
Install .NET Framework 4
Install MVC
Register ASP.NET with IIS (just to be safe run it again)
Create Website via IIS Management Console (use a new directory for the website)
Put your files inside the new directory
Make sure permissions are setup properly
That's it
I'm deploying an ASP.NET application to Windows Server 2003 under IIS
IIS is serving html pages fine but I get a page not found when I try and serve IIS pages
You may need to "register" IIS for ASP.NET applications. As an administrator, run the command "%systemroot%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i". In addition, you may need to convert your web site to an application through the IIS management console.
By default, IIS has ASP support disabled in IIS6.
A server running a member of the Microsoft® Windows® Server 2003 family supports application server functionality, with Microsoft ASP.NET as an option that you can enable when configuring the application server role. To deploy ASP.NET Web applications to a production server, you must be sure to enable the ASP.NET and Internet Information Services (IIS) roles on the production server before you distribute the application.
See here for instructions to enable it:
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/9fc367dd-5830-4ba3-a3c9-f84aa08edffa.mspx?mfr=true
Other possible reason could be Web Service Extensions, where ASP.NET version could have been disabled. My other post here explains steps to solve this.
Make sure the right .NET framework is installed properly
Make sure the ASP.NET extension is enabled
Under website properties, ASP.NET tab, make sure the right version is set.
After having this same issue and trying all of the above without any luck. We reinstalled SP2 for Windows 2003 and this resolved our issue. I too have seen this problem resolved a few times with the other answers. Most of the time just reinstalling .Net 2.0 resolves the issue but not this time.
For future reference, this could also be the issue:
IIS on a Windows Server 64-bit can only to run in either 32 or 64 bit mode.
In short you need to:
1) run adsutil.vbs to enable 32 bit asp.net apps on win 64
2) re-register IIS calling aspnet_regiis.exe
3) re-open IIS Manager, go into Web service extension list and ensure ASP.Net version {2/4.xxx} (32-bit) is set to Allowed
(You might need to do Steps 2 and 3 for both Framework 2.0 and 4.0 if you want to run asp.net apps on both versions)
Full details are in the following link: http://support.microsoft.com/kb/894435
Another future reference in case this is helpful to anyone who used a similar path to mine.
My back end for the ASP.NET app was MySql not Sql Server, which for me meant having a mysql connector, the reason my IIS was not serving the .aspx file is because on my development environment I was using a different version of the MySql connector than the one installed on my production environment, I updated the MySql connector on the production server to match the version Im using on the development environment and it worked great.