ERROR :

CS1703: An assembly with the same identity 'System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' has already been imported. Try removing one of the duplicate references


SOLUTION


Check the version of the .net Framework . in the project ,

Hosting ASP.NET 1.1 Application in IIS7 with Windows Server 2008 Environment

Migrating your ASP.NET 1.1 application from IIS 5.1 to IIS 7 is easy task , until you had installed all the patches and Service pack , while installing the IIS 7 install the IIS 6 Comparable tools also

Check List:

Mostly in Windows Server 2008 there won’t be ASP.NET 1.1 , so we need to install the .Net Framework 1.1 , then the service pack for .Net framework 1.1 then the security updates for asp.net 1.1 , After you installed all the patches you can find the ASP.NET 1.1 in the application pool (fig -1)

fig-1

Yes now your IIS 7 is ready for ASP.NET Application , then Create a Virtual Directory and assign the Specific folder of the application , then assign the asp.net 1.1 application pool to the application

Click on the application in the right hand side you can find the action window [fig-2]Click on the Basic Settings edit window will open [fig-3 ] in that select the ASP.NET 1.1 application Pool and press Ok

fig-2

fig-3

Tips & Tricks:

Tips 1 : Custom Error Click on the projects in the property area under IIS  Error Pages  open this right Click on the window and open the Edit window [fig-4] here you can set the customer error based on your needs [fig-5]

fig-4

fig-5

Tips 2: SMTP –Just fill the Necessary details

Tips 3: Authentication - Purpose is same as the previous version this time must user friendly then before

Common Errors:

IIS Worker process stopped. – If you had not installed Service pack for 1.1 this error will come

An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Ambiguous match found – if you had not assigned the correct application pool

Folks all the above said procedures, tips and error messages are what I had faced in my production environment. Kindly bear for my poor English

Error Message :

unable to start debugging on the web server. the type initializer for system.net.digestclient threw an exception

Cause : if your environment is VS2005 with .Net Framework 2.0 ,and if u have an assembly with security.dll this error will come ,

Solution : rename the assembly name

Error Message

Error 811 F:\MySampleProject\RptCrystalViewer.aspx: ASP.NET runtime error: '/LM/W3SVC/1/ROOT/MySampleProject/is not a valid IIS application. F:\MySampleProject\RptCrystalViewer.aspx 1 1 Finance

Cause : Due to Invalid path

Solution :

Right Click on the Project go to the web Tab and Change the path

Error Message

IIS Worker process stopped , When your Deploy your ASP.Net 1.1 Version of application in II7 , we need to set the application pool for Framework 1.1 , if you install Framework 1.1 it will automatically create , once the application pool is created and you had assigned to the the asp.net 1.1 application grt, it should work fine.. rit , but it wont , what it will do means it will stop the work process ,,.. you might ask why the hell it stops my work process ? good Question

y beacause ..... u r using microsoft products u have not installed the service pack that the reason ,,

So u need to the install the service pack for .net framework 1.1 , with asp.net 1.1 security update for framework 1.1 once your had installed it will work fine ..

Error Message :

ASP.NET Ajax client-side Framework failed to load

Solution :

add the tag in web config file

While using the Ajaxtoolkit and if you have different version of Framework you might receive this message

Error Message :

Error 2 Assembly 'AjaxControlToolkit, Version=3.0.30512.17815, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' uses 'System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

Solution :

in the web config file inside the configuration section add this tag

Error: The Web Server Could Not Find the Requested Resource while debugging the web application you might receive this type of error after you update the web application tools

Reason :
If you have installed the URLScan Filter this error will come , basically URLScan is for IIS 7 if you install for IIS 6 it will create this problem .

Solution:
Un install the URLScan Tool , Because IIS 6 has all the resources of URLScan

Nowadays i am mostly working in VS 2005 , i have a problem in master page . the problem is when i am creating the pages its not showing the option to select the master page, I am receiving this problem in my laptop but in my desktop I had installed the same version its showing the option .As a temporary solution I am adding the master page in code behind . any guess what could the problem . I had also installed the service pack 1 for VS 2005 in

both the PC

Development Environment :
Windows XP, IIS 6, VS 2005 , Framework 2.0 ASP.NET 2.0

Deployment Environment :
Windows Server 2008, IIS 7 , ASP.NET 2.0 and Framework 2.0

Error Message :
Request is not available in this context Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Web.HttpException: Request is not available in this contextSource Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:
[HttpException (0x80004005): Request is not available in this context]
System.Web.HttpContext.get_Request() +3465893
IIMSMain.Global.Application_Start(Object sender, EventArgs e) in C:\Prabakar\IIMS\Global.asax.cs:27
[HttpException (0x80004005): Request is not available in this context]
System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +3385130
System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +125
System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +182
System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +259
System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +245
[HttpException (0x80004005): Request is not available in this context]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3465475
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +69
System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +675
Version Information: Microsoft .NET Framework Version:2.0.50727.1434; ASP.NET Version:2.0.50727.1434

Solution

Change in Global.asax file in the

protected void Application_Start(Object sender, EventArgs e)
{
ApplicationConfiguration.OnApplicationStart(HttpContext.Current.Server.MapPath(HttpContext.Current.Request.ApplicationPath));
Masters.SystemFramework.ApplicationConfiguration.OnApplicationStart(HttpContext.Current.Server.MapPath(HttpContext.Current.Request.ApplicationPath));
}

Then change the application pool to classic .net , this is how i solved my problem