Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

x64 CF8 cfobject com error while 32 bit dll

New Here ,
Feb 02, 2011 Feb 02, 2011

hi  on a x64 windows x64 CF 8 server when I try to use cfobject  for test code it gives an error

the code is

<cfobject action="connect"  type = "COM"  class = "Microsoft.XMLDOM"  name = "XMLDoc">

at the first run  the error message  is :

c:\ColdFusion8\jintegra\bin\ntvinv.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform

at the second run and after  error change as :

An exception occurred when instantiating a COM object.
The cause of this exception was that: java.lang.RuntimeException: Can not use native code: Initialisation failed.

I saw a bug report

http://www.elliottsprehn.com/cfbugs/bugs/80973

but it was 2009. is there any solution

2.0K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Feb 02, 2011 Feb 02, 2011

Did you vote for the issue?  "Squeaky wheels" etc...

But CF still does not support COM on 64-bit, as far as I know.

So the only solutions I can think of are:

* roll back to a 32-bit CF install.  Bleah

* use a Java-based XML parser instead.

--

Adam

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Feb 03, 2011 Feb 03, 2011

yep I vote bug report.

the biggest disappointment for me. I thought it was solved within 3 years by the  Adobe.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Enthusiast ,
Feb 03, 2011 Feb 03, 2011
LATEST

I don't think this has anything to do with Adobe. It's an

architectural issue on all major OS and the problem comes from that

fact that 32bit libraries cannot be loaded into a process that has an

64bit address space. Period.

--

Mack

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources