Metadata contains a reference that cannot be resolved (MSCRM).

[Naveen MSCRM]

Hi Ivan,

I am having issue after moving the SSIS package to production. It is working good in my development and local machine.

Same package and config file is working good in my development machine (via SQL Agent). When I configure the same in Production SQL server, I am getting below error.

Protection level of the package is set to "EncryptAllwithPassword". 

   Code: 0xC002F304

   Source: Premises DFT Dynamics CRM Destination [43]

   Description: An error occurred with the following error message: "Metadata contains a reference that cannot be resolved: 'https://disco.crm4.dynamics.com/XRMServices/2011/Discovery.svc?wsdl'.".

End Error

Error: 2016-02-17 05:54:56.19

   Code: 0xC0047017

   Source: Premises DFT SSIS.Pipeline

   Description: Dynamics CRM Destination failed validation and returned error code 0xC020801C.

End Error

Thanks,

Naveen.

[Ivan Peev]

Hi Naveen,

I suspect you have issues with your firewall. I would recommend you discuss this issue with your admin.

[Naveen MSCRM]

Hi Ivan,

I am able to access MS CRM and Discovery URL from the production machine. I don't see any issues accessing the URLs.

Can you please let me know is there anything that we need to validate?

I have installed .NET Framework 4.5.1 and 4.5.2. 

Installed COZYROC licence.

Thanks,

Naveen.

[Ivan Peev]

Naveen,

When you are accessing the url do you use the exact same user account you use under SQL Job agent?

[Naveen MSCRM]

Hi Ivan,

The SQL Agent Job is running with account. I am able to access MS CRM. The config has common account/service account to access MS CRM. 

SQL Agent Service are running with "Network Service". 

Below is the sample of config node related to CRM:

DeploymentType=Crm2011;ServerHost=disco.crm4.dynamics.com;ServerUser=CRMSu...@naveencrm123.com;Password=xxxxxxxxxx;OrganizationName=ProductionCRM;ServerTimeout=100;RetainSameConnection=True;Compression=False;ConnectionSharing=False;CallerId=;ProxyHost=;ProxyPort=0;ProxyUser=;

Thanks,

Naveen.

[Ivan Peev]

Naveen,

So you are not testing with the same user account. You have to talk with your admin to give permission for the user account you use under SQL Job agent to connect to external servers. The other problem you may have is your DNS server. Either way talking with your admin is the next step.

[Naveen MSCRM]

Thanks Ivan. I will check with our Admin and get back if any help required.