Error when executing the Bulk Insert activity

Hello everyone.

I ask you if anyone in the community has ever encountered my same mistake (see message below) with the ‘Insert Bulk’ activity.

Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated.

I tried various solutions before reaching out to the community. Among the solutions I tested, I also tried to insert the Connect Timeout value in the connection string. Unfortunately without any positive feedback.

Please, anyone who has encountered the same problem as me and was able to solve it, could you help me?

Thank you all in advance, for your time and attention.

Best regards,
Fahd

Hello @Fahad_Mohammed , If you are try to insert Bulk data into database, Kindly check the connection string and test it. Increase the timeout period.

Hello @Gokul_Jayakumar,
I thank you first of all for your reply and for your time

I have tested the connection string several times and tried to put a timeout to 180000 millisecond. But the error persists

Hello @Fahad_Mohammed

Did you tried with a smaller set of data?? Maybe 2 or 3 to check whether the activity is working as expected.

Also to the activity did you modified the timeout?

Thanks

Hi @Fahad_Mohammed,

There may be rows that do not conform to the table rules. Try to add the lines one by one with a for, find the wrong line and analyze it.

Regards,
MY

@Fahad_Mohammed
Try the data contains 5 rows and bulk upade it and see the error occurs or not.
Other wise, read excel data and use for each activity and upload it one by one row using query.

Hi @Fahad_Mohammed ,
I had also faced such issue one time, I think it is some bug or don’t know but, it had been solved after I removed the columns in Build data table and re-entered everything.

Have a nice day!

Thanks & Regards,
Shubham Dutta

sorry i forgot to specify that this error comes out when i try to insert data in the microsoft sql db.

in any case, I tried to make the changes you suggested, unfortunately to no avail