InfoPath:Excellent site for InfoPath forms with SharePoint

http://www.bizsupportonline.net/sharepoint-infopath-integration.htm

InfoPath:How to create and deploy an InfoPath browser form template to SharePoint

In this InfoPath video, you learned…

• How to create a SharePoint form library and enable it to display InfoPath browser forms.
• How to check whether InfoPath Forms Services is correctly configured on SharePoint.
• How to create a browser-compatible InfoPath form template.
• How to deploy an InfoPath browser form template to SharePoint.

InfoPath:How to publish an InfoPath 2007 browser form to SharePoint

Learn which actions you have to take both in InfoPath and SharePoint before deploying an InfoPath form template to SharePoint so that it can be opened and/or filled out using a browser.

Problem

You have an InfoPath form template, which you want to open and/or fill it out using a browser.

Solution

There are several actions you have to take both in InfoPath and SharePoint before deploying a form template to SharePoint so that it can be opened and/or filled out using a browser. The solution described in this article is for InfoPath form templates that do not require administrator approval before deployment, that is, they do not contain .NET managed code.

Prerequisites on the Server

1. Windows SharePoint Services 3.0 must be installed.
2. Forms Server 2007 must be installed.
3. InfoPath Forms Services must be activated.

Refer to the SharePoint documentation for guidance on installing and activating InfoPath Forms Services.

Preparing a form template in InfoPath to become a browser-form

An InfoPath form template must be:

1. Browser-compatible
2. Browser-enabled

to be able to be displayed in a browser. You can make a form template browser-compatible by specifying compatibility setting, either up-front, when you first create the form template, or later, when you design the form template.
For more information on InfoPath browser-compatible forms, see

• Introduction to browser-compatible form templates

Setting browser-compatibility up front

When you first open the InfoPath client application you are presented with the Design a Form Template dialog box. You can check the Enable browser-compatible features only checkbox to make an InfoPath form template browser-compatible.
What this means is that the InfoPath designer will only present you with those features of InfoPath that are supported in both the InfoPath editor as well as the browser.
The benefit of choosing this option so early in the design phase is that you will not run the chance of using options that are not available to browser-forms and then have to change your form's design at a later stage because of this.

 

Figure 1. Enabling browser-compatible features when creating a new form template.

For more information on setting browser-compatibility, see

• Specify the compatibility settings for a form template
• Creating InfoPath Form Templates That Work With Forms Services

Setting browser-compatibility afterwards

You can set browser-compatibility after you have designed your form template by going to the Tools menu, and selecting the Form Options menu item to open the Form Options dialog box, and then clicking on the Compatibility category.
If you created a form template that contains features that are incompatible with InfoPath Forms Services, InfoPath will warn you of this and you will have to modify your form template to satisfy the compability requirements for browser-forms. You will have to fix the incompatibilities before proceeding.
If you don't fix the errors, you can still publish the browser-compatible form template to a server running InfoPath Forms Services. However, the form template may not work as intended/desired.
For a list of the features that are and are not supported in browser-forms, see

• Web browser compatibility in InfoPath Forms Services
• InfoPath 2007 features that are unavailable in InfoPath Forms Services
• View server-generated errors and messages in the Design Checker task pane

Tip: Specify browser-compatibility settings up front to avoid having to adjust your form template afterwards.

                                           Figure 2. Enabling browser-compatible features through the Form Options dialog box.

Browser-enabling a form template

Once you have designed your InfoPath form to be browser-compatible and are ready to publish it to SharePoint, you must make it browser-enabled before doing so.
While you can publish a browser-compatible form template to SharePoint without making it browser-enabled, you will not be able to open or fill out this form in a browser until you browser-enable it. This is an important fact to understand.

So how do you browser-enable an InfoPath form template?

Here is where InfoPath and SharePoint have to work together to make it able for you to browser-enable a form:

1. In InfoPath: Ensure that the form template does not contain any errors reported by the Design Checker.
2. In SharePoint: Configure InfoPath Forms Services to Allow users to browser-enable form templates (see figure 3).
3. In InfoPath: Check the Enable this form to be filled out by a browser checkbox when publishing the form template (see figure 4). 

                            Figure 3. Configuring Forms Services in SharePoint Central Administration Application Management

                                               Figure 4. Browser-enabling a form template in the Publishing Wizard.
If you do not configure InfoPath Forms Services before you try to browser-enable a form template, you will be presented with the following message in the Publishing Wizard:
"This form template is browser-compatible, but it cannot be browser-enabled on the selected site."

                           Figure 5. This form template cannot be browser-enabled message in the Publishing Wizard.
 
