• Resolve: Issue Accessing Data Source
• Resolve: SQL Credential Issue
• Resolve: Business Data Connectivity Metadata Store Is Currently Unavailable
• Resolve: Picker Issue Obtaining Business Data
• Resolve: Modifying a List/Library Page Makes the Ribbon Disappear
• Resolve: SharePoint Designer Task List Creation Error
• Resolve: VSTA Required Issue
This chapter explores various form issues that may arise during your SharePoint form development and suggests possible resolutions. It is suggested to browse through all the troubleshooting chapters to become aware of potential pitfalls.
This is one of the most common errors messages to receive, as shown in Figure 22.1, and means a problem exists with the data connection or data source itself.
Figure 22.1. Any issue with a data connection produces this error.
You can take several troubleshooting steps, as follows:
From Central Administration, follow these steps:
Figure 22.3. Checking the Allow Embedded SQL Authentication option resolves the exception error.
Figure 22.4. When the Business Data Connectivity Service is not started, you will receive this message in SharePoint Designer.
The Business Data Connectivity Service is probably not started on the server and therefore needs to be started. To do this, follow these steps:
Figure 22.5. Clicking the Start link starts the Business Data Connectivity Service.
When you use an external item picker on a SharePoint form, the control is configured to connect to the data source through SharePoint. Therefore, when attempting to preview the form, you receive a message in the picker dialog, as shown in Figure 22.6.
Figure 22.6. Previewing an external item picker produces this error when configured to connect through SharePoint.
You need to publish the form to SharePoint and test the connection there because the control is configured to connect through SharePoint itself.
The List/Library ribbon is contextual based on the current objects on the page. By default, only the List or Library web part exists and therefore the ribbon appears. When you modify a list or library page, the context is changed, as shown in Figure 22.7.
Figure 22.7. Modifying the page causes the ribbon to disappear.
Once the List or Library web part on the page is selected, the ribbon is displayed accordingly, as shown in Figure 22.8.
Figure 22.8. Selecting the List web part on the page produces the List ribbon.
When you are creating a new task, such as a to-do item, SharePoint Designer generates a content type with the name you enter. Therefore, if you attempt to use the same name, a message appears as shown in Figure 22.9.
Figure 22.9. Entering a task name that was already used produces this message.
If the original content type is not being used by another workflow or process, remove the content type from your site and attempt to create the task item again. Otherwise, provide a different name for the task.
To produce code within your form, you need to have VSTA installed on your machine. This is not installed automatically during the Office 2010 installation (or InfoPath 2010 installation). You will receive the error shown in Figure 22.10 if you do not have VSTA.
Figure 22.10. Not having VSTA installed produces this message when attempting to create code in your form.
To resolve this issue, follow these steps:
Figure 22.11. Changing the Visual Studio Tools for Applications to Run from My Computer installs the necessary files.
Sometimes just installing VSTA does not resolve the issue, especially on a virtual machine running a Windows Server product. A surefire way to allow VSTA to run is to select the Microsoft Office drop-down menu and select Run All from My Computer.
When a form is deployed as a content type either directly or through InfoPath Forms Services but then the form is removed or deactivated from the site collection, the content type still exists.
Because the content type still exists, when you attempt to create a new document using the form content type, SharePoint cannot find the form template. The error shown in Figure 22.12 is produced.
Figure 22.12. Removing a form template from InfoPath Forms Services produces this error when attempting to create a new instance.
If the form should no longer be used, make sure you remove the content type from SharePoint so that there is no reference to the deleted form. If the form is still being used, redeploy the form or make sure the form is activated on the site collection.
When your form needs to execute code and the security setting is not configured, you receive an error message similar to Figure 22.13.
Figure 22.13. Not setting a form’s security to Full Trust produces this security exception.
To resolve this issue, follow these steps:
18.223.206.225