Find the correct Organization Name in MSCRM 4.0

If you need to find the correct organization name of your ms crm 4.0 deployment, use the following query:

select uniquename from mscrm_config.dbo.organization

This is the name ms crm requires to connect to the correct organization.

Kevin Dosseray

Comments

Post a Comment

Popular posts from this blog

CRM 2011 Outlook Client: "An error occurred when verifying security for the message"

Installed the CRM 2011 Outlook Client today for a customer who had an on-premise installation of the CRM server. Installation went very smoothly (just click "next" a few times), but configuration was another story. At the configuration step where you need to fill in the CRM URL, you can test the connection and there I received an error saying that the CRM server wasn't accessible. I was sure I filled in the correct URL and that I was configuring with the correct user account as I copy/pasted it in a web browser and there it worked just fine. So I looked up the log file of the configuration (C:\Users\user\AppData\Local\Microsoft\MSCRM\Logs\Crm50ClientConfig.txt) and found the following error message in the file: "System.ServiceModel.FaultException: an error occurred when verifying security for the message" After some research I found out this was due to the fact that the CRM server's operating system time wasn't the same as the time settings on th...
Read more

New CRM 2011 VM on PartnerSource

Microsoft released a Virtual Machine for CRM 2011 on PartnerSource. The VM includes CRM 2011, SharePoint, Exchange, Outlook client and XRM scenarios such as portals. Please note that the VM must be run on a 64bit server with Hyper-V. You can download it here: https://mbs.microsoft.com/Cms/Templates/document/General.aspx?NRMODE=Published&NRNODEGUID={060C9677-229D-49E1-9F00-95E56D9F1657}&NRORIGINALURL=/partnersource/deployment/methodology/vpc/MSD_CRM2011VirtualMachine&NRCACHEHINT=Guest&wa=wsignin1.0
Read more

BizTalk Error: The adapter failed to transmit message going to send port

I was doing the following: in my orchestration I was sending a message to a custom WCF service. The message was build dynamically (custom .NET class) and passed to a send port configured for a WCF service. All looked fine (and compiled correctly) until I ran the application: I received the "The adapter failed to transmit message going to send port" error. After some investigation it turned out I received the error because the type of the message I was sending through the send port did not match with the type the WCF expected at the other end. After updating my message with the correct namespace, all worked fine again.
Read more