View Edwin Vriethoff's profile on LinkedIn

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

January 29, 2008   11:38


This product requires ASP.NET v2.0I’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

Tags: , , , , , .





InfoPath publishing: The following URL is not valid

November 14, 2007   10:05


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

InfoPath The following URL is not valid

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.

Tags: , , , .









The content expressed in this blog are those of Edwin Vriethoff and do not represent his employer's view in anyway. The contents of this blog has been carefully put together, but Edwin Vriethoff is not responsible in any way for any direct or indirect harm caused by individuals or organizations using the content of this blog in any way.