Archive for March, 2011

Download Adobe Reader X (offline installer)

March 22, 2011

Adobe has released Adobe Reader version X and is available for download for Windows, Mac OS X and Android version.

Adobe Reader version X comes with sandbox feature which is only for Windows which will improve the security of PDF reader.This feature will prevent the malicious attacks on the system.

Adobe has further plans to extend the sandbox feature to “read-only activities” so that the user’s sensitive and important informations and data are protected against the malicious attacks.

The new Protected Mode security feature is there by default in new Adobe Reader X , it blocks attempts by infected PDFs to write and execute code and prevents any file from doing any registry changes.

Download Adobe Reader X from the official website.

You can also download Adobe Reader X Offline


hMailServer free POP3 Server for Microsoft Windows Server 2008

March 21, 2011

hMailServer is a free e-mail server for Microsoft Windows. It’s used by Internet service providers, companies, governments, schools and enthusiasts in all parts of the world.

It supports the common e-mail protocols (IMAP, SMTP and POP3) and can easily be integrated with many existing web mail systems. It has flexible score-based spam protection and can attach to your virus scanner to scan all incoming and outgoing email.

Microsoft Dynamics CRM 2011 Technical Training Webcasts

March 18, 2011

We are happy to announce the following on-demand webcasts are posted on the MPN PLC and are ready for viewing. The webcasts were created by Microsoft Partner Technical Services and will help get you ready for the new product release.

 Descriptions of each webcast can be found on PartnerSource (sign in needed)

 Webcast topics (MPN sign in needed): 

CRM 4.0 Login failes ‘key expired’

March 16, 2011

On our CRM 4.0 Dev environment we experienced the following behaviour:

When opening CRM this message appeared:

The key specified to compute a hash value is expired, only active keys are valid.  Expired Key : CrmKey…

After searching on the machine I found that the Async service did not run, I started it but restarting the Async service (full name Microsoft CRM Asynchronous Processing Service) didn’t fix it until I did an IISRESET, and this solved the issue.

There is also an alternative solution.

On the server (remote dektop) do the following “C:\Program Files\Microsoft Dynamics CRM\Tools >Microsoft.Crm.Tools.WRPCKeyRenewal.exe /R”

Sample Data in CRM 2011

March 15, 2011

In the new release of Microsoft Dynamics CRM 2011 there is a built in mechanism to import sample data into your system. This will undoubtedly be a blessing to a lot of folks (sales folks running demos, consultants who want to show system customizations prior to a data migration, etc) who have had to rely on less than ‘ideal’ ways of getting sample data in a system.

Until now, we have had 3 options for bringing sample data into our systems:

1.Manually add sample data (time consuming, boring and inefficient)
2.Create CSV file(s) of sample data and use the built-in Import Tool (can be tricky for a non-technical user.)
3.Download the ‘Dynamics CRM 4.0 Sample Data’ extension from Microsoft (contains a set of CSV files of data and an XML data map. Requires use of the DATA MIGRATION MANAGER. Does not work with CRM Online)
While there are numerous options available for importing sample data, each of the above options has various drawbacks that many have found limiting. These limitations have given rise to the new SAMPLE DATA feature that is present in Microsoft Dynamics CRM 2011.


A utility that can be ran from the CRM website that automatically populates sample data into your system without use of the DMM or Import tools.

What Data is Created?

When executed, the sample data feature creates:

14 Accounts
14 Contacts (related to the above Accounts)
7 Opportunities (related to the above Accounts)
10 Cases (related to the above Accounts)
10 Leads
1 Sales Goal (and Metric)
8 Campaigns
24 Activities (due dates are based on when the sample data was imported; creates a mix of overdue and upcoming activities)
Note: All of the above records will be assigned to the user who started the Sample Data import process. Also, each record will have (sample) appended to the ‘name’ of the record

How Do I Get This Sample Data In My System?

