Working with a client in our Multi-tenant CRM environment who was doing a database migration into CRM and as part of the process, a backup of their Organization_MSCRM database was taken just prior to starting the migration in case it needed to be restored and run a second time. In this case it did, so I restored the database and let the client know he should be good to go. A few hours later I received a call that they were unable to add some new users, they would appear as available when using the...

Worked on a CRM which had a need to limit the users that could be chosen to a specific OU. This should be simple enough with the CRM deployment config tool following these instructions: http://support.microsoft.co... However it did NOT work. The error I got was: Command failed with the following message: The parameter does not start with '-'; The command I used that gave me this error was Microsoft.Crm.DeploymentCon... userorgsettings update -organization:<ORG_NAME> -propertyname:UserRootPath...

When developing for CRM, we like to keep our business login contained within its own class to be shared and used by other parts of the system. Most all of our CRM implementations have other applications accessing CRM in one way or another so this approach works well. This was fairly straight forward wtih the 3.0 callout model, you just had to put them in the same directory with your custom callout (C:\Program Files\Microsoft CRM\Server\bin\assembly\ in most cases) . The way around this is to either...

While performing an update to some code originally written for CRM 3.0 which I was upgrading to 4.0 and using the new 2007 version of the web services, I found myself getting an unusual error during one of the callouts. The code created a new custom entity from the data in an existing entity. This code was orginally written by another party and I"m not sure why they didn't use the mapping features in CRM to do this but it was coded manually. The entity with typecode '8' was not found in the Metadata...

The CRM 4.0 installer has a nice new feature. The ability to get upgraded setup files prior to running the instalation. A nice step forward to hopefully address setup issues which are often present in the first release of the components. Now for my Grip... I've rarely been lucky enough to get it right the first time. Usually I have to run the installer, fix a few things, and repeat until succesful. The problem is that their isn't any 'memory' of the upgraded setup files. If you have to run the installer...

While performing an upgrade from Microsoft Dynamics CRM 3.0 to 4.0, the upgrade installer halted early on with the following error message: Microsoft.Crm.Setup.Server.... failed Turns out that at some point the IIS Admin service was shutdown and disabled. Not sure how this occured since I had been running CRM 3.0 just prior to the install. So if you get unlucky enough to get this message, open up your services and Enable/Restart your IIS admin service. The setup continued without...

Another issue that may be faced when deploying custom .Net applications in the CRM root directory is the following error: 'Microsoft.Crm.WebServices.... Microsoft.Crm.WebServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad36... doesn't exist. You can resolve this one of two ways... 1. Add the following to your applications web.config (not CRM's web.config!) <assemblies> <clear/> <add assembly="*"/> </assemblies>...

Working for a client on an upgrade for 3.0 to 4.0 with an application that was in place under the CRM IIS directory as a virtual directory. Struggled trying to get this to work and respond as it did under 3.0. Basically, the site would work if it was it's own web site, but not as a virtual directory. To make matters worse, the only thing returned when you navigated to the site was a blank page. None of my code was executing and I wasn't getting any type of error message. Tried messing with every...