On the other hand, this seems to be an issue only in a specific environment. So, we wanted to check the settings on the environment.

Resolution Steps:

1) Made sure all the data connection files have the environment specific List GUIDs, URLs and so on

2) Made sure all the settings related to InfoPath Forms Services under Central Admin are proper: Enable web service proxy, Enable cross-data connections, Disable Anonymous access

3) Made sure all the relevant user profiles are properly imported under SSP

4) Made sure that the authentication Loopbackcheck registry entry is disabled on the WFE server

5) Made sure the alternate access mappings or managed paths are not breaking the web service calls in the interim

None worked. Finally, we have added a host file entry on the WFE server (we have only one WFE in our case) to point to its own IP, did a IIS reset  and it worked.

I have actually found this resolution on one of the blogs:

If the WFE servers are load-balanced, we need to add a host file entry on WFE pointing to its own IP on each of WFE. This is to deal with a known issue with InfoPath browser forms; all browser form calls to SharePoint web services will be made to the current machine that invoked the form.

1) Make sure that the project can be build successfully

2) Make sure all the assembly attributes (name, version, public key token and so on)

3) Try IISreset

4) Make sure ItemEventReceiver and FeatureReceiver class names are different

I will select a user in a people picker or contact selector control (Requestor field) on an InfoPath form and I need the user’s Work Phone number (Work Phone) to populate in another field.

Solution:

1) Create a receive data connection to pull the user profile details using UserProfile.asmx web service provided by SharePoint (GetUserProfleByName method needs to be selected)

2) Create a rule for the “Requestor” field with these Actions:

• Action 1: Set AccountName query field of UserProfile data connection to use the value of the user selected
• Action 2: Query UserProfile data connection
• Action 3: Set WorkPhone returned by the web service to the Work Phone field of the InfoPath form

This should do the trick. You can refer the below article for step by step procedure:

http://claytoncobb.wordpress.com/2009/06/21/userprofileservice-extended/

Please leave a comment in case you liked the post or you need my assistance in the course.

Concept:

I took the route of leveraging SharePoint Out-Of-The-Box versioning functionality instead of developing custom components as such.

As a matter of fact, if we cannot track the changes to the form field values within a InfoPath form then we should try and track it at the destination which is our SharePoint Form Library where these InfoPath forms get deployed.

In simple words…..If not the source, try to track it at the destination.

Steps:

1) Promote all the relevant fields from InfoPath form to SharePoint Form Library so that whatever values are updated get noted down at the SharePoint Form library level

2) Once you have promoted all the fields, you would need to create calculated columns for each of these promoted columns. This is because of the fact that the promoted fields are just dummy columns in the Form Library and we don’t have any control on them. So, we will have to create calculated fields to capture the values of these dummy columns.

3) Enable versioning on the SharePoint Form Library under List Settings -> Advanced Settings/Versioning Settings

This should create version(s) everytime the InfoPath form field values change.

Hope I have been clear on this. Please do not hesitate to leave a comment in case you are not able to understand the above specified steps or you were happy to reach this article.

1. Start -> Run -> regedit

2. Registry Key for server role (HKLM/Software/Microsoft/Shared Tools/Web Server Extensions/12.0/WSS/ServerRole) has to be changed from SingleServer to Application.

NOTE: Please make sure you make a backup of the registry before you make any changes. Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system.

Resolution: Signing the assemblies

1. Generate a KeyFile:  sn -k Remedykey.snk
2. Get the MSIL for the assembly: 

ildasm Remedy.dll /out:Remedy.il
3. Build a new assembly from the MSIL output and your KeyFile

ilasm Remedy.il /dll /key= Remedykey.snk

http://vspug.com/ggill1970/2008/01/18/pulling-in-querystrings-into-a-sharepoint-2007-survey/

http://blogs.msdn.com/visualstudio/archive/2009/10/29/how-to-fix-the-application-cannot-start-error.aspx

Resolution steps:

1. If the WSS is in a server farm, use the “SharePoint Products and Technologies Configuration Wizard” to disconnect the server from the farm.
2. Navigate to Start >Program > Microsoft SQL Server 2005 > Configuration Tools >SQL Server Configuration Manager
3. Navigate to SQL Server 2005 Network Configuration > Protocol for MSSQLSERVER
4. Right click Named Pipes and select Enable (if not enabled)
5. Restart SQL Server
6. Join back the server to server farm using “SharePoint Products and Technologies Configuration Wizard” and follow the wizards

Note: If the installation is a stand-alone installation, then you don’t need to worry about steps 1 & 6

Here are the steps:

1) Navigate to the site settings page of the site
2) Click on “Save site as a template” link
3) Specify title, filename and description. The template would be saved into site template gallery.
4) Navigate to the site template gallery, click on the template and save it to your local desktop
5) Change the file extension to the .cab
6) Extract manifest.xml file
7) Look for the TemplateID
6) This ID tells you which template the site was created in.

Here are the IDs of the site templates provided out of the box. If the template ID is above 1000, then it should be a custom template:

ID 0 = Global, Configuration 0 = Global Template
ID 1 = STS or SharePoint Team Site, Config 0 = Team Site
ID 1, Config 1 = Blank Site
ID 1, Config 2 = Document Workspace
ID 2 = MPS, or Meeting Place Sites, Config 0 = Basic Meeting Workspace
ID 2, Config 1 = Blank Meeting Workspace
ID 2, Config 2 = Decision Meeting Workspace
ID 2, Config 3 = Social Meeting Workspace
ID 2, Config 4 = Multipage Meeting Workspace
ID 3 = Centraladmin, config 0 – Central Admin Site
ID 4 = WIKI, Config 0 = Wiki site
ID5, Config 0 = Blog