We updated the project from 3.5 to dot net framework 4.0 ,build and deploy it on windows server 2003,the default page was loaded but when we access any other pages it shows error:
404 File Not Found
The page that you are looking for might have been removed,had its name changed, or is temporarily unavailable.
Again when I build the same project on the server the error goes off and the pages redirects as usual.But when I build on My Machine which has windows 7 and upload the dll ,the same problem occurs.Is there any thing to do with the dll with windows.
What could be the problem of this.We are tired searching of the solution.We would be grateful you provide us the actual cause of the problem.
I think the problems occur for os change. It does't support in Windows 7
Related
Created a asp.net 5 project with another team member and works on everyone's computer but mine. I get "Failed to load resource: the server responded with a status of 500 (Internal Server Error and the web page is blank.
I thought maybe I was missing a .net version but when downloading .NET Framework 4.6 it says ".NET Framework 4.6 or a later update is already installed on this computer."
If someone could point me in the right direction it would be a lot of help! Thanks!
The error code is very general in that some error happened in your code that stopped the execution of the webpage.
If you are running the webpage in debug mode from Visual Studio on your computer, VS should have stopped on the line of code containing the error.
If, for some reason, Visual Studio does not stop on the error, you can also look in Windows Logs -> Application. It should appear as an Asp.Net Warning with details regarding the error.
See Log #3:
http://blog.leansentry.com/the-server-logs-you-need-to-know-to-fix-any-iis-aspnet-error/
I figured out my problem! I had a dependency issue in my project.json file.
"Oracle.ManagedDataAccess": "12.1.2400"
"FluentNHibernate": "2.0.3"
"NHibernate.Caches.SysCache": "4.0.0.4000"
These packages didn't support dnx 5.0 so they couldn't be in the default dependencies section. They needed to go under dnx451 -> dependencies.
For this project I needed to install and run VS 2003 on Windows 7 using IIS 6.0 with Framework 1.1 on my sever because there was old VS2003 C# code on a remote server that needed updating and did not have VS 2003 installed only the DLL, PDB, aspx, and aspx.cs files. After porting the code over and making the needed changes on my local server, I discovered that while I could browse the page, I could not run the page with debugger and got this error: "... Unable to start debugging on the web server. There is no managed code running in the process. In order to attach to a process with the .NET debugger, managed code must be running in the process before attaching." I then started the application without Debugger and selected the w3wp.exe process for CLR in order to attach the process but I noticed that the process session was set to 0 and I still got that error again.
The following is done in IIS6 :
Application created.
DefaultAppPool (.NET framework 1.1 Integrated)(ApplicationPoolIdentity) is used
Browsing the web page works OK.
Authentication has Integrated Windows and ASP.NET Impersonation enabled.
I have runned aspnet_regiis from all the .net version in order
Set debug="true" in the web.config.
Thanks much for your help
Resolution:
Right click the ASP.Net project > Properties
select Configuration Properties > Debugging
Enable the below mentioned entries in 'Debuggers' frame.
ASP.Net Debugging
Unmanaged code debugging.
I had the same problem.
I fixed it.
Delete the virtual directory in IIS
Create the new virtual directory with different name other than the old one and configure the new virtual directory name in your visual studio solution.
I'm trying to deploy an ASP.Net application I developed to a Windows Server 2003 System but I get a error message when running the Site.
The first thing is that I get a Null Reference exception when I want to access my custom configuration section. So I figured that maybe the System.Configuration Assembly might not be installed. However I removed the reference and included the database directly into code to see if it works without.
But now I'm getting another error that a third party server control is not recognized.
Error Message: Server label
"trirand:JQGrid" unknown.
The same application runs just fine on my XP machine with IIS 6 installed so I wonder if I'm missing some installation. This is the first ASP.Net Application on that machine as before there were only ASP tools. I think that the .Net Framework 3.5 SP1 is installed but I'm not sure. Another question is if the ASP.Net is integrated into the .Net Framework of if I need a different install package.
Update:
I experienced a weird behaviour: I added the obviously wrong element <asdf> to the web.config file. On my development machine that gave me the expected error, but on the server nothing happened at all. So it seems like it some does not recognize my web.config file.
You need to check if the windows server system is loaded with the software your application required.
The folder v3.5 should be there in the following location.
C:\WINDOWS\Microsoft.NET\Framework\v3.5
Also you need to check if asp.net is installed on the system, if you are not sure then do install it, installing it if it is already there have no side effects.
To install asp.net type the following commands in DOS prompt.
cd C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
// then
aspnet_regiis.exe -i
Then also, confirm in IIS that correct version of asp.net is selected for your website.
To check; go to your website properties in IIS
then select ASP.NET tab then check ASP.NET version it should be 2.0.50727 for websites below .net version 4.0
Good Luck!
I am trying to port an existing ASP.Net 1.1 website to another web server that currently runs IIS7 and a number of websites that target either .Net 2.0, 3.5 or 4.0. All other sites continue to work perfectly. Unfortunately, I can only browse static files on the newly imported site. If I try to access any of the Features in IIS7 for the new site I get the following error dialog:
There was an error while performing
this operation.
Details:
Filename:
\\?\C:\Windows\system32\inetsrv\config\applicationHost.config
Error:
I followed the instructions on this page but am at a loss as to how to get this working.
I encountered this problem too this afternoon.
I did a quick google and found others with the same issue on the asp.net forum. The issue seemed to be that
Here is what got me past this error, hope it works for you.
the runtime tries to load the
corresponding configuration, it
doesn't take the bitness of the
application pool into the
consideration. As you know, ASP.NET
1.1 is only supported on 32-bit. So if you have a 64-bit OS, in order to
run ASP.NET 1.1, you have to enable
32-bit applications in the application
pool. So, with the QFE/SP2 on 64-bit
OS (and only on 64-bit OS), the
runtime is incorrectly looking for the
1.1 version of the configuration under Framework64, which does not exist.
Workaround:
Create the Framework64 directory for 1.1
md \windows\microsoft.net\framework64\v1.1.4322\config\
Copy the 32bit config to 64bit config location created in step 1.
copy \windows\microsoft.net\framework\v1.1.4322\config\machine.config
\windows\microsoft.net\framework64\v1.1.4322\config\
http://blogs.iis.net/wonyoo/archive/2009/06/18/workaround-running-asp-net-1-1-on-vista-sp2-ws08-sp2.aspx
I have moved a project from asp.net 2.0 to 3.5. The original project was using the atlas ajax extensions so I have modified the code to use the built in ajax features in 3.5.
When running the project within the dev environemnt (VS2008 on Vista Business SP1) and using the asp.net dev server I receive javascript errors such as WebForm_PostBackOptions which point to a missing handler/module.
If I deploy the project and run it stand alone within IIS or if I use Fiddler2 while running in VS2008 I do not see the errors and fiddler shows that the axd files are being downloaded correctly. Also deploying to a 2003 server does not show any issues.
I could just carry on and forget this as it works when deployed but I would like to understand what is happening. Has anyone got an ideas as to what is going on here and how to get the same results accross all environments?
Do you get these same errors when you run in VS2008 but with IIS instead of the dev server?