Showing posts with label ASP.NET Errors and Solution. Show all posts
Showing posts with label ASP.NET Errors and Solution. Show all posts

Thursday, January 24, 2019

Could not load file or assembly System.Web.Mvc, Version=3.0.0.1


Could not load file or assembly 'System.Web.Mvc, Version=3.0.0.1;Could not load file or assembly 'System.Web.Mvc, Version=3.0.0.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified;

Error:

System.IO.FileNotFoundException: Could not load file or assembly 'System.Web.Mvc, Version=3.0.0.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified

Solution:

  • Remove the MVC reference and add the correct reference to the project
  • Change the Copy Local property of the reference to true
  • Update the bindingRedirect setting in web.config as below

web.config runtime section:
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="1.0.0.0-3.0.0.0" newVersion="3.0.0.1" />
</dependentAssembly>

Change the Copy Local setting will include the System.Web.MVC.dll file in the bin folder when you publish the project, so that it works even if the server is not updated with the new version.

Error 3 'CompareAttribute' is an ambiguous reference between 'System.ComponentModel.DataAnnotations.CompareAttribute' and 'System.Web.Mvc.CompareAttribute'

Error 3 'CompareAttribute' is an ambiguous reference between 'System.ComponentModel.DataAnnotations.CompareAttribute' and 'System.Web.Mvc.CompareAttribute';Error 3;CompareAttribute is an ambiguous reference

Error:


Error 3 'CompareAttribute' is an ambiguous reference between 'System.ComponentModel.DataAnnotations.CompareAttribute' and 'System.Web.Mvc.CompareAttribute'

Cause:


This happens when running VS 11 with mvc Beta 4 and .Net 4.5.

Solution:


To make this work between .NET4 and .NET45 you need to add the below statement in those files to:

using CompareAttribute = System.Web.Mvc.CompareAttribute;

Wednesday, January 23, 2019

Error 8 The type or namespace name 'PagedList' could not be found

Error 8 The type or namespace name 'PagedList' could not be found;Error 8 The type or namespace name 'PagedList' could not be found (are you missing a using directive or an assembly reference?)

I encountered the below error while compiling the project.

Error 8 The type or namespace name 'PagedList' could not be found (are you missing a using directive or an assembly reference?)


Solution:

Try installing the PagedList.MVC NuGet package for your project.
You could use the following steps to do so :

Right-click your Project within the Solution Explorer
  • Choose the "Manage NuGet Packages" option that appears
  • Search for "PagedList.MVC" within the search box
  • Click "Install" on the first option that appears : 



This should add all of the appropriate references that you need. You'll then just need to add the appropriate using statements within your code (generally, you could right-click on the ToPagedList() method and choose the "Resolve..." option to do this automatically).

Wednesday, January 25, 2017

Telerik ASP.NET Ajax client-side framework failed to load

Telerik;0x800a139e - JavaScript runtime error: ASP.NET Ajax client-side framework failed to load;0x800a1391 - JavaScript runtime error: 'Sys' is undefined

For Internet Explorer users getting the following error:


Problem:

Recently I encountered an issue, RadScriptManager started throwing the following errors:

0x800a139e - JavaScript runtime error: ASP.NET Ajax client-side framework failed to load.

0x800a1391 - JavaScript runtime error: 'Sys' is undefined


This issue is observed on IE 11 and doesn't appear on Chrome or Firefox Browsers.

Suggested solution:


I had below in my web.config. I removed runtimeversion2.0 and it worked well.


<add name="Telerik_Web_UI_WebResource_axd" path="Telerik.Web.UI.WebResource.axd"
                 type="Telerik.Web.UI.WebResource" verb="*"
                 preCondition="integratedMode,runtimeVersionv2.0"/>  




Thursday, October 13, 2016

0 and 1 String was not recognized as a valid Boolean - Boolean Parameter in SQLDatasource

String was not recognized as a valid Boolean, System.FormatException: String was not recognized as a valid Boolean,Boolean parameter SQLDataSource,Setting up Boolean Value SQLDataSource InsertParameters

I had a SQLDataSource with insert parameters and one of which data type was set to Boolean. And I was setting the default value for insert parameters in code behind.

aspx code:
<asp:Parameter Name="bIsActive" Type="Boolean" />


I assumed that 1 or 0 would naturally be converted into Boolean when I did this:

SqlDataSource1.InsertParameters["bIsActive"].DefaultValue = c.Checked ? "1" : "0";


But instead I saw this:

String was not recognized as a valid Boolean.
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.FormatException: String was not recognized as a valid Boolean.
Fig 1: String was not recognized as a valid Boolean


ASP.NET can easily convert 1 and 0 (integer types), but struggles with Strings.

Solution:


I used True and False strings instead of 0 and 1.

SqlDataSource1.InsertParameters["bIsActive"].DefaultValue = c.Checked ? "True" : "False";

Thursday, October 6, 2016

