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


Sonicwall Port Forwarding (Wan port different from the Internal Port) Enhanced OS

For everyone you have a Sonicwall with enhanced OS and you want to forward a services but the WAN port need to be different from the LAN port. This one is a bit tricky.

Scenario Terminal Services Session

external IP : Port 3387 to Internal IP Port 3389

Create your WAN port Services (if it’s not Standard based on our scenario : 3387)

In the Sonicwall Management :

Go to :

Network -> Services -> Add Service *** Do not add a Services Group ! ***

Name : Custom RDP
Protocol : TCP(6)
Port Range : 3387 – 3387

Create you port forwarding with the Public Server Wizard as usual. (This is more simple all the rules will be created including the NAT)

Go to: Firewall, On the Top, Select Wizards
Select Public Server Wizard, Next
Select the services Type Created previously : Custom RDP, Next
Enter your internal server IP, Next
Enter your Public server IP, Next

Apply, Close

After we will modify the Translation Port manually.

Go To :

Network, Interface, NAT Policies.

Choose you NAT policy :

  • Original Source: Any
  • Translated Source: Original
  • Original Destination: rdp_publicIP
  • Translated Destination: rdp_privateIP
  • Original Service: Custom RDP
  • Translated Service: Terminal Services RDP
  • Inbound Interface: WAN
  • Outbound Interface: Any
  • Comment: Enter a short description
  • Enable NAT Policy: Checked
  • Create a reflective policy: Unchecked

The Translated Service must be change from Original to The internal Server port

Click OK

Test your RDP with you RDP client :

Address : PublicIP:3387

This should be good !


Sage CRM 7.1 : The Dashboard has experienced a problem. Please contact your system administrator

Test the following link :

http://{servername} /sdata/{crminstallname}j/sagecrm/-/$schema

If you received an error : Application Error or Runtime.


Activate all the Web Service Extention CGI / ISAPI

Reinstall the CRMRewriter

Open a command Prompt :

go to your Sage CRM Install Dir

cd tomcatbin

Type :
tomcat6 //DS//crmtomcat6

Reinstall : Program Files / IIS Aliases, Reinstall your Patch (SP1, Patch Number …)




Error VMware Tools after P2V

If you have any issue with VMware Tools after a P2V convertion, you need to verify if the folder redirection is enable, if yes update all those registry key if they have a UNC path :


HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell Folder
Check all the key and update all.

How to Uninstall HP Teaming Software

Click “Start,” then “Control Panel.”

Double-click the “Network Connections” icon. Right-click any one of the Local Area Connection (LAN) icons in the Network Connections window.

Select “Properties” in the menu that pops up. Locate the “HP Network Configuration Utility” option in the list of services and left-click it.

Click the “Uninstall” button that pops up in the Properties window. The HP Teaming Software will begin to remove itself from your system.

Click “Yes” when prompted to restart your computer after the uninstallation has completed.