[WebDNA] [BULK] SQL ODBC 00000 Error

This WebDNA talk-list message is from

2019


It keeps the original formatting.
numero = 114544
interpreted = N
texte = 2164 --_000_DF89B680A72D1D49A4CE61BDF2F53CDA48D420AFOCB56oswegoboce_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, So we are working on finally updating our dev environment. As we have not h= eard any word on the new windows version we are moving to 8.5.1 CentOS Serv= er version. Our Apps connect to MSSQL 2017 on a separate windows machine vi= a the SQL tag and ODBC. 95% of the time this works fantastic, but about 5% = of the time we get a SQL:00000 error and the query does not complete. We have not been able to reliably reproduce this error so we are not sure w= hat is causing it. We set up a trace on the ODBC driver to see what SQL was= doing and we found it logged this when the SQL:00000 happened: 1. TCP Provider: Error code 0x102 2. A network-related or instance-specific error has occurred while estab= lishing a connection to SQL Server. 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. 3. Login timeout expired 4. Error: 08003 This is odd to us as the server is always up and the very next SQL command = completes without issue. Haven't found anything of use on the google machin= e for the above errors either. We thought it might be a drop in the connect= ion so we decided to give installing the 'new' MSSQL Linux version to cut t= he network issues out of the equation. Even on the same machine accessing l= ocalhost we see the sporadic SQL:00000 error and the trace gives the above = error each time it fails. If we connect to the same SQL servers on our windows box however, we don't = see the SQL:00000 errors at all and the connection works like a champ. It s= eems this is an issue connecting to MSSQL from Linux via ODBC. Has anyone run into this issue or can point us in the right direction? We r= eally want to use the new version and keep finding road blocks! Thanks! Matt Buske --_000_DF89B680A72D1D49A4CE61BDF2F53CDA48D420AFOCB56oswegoboce_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

 

So we are working on finally updating our dev enviro= nment. As we have not heard any word on the new windows version we are movi= ng to 8.5.1 CentOS Server version. Our Apps connect to MSSQL 2017 on a sepa= rate windows machine via the SQL tag and ODBC. 95% of the time this works fantastic, but about 5% of the time w= e get a SQL:00000 error and the query does not complete.

 

We have not been able to reliably reproduce this err= or so we are not sure what is causing it. We set up a trace on the ODBC dri= ver to see what SQL was doing and we found it logged this when the SQL:0000= 0 happened:

  1. TCP Provider: Error code 0x102
  2. A network-related= or instance-specific error has occurred while establishing a connection to= SQL Server. 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 informat= ion see SQL Server Books Online.
  3. Login timeout expired=
  4. Error: 08003

 

This is odd to us as the server is always up and the= very next SQL command completes without issue. Haven’t found anythin= g of use on the google machine for the above errors either. We thought it m= ight be a drop in the connection so we decided to give installing the ‘new’ MSSQL Linux version to cut the ne= twork issues out of the equation. Even on the same machine accessing localh= ost we see the sporadic SQL:00000 error and the trace gives the above error= each time it fails.

 

If we connect to the same SQL servers on our windows= box however, we don’t see the SQL:00000 errors at all and the connec= tion works like a champ. It seems this is an issue connecting to MSSQL from= Linux via ODBC.

 

Has anyone run into this issue or can point us in th= e right direction? We really want to use the new version and keep finding r= oad blocks!

 

Thanks!

 

Matt Buske

 

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --_000_DF89B680A72D1D49A4CE61BDF2F53CDA48D420AFOCB56oswegoboce_-- . Associated Messages, from the most recent to the oldest:

    
  1. RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error ("Buske, Matthew" 2019)
  2. RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error ("Buske, Matthew" 2019)
  3. RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error ("Terry Nair" 2019)
  4. Re: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error (Donovan Brooke 2019)
  5. RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error ("Buske, Matthew" 2019)
  6. RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error ("Terry Nair" 2019)
  7. RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error ("Buske, Matthew" 2019)
  8. RE: [WebDNA] [BULK] SQL ODBC 00000 Error ("Terry Nair" 2019)
  9. [WebDNA] [BULK] SQL ODBC 00000 Error ("Buske, Matthew" 2019)
