How to Relink Multiple InfoPath Forms in SharePoint

After our farm migration, we realized that our new domain name and InfoPath didn’t get along.  Our old domain name was a simple http://intranet and all the InfoPath Forms were linked to that name.  After being asked to re-link several thousand forms (clicking one at a time) I started looking around the web for a solution.
Here is what I found:
1)    Open the library. Click Settings –> Form Library Settings –> Relink documents to this Library. Now copy the URL in your address bar.
2)    Open this page in SharePoint Designer. File –> Open –> paste the URL in the File name: field and click Open.
3)    If you don’t see the split screen layout, complete the following steps. Click on View –> Page –> Split
4)    Locate the <FORM> tag within the HTML section of the page and place the following code before the </FORM> tag.
<script type=”text/javascript” language=”javascript”>
function CheckAll(chk)
{
for (i = 0; i < chk.length; i++)
chk[i].checked = true ;
}
</script>
<input type=”button” value=”Check All” onclick=”CheckAll(document.forms.aspnetForm.chkRepair)” >
5) Save, Refresh the page, you should now see a Check All button in the bottom left corner of the page.

Here is what my HTML looks like:

<FORM id=”SubmitRepairDocsForm” method=”POST” action=””>
<INPUT id=”SubmitRepairRedirectList” type=”hidden” name=”SubmitRepairRedirectList” />
<INPUT id=”SubmitRepairRedirectFolder” type=”hidden” name=”SubmitRepairRedirectFolder” />
<INPUT id=”SubmitRepairDocs” type=”hidden” name=”SubmitRepairDocs” />
<SharePoint:FormDigest runat=server ForceRender=”true”/>
<script type=”text/javascript” language=”javascript”>
function CheckAll(chk)
{
for (i = 0; i < chk.length; i++)
chk[i].checked = true ;
}
</script>
<input type=”button” value=”Check All” onclick=”CheckAll(document.aspnetForm.chkRepair)” >

</FORM>

Edit…

If you want to speed up this process, you can also edit the RowLimit property.
Search in the code for RowLimit, by default it’s set to 100, change it to 500.

RowLimit Paged=”TRUE”&gt;500&lt;

An error occurred trying to publish this page on the set schedule. Republish the page with a new date or view the log if the problem continues.

An error occurred trying to publish this page on the set schedule. Republish the page with a new date or view the log if the problem continues.

 Following a recent server migration, we noticed that items were not being published at their designated start times.  Check Central Admin to make sure the following Timer Job Definitions are listed

Central Administration > Operations > Timer Job Definitions

Scheduled Approval 
Scheduled Page Review 
Scheduled Unpublish 
 
Variations Propagate Page Job Definition 
Variations Propagate Site Job Definition 

First, make sure you have the Office SharePoint Server Publishing Feature enabled.

Home > Site Settings > Site Features

Second, if the Feature is enabled, try to Deactivate then Activate.  This should install the Time Jobs in Central Admin.

The My Site of [user name] is scheduled for deletion

The My Site of [user name] is scheduled for deletion. As their manager you are now the temporary owner of their site. This temporary ownership gives you access to the site to copy any business-related information you might need. To access the site use this URL: http://mysite.sharepointed.com/personal/User_Name

After a manger forwarded me this email, I realized we had a configuration problem in our environment.

The problem was we had our LDAP Active Directory (AD) import configured to import all users regardless of their status. So, when the user was deleted from AD the manager received the email and was unable to see the My Site.

To fix the problem I updated the LDAP Search Filter to:

(&(objectCategory=person)(objectClass=user)( !(userAccountControl:1.2.840.113556.1.4.803:=2)))

Now the import will only grab active users from AD. This is allows plenty of time for the manager to look that users My Site before it is deleted.

In my case, we disable users in AD then sixty days later they are deleted from AD. Once deleted from AD the My Site will be deleted from SharePoint following the next FULL import of user profiles.

Where do I edit the LDAP Search Filter?
Here:
Shared Services Administration: [Your SSP Name] > User Profile and Properties > Manage Connections

An unexpected error has occurred.

When trying to access the Shared Service Provider (SSP) I received the following generic error:

An unexpected error has occurred.

Yes, the detail is overwhelming and pointed me directly at the problem.

To allow the .aspx page to show the detail behind the error I had to make a small change to the web.config file.  In my case the web.config file in question was located in the following location:

C:\Inetpub\wwwroot\wss\VirtualDirectories\7788

How did I know where this was located?  If you are in Central Administration and hover over the name of your SSP with your mouse, you should see the path at the bottom of the browser windows.  If not, right click and select Copy Shortcut and paste it into notepad.

Example:

http://sambets:7788/ssp/admin

The 7788 pointed me to the folder that contained the web.config I needed to edit.

Once you have located the needed web.config file make a copy of it. Open the original web.config file and make these two changes.

<SafeMode CallStack=”true“>

<customErrors mode=”Off” />

Save the file.

The page should now show you what is wrong with the file. In my case, there were a ton of “?” all over my web.config. How they got there I will never know.

New button missing from toolbar

I was working in a Document Library and the View was missing the New button to allow for folder creation.

Simple fix.

Site Actions > Edit Page > (the web part you want to fix) click edit > Modify Shared Web Part

In the Web Part properties window click on Edit the current view

Now scroll down to until you see Folders.

Select Show items inside folders  in Folders or Flat: 

 

Done.

This form has been closed.

When trying to create a workflow using Internet Explorer I received the following message:

The server is currently being taken down for maintenance. Check with your system administrator to see when this server is scheduled to come back online.
 
Click Try Again to attempt to load the form again. If this error persists, contact the support team for the Web site.

Click Close to exit this message.

This error was then followed up by another error:

This form has been closed.

We have InfoPath forms installed with workflows that have worked seamlessly, sooooo, I was a little perplexed when i started getting this error.

Answer:

 stsadm.exe -o unquiescefarm

I tried doing the same thing using Central Admin. with no luck

Central Administration > Operations > Quiesce Farm

New SSP

Existing site associations will change

The Web application you have selected to host the SSP administration site and/or My Sites already hosts other content sites.  These content site will automaticcly be associated with the new SSP.

I received this error when trying to replace my intranet site with my new SSP site.

CPU maxed out on the WFE server

if the CPU is maxed out on your SharePoint 2007 server check the Indexer Performance setting in Central Administration.  My setting was set to causing my CPU’s to run at 100% and nine instances of mssdmn.exe to run.  Updating the setting to Reduced brought the CPU’s back to a normal level.

Central Administration > Operations > Services on Server > Office SharePoint Server Search Service Settings

Can’t find the Business Data Catalog

I was doing a fresh install of MOSS and didn’t see the Business Data Catalog section listed in the SSP. The Business Data Catalog wasn’t there because I hadn’t enabled Enterprise Features in the Operations page.

Simple fix, in the Operations page look at the bottom of the page for the Upgrade and Migration section.  In there you will find Enable Enterprise Feature.  Click Enterprise and input your key.

Follow the directions on the screen and you should be ready to go.

Installing SharePoint on Windows Server 2008

To install SharePoint on a Windows Server 2008 machine you will need the SharePoint install that includes SP1.

but… do this first:

http://blogs.technet.com/wbaer/archive/2007/10/30/installing-windows-sharepoint-services-3-0-on-windows-server-2008.aspx

fun?

x86:

http://www.microsoft.com/downloads/details.aspx?FamilyID=ef93e453-75f1-45df-8c6f-4565e8549c2a&DisplayLang=en

x64:

http://www.microsoft.com/downloads/details.aspx?familyid=9FB41E51-CB03-4B47-B89A-396786492CBA&displaylang=en