MSXML issues in 64 bit

Discussion in 'Windows 64bit' started by mrjaxon@gmail.com, May 4, 2007.

  1. Guest

    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 MSXML 6 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 present in both the system32 and SysWOW64 directories,
    and the application works fine in a 32bit environment.
     
    , May 4, 2007
    #1
    1. Advertising

  2. Joe Fawcett Guest

    I've no idea but using msxml in .NET is deprecated at best, why not use the
    in-built classes?


    --

    Joe Fawcett (MVP - XML)
    http://joe.fawcett.name

    <> wrote in message
    news:...
    >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 MSXML 6 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 present in both the system32 and SysWOW64 directories,
    > and the application works fine in a 32bit environment.
    >
     
    Joe Fawcett, May 5, 2007
    #2
    1. Advertising

  3. Guest

    On May 5, 4:17 am, "Joe Fawcett" <> wrote:
    > I've no idea but using msxml in .NET is deprecated at best, why not use the
    > in-built classes?
    >
    > --
    >
    > Joe Fawcett (MVP - XML)http://joe.fawcett.name
    >
    > <> wrote in message
    >
    > news:...
    >
    > >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 MSXML 6 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 present in both the system32 and SysWOW64 directories,
    > > and the application works fine in a 32bit environment.


    well at this point moving to system.xml is not an option because all
    of our stylesheets aren't compliant. that is the eventual plan, but
    at this time we need to continue with MSXML 4 or 6.
     
    , May 7, 2007
    #3
  4. Guest

    On May 7, 7:21 am, wrote:
    > On May 5, 4:17 am, "Joe Fawcett" <> wrote:
    >
    > > I've no idea but using msxml in .NET is deprecated at best, why not use the
    > > in-built classes?

    >
    > > --

    >
    > > Joe Fawcett (MVP - XML)http://joe.fawcett.name

    >
    > > <> wrote in message

    >
    > >news:...

    >
    > > >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 MSXML 6 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 present in both the system32 and SysWOW64 directories,
    > > > and the application works fine in a 32bit environment.

    >
    > well at this point moving to system.xml is not an option because all
    > of our stylesheets aren't compliant. that is the eventual plan, but
    > at this time we need to continue with MSXML 4 or 6.


    - don't use MSXML in multi-threaded code. You may need to use
    FreeThreadedDOMDocument. Make sure to stress test before release.
    The MSXML/CLR interop issues are likely to only show up under stress/
    high-load.

    - It has been ages since I played with this, but if I remember
    correctly, the best bet is to use tlbimp.exe to generate an interop
    assembly against the MSXML interfaces. The CoCreate
    MSXML6.DOMDocument (or whatever you need) and cast as the generated
    interop classes.... YMMV

    -derek
     
    , May 8, 2007
    #4
  5. I know its not what you want to hear, but managed interop with MSXML has
    never been supported by the team, or ever recommended as a possible
    solution.

    <> wrote in message
    news:...
    >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 MSXML 6 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 present in both the system32 and SysWOW64 directories,
    > and the application works fine in a 32bit environment.
    >
     
    Alex Krawarik [MSFT], May 8, 2007
    #5
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Jimchip

    Re: MSXML problems

    Jimchip, Jul 17, 2003, in forum: Computer Support
    Replies:
    7
    Views:
    5,999
    Jimchip
    Jul 18, 2003
  2. JD

    Msxml.dll information

    JD, May 22, 2004, in forum: Computer Support
    Replies:
    4
    Views:
    5,236
  3. Andre Da Costa [Extended64]

    Re: Why does MSXML 4.0 not install on 64-bit?

    Andre Da Costa [Extended64], Apr 25, 2006, in forum: Windows 64bit
    Replies:
    3
    Views:
    2,242
    Patrick
    Apr 26, 2006
  4. MSXML issues in 64 bit

    , May 4, 2007, in forum: Windows 64bit
    Replies:
    2
    Views:
    4,520
    Doug Forster
    May 6, 2007
  5. BP
    Replies:
    2
    Views:
    1,175
    PhilSweet
    Dec 19, 2008
Loading...

Share This Page