UPDATE : I managed to find the solution so I will post it here for any
others that have the same issue :
We had to instrall a new ODBC driver and to modify the MS SQL connection
string.
Old string :
uri = mssql://DRIVER={SQL Server}
New string :
uri = mssql://DRIVER={ODBC Driver 13 for SQL Server}
We then ran into problems with web2py trying to recreate the auth tables
which already existed.
gluon.contrib.pypyodbc.ProgrammingError: ('42S01', "[42S01]
[Microsoft][ODBC Driver 13 for SQL Server][SQL Server]There is already an
object named 'auth_user' in the database.")
I found that this error message was somehow related to the files in the
databases folder within the application on the web2py server.
I thought that this folder was only used when connecting to a MySQL
database, but I now see that it is also referenced somewhere for the auth
tables when using a shared MS SQL database.
As a test, I renamed the databases folder under the web2py application (as
a backup), and then copied over a databases folder from a freshly created
web2py application. I then ran my MSSQL web2py application and it ran
correctly.
Hope this helps someone ;)
On Friday, June 19, 2020 at 7:44:53 AM UTC+2, Davidiam wrote:
>
> Good Morning,
>
> I would like to know what I would have to modify in order to connect to MS
> SQL from web2py with TLS 1.2. We are running web2py 2.18.5 on a Windows
> 2016 IIS server.
>
> Yesterday a security patch was installed to disable TLS 1.0 and 1.1 and
> enable TLS 1.2 and now all our MS SQL DB connections are failing.
>
> Thank you very much for your help on this, I would appreciate a rapid
> reply as our development in web2py is now blocked due to this.
>
> Kind Regards,
> David
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/web2py/851176bc-d7a9-4faf-ad0f-d28e47ccf28eo%40googlegroups.com.