Warning: If you ignore this message and continue to publish the form template, you will not be able to open or fill out the form using a browser, not even if you configure InfoPath Forms Services after you have published the form template. If you configure Forms Services after you have published a browser-compatible form template, you will have to re-publish the form template from within InfoPath and browser-enable it while re-publishing it.

Note: This was taken from the site http://www.bizsupportonline.net/browserforms/how-to-publish-infoPath-2007-browser-form-to-sharepoint.htm 


 Thanks

Windows:Event ID 7888(SharePoint AD user profile import error)

Issue:

When starting a full or incremental import of Active Directory, either manually or scheduled, the import is successful, but there is an error thrown as soon as the import is initiated. My assumption is the AD import kicks off several simulateous jobs such as updating users "My SharePoint Sites" in the MOSS and Office 2007 environments.
For reference, to kick off a manual import of AD: Central Administration > Shared Services > User Profile and Properties

Event ID 7888

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server General
Event ID: 7888

Description: A runtime exception was detected. Details follow.

Message: Access Denied! Only site admin can access Data Source object from user profile DB.

Technical Details:
System.UnauthorizedAccessException: Access Denied! Only site admin can access Data Source object from user profile DB.
at Microsoft.Office.Server.UserProfiles.SRPSite.AdminCheck(String message)
at Microsoft.Office.Server.UserProfiles.DataSource._LoadDataSourceDef(IDataRecord rec)
at Microsoft.Office.Server.UserProfiles.DataSource._LoadDataSourceDef(String strDSName)
at Microsoft.Office.Server.UserProfiles.DataSource..ctor(SRPSite site, Boolean fAllowEveryoneRead)
at Microsoft.Office.Server.UserProfiles.DataSource..ctor(SRPSite site)
at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.GetDataSource()
at Microsoft.Office.Server.UserProfiles.BDCConnector.RefreshConfiguration(String sspName)

Resolution

1. Navigate to: Central Administration > Operations > Services on Server > Office SharePoint Server Search.
2. In the "Configure Office SharePoint Server Search Service Settings" page, locate the account defined for "Farm Search Service Account" and write down the account name.
   1. For reference, the account defined serves as the account for the AD "Configure Profile Account" access account.
   2. For reference, you can get to AD Profile Account page: Central Administration > Shared Services > User Profile and Properties > Configure Profile Import.
3. Navigate to: Central Administration > Shared Services > Personalization services permissions.
4. On the "Manage Permissions: Shared Service Rights" page, add the account from before (or edit if already exists). The account needs one of the following permissions; I couldn't figure out which one:
   1. Manage user profiles
   2. Manage permissions

I've tested this resolution several times with success.
For reference, I've updated my Farm Search Service Account with the following permissions since the account in question will most likely be accessing the types of content referenced in the permissions at one point or another:

• Manage user profiles
• Manage audiences
• Manage permissions
• Manage usage analytics

Other Thoughts

As with Event ID 2424 I wrote about, I noticed that Event ID 7888 began around the time I installed the following WSS/MOSS security patches which came out prior to the SharePoint SP1 patch:

• WSS Update: kb934525
• MOSS Update: kb937832

I'm going to make the assumption that this error will occur as soon as you install the SharePoint SP1 patch as well.

Conclusion

Somewhere along the line, the WSS/MOSS and/or SharePoint SP1 update(s) are modifying existing permissions… Shame on the updates.
I've read other posts whose resolution is to add the account in question to the local administrators group. Although their resolution may work, the profile import account should not be a server administrator; the administrator role should be reserved for the global MOSS service account admin (the account used to install MOSS) and the configuration account (the account MOSS uses to provision databases and other content that was defined during the MOSS install).
Enjoy!

Good site for SharePoint quiries

Check this out...

http://wssv3faq.mindsharp.com/default.aspx

SharePoint:"Access is denied. Check that the Default Content Access Account has access to this content"

If you have this issue....

Check the steps

The resolution for this was to add the following registry key

1) Click Start, click Run, type regedit, and then click OK.
2) In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3) Right-click Lsa, point to New, and then click DWORD Value.
4) Type DisableLoopbackCheck, and then press ENTER.
5) Right-click DisableLoopbackCheck, and then click Modify.
6) In the Value data box, type 1, and then click OK.
7) Quit Registry Editor, and then restart your computer.

http://support.microsoft.com/kb/896861

SharePoint:The password for the content access account cannot be decrypted because it was stored with different credentials. Re-type the password for the account used to crawl this content.

Issue:

Our search is not working. The crawl log indicates following error: "Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. (The item was deleted because it was either not found or the crawler was denied access to it.)".

Resolution:

ad this problem and solved it by using user@domain.local instead of domain\user when specifying the Default Content Access Account. 

Central Administration --> SSP --> Search Administration | Default Content Access Account.