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

This WebDNA talk-list message is from

2019

It keeps the original formatting. numero = 114549
interpreted = N
texte = 2169--Apple-Mail-AF556C10-157D-4523-9873-B7596DAD3BA2Content-Type: text/plain;charset=utf-8Content-Transfer-Encoding: quoted-printableMight want to turn on WebDNA error reporting to see what WebDNA is doing at t=he time of the problem.=20D. Brooke Mobile> On Apr 5, 2019, at 7:02 AM, Buske, Matthew wrote:>=20> Hi Terry,> =20> Thanks for the info, it is appreciated. We tried the windows FCGI 8.6.1 bu=t we kept running into issues with certain tags not working so it doesn=E2=80==99t look like an option for us at this point. We had little time to make a d=ecision and went the Linux route to minimize the impact on our existing serv=ices. What is strange is this ODBC issue only happens with WebDNA- which mad=e me wonder if WebDNA doesn=E2=80=99t play well with the MSODBC driver=E2=80==A6> =20> Matt> =20> From: Terry Nair =20> Sent: Wednesday, April 3, 2019 6:50 PM> To: talk@webdna.us> Subject: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error> =20> Responding to the new Windows version (FCGI 8.6.1) only in your email =E2=80==A6.it is available and works beautifully. Been running it on Win 2012 R2 si=nce July 2018 with no issues even through regular Windows update and SSL ins=tallation / renewals. Nothing breaks.> =20> For your info =E2=80=A6.> =20> Cheers =E2=80=A6.Terry Nair> =20> From: Buske, Matthew =20> Sent: Wednesday, April 03, 2019 23:19 PM> To: > Subject: [WebDNA] [BULK] SQL ODBC 00000 Error> Importance: Low> =20> Hello,> =20> 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 Serve=r version. Our Apps connect to MSSQL 2017 on a separate windows machine via t=he SQL tag and ODBC. 95% of the time this works fantastic, but about 5% of t=he time we get a SQL:00000 error and the query does not complete.> =20> 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 d=oing and we found it logged this when the SQL:00000 happened:> TCP Provider: Error code 0x102> A network-related or instance-specific error has occurred while establishi=ng a connection to SQL Server. Server is not found or not accessible. Check i=f instance name is correct and if SQL Server is configured to allow remote c=onnections. For more information see SQL Server Books Online.> Login timeout expired> Error: 08003> =20> This is odd to us as the server is always up and the very next SQL command= completes without issue. Haven=E2=80=99t found anything of use on the googl=e machine for the above errors either. We thought it might be a drop in the c=onnection so we decided to give installing the =E2=80=98new=E2=80=99 MSSQL L=inux 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 tra=ce gives the above error each time it fails.> =20> If we connect to the same SQL servers on our windows box however, we don=E2==80=99t see the SQL:00000 errors at all and the connection works like a cham=p. It seems this is an issue connecting to MSSQL from Linux via ODBC.> =20> 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!> =20> Thanks!> =20> Matt Buske> =20> --------------------------------------------------------- This message is s=ent to you because you are subscribed to the mailing list talk@webdna.us To u=nsubscribe, 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 s=ent to you because you are subscribed to the mailing list talk@webdna.us To u=nsubscribe, 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 cl=ick links or open attachments unless you recognize the sender and know the c=ontent is safe.> =20> --------------------------------------------------------- This message is s=ent to you because you are subscribed to the mailing list talk@webdna.us To u=nsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/p=age.dna?numero=3D55 Bug Reporting: support@webdna.us--Apple-Mail-AF556C10-157D-4523-9873-B7596DAD3BA2Content-Type: text/html;charset=utf-8Content-Transfer-Encoding: quoted-printableMight want to turn on WebDNA error reportin=g to see what WebDNA is doing at the time of the problem.

D. Brooke Mobile

=
On Apr 5, 2019, at 7:02 AM, Buske, Matthew <MBuske2@citiboces.org> wrote:

Hi Terry,

Thanks for the info, it is appreciated. We tried the w=indows FCGI 8.6.1 but we kept running into issues with certain tags not work=ing so it doesn=E2=80=99t look like an option for us at this point. We had l=ittle time to make a decision and went the Linux route to minimize the impact on our existing services. What is st=range is this ODBC issue only happens with WebDNA- which made me wonder if W=ebDNA doesn=E2=80=99t play well with the MSODBC driver=E2=80=A6

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 ve=rsion (FCGI 8.6.1) only in your email =E2=80=A6.it is available and works be=autifully. Been running it on Win 2012 R2 since July 2018 with no issues eve=n through regular Windows update and SSL installation / renewals. Nothing breaks.

For your info =E2=80=A6.

Cheers =E2=80=A6.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 environ=ment. 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 separat=e 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 erro=r so we are not sure what is causing it. We set up a trace on the ODBC drive=r to see what SQL was doing and we found it logged this when the SQL:00000 h=appened:

TCP Provider: Error code 0x102
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 co=rrect and if SQL Server is configured to allow remote connections. For more informati=on see SQL Server Books Online.
Login timeout expired
Error: 08003

