
Overview
Dynamics CRM Connection Manager is SSIS Connection Manager for establishing Dynamics CRM connections. Use the API to build components based on Dynamics CRM Connection Manager.
Setup
Use the Dynamics CRM Connection Manager dialog to specify properties for connecting to Dynamics CRM service.
Server Options
- Edition
-
Specify edition. This property has the options listed in the following table.
Value Description CRM 2011 Connect to CRM 2011 web services. Requires .NET 3.0 and up. CRM 4.0 Connect to CRM 4.0 web services. CRM 3.0 Connect to Dynamics CRM 3.0.
- Deployment
-
Specify deployment type. This property has the options listed in the following table for CRM 2011 edition.
Value Description Office 365 Connect to Office 365 deployed Dynamics CRM. Federation Connect to Federation authenticated Dynamics CRM. Live Connect to Dynamics CRM Live service. This property has the options listed in the following table for CRM 4.0 edition.
Value Description Premise Connect to on-premise Dynamics CRM server. Live Connect to Dynamics CRM Live service. Hosted Connect to hosted Dynamics CRM.
- Server
-
Specify the name or IP address of the Dynamics CRM service. Microsoft-hosted Dynamics CRM uses different address for different regions. The addresses for each region and web service type are listed in the following tables.
-
Office 365 CRM 2011
Value Description disco.crm.dynamics.com North America (default) disco.crm4.dynamics.com EMEA disco.crm5.dynamics.com APAC -
Live CRM 2011
Value Description dev.crm.dynamics.com North America (default) dev.crm4.dynamics.co EMEA dev.crm5.dynamics.com APAC -
Live CRM 4.0
Value Description crm.dynamics.com North America (default) crm4.dynamics.com EMEA crm5.dynamics.com APAC
-
- User name
-
Specify user name to access Dynamics CRM.
- Password
-
Specify password to access Dynamics CRM.
- Organization
-
Select organization name. Note: Not available in CRM 3.0
- Time-out (secs)
-
Specify the number of seconds before timing out session connect. The default value of this property is 100 seconds.
- RetainSameConnection
-
Specify if all clients should use the same connection. This property has the options listed in the following table.
Value Description True All clients use same connection (default). False Every client use different connection.
- CallerId (1.6 SR-1)
-
Specify caller identifier for user impersonation.
- Test Connection
-
Confirm connection manager configuration by clicking Test Connection.
Proxy Options
- Host
-
Specify the name or IP address of the proxy server. If not specified, proxy server is not used.
- Port
-
Specify the port number on the proxy server to use for the connection.
- User name
-
Specify user name to access the proxy server.
- Password
-
Specify password to access the proxy server.
How to trace the web services calls in use?
You can use the regular .NET network tracing facilities to trace the web services calls. Follow these steps to enable tracing:
- Go to DTS\Binn folder and open DtsDebugHost.exe.config file in your favorite text editor.
- Include following settings inside configuration element:
<system.diagnostics> <trace autoflush="true" /> <sources> <source name="System.Net" maxdatasize="1024" tracemode="protocolonly"> <listeners> <add name="MyTraceFile" /> </listeners> </source> </sources> <sharedListeners> <add name="MyTraceFile" type="System.Diagnostics.TextWriterTraceListener" initializeData="c:\System.Net.trace.log" /> </sharedListeners> <switches> <add name="System.Net" value="Verbose" /> </switches> </system.diagnostics>
initializeData attribute controls where the trace log file is saved. Now when you execute a package inside Visual Studio, "c:\System.Net.trace.log" file will contain the web services tracing information. If you want to trace when you execute packages outside Visual Studio, include the settings above in DTExec.exe.config configuration file.
Make sure you comment or remove the tracing settings after you finish testing. Otherwise this may slow down your package execution speed considerably.

