RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error

This WebDNA talk-list message is from

2019


It keeps the original formatting.
numero = 114548
interpreted = N
texte = 2168 --_000_DF89B680A72D1D49A4CE61BDF2F53CDA48D442A1OCB56oswegoboce_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The tag that has caused us the most problems that we couldn't work around w= as [thisurl]- no matter what we did it wouldn't return a value and was empt= y no matter what page we hit. Matt From: Terry Nair Sent: Friday, April 5, 2019 9:02 AM To: talk@webdna.us Subject: RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error Don't mind me asking but what were the tags that you had issue with on the = Windows FCGI 8.6.1 version? Would like to know if we have the same issues. = So far ...we have nothing unusual ......so would be nice to know. Many than= ks in advance. Cheers TDn From: Buske, Matthew > Sent: Friday, April 05, 2019 20:02 PM To: talk@webdna.us Subject: RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error Hi Terry, Thanks for the info, it is appreciated. We tried the windows FCGI 8.6.1 but= we kept running into issues with certain tags not working so it doesn't lo= ok like an option for us at this point. We had little time to make a decisi= on and went the Linux route to minimize the impact on our existing services= .. What is strange is this ODBC issue only happens with WebDNA- which made m= e wonder if WebDNA doesn't play well with the MSODBC driver... Matt From: Terry Nair > Sent: Wednesday, April 3, 2019 6:50 PM To: talk@webdna.us Subject: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error Responding to the new Windows version (FCGI 8.6.1) only in your email ....i= t is available and works beautifully. Been running it on Win 2012 R2 since = July 2018 with no issues even through regular Windows update and SSL instal= lation / renewals. Nothing breaks. For your info .... Cheers ....Terry Nair From: Buske, Matthew > Sent: Wednesday, April 03, 2019 23:19 PM To: > > Subject: [WebDNA] [BULK] SQL ODBC 00000 Error Importance: Low 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 --------------------------------------------------------- This message is s= ent 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 --------------------------------------------------------- This message is s= ent 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 CAUTION: This email originated from outside of the organization. Do not cli= ck links or open attachments unless you recognize the sender and know the c= ontent is safe. --------------------------------------------------------- This message is s= ent 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 --------------------------------------------------------- This message is s= ent 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_DF89B680A72D1D49A4CE61BDF2F53CDA48D442A1OCB56oswegoboce_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The tag that has caused us the most problems that we= couldn’t work around was [thisurl]- no matter what we did it wouldn&= #8217;t return a value and was empty no matter what page we hit.


Matt

 

From: Terry Nair <terrynair@prism4u.com>= ;
Sent: Friday, April 5, 2019 9:02 AM
To: talk@webdna.us
Subject: RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Erro= r

 

Don’t mind me asking but = what were the tags that you had issue with on the Windows FCGI 8.6.1 versio= n? Would like to know if we have the same issues. So far …we have not= hing unusual ……so would be nice to know. Many thanks in advance.

 

Cheers TDn

 

From: Buske, Matthew <MBuske2@CiTiboces.org>
Sent: Friday, April 05, 2019 20:02 PM
To: talk@webdna.us
Subject: RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Erro= r

 

Hi Terry,

 

Thanks for the info, it is appreciated. We tried the= windows FCGI 8.6.1 but we kept running into issues with certain tags not w= orking so it doesn’t look like an option for us at this point. We had= little time to make a decision and went the Linux route to minimize the impact on our existing services. What is s= trange is this ODBC issue only happens with WebDNA- which made me wonder if= WebDNA doesn’t play well with the MSODBC driver…

 

Matt

 

From: Terry Nair <terrynair@prism4u.com>
Sent: Wednesday, April 3, 2019 6:50 PM
To: talk@webdna.us
Subject: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error

 

Responding to the new Windows v= ersion (FCGI 8.6.1) only in your email ….it is available and works be= autifully. Been running it on Win 2012 R2 since July 2018 with no issues ev= en through regular Windows update and SSL installation / renewals. Nothing breaks.

 

For your info ….

 

Cheers ….Terry Nair<= /o:p>

 

From: Buske, Matthew <MBuske2@CiTiboces.org>
Sent: Wednesday, April 03, 2019 23:19 PM
To: <talk@webdna.us> <= ;talk@webdna.us>
Subject: [WebDNA] [BULK] SQL ODBC 00000 Error
Importance: Low

 

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 mai= ling 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

----------------------------------------------------= ----- 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

<= span style=3D"font-size:10.0pt;color:#9C6500">CAUTION: This email originated from outside of t= he organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.<= o:p>

 

------------------------------------------------= --------- This message is sent to you because you are subscribed to the mai= ling 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

----------------------------------------------------= ----- 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

