sh al

sh al

  • NA
  • 1
  • 1.7k

Parser Error

Jun 24 2012 6:26 AM
Hi,

We have developed an application using ASP.net 2008 and SQL server 2008. when it runs locally, it works okay but when it is published to a host. It creates following error:

Parser Error

Description: 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.

Parser Error Message: Could not load file or assembly 'Telerik.Web.UI, Version=2010.2.929.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Source Error:


Line 1:  <%@ page title="" language="C#" masterpagefile="~/MasterPages/ProductsCatalog.master" autoeventwireup="true" inherits="ProductsCatalog_Subcategories, App_Web_subcategories.aspx.915388b4" enableviewstatemac="false" theme="Austin4" viewStateEncryptionMode="Never" maintainScrollPositionOnPostBack="true" %>
Line 2:      <%@ Register Assembly="Telerik.Web.UI" Namespace="Telerik.Web.UI" TagPrefix="telerik" %>
Line 3:  <asp:Content ID="Content1" runat="server" ViewStateMode="Disabled" ContentPlaceHolderID="ContentPlaceHolder2">

Source File: /ProductsCatalog/Subcategories.aspx    Line: 1

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Telerik.Web.UI, Version=2010.2.929.40, Culture=neutral, PublicKeyToken=121fae78165ba3d4' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.237



Any comment or suggestion for resolving this error is appreciated.


Answers (1)