Archives | December 2009

Below are the screenshots that demonstrate the steps I followed when installing Identity Lifecycle Manager in my lab. Cloned 2008 Server 32 Bit for ILM (Note that I cloned my SharePoint dev server) DCPromo and activate AD role Create ILMService Account Add to domain admins Installed new database server Install ILM Now install metadata services and user provisioning ============================================================================================ Install the Microsoft Identity Integration Server 2003 Resource Tool Kit ===================================================================================...

---

I often have clients ask for examples of Excel Services dashboards.  Below are two screenshots of demo dashboards I developed back in 2008.  The  data is pulled from the Microsoft Dynamics Two Inc. sample database using SQL queries that I authored specifically for these demos. Vendor Dashboard with KPI’s (Click to view full size) Customer Dashboard (Click to view full size)

---

This is the second posting I’ve put together regarding OWSTimer.  In a previous post I had a client who simply pegged the timer by running a batch update against thousands of list items subsequently kicking off thousands of workflows.  In a more recent encounter, one of my clients called me with the OWSTimer again going mad, but for a completely different reason.  Problem OWSTimer.exe taking 100% CPU and/or creating Gigabyte sized log files. Solution Below  are the steps I used to troubleshoot the client’s environment with the actual screenshots.  In the end I believe...

---

Sometimes InfoPath doesn’t allow you to rename your main data source so you are stuck with a name that doesn't necessarily match with the function of the form.  This is very common for those of us that like to use Microsoft’s InfoPath templates as a head start.  For example, a form designed based upon an InfoPath sample may include the "expenseReport" name. This is quite annoying especially when you need to compile the datasource with the "xsd /c" command and the output classname is less than helpful.   Below is the example of a form data source that was created...

---

Problem You are receiving the error similar to the one below when attempting to execute a SharePoint WWF workflow.  ====================================================================================== 11/19/2009 10:52:19.18     w3wp.exe (0x17FC)                          0x157C    Windows SharePoint Services      Workflow Infrastructure          88xr   ...

---