After updating Infopath Browser Enabled Form Template, new field became read-only on old/existing forms

Problem: After updating Infopath Browser Enabled Form, the newly added field became read-only on old forms. If you open the existing forms in notepad, you will not see your new field in the xml.

Soln: This happens when you choose 'Do nothing' on version upgrade. To make the fields selectable/editable, republish the form with the following options. Go to Tools -> Form Options -> Versioning -> On version upgrade, choose "Automatically upgrade existing forms". Once the new version is uploaded in Central Admin, go back to your old forms, you should see your new fields as editable.

Moss - importing profiles from Active Directory

While trying to configure import user profiles from AD, encountered the following warning message:

'This directory service setting has not been validated because the current user is not authenticated to the directory. It may be a valid setting. Do you want to save this directory service connection setting?'

This could happen when in configurating the Import Connection, 'Use Default Account' is selected. This default account refers to the application pool account. If this is a local account user profiles cannot be imported. In the Authentication Information section in the bottom of the Edit Connection page, click 'Specify Account' and specify a domain account. Go back to the 'User Profiles and Properties' page and 'Start full import'.

Message: Cannot open log for source 'ExceptionManagerInternalException'. You may not have write access.

Message: Cannot open log for source 'ExceptionManagerInternalException'. You may not have write access.

Came across this message when trying to write to the event log using Microsoft.ApplicationBlocks.ExceptionManagement.dll in the Infopath (IFS) form codebehind. However, if you are an administrator of the box (web server where this is running on), you won't have a problem writing to the event log. Since we cannot grant all users administrator rights, that option is out.

Solution: by default, a sharepoint site uses impersonation. Use the SPSecurity class:

SPSecurity.RunWithElevatedPrivileges(delegate()
{
ExceptionManager.Publish(ex);

});

As a side note, do not mess with the existing settings in web.config of the sharepoint site. Taking out impersonate="true" messed up our BDC and other things....

Infopath Submit Error

Came across this error today while trying to use ExceptionManager to write to the eventlog:
Message: The form cannot be submitted to the following location: http://d7014yleimoss:2007/Investments/10118.xml. There is a problem with the Web server. Make sure the Web server exists, try again later or contact the Web server administrator.

Happily this didn't take me time to figure out.

Solution: The user role was created to be able to submit the form, BUT the user was not granted 'contribute' access to to the Forms Library 'Investments'. Grant the logon user the 'contribute' access in the Forms Library Settings and the form submitted successfully.

BDC authentication RevertToSelf

Recently there is a case where we need to use BDC to generate some views from our sqlserver database. We have a database with a sqlserver serviceID. However, we do not want to setup SSO. One of the developers is supposed to provide a solution to this view since I was on vacation. He used Passthrough as the AuthenticationMode in the BDC application definition. However, that is not a viable solution considering we have no access to the database and we do NOT want to keep adding IDs to the database, adds an extra step to maintenance. (It actually pisses me off to some extend since he didn't even bother to figure out a workable solution for our particular environment.)

Anyhoo, using RevertToSelf would work in our particular case. In the RevertToSelf scenario, the BDC will be using the application pool account to reach out to the database. We only have to give access to this one account in the database. Saved us a lot of time. In addition to putting this ID for access to the database, this ID also needs access to the BDC Entity on the SSP page (SSP > Business Data Catalog Applications > YourLOBSystem > YourView > Manage Permissions). Also noticed that other domain IDs that try to access the BDC list webpart also needs to have their IDs here! ...

This form template is browser-compatible, but it cannot be browser-enabled on the selected site !!!

Get error:
This form template is browser-compatible, but it cannot be browser-enabled on the selected site
when trying to published a full-trust infopath browser enabled form.

Soln: must activate Office SharePoint Server Enterprise Site Collection features
(Features such as the business data catalog, forms services, and Excel Services, included in the Office SharePoint Server Enterprise License) from the Central Admin site also, besides the site feature and site collection that you are publishing to

Central Administration > Site Settings > Site Features
activate Office SharePoint Server Enterprise Site Collection features

MOSS AAM - Need Redirecting to alternate url (but same page!)

Problem: We had a moss site of , added alternative access mapping (AAM) so collegues of other countries can view the pages. The changed in url messed up the infopath browser-enabled forms that was on the old site. errors could be prompting you to save the form or saying the form has been closed. However, forms will open and work well on the new url.


Soln: To prevent users from using the old url, we had to do a redirect like so on the same default.aspx page:

<asp:Content ContentPlaceHolderId="PlaceHolderAdditionalPageHead" runat="server">
<META Name="CollaborationServer" Content="SharePoint Team Web Site">

<script type="text/javascript">

//add here:
var url = window.location.href;
if(url.search(/servername:1234/i) != -1){
window.location="http://servername.co.com:1234/default.aspx";
}
//
var navBarHelpOverrideKey = "wssmain";
</script>


</asp:Content>

access denied going to newly created sharepoint (moss) site

Encountered this problem:

Created a moss site using host header (http://intranet.machinename.com), created site collection of / and /sites/hr. tried to logon but kept getting prompted. no matter what id used, access always denied.

Soln: to to Central Administration, Application Management, Authentication Providers, click on zone, make sure IIS Authentication Settings is set to NTLM (was kerberos!).

Infopath form upload, stuck on installing, upgrading etc

Problem: This is a new issue that suddently happened after I published a form with databinding issues (trying to use dynamic links). After going to 'Manage Form Templates' in Central Administration, Application Management, the form is stucked on upgrading. Checked Operations -> Timer job definitions, and status, try to delete the job and redo to no avail.

Solution: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm.exe -o execadmsvcjobs

Infopath browser form - test from client, doesn't see properties show up on sharepoint list/library

Problem: when testing from the client with the infopath form, submitting to sharepoint library, only see the name column, none of the properties seemed to be populated/promoted. On the repair documents/relink documents page, shows up as the 'Form' content type instead of the 'Investment' content type. (Investment is the content type of the published form.)

Soln: Steps to resolve: check the site content type, make sure the default content type is Investment, not Form. Reset IIS, resubmit from client should see the properties.