While working on InfoPath 2007 and Office SharePoint Server 2007 (Beta 2) the other day, I've encountered a strange error. I get the following error whenever I try to publish my InfoPath form:
It says "The following URL is no valid". No matter what URL is entered, the same error will appear. After struggling on it for half-a-day, a colleague of mine finally managed to solve it (Thanx buddy!). The solution is to stop the System Event Notification service.
Everything should work accordingly after that.
Sunday, August 06, 2006
InfoPath.Form.URL.Not.Valid
Subscribe to:
Post Comments (Atom)
12 Code Review(s):
You are great. I 've seen something similar in a previous internal SPS2003 VPC :) but could thought of it.
Thanx, you saved me a lot of time.
Thank you so much! Works like a dream!
Thanks for that. It really does work.
But does anyone know why it works?
This doesn't work for me. Is there some source of how best to use MOSS 2007 and InfoPath. Seems my time could be better used than installing, re-installing, etc.
Thanks
This didn't work for me. What I eventually found worked is when I moved the site to be at the root of the web application. Previously, there was nothing at the root. Good luck to all getting this error.
I was one of the people for whom disabling SANS did not make the error go away. However, having battled the problem and searched the Internet for clues (with little results) I decided to do a little troubleshooting of my own. I won't get into details of how I got at the solution, but here is what immediately worked for me , and hopefully will work for other people.
1. Open regedit.exe, go to "HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\Internet\Server Cache"
2. Delete all subkeys of "Server Cache" key, they are in form of http://xxxxxxx
3. Update "Count" value of "Server Cache", setting it to 0.
4. Close regedit.
5. Close and reopen InfoPath and try publishing the form now.
Thank you very much.... from a MSFT FTE...
Just to add something more-- (and to say thanks, because we also needed to clear the registry cache to fix this).
We found a problem in IIS was responsible for the forms not getting posted. We had an alternate access mapping and the web application lost its http header. The info needed in the header is:
Custom header name:
MicrosoftSharePointTeamServices
Custom header value:
12.0.0.4518
Without this info, apparantly infopath forms doesn't see that the url goes to a sharepoint server, and doesn't think it can publish the form.
thank you verry much Piotr L.
I seem to have broken my ability to publish to SharePoint from InfoPath after installing Visual Studio Extensions for WSS v1.1. I had this same problem with v1.0 but was able to fix by simply uninstalling. This does not work with v1.1.
I am running this on Windows XP. The error that I get is "The following URL is not valid: ..." when trying to publish an InfoPath 2007 form to MOSS 2007 running InfoPath Forms Services. I'm not sure how these are connected.
I've tweaked my registry to allow installation on XP and to try cleaning the Server Cache at "HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\Internet\Server Cache".
Any ideas on how to get InfoPath working again? I no longer need VSE on my local machine.
Stopping the System Event Notification service did nothing for me. A co-worker can publish with no problems. So, I see this as a client issue.
Thanks.
Make sure you have a site at root level. no need to stop system event notification. I have just created site at root level. when we create new site collection at that time do not forget to create root level site, if u create root level site it avoid the error "the following url is not valid" wich will come afterwards.
Hey,
I was having this problem as well and did a fiddler trace and compared a site that was working properly and one that was not
X-Powered-By: ASP.NET
MicrosoftSharePointTeamServices: 12.0.0.6324
Date: Wed, 01 Apr 2009 13:41:17 GMT
the MicrosoftSharePointTeamServices was not appearing the http response header in the non working site, thus rediscovering anonymous jan 2008.
After searching the SP XML config files and other useless 12 entries, I duh..IIS.
To correct the problem go into iis 6/7 and compare the HTTP Response Header entries. You will have the X-Powered-By:Asp.Net but could be missing the MicrosoftSharePointTeamServices entry.
Of course the 12.0.0.6324 is your Hotfix, Service pack level so its probably different for you.
Hope this helps.
Post a Comment