MSXML issues in 64 bit mrjaxon[ at ]gmail.com 5/4/2007 6:32:10 PM MSXML issues in 64 bit I have a C# web application which leverages MSXML that I am trying to migrate to a 64 bit environment. Currently the application is built on the .NET 2.0 Framework and using MSXML 6 (though I had the same issues using version 4). The OS I am running the app on is Windows Server 2003 x64. I am using the x64 version of MSXML6 on the server. My dev environment is Windows XP 32 bit SP2. I have tried to compile the projects for "anycpu" and "x64" with the same results. The Interop.MSXML2.dll was generated by my dev environment automatically when I added the MSXML 6 reference to my project. Essentially whenever the program tries to instantiate a FreeThreadedDOMDocument40, it throws an exception with the message, "Object reference not set to instance of an object". I have tried to use MSXML 4 and 6 (both are installed on the server) with the same results. The line of code is: cXMLDOM = new FreeThreadedDOMDocument40Class(); The program seems to be able to find the Interop.MSXML2.dll (I used FuselogVW.exe to confirm it), but it is still unable to find the necessary DLLs in the system directories. The msxml6.dll and msxml6r.dll are presant in both the system32 and SysWOW64 directories, and the appliation works fine in a 32bit environment.

Re: MSXML issues in 64 bit "Tony Sperling" <tony.sperling[ at ]dbREMOVEmail.dk> 5/4/2007 7:54:51 PM We don't really deal with that many programming issues here, most of it concerns general 'User' issues with the 64bit Editions. I found one link that might lead you further but it was dead just now- try later and see, http://www.dotnet247.com/247reference/a.aspx?u=http://support.microsoft.com/default.aspx?scid=kb or put that exact error message in a searchbox (Google/Yahoo?) there are plenty of hits. Or try a developer NG here, they should know more. Tony. . . <mrjaxon[ at ]gmail.com> wrote in message news:1178303530.370025.51430[ at ]n76g2000hsh.googlegroups.com... [Quoted Text] > MSXML issues in 64 bit > > I have a C# web application which leverages MSXML that I am trying to > migrate to a 64 bit environment. Currently the application is built > on the .NET 2.0 Framework and using MSXML 6 (though I had the same > issues using version 4). The OS I am running the app on is Windows > Server 2003 x64. I am using the x64 version of MSXML6 on the server. > My dev environment is Windows XP 32 bit SP2. I have tried to compile > the projects for "anycpu" and "x64" with the same results. The > Interop.MSXML2.dll was generated by my dev environment automatically > when I added the MSXML 6 reference to my project. > > Essentially whenever the program tries to instantiate a > FreeThreadedDOMDocument40, it throws an exception with the message, > "Object reference not set to instance of an object". I have tried to > use MSXML 4 and 6 (both are installed on the server) with the same > results. The line of code is: > > cXMLDOM = new FreeThreadedDOMDocument40Class(); > > The program seems to be able to find the Interop.MSXML2.dll (I used > FuselogVW.exe to confirm it), but it is still unable to find the > necessary DLLs in the system directories. The msxml6.dll and > msxml6r.dll are presant in both the system32 and SysWOW64 directories, > and the appliation works fine in a 32bit environment. >

Re: MSXML issues in 64 bit "Doug Forster" <nobody[ at ]nowhere,com> 5/6/2007 9:24:23 PM I think you want a FreeThreadedDOMDocument60 FreeThreadedDOMDocument40 points at MSXML4 and there is no 64 bit version of this. Cheers Doug Forster <mrjaxon[ at ]gmail.com> wrote in message news:1178303530.370025.51430[ at ]n76g2000hsh.googlegroups.com... [Quoted Text] > MSXML issues in 64 bit > > I have a C# web application which leverages MSXML that I am trying to > migrate to a 64 bit environment. Currently the application is built > on the .NET 2.0 Framework and using MSXML 6 (though I had the same > issues using version 4). The OS I am running the app on is Windows > Server 2003 x64. I am using the x64 version of MSXML6 on the server. > My dev environment is Windows XP 32 bit SP2. I have tried to compile > the projects for "anycpu" and "x64" with the same results. The > Interop.MSXML2.dll was generated by my dev environment automatically > when I added the MSXML 6 reference to my project. > > Essentially whenever the program tries to instantiate a > FreeThreadedDOMDocument40, it throws an exception with the message, > "Object reference not set to instance of an object". I have tried to > use MSXML 4 and 6 (both are installed on the server) with the same > results. The line of code is: > > cXMLDOM = new FreeThreadedDOMDocument40Class(); > > The program seems to be able to find the Interop.MSXML2.dll (I used > FuselogVW.exe to confirm it), but it is still unable to find the > necessary DLLs in the system directories. The msxml6.dll and > msxml6r.dll are presant in both the system32 and SysWOW64 directories, > and the appliation works fine in a 32bit environment. >