Setup failed to determine whether a supported version of Microsoft Outlook is installed : Outlook Client Setup failed for Outlook 2010

You may receive the below mentioned error while installing Outlook Client for Outlook 2010 as shown below.

The Fix is as below:




Close the setup windows from the taskbar, and it will prompt for confirmation to close. Click "Yes". (Shown as below)

The setup will continue.




Once setup completed you could open the outlook and configure it. 


Remember the Rollup update 7 is most recommended and then you could install any latest Rollup updates. Currently Rollup Update 12 is available. 


Also Some Other posts says about setting registry key and it did not worked for me. The setting as below



[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRMClient]
"IgnoreChecks"=dword:00000001

New Microsoft Dynamics CRM VPC available for download for partners

The download requires partner authentication. 


It has 
Windows 2003 which expires on august 2011
Microsoft Dynamics CRM 4.0 with Rollup 11
Office 2010
SharePoint
Demo tools etc...

CRM 4 July 2010 VPC.part01.exe	https://mbs.microsoft.com/fileexchange/?fileID=d4dc2e74-56ea-42a6-9138-3ac6cd6e1aad
CRM 4 July 2010 VPC.part02.rar	https://mbs.microsoft.com/fileexchange/?fileID=b893ee03-1a0c-4aec-8da9-6586a8efc9d0
CRM 4 July 2010 VPC.part03.rar	https://mbs.microsoft.com/fileexchange/?fileID=42fce544-1b14-4e1a-a477-e04c56c51c39
CRM 4 July 2010 VPC.part04.rar	https://mbs.microsoft.com/fileexchange/?fileID=385a09e6-d9ae-4991-bfb5-b028102e80d8

Validate a user name and password against active directory

The below code uses .Net framework 3.5 and is a console application


using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.DirectoryServices.AccountManagement;

namespace MyConsoleApplication
{
    class Program
    {
        static void Main(string[] args)
        {
            // create a "principal context" - e.g. your domain (could be machine, too)
            using (PrincipalContext pc = new PrincipalContext(ContextType.Domain, "contoso"))
            {
                // validate the credentials
                bool isValid = pc.ValidateCredentials("brianc", "pass@word1");
                Console.WriteLine(isValid.ToString());
                Console.ReadLine();
            }
        }
    }
}

MS Dynamics CRM.... There is an error in XML document. Invalid Operation Exception

When using SDK dlls for retrieve records i got the error saying "Invalid Operation Exception" with inner exception "There is an error in XML document".

The error was repeating for all request like web service, crm grid xml etc...

The solution was:

I found the CRM record details in some attribute with � within the string value. This character is against the XML document standards. so remove the value and save it...

The unanswered question is Why Microsoft left this as bug

Another possibility of the same error is : If we are not set the ReturnDynamicEntity = True for the query expression, will get error "There is an error in XML document".

XMLHTTPRequest will fail if internet connection uses proxy server.

The XMLHTTPRequest will fail if you have proxy configured. we need use WinHttp instead of it. Refer the code pasted below.

if(sProxyIPAddress.Length != 0)
{
WinHttp.WinHttpRequest xmlhttp = new WinHttp.WinHttpRequest();
//Accessing the web service using Get method
xmlhttp.Open("GET", "http://www.webservicex.net/CurrencyConvertor.asmx/ConversionRate?FromCurrency=" + sfromCurrencyCode + "&ToCurrency=" + sBaseCurrency , null);
xmlhttp.SetProxy(2,sProxyIPAddress, null);
xmlhttp.Send(null);
xmlresult.loadXML(xmlhttp.ResponseText);
}
else
{
//Accessing the web service using Get method
MSXML2.XMLHTTP30Class xmlhttp = new MSXML2.XMLHTTP30Class();
xmlhttp.open("GET", "http://www.webservicex.net/CurrencyConvertor.asmx/ConversionRate?FromCurrency=" + sfromCurrencyCode + "&ToCurrency=" + sBaseCurrency, false, null, null);
xmlhttp.send(null);
xmlresult.loadXML(xmlhttp.responseText);
}

How to call parent windows functions in Java Scripts

The following code will help you to call the parent windows javascript methods. It will work if the window is not closed.

window.opener.parent.CommonConvertPreferredCurrency()

Eg:

if(!window.opener.closed) {
if(window.opener.parent.CommonConvertPreferredCurrency) { window.opener.parent.CommonConvertPreferredCurrency(); } }

Global Javascript function for MS CRM Entities

Normally it is not possible to write Global/Common Javascript methods for CRM entities, becuase it allowing to write inside the event scripts.

To obtain this write the javascript function inside the entity event handler and assign to a global variable. Then the variable will be act as function.

To declare a variable as global just declare without "var" in statements.

Eg:

CommonConvertPreferredCurrency = ConvertPreferredCurrency;

function ConvertCurrencySymbol(currencySymbol){
// to do
}

The global functions can be called in same form anywhere in same form. However it will not work as .js files

Javascript will fail/ throw error if last line is commented

CRM Javascript will stop running or throw error if the last line of code(Exact last line) is commneted.

This is becuase CRM Entity Edit form saves the script by adding closing backet to end of the script without adding carrige return before to it. So that the added closing bracket will come as commented.

OnChange event of MS CRM lookup control

The OnChange of the MS CRM Lookup control will not fire, if previously any lookup attribute has been filled by selecting the value from the Form Assistant.

A solution for this isuue is to call FireOnChange in OnSave by checking it.


I have found this problem only for the LookUp Controls

Outlook appointment non- invitee attendies will not be saved in CRM

The appointment which have non-inviting attendies, the name will not be saved in the MS CRM Appointments. After the synchrnisation happens between MS CRM outlook, the non-invities will be erased.

To overcome this I suggest to wite a windows service which fetch the list of Exchange server appointment attanedies and saves in MS CRM appointment invitees. This has to happen in intervals less than MS CRM synchronisation intervals.

The defect of the above approach is the disability to save as non-invitee itself.