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

This WebDNA talk-list message is from

2019


It keeps the original formatting.
numero = 114552
interpreted = N
texte = 2172 --_000_DF89B680A72D1D49A4CE61BDF2F53CDA48D45DA7OCB56oswegoboce_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Fixing thisurl would be fantastic. Our sites rely heavily on thisurl- I wou= ld really love to not have to work around this one as it would result in a = massive lift... Thanks for confirming it's not just us seeing the issue, we wondered if we = were the only ones! Matt From: Terry Nair Sent: Friday, April 5, 2019 6:11 PM To: talk@webdna.us Subject: RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error Tried the plain vanilla [thisurl] & [thisurlplusget] tag and can confirm, i= t does not work just like you stated. That said, a possible workaround woul= d be to hard code tag each page with a text variable that identity the page= path. You can then use that text variable when the user lands on that page= .. Needless to say, fixing the [this url] would be cool, maybe in future updat= ed versions of 8 for Windows. Incidentally, is there a reference page on We= bDNA that list all the verified outstanding bugs / broken tags for a partic= ular version / OS of WebDNA? If there isn't ....maybe attach it as a footno= te to the WebDNA Resource page under the affected tag for reference. Cheers TDn From: Buske, Matthew > Sent: Friday, April 05, 2019 23:47 PM To: talk@webdna.us Subject: RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error 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 --------------------------------------------------------- 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_DF89B680A72D1D49A4CE61BDF2F53CDA48D45DA7OCB56oswegoboce_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Fixing thisurl would be fantastic. Our sites rely he= avily on thisurl- I would really love to not have to work around this one a= s it would result in a massive lift…

 

Thanks for confirming it’s not just us seeing = the issue, we wondered if we were the only ones!

 

Matt

 

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

 

Tried the plain vanilla [thisur= l] & [thisurlplusget] tag and can confirm, it does not work just like y= ou stated. That said, a possible workaround would be to hard code tag each = page with a text variable that identity the page path. You can then use that text variable when the user lands on = that page.

 

Needless to say, fixing the [th= is url] would be cool, maybe in future updated versions of 8 for Windows. I= ncidentally, is there a reference page on WebDNA that list all the verified= outstanding bugs / broken tags for a particular version / OS of WebDNA? If there isn’t ….maybe at= tach it as a footnote to the WebDNA Resource page under the affected tag fo= r reference.

 

Cheers TDn

 

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

 

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 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_DF89B680A72D1D49A4CE61BDF2F53CDA48D45DA7OCB56oswegoboce_-- . 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)
2172 --_000_DF89B680A72D1D49A4CE61BDF2F53CDA48D45DA7OCB56oswegoboce_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Fixing thisurl would be fantastic. Our sites rely heavily on thisurl- I wou= ld really love to not have to work around this one as it would result in a = massive lift... Thanks for confirming it's not just us seeing the issue, we wondered if we = were the only ones! Matt From: Terry Nair Sent: Friday, April 5, 2019 6:11 PM To: talk@webdna.us Subject: RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error Tried the plain vanilla [thisurl] & [thisurlplusget] tag and can confirm, i= t does not work just like you stated. That said, a possible workaround woul= d be to hard code tag each page with a text variable that identity the page= path. You can then use that text variable when the user lands on that page= .. Needless to say, fixing the [this url] would be cool, maybe in future updat= ed versions of 8 for Windows. Incidentally, is there a reference page on We= bDNA that list all the verified outstanding bugs / broken tags for a partic= ular version / OS of WebDNA? If there isn't ....maybe attach it as a footno= te to the WebDNA Resource page under the affected tag for reference. Cheers TDn From: Buske, Matthew > Sent: Friday, April 05, 2019 23:47 PM To: talk@webdna.us Subject: RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error 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 --------------------------------------------------------- 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_DF89B680A72D1D49A4CE61BDF2F53CDA48D45DA7OCB56oswegoboce_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Fixing thisurl would be fantastic. Our sites rely he= avily on thisurl- I would really love to not have to work around this one a= s it would result in a massive lift…

 

Thanks for confirming it’s not just us seeing = the issue, we wondered if we were the only ones!

 

Matt

 

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

 

Tried the plain vanilla [thisur= l] & [thisurlplusget] tag and can confirm, it does not work just like y= ou stated. That said, a possible workaround would be to hard code tag each = page with a text variable that identity the page path. You can then use that text variable when the user lands on = that page.

 

Needless to say, fixing the [th= is url] would be cool, maybe in future updated versions of 8 for Windows. I= ncidentally, is there a reference page on WebDNA that list all the verified= outstanding bugs / broken tags for a particular version / OS of WebDNA? If there isn’t ….maybe at= tach it as a footnote to the WebDNA Resource page under the affected tag fo= r reference.

 

Cheers TDn

 

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

 

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

XMLNodes Error (2007) Dubble Sku's in a Database (1999) Execute Applescript (1997) Mem per threads (1998) insert graphic in email (2000) Online reference (1997) Paranoid about serial numbers...not (1998) Secure Server (1999) Max Record length restated as maybe bug (1997) HEADER AND FOOTER (1997) Strange ThisURL under Linux (2000) HELP WITH DATES (1997) [WebDNA] [table] weirdness maybe? (2014) Moment of Thanks (1997) Opinion: [input] should be called [output] ... (1997) RE: redirect with more than 256 characters (1999) Forum - Test Request (2005) WebCat2.0 [format thousands .0f] no go (1997) [OT] Happy Turkey Day! (2003) [lineitems] (2000)