Edwin Vriethoff » Infopath

This product requires ASP.NET v2.0 to be set to ‘Allow’ in the list of Internet Information Services (IIS) Web Server Extensions

Edwin Vriethoff — Tue, 29 Jan 2008 10:38:10 +0000

I’m currently performing a migration process and during the Moss installation the following error message is presented:

“This product requires ASP.NET v2.0 to be set to ‘Allow’ in the list of Internet Information Services (IIS) Web Server Extensions. If it is not available in the list, re-install ASP.NET v2.0.”

But on my machine Visual Studio 2005 and .NET2 are installed, so that’s a bit strange. Checking out the IIS extensions panel is indeed not showing the v2.0 version.

To solve the issue open your command prompt en navigate to:
%drive%\Windows\Microsoft.NET\Framework\v2.0.nnnnn
where nnnnn is the least significant version number of ASP.NET 2.0.

Now run the following command at the command prompt:
“aspnet_regiis.exe -iru -enable”
and the issue should be fixed.

Source: Office online – Windows SharePoint Services 2.0 IT Documentation

InfoPath publishing: The following URL is not valid

Edwin Vriethoff — Wed, 14 Nov 2007 09:05:02 +0000

After publishing a lot of InfoPath forms, suddenly InfoPath 2007 started to present me with an error:
The following URL is not valid: www.url.com

The error made it completely impossible to publish any document to my SharePoint site. After searching some time on Google I found a few solutions which didn’t work for me:

But the post from Firedancer worked all right.

The solution is to stop the System Event Notification service. It seems to me that it is more a work around as a solution, so after publishing enable the service again.

[update 15-11-2007]
You’ll only have to stop the System Event Notification service for one time. After you published the form resume the service. All new publications will go allright again. I guess that something that went wrong in the SharePoint database gets fixed after the forced publication.

How to quickly edit multiple Web Service urls inside an InfoPath form

Edwin Vriethoff — Sat, 10 Nov 2007 19:06:09 +0000

A good way to communicate with SharePoint from within a InfoPath form is to use Web Services. Normally you will manage the data source type Web Service with the help of the Data Connection Wizard. To investigate the web service you often have to supply the wizard with some example parameters, especially when the web service doesn’t return any result with empty parameters. Providing those parameters can take quite some time if you have to update more as one web service.

One of my current projects included 5 InfoPath forms with each 6 web services. Clicking through the Data Connection Wizard to update the url would take quite some time and I only needed to change the location. My test environment used the same web service as in production, but because of the different server name I had to update the urls to make the InfoPath forms work.

I found some interesting instructions in the InfoPath documentation and I decided to take it to the test. It turned out to be a good and quick way to update the urls. If you are facing the same situation as me follow these steps:

Open your XSN file inside InfoPath
Choose “Save As Source Files…” from the File menu and select a location on your hard disk to store the source files
Open the location on your hard disk with Windows Explorer. You will see all the files that are normally contained in the xsn file. One of these files is called manifest.xsf which contains information about the form like the urls from our web services
Open the manifest.xsf file inside your favorite text editor like Notepad and do a search and replace for the url that needs to be changed
Save the edited manifest.xsf file
Open the manifest.xsf file again but now with InfoPath
Continue to edit your form or publish it again
That’s it! All urls are updated within a single minute

Take in mind that you cannot always use this method. If the structure of your Web Service changed you have to run the Data Connection Wizard again, but for changing only the urls this method will save you quite some time.

InfoPath IXMLDOMDocument: Reference to undeclared namespace prefix

Edwin Vriethoff — Tue, 30 Oct 2007 11:00:49 +0000

By making use of the Microsoft Office Interop libraries it is possible to fill an InfoPath form automatically. This can be useful when you would like to run a large batch of initial settings.

Trying to set a query property in the DOM of a data source I received the error “Reference to undeclared namespace prefix: ‘tns’”. The reason of this error is that the xml contains multiple namespaces and that you have to explicitly define the namespace to use.

By default the DOM property you can access from the XDocument are of the type IXMLDOMDocument. But working with this type, does not allow you to set the required namespace for your selections. To get around the issue convert the IXMLDOMDocument to a IXMLDOMDocument2 which makes it possible to define a “SelectionNamespaces” property. If you fill this property with the required documentElement’s namespace, the xpath selection of your node will succeed and the error is gone.

Below is an example of the Data source’s IXMLDOMDocument2 content (xml) and some demo code to select the required node.

IXMLDOMDocument2 content

dataFormSolution” xmlns:tns=”http://tempuri.org/” xmlns:my=”http://schemas.microsoft.com/office/infopath/2003/myXSD/
2007-09-05T13:53:48″ xmlns:_xdns0=”http://schemas.microsoft.com/office/infopath/2003/
changeTracking” xmlns:soap=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:xsi=”http://www.w3.org/2001/
XMLSchema-instance” xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:diffgr=”urn:schemas-microsoft-com:
xml-diffgram-v1″ xmlns:msdata=”urn:schemas-microsoft-com:xml-msdata”>



   http://portal.site.org/
   Employees

Example code

private static void DemoCode()
{
//Start application and load the xsn file
Application application = new ApplicationClass();
XDocument document = application.XDocuments.NewFromSolution(”c:\test.xsn”);

//Get the XML Document Object Model of the webservice datasource
//and load/convert the type IXMLDOMDocument as IXMLDOMDocument2
IXMLDOMDocument2 docDom = document.DataObjects["WebService_SearchEmployee"].DOM as IXMLDOMDocument2;

//retrieve the namespace and set the SelectionNamespaces property
string tsnNamespace = GetTNSNamespace(docDom);
docDom.setProperty(”SelectionNamespaces”, tsnNamespace);

//Get the required node
IXMLDOMNode nodeEmployeeName = docDom.selectSingleNode(”//tns:name”);
}

private static string GetTNSNamespace(IXMLdocDomument2 xmlDoc)
{
return xmlDoc.documentElement.attributes.getNamedItem(”xmlns:tns”).xml;
}