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.
- Start > Run > type cmd and press Enter (or type cmd in the search box in Vista/Windows 7).
- In the Command Prompt type osql -E -S pcname\CRM and press Enter.
- At the number prompt type drop database mscrm_msde and press Enter.
- At the next number prompt type go and press Enter.
- 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.
Labels: crm, sql express
permalink posted by Brian Reid : 8:53 AM
0 comments 
The Microsoft Dynamics CRM 4.0 Outlook client software, when installed on a terminal server (Microsoft or Citrix) results in the CRM toolbar (which is part of the CRM Outlook Add-in) appearing for all users of the server regardless of whether or not they require the functionality of CRM and irrespective of whether or not they have an account on the CRM system.
The CRM toolbar appears because the Outlook CRM Add-in is loaded, and the add-in is loaded because of the following registry key:
HKCU\Software\Microsoft\Office\Outlook\Addins\crmaddin.addin
Removal of this key from the users' registry stops the add-in appearing under Outlook and stops the add-in loading. There is though one problem with this. At the users login a program runs that recreates this key if it is missing, so that registry key needs to be removed as well. This one is:
HKLM\SOFTWARE\Microsoft\Windows\Current Version\run and the deletion of the MSCRM value (keeping a copy of the data in this value for later).
For all users logging into a computer running the CRM Outlook client would now only get the add-in if the first registry key above exists, so existing CRM users are not affected by this change. Remove the first registry key above from any user who does not use CRM and remove the second key one from the machine and all new users will not get CRM. To give new users the CRM Outlook add-in just run the command line that was the data of the MSCRM registry value (where x is the drive where the CRM software is installed):
x:\program files\microsoft dynamics
crm\client\configwizard\crmforoutlookinstaller.exe /activateaddin
All the above works fine on a standard client, but if you need to do the above on a terminal server then you need to be aware of the shadow copy of the registry keys that terminal servers use to create the initial users profile the first time they login. Because the CRM client is initially installed with the CHANGE USER /INSTALL command active the registry stores a copy of the first registry key above so that it can be applied to users when their profile is created. This registry key needs to be removed as well. You will find this key at:
HKLM\SOFTWARE\Microsoft\Windows NT\Terminal
Server\Install\Software\Microsoft\Office\Outlook\Addins\crmaddin.addin
Note that you do not need to be in change user install mode when you make this change, as we are not uses these changes to affect existing user profiles, just stopping new user profiles from loading the CRM add-in if they do not need to. To change existing user profiles just delete the first registry key above from their profile using a script or manual action or whatever method you prefer. Of course you will need to have done the other steps above before this or the registry key will be recreated the next time they login.
Labels: citrix, crm, terminal server
permalink posted by Brian Reid : 9:43 AM
0 comments
Having recently installed Microsoft Dynamics CRM 3.0 I found that when I wanted to send an email to a contact in the system it failed with the error message "Invalid Visibility".
This error occurs because the code that sends the email does not complete successfully, and in my case because of anti-spam restrictions enabled on the Exchange Server that was being used as the SMTP gateway. The Exchange Server is the organisations only SMTP server, and the corporate firewall allows SMTP inbound and outbound only from this machine. Therefore this Exchange Server has a series of global message filters enabled which where activated on the SMTP virtual server on this machine. One of these anti-spam settings was to reject any mail on the SMTP virtual server that was from the domain name of the company and not authenticated. This stops lots of spam from outside the network that poses as if it where from inside the network, but as the CRM SMTP session was not authenticated, it too fell into this category.
So when CRM tried to send email, it received behind the scenes a 550 error - Sender Denied and so it generated the Invalid Visibility message.
Therefore, in this case, the fix was to authenticate the session, but alternatives exist such as providing a dedicated SMTP virtual server for the CRM application and additional routes outbound through the firewall for SMTP.
In addition to the above, the same error can be caused by other SMTP failures, so if you are getting the same error then open a command prompt on the CRM server and enter the following commands, waiting for an error and then using this to diagnose the reason why CRM 3.0 will not send emails for you (if anonymous email is allowed).
TELNET
smtp_server_name 25
HELO
crm_server_nameMAIL FROM:
email_address@yourdomainRCPT TO:
recipient@externaldomainDATA
TO:
email_address@yourdomainFROM:
recipient@externaldomainSUBJECT: CRM Test
blank line needed hereSome text to act as the body of the message
.
Always finish the email with a full-stop on a line on its ownLabels: crm
permalink posted by Brian Reid : 9:28 AM
2 comments
Archive
March 2005
July 2005
February 2006
May 2006
November 2006
March 2007
May 2007
June 2007
August 2007
April 2008
May 2008
June 2008
September 2008
October 2008
November 2008
January 2009
February 2009
March 2009
April 2009
May 2009
June 2009
July 2009