Sage CRM 7.0 / 7.1 Http Error 503 Service Unavailable

When you install Sage CRM 7.0 and 7.1 on 2008 R2 or SBS 2011 you might have issue : http error 503 service unavailable.

You will notice the CRM App Pool and the CRMRewriter App pool is stopped.

In the Event log you will have an event id : 2282


The  module DLL ‘C:program filesMicrosoftExchanger ServerV14Binkerbauth.dll’ could not be loaded due to a configuration problem. The current configuration only supports loading images built for a x86 processor architecture.

This might occurred with several DLL.

The kerbauth.dll only work 64 bit.

In the applicationHost.config file for IIS (located in C:WindowsSystem32inetsrvconfig). Stop IIS and edited the file. In the globalModules section, add at the end of the line for kerbauth, and added the precondition=”bitness64” attribute as follows:

<add name=”kerbauth” image=”C:Program FilesMicrosoftExchange ServerV14Binkerbauth.dll” preCondition=”bitness64″ />

Those DLL might need the same :

Both were listed in the <isapiFilters> section of the applicationHost.config file:

<filter name=”Exchange OWA Cookie Authentication ISAPI Filter” path=”C:Program FilesMicrosoftExchange ServerV14ClientAccessowaauthowaauth.dll” enabled=”true” preCondition=”bitness64″ />

<filter name=”Exchange ActiveSync ISAPI Filter” path=”C:Program FilesMicrosoftExchange ServerV14ClientAccesssyncbinAirFilter.dll” enabled=”true” preCondition=”bitness64″ />

Restart IIS and CRM.


Horde Session Error

If you received an error when you open Horde email client :

A fatal error has occurred
Session cookies will not work without a FQDN and with a non-empty cookie domain. Either use a fully qualified domain name like “” instead of “http://example” only, or set the cookie domain in the Horde configuration to an empty value, or enable non-cookie (url-based) sessions in the Horde configuration.
Details have been logged for the administrator.

In the file :

Change the value for $conf[‘session’][‘usr_only_cookies’] = false

Exim Forward email to a specific Route

In the WHM, go to : Exim Configuration Editor, Advanced Editor

In the Router Section Add the 4 lines  (Look at the screen shot)

driver = manualroute
transport = remote_smtp
route_data = ${lookup{$domain}lsearch{/etc/staticroutes}}

After go into SSH and edit the following file :

nano /etc/staticroutes

The structure will be : (domainname: ip)

To ensure Exim will accept the domain to relay edit the following file :

nano /etc/secondarymx

The structure will be : (domainname)



On the new Release of CPANEL, the screen shot is :




Sage CRM 7.0 C, 7.1 and Classic Outlook 2010 Plug In


If you have any issue with the Classic Outlook 2010 Plug in, including installation or doesn’t display in Outlook 2010.

Ensure you have MSXML 4.0 Service Pack 2 installed on your computer

Choose your language

Download the first Link :

MSXML.msi                        (5.0 MB)




Sage CRM 6.2, 7.0, 7.1 Error 500 Another solution!


For users having issue with Sage CRM 6.2 and up. You can follow this instruction :


But, I found another issue this issue is related to the UAC control. DISABLE IT and your CRM will work.

to disable UAC :

Start, run, msconfig, Tools Tab, change UAC setting, Launch, Lower the level to the floor, Apply and Reboot the Server.



SageCRM 7.1 FileIT / File e-mail issue Exchange Integration

For those user having issue with File IT / File E-mail (Server not responding).

For now I will need to investigate more closely with Sage, but if you use your External IP and CRM only with the port 443 (SSL). Open up the port 80 was not an option.  The FileIT is not responding even with Outlook 2007 / 2010.

The only way to have this feature working. I needed to edit the registry (use at your own risk)

In the registry :


Update the 3 registry key below (Don’t touch the other one)

HTTPS : Reg_DWORD-> update it to  : 0x00000000

ServeurName : REG_SZ -> your_internal_server_name (Netbios)

Port : Reg_DWORD -> 0x00000050

Close Registry and Outlook, Re-Open Outlook,

You are good to GO.

FYI : You can only do your file e-mail internally or over VPN.



Sage CRM 7.1 and Exchange Integration issue after upgrading from Exchange 2007 to 2010


After a migration from Exchange 2007 to 2010. The Exchange integration was broken with Sage CRM 7.1

After many hours of research, even if you recreate everything from scratch according to the Sage documentation,  *User, Exchange User Rights, WebServices Testing … reinstallation of CRM, manually edit the integration nothing was working.

To have this re-enable properly, Go to :

Administration -> System behavior -> Turn OFF the option : Use exchange Server Integration.

IIS Reset

Administration -> System behavior -> Turn ON the option : Use exchange Server Integration.

Go to your Exchange Integration, reenter your information according to the Sage CRM documentation and your good to go.

Thanks to Sage Technical Support for not knowing this information ! This gave me an headache for couple  of hours.



IBM Server XSeries Vmware Hypervisor Boot Failed

After Powering up the servers even couples of times. You might have a strange boot up issue with your Hypervisor and and IBM XSeries with an EFI Firmware.

During the last stage of the Boot Sequence you might received :

Hypervisor : Boot Failed or the system loop and restart.

To avoid this behavior, Go to your System Boot Sequence and ADD : Legacy Only as the first Boot Device.

This will force the EFI to turn off and boot as a Normal “Legacy” Bios and Power up again your Hypervisor !

Thanks to the IBM Technical support for this one.

For more information read page 5 (or the whole document): introducing_uefi-compliant_firmware_on_ibm_system_x.1.0