topic Re: ERROR: CONNECTOR CONNECT ERROR: ERRORSOURCE: MICROSOFT OLE DB DRIVER FOR SQL SERVER, ERRORMSG: LOGIN TIMEOUT EXPIRED in QlikView

ERROR: CONNECTOR CONNECT ERROR: ERRORSOURCE: MICROSOFT OLE DB DRIVER FOR SQL SERVER, ERRORMSG: LOGIN TIMEOUT EXPIRED

Frode — Mon, 26 Jan 2026 18:19:17 GMT

We are running QV 12.40 April 2019 SR3 on a cluster with five servers , two for Distribution Service sharing the load.

I have a problem with one Distribution Server after the Distribution Service stopped yesterday night and when starting it again jobs started failing with the error;

0171 OLEDB CONNECT TO *** (XPassword is ***)
Error: Connector connect error: ErrorSource: Microsoft OLE DB Driver for SQL Server, ErrorMsg: Login timeout expired Execution Failed

When restarting the same job on the other Distribution Server it runs fine. Tried to restart server and services , with the same result. Jobs run fine on the other Distribution server but not on the other.

Any idea of what to look for , or what to do?

/Regards Frode

Re: ERROR: CONNECTOR CONNECT ERROR: ERRORSOURCE: MICROSOFT OLE DB DRIVER FOR SQL SERVER, ERRORMSG: LOGIN TIMEOUT EXPIRED

Vikram_Jayakumar — Fri, 09 Jul 2021 02:23:49 GMT

Hi @Frode

Best place to start troubleshooting would be to check the ProgramData Distribution Service folder for corruption (usually detected when files are not updated)

If you find it to be problematic

- Stop the QlikView Distribution Service
- Rename it to make a backup
- Start again the QlikView Distribution Service and run a test, check if tasks are correctly load balanced by checking the task logs in the QMC.

Hope this helps. Good luck

Re: ERROR: CONNECTOR CONNECT ERROR: ERRORSOURCE: MICROSOFT OLE DB DRIVER FOR SQL SERVER, ERRORMSG: LOGIN TIMEOUT EXPIRED

Frode — Sun, 11 Jul 2021 11:17:51 GMT

Hi!

Thanks for the input , but in the end it turned out to be a network issue.

We have two network cards installed on the Distribution Servers and when restarted it came up with "faulty" IP address.

When we restarted again and "forced" it to use the "old IP" address everything worked fine again.

/Regards Frode