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

This WebDNA talk-list message is from

2019


It keeps the original formatting.
numero = 114547
interpreted = N
texte = 2167 This is a multipart message in MIME format. ------=_NextPart_000_0020_01D4EBF2.BF847910 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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 thanks 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 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 strange 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 > 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 ..it 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 installation / 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 heard any word on the new windows version we are moving to 8.5.1 CentOS Server version. Our Apps connect to MSSQL 2017 on a separate windows machine via 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 what 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 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 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 machine for the above errors either. We thought it might be a drop in the connection so we decided to give installing the 'new' MSSQL Linux version to cut the network issues out of the equation. Even on the same machine accessing localhost 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 seems 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 really want to use the new version and keep finding road 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=55 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=55 Bug Reporting: support@webdna.us CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. --------------------------------------------------------- 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=55 Bug Reporting: support@webdna.us ------=_NextPart_000_0020_01D4EBF2.BF847910 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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 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 = 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 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 strange 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 version (FCGI 8.6.1) only in = your email ….it 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 installation / renewals. Nothing = breaks.

 

For your info ….

 

Cheers ….Terry = Nair

 

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 environment. As we have not heard = any word on the new windows version we are moving to 8.5.1 CentOS Server = version. Our Apps connect to MSSQL 2017 on a separate windows machine = via 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 what 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 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 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 machine for the above errors either. We = thought it might be a drop in the connection so we decided to give = installing the ‘new’ MSSQL Linux version to cut the network = issues out of the equation. Even on the same machine accessing localhost = 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 seems 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 really want to use the new version and keep finding = road 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/p= age.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/p= age.dna?numero=3D55 Bug Reporting: support@webdna.us =

CAUTION: This email originated from = outside of the organization. Do not click links or open attachments = unless you recognize the sender and know the content is = safe.

 

--------------------------------------------------------- = 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/p= age.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 ------=_NextPart_000_0020_01D4EBF2.BF847910-- . 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)
2167 This is a multipart message in MIME format. ------=_NextPart_000_0020_01D4EBF2.BF847910 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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 thanks 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 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 strange 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 > 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 ..it 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 installation / 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 heard any word on the new windows version we are moving to 8.5.1 CentOS Server version. Our Apps connect to MSSQL 2017 on a separate windows machine via 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 what 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 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 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 machine for the above errors either. We thought it might be a drop in the connection so we decided to give installing the 'new' MSSQL Linux version to cut the network issues out of the equation. Even on the same machine accessing localhost 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 seems 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 really want to use the new version and keep finding road 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=55 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=55 Bug Reporting: support@webdna.us CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. --------------------------------------------------------- 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=55 Bug Reporting: support@webdna.us ------=_NextPart_000_0020_01D4EBF2.BF847910 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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 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 = 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 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 strange 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 version (FCGI 8.6.1) only in = your email ….it 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 installation / renewals. Nothing = breaks.

 

For your info ….

 

Cheers ….Terry = Nair

 

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 environment. As we have not heard = any word on the new windows version we are moving to 8.5.1 CentOS Server = version. Our Apps connect to MSSQL 2017 on a separate windows machine = via 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 what 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 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 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 machine for the above errors either. We = thought it might be a drop in the connection so we decided to give = installing the ‘new’ MSSQL Linux version to cut the network = issues out of the equation. Even on the same machine accessing localhost = 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 seems 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 really want to use the new version and keep finding = road 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/p= age.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/p= age.dna?numero=3D55 Bug Reporting: support@webdna.us =

CAUTION: This email originated from = outside of the organization. Do not click links or open attachments = unless you recognize the sender and know the content is = safe.

 

--------------------------------------------------------- = 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/p= age.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 ------=_NextPart_000_0020_01D4EBF2.BF847910-- . "Terry Nair"

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:

[LookUp] (1999) frames & carts (1997) [ot] g5 xserve drives (2004) multi-paragraph fields (1997) Leap Day Triggers? (2000) Help- Spam Bots are spamming my site. (2007) Forcing a NEWCART (1997) Protect vs Authenicate (1997) [SearchString] (1998) too many nested tags ... (1997) User Defined Sorting (1997) wcat 4.5/WebStar V uninstall (2002) Webstar 1.3.1 PPC (1997) Search results templates (1996) Tab Charactor (1997) Moment of Thanks (1997) Emailer choke (1997) WebDNA problem (2006) Error Lob.db records error message not name (1997) WebCat and image maps (1997)