Re: org.jawin.COMException: 8002802b: Element not found.

David Rhodes <[email protected]>
Newsgroups gmane.comp.windows.devel.jawin
Message-ID <[email protected]>
You should use regsvr32.exe -u <olddllname.dll> to unregister the old one
and regsvr32 <newdllname.dll> on the new one. It's a bit of a hack to just
replace the file. I wouldn't recommend it.

At this point, it might be a good idea to search the registry for any
reference to qbxmlrd.dll and delete the keys..then start over.

dave

-----Original Message-----
From: Roy Collins [mailto:[email protected]]
Sent: Thursday, March 31, 2005 12:01 PM
To: [email protected]
Subject: Re: [JAWIN] org.jawin.COMException: 8002802b: Element not found.

I finally solved the problem.  It was a version conflict.  I do not
understand how COM entries work in the registry at all.  I searched for the
GUID of the library that was created from typebrowser which lead me to
another CLSID or GUID... whichever it is.  Under the referenced ID was a
folder tree for 2 different versions.  There was an old version listed for
an old quickbooks version that had been uninstalled a while ago.  Anyway in
common files the QBXMLRP.dll was referenced and was an old version.  I ran
typebrowser on the new QBXMLRD.dll file in the program directory, the only
one I knew existed at the time.  Somehow windows chooses a path when
referencing that GUID but it followed a path back to the old version of
file.  I replaced the version of the old file with the new version and now
everything works.  So old registry entries pointing to an old file are
followed when referencing a newer installed file with a new GUID. I have no
idea how it all works.  How can I be sure removing an application removes
these old entries?  I have a feeling that if  this program is used on a
computer that had ever upgrade then it will have the same problem.  Well
thanks to everyone for all the help.  I truely appreciate it.

<snip>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.