the last run terminated after 1:02 minutes, with the error message highlighted below. Basically, what this means was the SQL server was not accepting connections. The good news is the run did terminate, which will allow the subsequent scheduled run to qui

Question

Connection from chi-monkey

            Designer x64   Started running at 2025-02-07 11:46:55

            Designer x64   Running at a Low Priority.

            Designer x64   This is AMP Engine; running 4 worker threads; memory limit 25.6 GB.

            Input Data (85)            Error SQLDriverConnect: [Microsoft][ODBC Driver 18 for SQL Server]Named Pipes Provider: Could not open a connection to SQL Server [53]. [Microsoft][ODBC Driver 18 for SQL Server]Login timeout expired[Microsoft][ODBC Driver 18 for SQL Server]A network-related or instance-specific error has occurred while establishing a connection to xxxx.database.windows.net Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.

            Filter (77)        0 records were True and 0 were False

            Designer x64   Finished running in 1:02 minutes

Answer 1

The error message means that the instance you were trying to connect to was not reached. There can be many reasons for this, including mistakes like mispelling the server name, the firewall not permitting connection from the address, the server being down due to an issue in the Azure data centre, and the list goes on.

Since you did not say which troubleshooting you have conducted on your own, I will not spend more time in speculation.