The best part about the built-in sample data in CRM 2011 is that it is easily brought into the system by clicking one button! No CSV files or XML map files! No need to install the Data Migration Manager!

1.Navigate to Settings > Data Management > Sample Data
2.When Sample Data is clicked, the following screen will display. Simply click the ‘Import Sample Data’ button and the import process will begin (after a few seconds)!

How do I remove the Sample Data?

Removing the sample data is as easy as adding it (no need for manual deletion via Advanced Find!). To remove the data, navigate to the Sample Data section again and click the ‘Remove Sample Data’ button. The process will start automatically and will remove all the sample data in the system.

Will the sample data import tool populate my custom fields?

Unfortunately the Sample Data tool will not populate data into your custom fields. You will still need to manually add data into any custom fields.

The sample data tool loads ‘basic’ information for each record type (name, addresses, phone numbers, email addresses, etc).

Shared Services Administration: Error Access is Denied

March 14, 2011

If you was using a domain admin account and still ran into this error. According to the MSDN forums, the resolution is as follows:

Central Administration >> Application Management >> Policy for Web Application >> Add Users >> Select the Web Application (All Zones) >> Web Application >> (Add the user) >> Full Control >> Finish

Additionally, you may also need to perform the following once you have permissions: SharedServices1 >> “User Profiles and My Sites” >> “Personalization Services Permissions”

Update Rollup 16 for Microsoft Dynamics CRM 4.0

March 11, 2011

The Microsoft Dynamics CRM Sustained Engineering (SE) team released Microsoft Dynamics CRM 4.0 Update Rollup 16 on Thursday, March 10, 2011.

The links below will take you to the necessary information about Update Rollup 16.

General details about Update Rollup 16

Update Rollup 16 is cumulative. However, the Update Rollup 16 CRM Client and Data Migration Client packages require Update Rollup 7 to be installed. For all other CRM components, you do not need to install any previous Update Rollups prior to Update Rollup 16.

The Update Rollup 16 download contains updates for the 40 supported Language Packs. Prior to installing the Update Rollup 16 Language Pack, you must install the original Language Pack.  

  • If you have Language Packs installed, you should
  1. Download the Update Rollup 16 Language Pack
  2. Install the Update Rollup 16 Language Pack
  3. De-provision the Language Pack
  4. Re-provision the Language Pack

Information about how to avoid reboots when installing the CRM Outlook Client can be found in the Update Rollup 4 blog posting.  

The Update Rollup 16 Client can be deployed before the server is upgraded to Update Rollup 16.

Steps to make the Update Rollup 16 Client available via AutoUpdate can be found in the Update Rollup 4 blog posting. The Link and Patch IDs can be found in KB article 2477743.

Each update rollup could have fixes that require manual configuration. Please see the “Hotfixes and updates that you have to enable or configure manually” section in KB article 2477743.

How to get support for Update Rollup 16

For support, please contact Microsoft Product Support. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:;[LN];CNTACTMS.

Note: In special cases, charges ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Microsoft Office SharePoint Server 2007 and 2010 Build Number Version String

March 8, 2011

Microsoft Office SharePoint Server 2007
Build Number Version String
4518 RTM / first release
6219 Service Pack 1
6318 Infrastructure Update
6327 Cumulative Update October 2008
6335 Cumulative Update December 2008
6341 Cumulative Update February 2009
6421 Service Pack 2
6504 Cumulative Update April 2009
6510 Cumulative Update June 2009
6520 Cumulative Update October 2009
6524 Cumulative Update December 2009
6529 Cumulative Update February 2010
6535 Cumulative Update April 2010
6539 Cumulative Update Juni 2010
6545 Cumulative Update August 2010
6548 Cumulative Update October 2010
6550 Cumulative Update December 2010
Microsoft Office SharePoint Server 2010
Build Number Version String
4514 Beta 2
4730 RC1
4755 RTM / official release
5114 Hotfix Update June 2010
5123 Cumulative Update August 2010
5128 Cumulative Update October 2010
5130 Cumulative Update December 2010