This is odd to us as the server is always up and the v=ery next SQL command completes without issue. Haven=E2=80=99t found anything= of use on the google machine for the above errors either. We thought it mig=ht be a drop in the connection so we decided to give installing the =E2=80=98new=E2=80=99 MSSQL Linux version to cut the= network issues out of the equation. Even on the same machine accessing loca=lhost we see the sporadic SQL:00000 error and the trace gives the above erro=r each time it fails.

If we connect to the same SQL servers on our windows b=ox however, we don=E2=80=99t see the SQL:00000 errors at all and the connect=ion works like a champ. It seems this is an issue connecting to MSSQL from L=inux 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 roa=d blocks!

Thanks!

Matt Buske

--------------------------------------------------=------- This message is sent to you because you are subscribed to the mailin=g listtalk@webdna.us To unsubscribe, E-mail t=o: 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 l=isttalk@webdna.us To unsubscribe, E-mail t=o: 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 or=ganization. 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 tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leav=e@webdna.usarchives: http://www.w=ebdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us=---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list talk@webdna.usTo unsubscribe, E-mail to: talk-leave@webdna.usarchives: http://www.webdna.us/page.dna?numero=3D55Bug Reporting: support@webdna.us--Apple-Mail-AF556C10-157D-4523-9873-B7596DAD3BA2--. Associated Messages, from the most recent to the oldest:

RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error ("Buske, Matthew" 2019)
RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error ("Buske, Matthew" 2019)
RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error ("Terry Nair" 2019)
Re: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error (Donovan Brooke 2019)
RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error ("Buske, Matthew" 2019)
RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error ("Terry Nair" 2019)
RE: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error ("Buske, Matthew" 2019)

2169--Apple-Mail-AF556C10-157D-4523-9873-B7596DAD3BA2Content-Type: text/plain;charset=utf-8Content-Transfer-Encoding: quoted-printableMight want to turn on WebDNA error reporting to see what WebDNA is doing at t=he time of the problem.=20D. Brooke Mobile> On Apr 5, 2019, at 7:02 AM, Buske, Matthew wrote:>=20> Hi Terry,> =20> Thanks for the info, it is appreciated. We tried the windows FCGI 8.6.1 bu=t we kept running into issues with certain tags not working so it doesn=E2=80==99t look like an option for us at this point. We had little time to make a d=ecision and went the Linux route to minimize the impact on our existing serv=ices. What is strange is this ODBC issue only happens with WebDNA- which mad=e me wonder if WebDNA doesn=E2=80=99t play well with the MSODBC driver=E2=80==A6> =20> Matt> =20> From: Terry Nair =20> Sent: Wednesday, April 3, 2019 6:50 PM> To: talk@webdna.us> Subject: EXTERNAL EMAIL: RE: [WebDNA] [BULK] SQL ODBC 00000 Error> =20> Responding to the new Windows version (FCGI 8.6.1) only in your email =E2=80==A6.it is available and works beautifully. Been running it on Win 2012 R2 si=nce July 2018 with no issues even through regular Windows update and SSL ins=tallation / renewals. Nothing breaks.> =20> For your info =E2=80=A6.> =20> Cheers =E2=80=A6.Terry Nair> =20> From: Buske, Matthew =20> Sent: Wednesday, April 03, 2019 23:19 PM> To: > Subject: [WebDNA] [BULK] SQL ODBC 00000 Error> Importance: Low> =20> Hello,> =20> 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 Serve=r version. Our Apps connect to MSSQL 2017 on a separate windows machine via t=he SQL tag and ODBC. 95% of the time this works fantastic, but about 5% of t=he time we get a SQL:00000 error and the query does not complete.> =20> 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 d=oing and we found it logged this when the SQL:00000 happened:> TCP Provider: Error code 0x102> A network-related or instance-specific error has occurred while establishi=ng a connection to SQL Server. Server is not found or not accessible. Check i=f instance name is correct and if SQL Server is configured to allow remote c=onnections. For more information see SQL Server Books Online.> Login timeout expired> Error: 08003> =20> This is odd to us as the server is always up and the very next SQL command= completes without issue. Haven=E2=80=99t found anything of use on the googl=e machine for the above errors either. We thought it might be a drop in the c=onnection so we decided to give installing the =E2=80=98new=E2=80=99 MSSQL L=inux 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 tra=ce gives the above error each time it fails.> =20> If we connect to the same SQL servers on our windows box however, we don=E2==80=99t see the SQL:00000 errors at all and the connection works like a cham=p. It seems this is an issue connecting to MSSQL from Linux via ODBC.> =20> 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!> =20> Thanks!> =20> Matt Buske> =20> --------------------------------------------------------- This message is s=ent to you because you are subscribed to the mailing list talk@webdna.us To u=nsubscribe, 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 s=ent to you because you are subscribed to the mailing list talk@webdna.us To u=nsubscribe, 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 cl=ick links or open attachments unless you recognize the sender and know the c=ontent is safe.> =20> --------------------------------------------------------- This message is s=ent to you because you are subscribed to the mailing list talk@webdna.us To u=nsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/p=age.dna?numero=3D55 Bug Reporting: support@webdna.us--Apple-Mail-AF556C10-157D-4523-9873-B7596DAD3BA2Content-Type: text/html;charset=utf-8Content-Transfer-Encoding: quoted-printableMight want to turn on WebDNA error reportin=g to see what WebDNA is doing at the time of the problem.