Archives | February 2009

Problem You want to use the People Picker functionality in InfoPath that SharePoint supports natively. *** Look for the common mistakes section at the bottom of this article *** *** To query additional information about the selected user see this article: http://www.sharepointassist.com/2010/02/02/querying-sharepoint-profile-data-from-an-infopath-form/ *** Solution Follow the steps very carefully below.  It takes a lot of steps to get the contact selector working in InfoPath but once you get it working you shouldn’t have any problems doing it again.  Note that the example below assumes...

---

Problem You have developed an ASP.Net (aspx) web application that you are deploying to the applications (_layouts) folder in Microsoft Office SharePoint Server (MOSS) or Windows SharePoint Services (WSS) or you have developed an ASP.Net (aspx) page that supports a feature such as Association.aspx or Initiation.aspx. When deployed you received the following message(s) Solution Step 1 – Copy the assembly to your SharePoint application’s  bin directory Copy the assembly (dll) to the bin directory of the SharePoint server which is usually located in c:\inetpub\wwwroot\wss\VirtualDirectories\SharePoint80...

---

Problem SharePoint Server Search Service is filling up your C:\ drive by writing its search index to C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications. Explanation When you configure SharePoint one of the first services started is the SharePoint Server Search Service(MOSS 2007). It's a common mistake to allow your shared service provider to utilize the default search index location: C:\Program Files\Microsoft Office Servers\12.0\Data\Office Server\Applications . As your search corpus grows, so does the search index (at roughly 30% of the corpus) eventually the resulting...

---

Problem SQL Server has a broken reference somewhere preventing you from deleting a maintenance job, presumably a job that you created as a maintenance plan. OR (worse yet SQL claims that it isn't "aware" of this job) Solution So the ultimate solution to this problem is to delete the job and all of its references/dependencies/children using a stored procedure (don't worry, I provided the stored procedure below). Step 1 Backup your msdb database. Step 2 Select the sysjobs from the msdb database and copy the job_id of the plan in question. Match up the name of the job with the item...

---

Problem You have a workflow that, on submission of a document, stops because the document is checked out. Solution Step 1 Open your workflow using SharePoint Designer and add a workflow step at the top of your workflow with the name Wait. Step 2 Add a workflow action Wait For Field Change in Current Item Step 3 Update the action to Wait for Checked Out To “to be empty”. Step 4 Test the workflow and verify the wait is executed ...

---