This Page Can’t Be Displayed Turn On TLS 1.0, TLS 1.1, And TLS 1.2

This Page Can’t Be Displayed Turn On TLS 1.0, TLS 1.1, And TLS 1.2,This page can't be displayed error,Cannot Access Some HTTPS Sites with Internet Explorer

For Internet Explorer users getting the following error:

This page can’t be displayed - Turn on TLS 1.0, TLS 1.1, and TLS 1.2
in Advanced settings and try connecting to https://websitename
again. If this error persists, contact your site administrator.
Change settings. 
This issue is observed on IE 11 and doesn't appear on Chrome or Firefox Browsers.


Resolution:


 Launch Internet Explorer | Tools (Alt+X on IE 11) | Options | Advanced and make sure the settings match those below: 


Monday, October 3, 2016

Error Creating Control - Failed to create designer 'Telerik.Web.UI.

Telerik Error Creating Control,Error Creating Control Failed to create designer, Telerik Design time error,RadControls
You’ll find this error from time to time when switching to Design View in Visual Studio to work with Telerik Radcontrols, especially after Upgrading to a new version of Telerik UI for ASP.NET Ajax.


Causes:

  • There is a GAC-reference for the Telerik.Web.Design assembly in the project and the      GAC has been updated. As a result, the Telerik.Web.Design assembly, referenced by the WebSite, does not exist in the GAC.
  • The reference to the Telerik.Web.UI assembly (either in Register directive or web.config, or Telerik http handlers/modules registrations in web.config) contains hard-coded version number which does not match the version of the Telerik assembly referenced in your project.
  • Open the application in a machine that doesn't have Telerik UI Installed.


Fortunately there are several ways to solve this problem:

  • GAC Deploy the required version of the Telerik.Web.Design.dll.

The Telerik.Web.Design assembly contains the Visual Studio designers of the controls. 
          Telerik.Web.UI.dll requires Telerik.Web.Design.dll of the same version in the GAC.
Use the command gacutil /i [path to Telerik.Web.Design.dll with latest version]

  • Bin-deploy the design-time assembly Telerik.Web.Design.dll

Remove Telerik.Web.Design.dll from the GAC
Copy Telerik.Web.Design.dll to the bin folder
          Restart Visual Studio

  • Bin-deploy the assembly Telerik.Web.UI.Skins.dll
Copy Telerik.Web.Skins.dll to the bin folder
          Restart Visual Studio
  • In web.config file, removing the specific version, Culture, and PublicKeyToken from the Telerik.Web.UI.WebResource.axd entry.

         Correct Syntax:
        <add path="Telerik.Web.UI.WebResource.axd" type="Telerik.Web.UI.WebResource" verb="*"   validate="false"/>

The second solution did the trick for me. Hopefully one of the above solutions will work for you.

Monday, September 26, 2016

Configuring IIS Express failed with the following error Unable to access the IIS metabase


After installing Visual Studio 2013 and opening my solution, I received the below error:

Configuring IIS Express failed with the following error:
Unable to access the IIS metabase. You do not have sufficient privilege to access IIS web sites on your machine.

The root problem was that the "My Documents" folder had setup to be on a network share, and the share was not accessible. Once I changed the "My Documents" folder location to a local folder (by modifying the registry value), it started working again.


Changing this key worked for me:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\Personal


I know that this may not be a common scenario that you might run into, but I've posted it here because it gives the same symptoms.
Registry Editor




Sunday, July 5, 2009

Null Reference Exception in SessionStateModule

The Null Reference Expection in SessionStateModule.PollLockedSessionCallbacks() is happening when the page is viewed and refreshed twice in Unhandled Exception.


Possible Reasons:


1. Sql Server Session state

2. After applying windows update for .NET

3. Impersonation

4. Threading Issue

5. custom IIdentity object to authenticate users

6. Improper Serialization



Possible solutions:


1. use Inproc session state for debugging. Set the SQl state in web.config and machine.config to InProc


2. If the page is not using Session variable, Set the SessionState as OFF


3. Remove the Security Update for .NET Framework 2.0 (KB928365) from the machine


4. Instead of using the custom IIdentity object to track authenticated users change the code to use a static, thread-safe collection and pull authenticated users from this collection instead of the HttpContext.Current.User property.


5. Move any assignments to Context.User into Context.Session since impersonation could be done where needed rather than assigning it for the lifetime of execution.


6. Take the custom Security.Principal class out of the website project, and compile it as a Class library into a .DLL (assembly). Sign the .DLL with a Strong Name, and place it in the GAC. Adjust your code that references the custom Principal to call the code in its new location, if necessary

7. Add a Reference to the new assembly in your website project


8. If you use a WebSetup project to install your website, as I did, you can have it place the assembly into the server's GAC for you, during the installation.


9. Use the hot fix KB942086

It is available at http://support.microsoft.com/kb/942086


10. It applies to .NET Frame work 2.0