Archive for January, 2012

Update Rollup 6 for Microsoft Dynamics CRM 2011 (KB 2600640)

January 25, 2012

Microsoft has released Update Rollup 6. This is a tested, cumulative set of updates for Microsoft Dynamics CRM 2011. It includes performance enhancements that are packaged together for easy deployment.


Microsoft has released Update Rollup 6 for Microsoft Dynamics CRM 2011 Server, Microsoft Dynamics CRM for Microsoft Office Outlook, Microsoft Dynamics CRM 2011 Language Packs, and Microsoft Dynamics CRM 2011 E-mail Router.

For more information about this release, see Microsoft Knowledge Base article 2600640:

Update Rollup 6 is available for Microsoft Dynamics CRM 2011

To maintain parity between the application components of Microsoft Dynamics CRM 2011, this update rollup includes packages for Microsoft Dynamics CRM Server, Microsoft Dynamics CRM for Outlook, Microsoft Dynamics CRM Language Packs, and Microsoft Dynamics CRM E-mail Router.

System requirements

Supported Operating Systems: Windows 7, Windows Server 2008, Windows Vista, Windows XP


  • This update must be installed on a computer that is running Microsoft Dynamics CRM 2011.
  • This update requires Microsoft .NET Framework 4. 


Click the file you want to download from the list below.

Important: The language pack must be installed before you can apply the update rollup for that language pack. Download and install a language pack at Microsoft Dynamics CRM 2011 Language Pack.

To install this update rollup, do one of the following:

  • To start the installation immediately, click Run.
  • To save the download to your computer for installation later, click Save.
  • To cancel the installation, click Cancel.

How to increase SharePoint Upload Size Limit

January 19, 2012

First, increase the Maximum Upload Size for a specific web application.

  • Go to the Central Administration > Application Management > Web Application General Settings
  • Specify the new maximum upload size for your webapplication. For now, we are setting it to 256MB. It could be even set upto 2GB.

Your second step should be to try increasing your default chunk size of large files by trying this STSADM command:

Stsadm.exe –o setproperty –pn large–file–chunk–size –pv   

  • This basically denotes the chunk of data that can be read from SQL Server at one time.
  • The -pv which determines the property value stands for the upload size in bytes (B).
  • It could be set to a maximum of 2GB i.e. (2,147,483,648 B).
  • Do an IISRESET

Next, in web.config file of your particular web application, under the httpRuntime tag in system.web section, increase the upload limit to match the value that you set earlier in central administration. You also need to add the execution timeout to allow more time before the upload operation times out as shown in the example below:

httpRuntime executionTimeout=”300″ maxRequestLength=”256000″


  • 300 means 5 minutes as execution time out
  • 256000 allows uploading 256 MB files.

After the above changes, MOSS would allow files of more than 50 MB to get uploaded easily. Incase you still face challenges, check if the file you are trying to upload, is it a blocked file type e.g. EXE, DLL, etc.

Virtual PC how we can extend the expiration date

January 16, 2012

What happens when a VPC expires?

The VPC normally doesn’t have any special mechanism for the expiration. It is just the normal Windows Server trial software license expiration. Well, this is the case for the Microsoft Dynamics CRM VPCs, though in other Microsoft CTP VPCs like Visual Studio the expiration is on the Visual Studio license.

Normally, when a Dynamics CRM VPC expires what happens is that the machine will keep restarting each one hour, which effectively leaves the VPC totally useless. However, one hour should be enough time to extract all the data and customisations that you need from it. A fast option can be creating a database backup and take it out of the VPC.

How do we know when a VPC Expires?

This actually depends on the trial license expiration date. In the Microsoft Dynamics CRM, the trial license is the Windows Server license so we can just write in command window “winver” and we will see the following screen which provides the expiration date. (Seen on Girish Raja’s Blog)

How Can I extend the VPC expiration?

Extending the VPC expiration involves changing the VPC system date time to avoid reaching the expiration date. This basically will make the VPC useless for production however it can get you some useful extension on the VPC life, specially if you have created a nice demo VPC and you want to keep it while building a new one.

The main problem with changing the VPC system date, is that by default it automatically synchronises with the host system date time, which means that you would need to change the date and time on your machine. Whit the added problem that in a domain joined machine you shouldn’t do that.

