Some developers have reported to us this error when they try to publish a new InfoPath template to some of our MOSS 2007 farms. After research on it and try several ways to solve it I think that we have fixed the problem.
If you googling on the net for this error you will find many blogs talking about several ways to solve it making some changes on the server: stop the System Event Notification service, delete SSP and create a new one, if you are using SPS 2003, uninstall .NET 2.0,… etc. Some of them (like the one related to SSP or the .NET 2.0 solution) I can’t understand how they can solve the issue, but in any case if you apply them it is possible that they started a lot of others errors and issues.
A good point to start is to check if your farm has a site in the root. If in your farm all the sites are created under a virtual path such as “/sites/”, InfoPath can’t publish. The best way to do it is trying to access to the root site typing in your Internet Explorer a URL similar to that: https:\\myMossFarm.accenture.com\
If the root site exists, a team site will be displayed (after you enter your credentials and if you are an administrator or have rights to view it). If the site doesn’t appears, you have to request to your administrator to create a root site on the farm following these steps:
-
On the SharePoint Central Administration home page, click the Applications Management tab on the top link bar, then in the SharePoint Web Application Management section, click Create or extend a Web application.
-
On the Create or Extend Web Application page, in the Adding a SharePoint Web Application section, click Create a new Web application.
-
On the Create New Web Application page in the IIS Web Site section, the Create a new IIS web site radio button should be selected. If not, select it.
-
Fill the rest of fields accordingly with your farm configuration and click Create button.
If some developers still receiving the same error, you can try to execute these steps on the developer machine:
-
Open regedit.exe, go to “HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Common\Internet\Server Cache”
-
Delete all subkeys of “Server Cache” key, they are in form of http://xxxxxxx
-
Update “Count” value of “Server Cache”, setting it to 0
-
Close regedit
-
Close and reopen InfoPath and try publishing the form now
Angel Perez Palacios 
Thanks for posting this info. I'm currently having this problem and cannot get it solved. I've published many forms, as recently as just a few weeks ago, to our corporate Sharepoint environment. Suddenly my InfoPath client returns this error message immediately after clicking 'next' when entering the URL. Others are able to publish to the sites using the same form without issues. I've tried the System Event Notification process remedy and just tried the regedit fix above, but both did not resolve the problem. If you've heard of other potential solutions, I would be very interested.
LikeLike
Hi Shawn,
Please, try with this:
Go to Tools > Form Options > Security and Trust and Uncheck “automatically determine security level” and select “Domain” as the level of trust. Click “Ok”.
And then stop the “System Event Notification” service.
Is the error fixed now?
Do you know if your MOSS 2007 server has been updated recently (to SP2 for example)?
LikeLike
I have the same issue and have run through all the scenarios I could find: yes, there is a site coll at root (can successfully publish to root site coll, but no sites in managed path); tried turning off System Event Notification on all WFEs and local machine; deleted server cache on local machine;
We DID just upgrade to WSS sp2. The only thing I can think of is one of the customizations wasn't working and someone on the team might have changed the MicrosoftSharePointTeamServices header #. Is there a way to figure out what that header number should be based on version/hotfix?
LikeLike
Thanks for the additional suggestion Angel – I tested it but still received the invalid URL error. I believe we've moved to SP2. After I first experienced this issue, it seemed to be resolved after I changed my pwd (which is necessary every 60 days). I recently changed my admin acct password and that seems to coincide with this issue recurring. I'm thinking there may be a credential caching conflict with my account on this PC because I'm able to publish from others' PCs and other users are able to login to mine and publish. I'm not sure where such credentials would be cached however, nor how to get them reset.
LikeLike
Update – I just reset my system password and the issue is now resolved. I do not understand why/where/how this resolves the problem, just that I'm able to publish forms again. So if you have any thoughts on how the system credentials and InfoPath publishing are interrelated, I'd be very interested!
Thanks!
-Shawn
LikeLike
Hi Shawn,
The problem could be related with the passwords cache of your PC. Everytime I change my password (every 75 days), I'm open Start –> Run, type the following command and click OK:
rundll32.exe keymgr.dll, KRShowKeyMgr
The “Stored User Names and Passwords” window appears and you can find the entry related to your MOSS site.
My MOSS related entries used to have the format:
Microsoft_WinInet_mySiteURL:443
You can edit it and change your credentials or you can delete it and the next time you access to your MOSS site a new entry will be created for it including your new password.
LikeLike