--------------------------------------------------------- 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_DF89B680A72D1D49A4CE61BDF2F53CDA48D442A1OCB56oswegoboce_-- . 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)
2168 --_000_DF89B680A72D1D49A4CE61BDF2F53CDA48D442A1OCB56oswegoboce_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The tag that has caused us the most problems that we couldn't work around w= as [thisurl]- no matter what we did it wouldn't return a value and was empt= y no matter what page we hit. Matt From: Terry Nair Sent: Friday, April 5, 2019 9:02 AM To: talk@webdna.us Subject: RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error Don't mind me asking but what were the tags that you had issue with on the = Windows FCGI 8.6.1 version? Would like to know if we have the same issues. = So far ...we have nothing unusual ......so would be nice to know. Many than= ks in advance. Cheers TDn From: Buske, Matthew > Sent: Friday, April 05, 2019 20:02 PM To: talk@webdna.us Subject: RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error Hi Terry, Thanks for the info, it is appreciated. We tried the windows FCGI 8.6.1 but= we kept running into issues with certain tags not working so it doesn't lo= ok like an option for us at this point. We had little time to make a decisi= on and went the Linux route to minimize the impact on our existing services= .. What is strange is this ODBC issue only happens with WebDNA- which made m= e wonder if WebDNA doesn't play well with the MSODBC driver... Matt From: Terry Nair > Sent: Wednesday, April 3, 2019 6:50 PM To: talk@webdna.us Subject: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error Responding to the new Windows version (FCGI 8.6.1) only in your email ....i= t is available and works beautifully. Been running it on Win 2012 R2 since = July 2018 with no issues even through regular Windows update and SSL instal= lation / renewals. Nothing breaks. For your info .... Cheers ....Terry Nair From: Buske, Matthew > Sent: Wednesday, April 03, 2019 23:19 PM To: > > Subject: [WebDNA] [BULK] SQL ODBC 00000 Error Importance: Low 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 --------------------------------------------------------- This message is s= ent 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 --------------------------------------------------------- This message is s= ent 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 CAUTION: This email originated from outside of the organization. Do not cli= ck links or open attachments unless you recognize the sender and know the c= ontent is safe. --------------------------------------------------------- This message is s= ent 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 --------------------------------------------------------- This message is s= ent 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_DF89B680A72D1D49A4CE61BDF2F53CDA48D442A1OCB56oswegoboce_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The tag that has caused us the most problems that we= couldn’t work around was [thisurl]- no matter what we did it wouldn&= #8217;t return a value and was empty no matter what page we hit.


Matt

 

From: Terry Nair <terrynair@prism4u.com>= ;
Sent: Friday, April 5, 2019 9:02 AM
To: talk@webdna.us
Subject: RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Erro= r

 

Don’t mind me asking but = what were the tags that you had issue with on the Windows FCGI 8.6.1 versio= n? Would like to know if we have the same issues. So far …we have not= hing unusual ……so would be nice to know. Many thanks in advance.

 

Cheers TDn

 

From: Buske, Matthew <MBuske2@CiTiboces.org>
Sent: Friday, April 05, 2019 20:02 PM
To: talk@webdna.us
Subject: RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Erro= r

 

Hi Terry,

 

Thanks for the info, it is appreciated. We tried the= windows FCGI 8.6.1 but we kept running into issues with certain tags not w= orking so it doesn’t look like an option for us at this point. We had= little time to make a decision and went the Linux route to minimize the impact on our existing services. What is s= trange is this ODBC issue only happens with WebDNA- which made me wonder if= WebDNA doesn’t play well with the MSODBC driver…

 

Matt

 

From: Terry Nair <terrynair@prism4u.com>
Sent: Wednesday, April 3, 2019 6:50 PM
To: talk@webdna.us
Subject: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error

 

Responding to the new Windows v= ersion (FCGI 8.6.1) only in your email ….it is available and works be= autifully. Been running it on Win 2012 R2 since July 2018 with no issues ev= en through regular Windows update and SSL installation / renewals. Nothing breaks.

 

For your info ….

 

Cheers ….Terry Nair<= /o:p>

 

From: Buske, Matthew <MBuske2@CiTiboces.org>
Sent: Wednesday, April 03, 2019 23:19 PM
To: <talk@webdna.us> <= ;talk@webdna.us>
Subject: [WebDNA] [BULK] SQL ODBC 00000 Error
Importance: Low

 

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 mai= ling 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

----------------------------------------------------= ----- 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

<= span style=3D"font-size:10.0pt;color:#9C6500">CAUTION: This email originated from outside of t= he organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.<= o:p>

 

------------------------------------------------= --------- This message is sent to you because you are subscribed to the mai= ling 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

----------------------------------------------------= ----- 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

--------------------------------------------------------- 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_DF89B680A72D1D49A4CE61BDF2F53CDA48D442A1OCB56oswegoboce_-- . "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:

Code database (1998) Cookies? (1997) Searching multiple records for certain info (2000) RE:It just Does't add up!!! (1997) RE: PIXO support (1997) I think WebDNA-Talk died ... :( (1997) A question for the experts (2000) Version f1 status (1997) [WebDNA] Setting Content-Type within [returnraw] - not working (2010) Web Catalog 2 demo (1997) Fuzzy on [url] context (1998) WebCat2b12plugin - [search] is broken ... not! (1997) PCS Frames (1997) [group] ? (1997) WebDelivery downloads alias, not original ? (1997) Re:need help please (1997) [WebDNA] opinions on [switch] [case]... (2009) typhoon... (1997) I have observed and I am gone. (1998) Re[2]: Wierd problem with 3.08 WIN Version (2000)