Devart Forums

All of our scheduled packages were working fine and we suddenly started getting the error below across all of our scheduled SSIS packages when they attempt to run. Our packages are scheduled to run by windows task scheduler and they kick off a batch script that uses dtexec to execute the package. When we run the packages manually through the development environment they work fine. Has anyone run into anything like this before?

Error Description: Devart.Data.BigQuery.BigQueryException (0x80004005): The underlying connection was closed: An unexpected error occurred on a send. ---> Devart.Data.BigQuery.BigQueryException (0x80004005): The underlying connection was closed: An unexpected error occurred on a send.

rjdkey wrote: ↑Thu 03 Jun 2021 20:57When we run the packages manually through the development environment they work fine.

Tell us if it is the same computer or a different one? At first check the network connection on the production computer. Besides, it can be some issues with TLS 1.2 protocol. Have you changed SSL policies recently in your Google account?
https://cloud.google.com/load-balancing ... s-concepts

We were able to resolve the issue by adding a proxy server and port into the Devart Connection manager. It was very strange as the package would run fine as long as you were connect to the virtual machine (VM) that it was running on (through remote desktop). It would run in the SSDT 2017 development environment, it would run when you manually kicked off the batch script (dtexec) that runs the job, and it would even run when task scheduler kicked of the batch script on schedule. As soon as you disconnected from the VM (even if you were still logged into the VM) you would get that error on any jobs that ran after that or any jobs that were in the middle of running. There must be a change in network behavior when you are connected vs. disconnected to the VM that gets resolved when going through the proxy server. Again, all of this was working fine up until a week ago so there must have been some networking change that was implemented. Wanted to get this information into the forums in case anyone else runs into a similar issue.

These are definitely some network issues not related to the Devart provider.

Check the firewall settings on the virtual machine. Check black or white lists of IP-addresses that have access to the Internet. As I understand, the network behavior changes depending on an RDP connection. It is not a normal situation. What type of network connection is used for the virtual machine? Is the virtual machine a member of real network (bridge connection)? Maybe the virtual machine has only NAT or inner virtual network connection?