This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

"[System.ComponentModel.Win32Exception] The network path was not found" Error in Job service logs

Hi,

We have configured 2 job servers local and remote. Local job server connects to DB directly whereas Remote job server connects to DB via App server. We have added "SQL processing Server" function to Remote job server and it is able to process sql processes but we are getting below error in job service logs of remote job server.

\REMOTEJOBSERVER1 - VI.JobService.JobComponents.SQLComponent - F7E59028-E716-4CB0-B972-34FBFB7AA141: Errors occurred
[810143] Database error 53: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
[System.Data.SqlClient.SqlException] A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
[System.ComponentModel.Win32Exception] The network path was not found

We are not able to understand this issue as it is processing all the sql processes but throwing this error as well. Please suggest the right way to handle this. Thank you.

  • Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

    Did you verfiy like suggested?

  • this job server is not connected to db directly; it connects to db via app server. Even sql processes are getting executed by this job server. And we verified the instance name and it is correct.

  • What version are you using?

    Just asking, what sense does it make to connect a Job Service for the job transport via the application server, but want to execute direct SQL tasks?

    And, you have to distinguish between the job transfer (reading and writing to the Job Queue) and executing process steps against the database (SQL Components, HandleObjectComponent, ScriptComponent). The connection type used for the latter has to be configured independently from the job server connection.

    I assume you haven't done that and that's why the SQL jobs are trying to contact the SQL Server directly.

    Again, executing SQL tasks via the application server doesn't make any sense at all.

  • We are using version 8.0. Our thought process is to have sql server load balancing on local job server and remote job server. And we have configured remote job server through Designer. 

  • I think you misunderstood me. I am not against load-balancing. But for a remote job server that should execute SQL tasks you need to be able to access the database via the normal SQL connection means. 

    The Job Service is able to load the jobs via the Application Server but for the execution, he needs direct SQL Server access. This is true for all the tasks of the SQL Component and the Delay Component.

    In regards to the configuration of the Job Services. You did create two connection data entries in the Designer, one against an application server and a fallback connection against the database, aren't you?

  • Hi,


    i think it has something to do with DNS..., try to specify FQDN for Data Source in DialogDatabase.ConnectionString 
    for example:

    Data Source=mydbserver.domain.net;Initial Catalog=myidmdb;User ID=myuser;Password=mypassword;Pooling=False

    regards,
    Tarigh