InfoPath Dev

We have an InfoPath form with qRules that works fine on existing clients. But, qRules fail to load when the same form is opened on a new Windows 7 client that is imaged from a PC that was never used in our environment before. I didn't get any error as it has both .NET 3.5 and .NET 4.5.1 installed, with .NET Programmability support enabled for InfoPath. I am attaching screenshots of InfoPath form views displaying QdabraRules data source values, from both clients.

qRules loaded on Client 1:

qRules not loaded on Client 2:  

What should I check into to narrow down and fix the issue?

Can someone please throw light on it?

Thanks!

Wow - I haven't seen this before - nice job of narrowing things down tho.

Can you try opening the form in design mode on the machine in question and previewing the form? Same results?

I'm going to ask Jim to take a look at this post and chime in with any ideas as well.

Jim suggested this was possibly security settings in Internet Explorer also suggested checking event logs on the machine....

I would also suggest adding custom code to a simple form and trying that on the machine in question (unless you have other forms with custom code that do work as anticipated?). Let me know if you need a form with a few lines of code in it to test with.

Thank you Hilary Stoupa, for looking into this issue.

I got the following error while trying to preview the form in design mode on Client 2.

System.Security.SecurityException
Request failed.
   at Microsoft.Office.InfoPath.MsxmlNavigator.IsValidNode(MsxmlNode test)
   at Microsoft.Office.InfoPath.MsxmlNavigator.MoveToFirstChild()
   at MS.Internal.Xml.XPath.XPathChildIterator.MoveNext()
   at MS.Internal.Xml.XPath.ChildrenQuery.Advance()
   at MS.Internal.Xml.XPath.AttributeQuery.Advance()
   at MS.Internal.Xml.XPath.XPathSelectionIterator.MoveNext()
   at System.Xml.XPath.XPathNavigator.SelectSingleNode(XPathExpression expression)
   at System.Xml.XPath.XPathNavigator.SelectSingleNode(String xpath)
   at Qdabra.Tools.RulesLibrary.Commands.ExecuteCommand()
   at Qdabra.Tools.RulesLibrary.qRulesMain.ExecuteCommand(XmlEventArgs e)
   at Qdabra.Tools.RulesLibrary.FormCode.QdabraRules__Command_Changed(Object sender, XmlEventArgs e)
   at Microsoft.Office.InfoPath.Internal.XmlEventHost.GenericProxy(Object genericDelegate, DataDOMEvent dataDOMEvent, InfoPathEvents type)
   at Microsoft.Office.InfoPath.Internal.XmlEventHost.ChangedProxy(DataDOMEvent dataDOMEvent)
   at Microsoft.Office.Interop.InfoPath.SemiTrust._DataDOMEventSink_SinkHelper.OnAfterChange(DataDOMEvent pDataDOMEvent)

Googling for this error led me to take a shot at upgrading MS Office to the latest service pack.

Client 2 (the machine having the issue) was having the original release [Version:12.0.4518.1014] of Microsoft Office InfoPath 2007. Upgrading it to SP3 [Version:12.0.6606.1000] fixed it.

Thanks again for helping me to narrow down the problem.

Oh, super excellent. Glad you found it, and glad you found a fix - thanks so much for posting!