Where is SharePoint web.config

March 4, 2011

There is a separate web.config file for each Web Application / IIS Website which is running an instance of SharePoint. For example, if Sharepoint, Central Admin and the MySite host are all running as separate Web applications (different Application pools) on separate IIS sites, there will be a web.config file in the root of the virtual directory for each application. There is also a separate web.config file which contains configuration details for the “_layouts”, “_catalogs”, etc directories of SharePoint sites.

You should not make changes to the web.config file in a production environment, or while in production. Back up your entire SharePoint environment, including all databases prior to commencing any major troubleshooting or configuration changes. You should attempt and test any modifications to the web.config file in a non-production environment which is configured the same as the live environment. Once you are confident the the changes apply the necessary changes if required to the live environment while it is not in use. The IIS Website will automatically reset when the web.config file is saved so changes will be applied immediately. Be sure that you have not left syntax or any other errors in the file before saving changes.

The web.config files are genearally found in the following locations:

  • web.config file in the root folder of each virtual server / IIS Application.

This is the usually the file that contains most of the web configuration of a SharePoint site collection. To display full errors you would need to modify this web.config file. There may be one for each of the SharePoint applications running in some cases (MySites, Multiple Portals or Instances of SharePoint, Central Admin, etc.). If this is the case, you will only need to modify the web.config file which is in the root of the virtual directory for the instance of SharePoint which you using. To find out which directory is used by various SharePoint applications/websites, view the properties of the SharePoint website in IIS and from the “Home Directory” tab, the value in the “Local path” field will take you to the directory where the web.config file is for the specific instance of SharePoint / Application in IIS.

  • web.config file used in Web Part resources for the Global Assembly Cache (GAC)
Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\wpresources
  • web.config configuration file(s) for extending other virtual servers
Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\CONFIG
  • web.config file which defines configuration settings for the /_vti_bin virtual directory
Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\ISAPI
  • web.config file which defines configuration settings for the /_layouts virtual directory
Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\TEMPLATE\LAYOUTS
  • web.config configuration file for Central Administration pages.
Local_Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\TEMPLATE\ADMIN\Locale_ID

SharePoint Web.Config: How to Show Full Errors

March 3, 2011

Enable display of error details and stack trace when an error occurs

Replace the following error messages with a more meaningful description of the cause of the error by disabling custom errors and enabling the track trace to be displayed as well.

An unexpected error has occurred
An error occurred during the processing of…

To display full errors and the stack trace of the error, you need to modify the web.config file for the Web Application which SharePoint is running on. There are a number of web.config files required to configure various components of SharePoint. See notes below for more information about modifying the web.config file to display errors.

Enable Custom Errors: Set the customErrors mode to “Off”

<system.web> …<customErrors mode=”On” />
Change To:
<system.web> …

<customErrors mode=”Off” />

Enable the Call Stack Trace: Set the CallStack value of the SafeMode element to “true”


<SafeMode … CallStack=”false” … >


Change To:

<SafeMode … CallStack=”true” … >


Enable Debugging Mode: Set batch and debug to “true”

Find: <compilation batch=”false” debug=”false”>

Change To: <compilation batch=”true” debug=”true”>

Enable the ASP.NET tracing feature:

Include the following line in the <system.web> element of the web.config file.

<system.web> …

<trace enabled=”true” pageOutput=”true”/>

By default, SharePoint will only display a basic message to users when an error occurs. The message is virtually useless when trying to troubleshoot an issue, so by enabling more descriptive errors to display, including the stack trace which should help you find the cause of the error. You should not make changes to the web.config file in a production environment, or while in production. Back up your entire SharePoint environment, including all databases prior to commencing any major troubleshooting. You should attempt to replicate and resolve the problem in a non-production environment, and apply the necessary changes to the live environment when it is not in production. In many cases, the web.config will not need to be modified in the live environment as the cause of an error will be known after troubleshooting in a production environment.