I am trying to deploy an Ajax-enabled ASP.NET 2.0 web application that leverages NHibernate for OR-mapping. Works fine locally, but when I deploy to the web server and browse to the Login.aspx page, I get the following error. Can someone tell me what the
problem means? And if I need to download a new version of MSXML parser to install on the web server, where can I find it?
---------IGNORE----------
---------IGNORE----------
Server Error in '/' Application.
Configuration Error
Description:
An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Could not load file or assembly 'Microsoft.MSXML, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Source Error:
Line 52: <add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> Line 53: <add assembly="vjslib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> Line 54: <add assembly="Microsoft.MSXML, Version=8.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> Line 55: <add assembly="Microsoft.VisualStudio.OLE.Interop, Version=7.1.40304.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/> Line 56: <add assembly="Microsoft.VisualStudio.ProjectAggregator, Version=8.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.MSXML, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' 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:2.0.50727.1433; ASP.NET Version:2.0.50727.1433
Makes sense, but what version would this be? Below is a link to a list of Microsoft.MSXML versions and there is no 8.0.0.0. Is it possible that any 8.x version would be suitable?
It seems that the server doesn't have the installation of Microsoft Document Explorer 2005. This assembly's FileVersion should be "8.0.50727.42".
To resolve this issue, you can try to locate the dexplore.msi file from "C:\Program Files\Common Files\Microsoft Shared\Help 8\Microsoft Document Explorer 2005" (from machine that has Visual Studio 2005), and then install it in
the server.
I look forward to hearing from you.
Thomas Sun
Microsoft Online Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.
Thank you for your reply. We had to take a different architectural direction because we were wasting too much time on this. Although it seems like your solution should have worked. Thanks for the help.
amarzi
Member
7 Points
5 Posts
Cannot load file or assembly Microsoft.MSXML version 8.0.0.0
Nov 03, 2008 07:43 PM|LINK
Hi,
I am trying to deploy an Ajax-enabled ASP.NET 2.0 web application that leverages NHibernate for OR-mapping. Works fine locally, but when I deploy to the web server and browse to the Login.aspx page, I get the following error. Can someone tell me what the problem means? And if I need to download a new version of MSXML parser to install on the web server, where can I find it?
---------IGNORE----------
---------IGNORE----------
Server Error in '/' Application.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Could not load file or assembly 'Microsoft.MSXML, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Source Error:
Source File: C:\Websites\tradetracker\web.config Line: 54
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.MSXML, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' could not be loaded.
Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433
MSXML 8
Bruce L
All-Star
18102 Points
2841 Posts
Re: Cannot load file or assembly Microsoft.MSXML version 8.0.0.0
Nov 04, 2008 03:52 AM|LINK
This error means that asp.net cannot find the assmebly Microsoft.MSXML in neither the application's bin directory nor the GAC.
I don't believe this assembly is a standard .NET assembly. I think you may need to upload the dll into the application bin directory.
http://www.discountASP.NET
amarzi
Member
7 Points
5 Posts
Re: Cannot load file or assembly Microsoft.MSXML version 8.0.0.0
Nov 04, 2008 01:46 PM|LINK
Makes sense, but what version would this be? Below is a link to a list of Microsoft.MSXML versions and there is no 8.0.0.0. Is it possible that any 8.x version would be suitable?
http://support.microsoft.com/kb/269238Thomas Sun –...
All-Star
64981 Points
5621 Posts
Re: Cannot load file or assembly Microsoft.MSXML version 8.0.0.0
Nov 06, 2008 07:41 AM|LINK
Hi,
It seems that the server doesn't have the installation of Microsoft Document Explorer 2005. This assembly's FileVersion should be "8.0.50727.42".
To resolve this issue, you can try to locate the dexplore.msi file from "C:\Program Files\Common Files\Microsoft Shared\Help 8\Microsoft Document Explorer 2005" (from machine that has Visual Studio 2005), and then install it in the server.
I look forward to hearing from you.
Microsoft Online Community Support
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.
amarzi
Member
7 Points
5 Posts
Re: Cannot load file or assembly Microsoft.MSXML version 8.0.0.0
Nov 06, 2008 02:10 PM|LINK
Thank you for your reply. We had to take a different architectural direction because we were wasting too much time on this. Although it seems like your solution should have worked. Thanks for the help.