Archive for the 'MOSS 2007' Category

Pages with PDF Icon prompt for password.

midhun July 8th, 2009

Had a strange issue of the pages on a publishing site with pdf icon in them were prompting for password. If I hit cancel the I see that the only elements which didnot render correctly were the pdf icons which showed up as a white box with a red cross in them.

I copied it from the internet from adobe site

The solution:

Add the local system users group (LOCALMACHINE\Users) to the Access Control List of the file (icon).

Permissions for Icon File

Permissions for Icon File

You might want to check if the file is blocked since it comes from an external source. In such a case unblock and apply.

Unblock File

Unblock File

SharePoint People Search Giving No Results

midhun February 9th, 2009

Recently when moving ‘My sites’/'My Profile’ location from one web application to another, i faced the following issue. The customer needed just the profile pages with ‘My Sites’ functionality turned off.

Problem/Issue : When searching for people using people search no results are shown.

Setup : The my sites location is also on the main portal page. The main portal URL is http://clientmainportalurl and the ‘My Sites’/'My Profile’ URL was http://clientmainportalurl/profile/

Cause : In my case I found the content source ‘Local Office SharePoint Server sites’ did not contain the Shared Service Provider as a start address. This caused the profile pages not to be indexed even though the start address of the main portal was included.

Resolution : Add the SSP (Shared Service Provider) application as the start addresses (with protocol handler http).  If you try to add the url http://clientmainportalurl/profile it will not be accepted because the http://clientmainportalurl/ is already added as a start address.

Microsoft Office InfoPath 2007 – The following URL is not valid

midhun November 17th, 2008

For some strange reason I see that on one of the servers when we try to publish an InfoPath form, it gives the error – The following URL is not valid

InfoPath 2007 - The Following URL is not valid

InfoPath 2007 - The Following URL is not valid

I go into Central Administration -> Application Management -> InfoPath Forms Services and see for any configuration errors, nothing found. As usual I looked on Google if any one had already faced such a problem. I see Firedancer’s blog where the suggested solution was to Stop the System Event Notification Service.  I tried that but no luck.

Services - System Event Notification Service

Services - System Event Notification Service

I stopped the service and tried to publish it but no luck. Then I saw an Anonymous comment in the same site that he moved the Site Collection to the root(/) and he was able to get the publishing work. I realized then that on this particular server we didn’t create a site collection on the root level but have been using the managed path (sites).

So I went ahead and created the site collection at the root path.

Top Level Site Successfully Created

Top Level Site Successfully Created

Now I try the publishing process again. This time the Publishing Wizard goes through and the form is Published.

InfoPath Publishing Wizard

InfoPath Publishing Wizard

InfoPath Publishing Wizard

InfoPath Publishing Wizard

InfoPath Publishing Wizard

InfoPath Publishing Wizard

InfoPath Publishing Wizard

InfoPath Publishing Wizard

InfoPath Publishing Wizard

InfoPath Publishing Wizard

Now to investigate further, I deleted the site collection at the root and then tried the publishing process again. This time too the publishing process went through. I repeated this on another site collection just to confirm the result.

Summary:

  • When you get the error “The following URL is not valid” in InfoPath 2007 when publishing an InfoPath form check if there is a site collection on the root path (/). If there was never a site collection created there and you don’t want a site collection there, just create the site collection, publish the InfoPath form where ever you wanted to publish and delete the site collection at root(/). Going forward there should not be any problems publishing InfoPath forms.