2164 --_000_DF89B680A72D1D49A4CE61BDF2F53CDA48D420AFOCB56oswegoboce_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, So we are working on finally updating our dev environment. As we have not h= eard any word on the new windows version we are moving to 8.5.1 CentOS Serv= er version. Our Apps connect to MSSQL 2017 on a separate windows machine vi= a the SQL tag and ODBC. 95% of the time this works fantastic, but about 5% = of the time we get a SQL:00000 error and the query does not complete. We have not been able to reliably reproduce this error so we are not sure w= hat is causing it. We set up a trace on the ODBC driver to see what SQL was= doing and we found it logged this when the SQL:00000 happened: 1. TCP Provider: Error code 0x102 2. A network-related or instance-specific error has occurred while estab= lishing a connection to SQL Server. 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. 3. Login timeout expired 4. Error: 08003 This is odd to us as the server is always up and the very next SQL command = completes without issue. Haven't found anything of use on the google machin= e for the above errors either. We thought it might be a drop in the connect= ion so we decided to give installing the 'new' MSSQL Linux version to cut t= he network issues out of the equation. Even on the same machine accessing l= ocalhost we see the sporadic SQL:00000 error and the trace gives the above = error each time it fails. If we connect to the same SQL servers on our windows box however, we don't = see the SQL:00000 errors at all and the connection works like a champ. It s= eems this is an issue connecting to MSSQL from Linux via ODBC. Has anyone run into this issue or can point us in the right direction? We r= eally want to use the new version and keep finding road blocks! Thanks! Matt Buske --_000_DF89B680A72D1D49A4CE61BDF2F53CDA48D420AFOCB56oswegoboce_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

 

So we are working on finally updating our dev enviro= nment. As we have not heard any word on the new windows version we are movi= ng to 8.5.1 CentOS Server version. Our Apps connect to MSSQL 2017 on a sepa= rate windows machine via the SQL tag and ODBC. 95% of the time this works fantastic, but about 5% of the time w= e get a SQL:00000 error and the query does not complete.

 

We have not been able to reliably reproduce this err= or so we are not sure what is causing it. We set up a trace on the ODBC dri= ver to see what SQL was doing and we found it logged this when the SQL:0000= 0 happened:

  1. TCP Provider: Error code 0x102
  2. A network-related= or instance-specific error has occurred while establishing a connection to= SQL Server. 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 informat= ion see SQL Server Books Online.
  3. Login timeout expired=
  4. Error: 08003

 

This is odd to us as the server is always up and the= very next SQL command completes without issue. Haven’t found anythin= g of use on the google machine for the above errors either. We thought it m= ight be a drop in the connection so we decided to give installing the ‘new’ MSSQL Linux version to cut the ne= twork issues out of the equation. Even on the same machine accessing localh= ost we see the sporadic SQL:00000 error and the trace gives the above error= each time it fails.

 

If we connect to the same SQL servers on our windows= box however, we don’t see the SQL:00000 errors at all and the connec= tion works like a champ. It seems this is an issue connecting to MSSQL from= Linux via ODBC.

 

Has anyone run into this issue or can point us in th= e right direction? We really want to use the new version and keep finding r= oad blocks!

 

Thanks!

 

Matt Buske

 

--------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us --_000_DF89B680A72D1D49A4CE61BDF2F53CDA48D420AFOCB56oswegoboce_-- . "Buske, Matthew"

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

WebCat for Unix?? (1997) Problems with webcat 2.01 for NT (1997) verify online (1997) feature request-- [epoch] (2004) using showpage and showcart commands (1996) Searching multiple fields (1997) two unique banners on one page (1997) Weird problems with [SHOWIF]s (1997) Nested vs conditional (1997) WebSTAR and WebSTAR/SSL with WebCatalog plugins (1998) WebMerchant 3.0? (1998) The Classifieds template set (2003) Online reference (1997) Store Admin Problems (1999) More WebMerch<->MacAuthoriz (1997) [fullPath] bug? (1998) Sku numbers (1997) quantity minimum problem (1997) format_to_days on NT (1997) More Discount Pricing thoughts/efforts (1998)