Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
piotrek_w
Contributor III
Contributor III

Data Gateway - Connector error gRPC server failed to initialize after 3 attempts (DirectAccess-5000)

Hi All,

 

After the upgrade from Data Gateway 1.7.0 to 1.7.3 file connector or ODBC connector are not working any longer.

Connector process started but gRPC server failed to initialize after 3 attempts (DirectAccess-5000)

Environment:

  • Windows Server 2022 Standard
  • Microsoft .Net Runtime 8.0.11
  • Microsoft ASP.NET Core 8.0.11
  • Microsoft Visual C++ 2015-2022 Redistributable
  • Data Gateway 1.7.3

Data Gateway status is Connected. 

For instance: using ODBC connector I can test connection and status is successful. I can then connect to SQL server find data base and table. I can even see the sample data and generate script. Everything seems to work unless I run the script. Then I get an errors:

File connector
(Connector error: Unknown reason:. Connector process started but gRPC server failed to initialize after 3 attempts (DirectAccess-5000)
ODBC connector
Connector error: Unknown reason:. Connector process started but gRPC server failed to initialize after 3 attempts (DirectAccess-1500)

In logs I can see:

[DEBUG] DAG - RequestId=NA ClientSessionId= ReloadId=NA AppId=NA Message=Testing connection to connector on port 49152, attempt 1 of 3. ODBC process (12408)
[ 8] [WARN ] DAG - RequestId=NA ClientSessionId= ReloadId=NA AppId=NA Message=ODBC connector process (12408) with worker process (22624) is not listening on Data Port: 49152 or Management Port: 49153, attempt 1 of 3
[ 8] [DEBUG] DAG - RequestId=NA ClientSessionId= ReloadId=NA AppId=NA Message=Testing connection to connector on port 49152, attempt 2 of 3. ODBC process (12408)
[ 8] [WARN ] DAG - RequestId=NA ClientSessionId= ReloadId=NA AppId=NA Message=ODBC connector process (12408) with worker process (22624) is not listening on Data Port: 49152 or Management Port: 49153, attempt 2 of 3
[ 8] [DEBUG] DAG - RequestId=NA ClientSessionId= ReloadId=NA AppId=NA Message=Testing connection to connector on port 49152, attempt 3 of 3. ODBC process (12408)
[ 8] [WARN ] DAG - RequestId=NA ClientSessionId= ReloadId=NA AppId=NA Message=ODBC connector process (12408) with worker process (22624) is not listening on Data Port: 49152 or Management Port: 49153, attempt 3 of 3
[ 8] [WARN ] DAG - RequestId=NA ClientSessionId= ReloadId=NA AppId=NA Message=ODBC connector process (12408) with worker process (22624) failed readiness check, going to kill it...
[ 8] [INFO ] DAG - RequestId=NA ClientSessionId= ReloadId=NA AppId=NA Message=An old instance of ODBC (12408 started 5 seconds ago) is running, going to kill it...

Is it something related with the port? 

Why File connector and ODBC connector are listening on port 49152? I could not find this port in documentation...

Any ideas? 

Thanks in advance!

 

BR,

Piotr

 

 

 

 

Labels (3)
0 Replies