Not able to connect with CRM after 300000 lakhs records from ssis

(0) Share

Report

Posted on by Dhiraj Raghuvanshi

Hi,

I trying to insert the data around 40lakhs from ssis to crm , i am fetching the data from sql using oledb connection and insert the data into crm through Script Component but when ssis insert 3 lakhs records into crm after that i am getting error "An unsecured or incorrectly secured fault was received from the other party".

so i want to know why after inserting 3 lakhs records into crm issue is coming?

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (0)

ram r on at

Like (0)

Report

Could be related to organization service timeout, try setting timeout property in OrganizationServiceProxy.

Was this reply helpful? Yes No
Dhiraj Raghuvanshi 45 on at

Like (0)

Report

I tried this solution but its not working....below is my code

OrganizationServiceProxy Orgproxy = new OrganizationServiceProxy(new Uri(CrmUrl), null, credentials, null);

Orgproxy.Timeout = new TimeSpan(0, 5, 0);

organizationservice = Orgproxy;

Was this reply helpful? Yes No
Gopalan Bhuvanesh 11,401 on at

Like (0)

Report

After how many minutes it is timing out?

Was this reply helpful? Yes No
Dhiraj Raghuvanshi 45 on at

Like (0)

Report

my ssis package taking 5 hours for 3lakhs records to inserting data into crm...so after 5 hours its says "An unsecured or incorrectly secured fault was received from the other party"

Was this reply helpful? Yes No
Gopalan Bhuvanesh 11,401 on at

Like (0)

Report

I am not sure.

If it is exactly 5hours, this could be because of a timeout set for 300minutes, somewhere within the pipeline for the connection or any of the accounts used.

Was this reply helpful? Yes No
Gopalan Bhuvanesh 11,401 on at

Like (0)

Report

Hi

Please refer the following link for different timeout and record number limits:

blogs.msdn.microsoft.com/.../microsoft-dynamics-crm-timeout-settings

community.dynamics.com/.../microsoft-crm-2011-timeouts-and-limits

Was this reply helpful? Yes No
ram r on at

Like (0)

Report

Try something like this,

new TimeSpan(1,0, 0, 0);

Was this reply helpful? Yes No
Suggested answer

prt33k 6,907 on at

Like (0)

Report

Hi Dhiraj,

Whenever running such bulk operation, it is always good to renew proxy if expired.

You can basically do that in the catch block of the code and then continue with process.

However this exception itself can happen because of multiple reason and I dont see timeout to be the issue here.

The issue also happen if there is difference in time on web server and client machine.

Thanks,

PS

Was this reply helpful? Yes No
ashlega 34,477 on at

Like (1)

Report

Hi Dhiraj,

This happens, so you can try to adjust the timeout as have been suggested. I find it very useful , though, when ssis package can simply start from where it failed - this usually requires an order by condition to be added to those fetch queries.. or some sort of tracking mechanism where you would mark processed records, for example.. so you don't have to process them again..

Was this reply helpful? Yes No
Dhiraj Raghuvanshi 45 on at

Like (0)

Report

Hi prt33k ,

Can you give some example how to renew proxy in catch block?

Was this reply helpful? Yes No