General

Re: QueryInterface for interface IXMLDOMDocument faile

dpinkerton — Wed, 22 Jun 2005 14:43:15 GMT

Hi Patrick -
Yes I have IE installed.

After a day and a half I got nowhere so I opened a ticket with microsoft. Their answer is for me to not automate IP from code, which was my ultimate plan anyway. So I'm taking a different route and not automating IP - just loading a copy of the template xml and starting from there - also I will use system.xml to manipulate the xml, not the infopath xml package.

I'd still like to understand why the other code stopped working - and I have it saved in my class for possible later use.

The error concerns me because I can't say that I won't need to use the infopath packages later in my project - but I guess I will worry about that then.

I will post any more info i find.

Thanks!

Re: QueryInterface for interface IXMLDOMDocument faile

Patrick Halstead — Wed, 22 Jun 2005 02:30:06 GMT

Hi Donna,
I have no idea, but please let us know what you find out. Random question: Do you have Internet Explorer installed?

Patrick Halstead [InfoPath MVP]
InfoPathDev

Re: QueryInterface for interface IXMLDOMDocument faile

dpinkerton — Tue, 21 Jun 2005 16:00:22 GMT

I have completely uninstalled and reinstalled all office 2003 products including infopath - and I am still getting an error. It has changed slightly - it is now:
[System.Runtime.InteropServices.COMException]
Message "Interface not registered"
ErrorCode -2147221163 Integer
Source "Microsoft.Office.Interop.InfoPath"
StackTrace " at Microsoft.Office.Interop.InfoPath.XDocumentClass.get_DOM()
at MMDS.CreateBlankForm.Page_Load(Object sender, EventArgs e) in D:\Inetpub\wwwroot\MMDS\Forms\CreateBlankForm.aspx.vb:line 89" String

It occurs at the same line as previously stated. The other thing that is going on is that these lines:

ipApp = New Microsoft.Office.Interop.InfoPath.ApplicationClass
newXMLForm = ipApp.XDocuments.NewFromSolution("D:\Inetpub\wwwroot\MMDS\OALPrescriptionForm.xsn")

Used to launch InfoPath client on the server - but now the executable opens in the background - I can see it in Task Manager - but no UI opens as before. I'm assuming this is related to my issue. (This is actually kind of a nice feature if I could get it to work this way.)

Does anyone have any ideas at all?

Thanks!

Re: QueryInterface for interface IXMLDOMDocument faile

dpinkerton — Mon, 20 Jun 2005 19:24:46 GMT

Ok - I reinstalled infopath and now I get a different error:

Interface not registered

It's occuring on the DOM.selectSingleNode line below - which is the first time I reference the Microsoft.Office.Interop.InfoPath.Xml dll.

ipApp = New Microsoft.Office.Interop.InfoPath.ApplicationClass
newXMLForm = ipApp.XDocuments.NewFromSolution ("D:\Inetpub\wwwroot\MMDS\OALPrescriptionForm.xsn")

Dim nodeQueryCustomerId As IXMLDOMNode
nodeQueryCustomerId = newXMLForm.DOM.selectSingleNode("//s0:customerId")

As far as I can tell this dll is registered (I scan registry for Microsoft.Office.Interop.InfoPath.Xml and it finds it). I'm a novice at registries and COM so I sure could be missing something.

However in my reference in my vbproj it is not finding this dll in the c:\windows\assembly\GAC like I think it's supposed to.

And when I go to add the reference in vbproj it's not listed under the COM tab ....

Just to reiterate - this code worked all last week but stopped working today after I ran ms updates - AND I uninstalled some other forms packages I had evaluated.

I think I might have screwed up my PIA's when I reinstalled InfoPath, but before that I was getting the other error above, so ....

Can someone please give me a clue? Thanks!

Donna

QueryInterface for interface IXMLDOMDocument faile

dpinkerton — Mon, 20 Jun 2005 16:45:30 GMT

Hello -

I'm suddenly getting an exception where i did not previously get one.

The exception is an InvalidCaseException with the message:
QueryInterface for interface Microsoft.Office.Interop.InfoPath.Xml.IXMLDOMDocument failed.

I got this error after I ran microsoft updates and restarted my machine. Now my app won't run because it throws this error when executing a selectSingleNode:

Dim nodeQueryCustomerId As IXMLDOMNode
nodeQueryCustomerId = newXMLForm.DOM.selectSingleNode("//s0:customerId")

which previously ran for days with no issues. :(

I'm assuming it's the update - but I'm not sure where to look.

Similar google finds (for other windows apps) seem to point towards security/access issue, but nothing has changed for me. The web application runs under my user name right now on my box - and I am an administrator.

Any clues (or outright solutions) would be great!

Thanks
Donna