.NET Framework Bookmark and Share   
 index > 64-Bit .NET Framework Development > SqlXmlCommand object creation throws exception
 

SqlXmlCommand object creation throws exception

Hi
We are testing our 32-bit .NET application on 64-bit environment ( 64-bit AMD Processor + 64 bit Windows 2003 Server + 64 bit .NET Framework + 32-bit Application).
This application uses SqlXml3.0 to fire XPath queries on Database using SqlXmlCommand object.
On the very first line where SqlXmlCommand object gets created, it throws following exception:

Retrieving the COM class factory for component with CLSID {83D0FC3E-8B31-4B35-A1B2-346BA3954513} failed due to the following error: 80040154.

Does anyone has any idea what i can be the cause for this.

Thanks in advance.
Regards
Gagan
Gagan Sharma
I got the solution for this. It requires SQLXML 4.0. After installing SQLXML 4.0 it worked properly.

-Gagan
Gagan Sharma
I got the solution for this. It requires SQLXML 4.0. After installing SQLXML 4.0 it worked properly.

-Gagan
Gagan Sharma

I got it to work when selectingx86 instead of any CPU in the target platform in the C# projectproperties.Perhaps SQLXML 3.0 SP3 only works with 32-bit compiled applications.

If you look at the properties of the reference it says that it was compiled agains .NET FW v1.0.3705. Perhaps you need .NET FW 1.x installed as well.

Cheers

Niklas

NiklasEngfelt

Installing SQLXML 4.0 SP1 was the solution, however I had to change the reference in my .NET application and rebuild it.

Michel

Michel Gerber

You can use google to search for other answers

Custom Search

More Threads

• visual studio 2005 vista 64bit build configuration manager setting and application speed
• CAPICOM for 64 bitness
• Building a 64 bit version of a WPF app that uses windows media player
• clickonce ProcessorArchitecture
• Problem: float +- operators give different results depending on computation order, flags, Win32/x64
• how to do .net performance measures
• TLB Generation for x64 for .NET apps
• SignedCms.ComputeSignature
• NT Framework, .dll
• Marshal.AllocHGlobal() works well in x86 but not in x64.