Front-end file system cache problems might occur after a SharePoint configuration database restore.

March 25, 2010   17:41


database_restore_file_cache_problemsLast week I was working at a client who just restored one of their SharePoint environments because of a site error. Everything was functioning like normal, until we discovered a major issue with the InfoPath forms publishing mechanism.

For some of the Infopath forms we received an error while upgrading the form to a newer version. The error statement told us that we could not update the form because of an object in the database with the same ID.

To resolve the error we tried to remove the existing form, but instead of removing the form, SharePoint decided to do the opposite and it tried to start some kind of upgrade process. We had no more options to upgrade or even delete the existing form.

(more…)

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.