Tag Info

Hot answers tagged

3

You mention that the form is stored in http://sharepoint/travel, but the error mentions the form residing in http://sharepoint/services. It could be that /travel and or /services are (in) different site collections using explicit managed paths. Get a listing of all Site Collections in that Web Application and see if this is the case.


2

Because there is no resources file specified in the call to the some resource key in your web part, SharePoint will look in the default places where you can place your resources files in the following order (given that your language is US-English). You must check all resources strings in your web part also ULS should have some string like "Localized ...


1

There is a lot that can be wrong (particularly when you inherit a farm like this...) Have a look at the Alternate Access Mapping for the Web Applications in question. Are they in the same Zone? Also, looking at the URL it appears that the URL to Forms Server "vshoprspfe" is the part that is tripping up InfoPath. When you Published the form did you use ...


1

Might be a long shot but doesn't take more that a minute to try: If you have the form template (.xsn) that was created by designer you can save it as the source files (in designer 2010 it's in the publish options). Look at the manifest file in notepad and see if you can find a reference to the bad location. If found, change to the correct location and then ...


1

Have a look at troubleshooting the hidden taxonomy list on the site throwing the error. This post mentions that may be the root of the error. You may be able to open some of the documents that use broken values and then save them back. http://share-my-point-2010.blogspot.com/2012/09/error-from-sharepoint-site-index-was.html There is also a repair script ...


1

As is evident from the first error there is an issue with finding assembly information. This may mean you may have changed namespace, class name etc. Normally AlwaysForceInstall = true should take care of the feature which is not uninstalled. Value TRUE specifies that the Feature is installed by force during installation even if the Feature is already ...


1

This is an error that may be caused from corrupted downloaded files, to fix that: Start Run and type regedit Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run folder Delete the Error_access_disabled_by_policy file Restart then try to reinstall the prerequisites wizard.


1

I had a similar problem and found it was due to the request management service routing from my web application host header to the server name. I found the following line in the log file: Request Management Mapping URI from ...


1

From memory the FormServerTemplates library always gets created in the root site of site collections. The path you have for your template http://vshoprspfe/services/FormServerTemplates/TravelAuthority.xsn makes me think /services is a site collection different than the one the travel library sits in (/). You say you have deployed the admin approved form ...



Only top voted, non community-wiki answers of a minimum length are eligible