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

Roy Collins <[email protected]>
Newsgroups gmane.comp.windows.devel.jawin
Message-ID <[email protected]>
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.

----- Original Message -----
From: "Robert Hastings" <[email protected]>
To: <[email protected]>
Sent: Thursday, March 31, 2005 11:59 AM
Subject: Re: [JAWIN] org.jawin.COMException: 8002802b: Element not found.


> To run the typebrowswer I moved the extracted files to a path without any
> spaces in it, cd'd to the typebrowser directory and ran:
>
> java -jar jawinBrowser.jar
>
> To run my JUnit test I added this to the cmd line:
>
> -Djava.library.path=c:\wk\jawin-2.0-alpha1\bin
>
> And had jawin.jar in my classpath.
>
> Hope that helps,
> Robert
>
> -----Original Message-----
> From: Discussion of Java/Win32/COM integration with Jawin
> [mailto:[email protected]] On Behalf Of Roy Collins
> Sent: Wednesday, March 30, 2005 9:10 PM
> To: [email protected]
> Subject: Re: [JAWIN] org.jawin.COMException: 8002802b: Element not found.
>
> What did you have to do to get the 2.0 to work.  What was the java
> command?
> I have set both the classpath and the library path.  Is there anything
> specila that you had to do?
> ----- Original Message -----
> From: "Robert Hastings" <[email protected]>
> To: <[email protected]>
> Sent: Wednesday, March 30, 2005 4:07 PM
> Subject: Re: [JAWIN] org.jawin.COMException: 8002802b: Element not found.
>
>
>> It was the space in the path problem.
>>
>> Anyway, in my confusion I was using the 2.0 alpha.
>>
>> Roy, the 2.0 worked. Also, thanks for the documentation tips. I was able
>> to
>> get them without registering?
>>
>> Robert
>>
>> -----Original Message-----
>> From: Discussion of Java/Win32/COM integration with Jawin
>> [mailto:[email protected]] On Behalf Of Morten Andersen
>> Sent: Wednesday, March 30, 2005 12:59 PM
>> To: [email protected]
>> Subject: Re: [JAWIN] org.jawin.COMException: 8002802b: Element not found.
>>
>> Hi Robert
>>
>> Robert Hastings wrote:
>>> I've downloaded the 1.2alpha and I can't seem to get the typebrowser to
>> find
>>> the stylesheets. Josh? I just ran the typebrowser.jar file is there
>>> something else I need to do?
>>>
>>
>> I may have made a mistake when packaging the 2.0alpha, but I suspect
>> instead that you trying to launch the typebrowser from another folder
>> that the "typebrowser"-folder?
>>
>> E.g. "java -jar typebrowser/jawinBrowser.jar" from the root of your
>> jawin installation folder will NOT work
>> Only "java -jar jawinBrowser.jar" in the typebrowser folder will work.
>>
>> Also we once had some reports of problems with spaces in the path for
>> the typebrowser project? - perhaps this can be the case too?
>>
>> Hope this helps you - best regards
>> Morten
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.