Giving a laptop to a new user when CRM 4.0 Offline Mode is installed on it

Posted on Leave a commentPosted in crm, sql express

When someome leaves a company, or their laptop is replaced and they get a new laptop, their old laptop goes somewhere. If that somewhere is to a new user and that laptop had an installation of CRM 4.0 configured in Offline Mode installed on it then you will get the following error message when you attempt to run the Configuration Wizard to set up CRM within Outlook for the new user:

Microsoft Dynamics CRM for Outlook with Offline Access has already been configured for a user on this computer. Only one user can be configured per computer for Microsoft Dynamics CRM for Outlook with Offline Access.

This problem is down to the existance of the CRM SQL Server 2005 Express Edition database on that computer. Uninstalling CRM and reinstalling it does not fix the issue, and it would be fixed by removing SQL Server 2005 Express Edition as well – but that is overkill.

All you need to do is to remove the MSCRM_MSDE database. And the easiest way to do this is to use the osql command line tool.

  1. Start > Run > type cmd and press Enter (or type cmd in the search box in Vista/Windows 7).
  2. In the Command Prompt type osql -E -S pcname\CRM and press Enter.
  3. At the number prompt type drop database mscrm_msde and press Enter.
  4. At the next number prompt type go and press Enter.
  5. Finally type quit followed by Enter to exit from osql.

You can now run the CRM 4.0 Configuration Wizard for this new user and choose Offline Mode if you wish – a new database will be created.

Windows 2008, IIS 7.0, 64 bit Server, Terminal Services Web Application and Access Databases

Posted on Leave a commentPosted in 2008, 64 bit, access, iis, oledb, proxy, sql express, windows, x64

This is a long list of pre-requisites, but for your information they do not work together.

  1. If you have a web site that uses Access as its data storage and you migrate that site to an x64 Windows machine then access to the Access MDB file ceases with the following error: “‘Microsoft.Jet.OLEDB.4.0’ provider is not registered on the local machine”.
  2. On IIS 6.0 you need to set the entire web server to 32 bit mode, but on Windows 2008/IIS 7.0 you can set each application pool to 32 or 64 bit. This is a property found under Advanced Settings for the application pool. To gain access to Access MDB files the application pool needs to run in 32 bit mode.
  3. If you have TSWeb installed, then you also have installed the RPC/HTTP proxy component.
  4. If you have the RPC/HTTP proxy component installed any 32 bit application pool will fail upon starting – Error 5139 for Microsoft-Windows-WAS.

So to use Access databases in a legacy web application migrated to Windows 2008, 64 bit, with TSWeb also installed either uninstall TSWeb (and RPC/HTTP proxy), or use a different server, or rewrite the web application to use SQL Express. Supposedly this will be fixed in the first service pack for Windows 2008.

There – it only took 6 hours to work that one out!