However, we can use a little trick on the VPC configuration file to disable the Date Time host synchronisation and then make the VPC travel back in time (remember the VPC cannot be joined to an external VPC domain). In order to do that you just need to open the VMC file and modify or add the host time sync section as shown below.

            <allow type="boolean">true</allow>
 <host_time_sync> <enabled type="boolean">false</enabled> </host_time_sync>


I found this information on Jeff Beehler’s blog, which provides a more details on it, and some links on how you can achieve the same if you are using Virtual Server.


Finding out the expiration of your VPC will depend normally on the trial software license expiration that you are using. In the Microsoft Dynamics CRM Demo VPC case depends on the Windows Server trial expiration date, that you can check using “winver” command. Once the VPC has expired the behaviour will depend on the trial license, the Windows Server case will keep restarting each hour.

It is possible to extend the life of the VPC by changing the date time of the system, although you might need to un-synchronise the VPC clock as shown previously.

Queue Service and Event Service will not start in a virtualized environment

January 13, 2012

The 1053 error message is one that I have come across in many environments where customers have chosen to virtualize Project Server 2007. In short, the Microsoft Office Project Server Queue Service and Event Service fail to start in a timely manner.

As a result, one or both of the services may be stopped and refuse to start. Additionally, errors may be appearing in the event viewer, and sometimes jobs in the Queue Service will not show as processing or may fail completely. 

While this issue has caused headaches for more than few customers,  it is important to note that the issue with the Queue Service and the Event Service not starting in a timely fashion is not related to or caused by Microsoft Project Server. Rather it is due to the nature of virtualization and how the virtualized environments respond.

The good news is there is a fairly straight forward fix.

To date, I have not seen this issue occur on a physical server.

Just as the error message states, the error occurs because the virtual servers are unable to restart the Microsoft Office Project Server Queue Service and Event Service in a timely manner. 

I have used the following steps to successfully resolve the error:

1.       Identify the drive on which ProjectServer was installed.

2.       Open a command prompt on the front-end servers (where the error is occurring) and navigate to the following path:

C: \Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin

Once you have arrived at the bin directory, type the following command:

Psconfig –cmd upgrade –inplace b2b –wait -force

Note: Since C: is the default path for the Project Server installation, C: has been used in this example. If a different drive letter has been used, use that drive letter instead.

This process will finalize any updates prior to implementing the fix.

3.       Once this process has completed, open the registry editor


Once the registry editor has been opened navigate to


Here it will be necessary to create a new DWORD key with the following value:

ServicesPipeTimeout DWORD 60000 (decimal)

Note: 60000 = 60 Seconds.

4.       Next, look for the WaitToKillServiceTimeout key – take note of its current value – and then change the value to 120000

Note: 120000=120 Seconds.

5.       Reboot the Server.

Test by going to Start=>Run=>services.msc and examining the Microsoft Office ProjectServer Queue Service and Event Service. These services should now show as started, and assuming nothing else is wrong with the environment, the Queue Service should now be able to process jobs. The error messages in the event viewer should also have stopped.

Source: Project Server Blogs

Silverlight Organization Chart for SharePoint

January 12, 2012

It is a silverlight Chart control which retrieves data from the SharePoint list.

See Full Screenshot: Screen 1 | Screen 2 | Live Demo with Sample Data


  • Collapse/Expand of Nodes
  • Reset Root anywhere within the Org Chart
  • Root can be permanently set in web part through parameters
  • Optionally draws dotted line based on input data.



Microsoft Public Sector Demo Network

January 1, 2012

Demo Solutions

  • All-Up BI Demo Image X 
  • All-up- BI Demo: Release 9.5 
  • All-Up Sharepoint 2010-10 Demo 
  • Citizen Services Platform 2.0 Demo 
  • Education Solutions for Sharepoint 2010 
  • Federal Demo Solutions (Office Sharepoint 2007 RTM) 
  • Fusion Center Solution Demo 
  • Government Solutions for Sharepoint 2010 
  • Grants Manager Solution Accelerator 
  • Microsoft 311 Citizen Services Solution Accelerator 
  • Microsoft Lync and Polycom Health Demo 
  • Private Cloud Demos with System Center 2012 
  • State and Local Government Demo Solutions (Office Sharepoint 2007 RTM) 
  • TeachTec Educator Desktop Demo