Re: [QATrack+ 1322] manage.py migrate issuer

[Kym Nitschke]

Hi,

We have just finished installing QA Track+ on Windows with Microsoft SQL Server. We experienced a similar error. The error disappeared when we configured the SQL server for server authentication of user logins rather than windows authentication.

Regards,

Kym Nitschke

> On 16 May 2019, at 8:06 pm, rachid....@gmail.com wrote:
>
> Dear all,
>
> I am a new user of QAtarck+ and thank you for sharing !
> Until now impossible to use it
> at this command line : python manage.py migrate
>
> I get the followinf error message. Someone can help me.
> Thank you
> Rachid
>
> Traceback (most recent call last):
> File "C:\Python36\lib\site-packages\django\db\backends\base\base.py", line 213, in ensure_connection
> self.connect()
> File "C:\Python36\lib\site-packages\django\db\backends\base\base.py", line 189, in connect
> self.connection = self.get_new_connection(conn_params)
> File "C:\Python36\lib\site-packages\sql_server\pyodbc\base.py", line 314, in get_new_connection
> timeout=timeout)
> pyodbc.InterfaceError: ('28000', "[28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'qatrack'. (18456) (SQLDriverConnect); [28000] [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute (0); [28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'qatrack'. (18456); [28000] [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute (0)")
>
> The above exception was the direct cause of the following exception:
>
> Traceback (most recent call last):
> File "manage.py", line 10, in <module>
> execute_from_command_line(sys.argv)
> File "C:\Python36\lib\site-packages\django\core\management\__init__.py", line 364, in execute_from_command_line
> utility.execute()
> File "C:\Python36\lib\site-packages\django\core\management\__init__.py", line 356, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
> File "C:\Python36\lib\site-packages\django\core\management\base.py", line 283, in run_from_argv
> self.execute(*args, **cmd_options)
> File "C:\Python36\lib\site-packages\django\core\management\base.py", line 330, in execute
> output = self.handle(*args, **options)
> File "C:\Python36\lib\site-packages\django\core\management\commands\migrate.py", line 83, in handle
> executor = MigrationExecutor(connection, self.migration_progress_callback)
> File "C:\Python36\lib\site-packages\django\db\migrations\executor.py", line 20, in __init__
> self.loader = MigrationLoader(self.connection)
> File "C:\Python36\lib\site-packages\django\db\migrations\loader.py", line 52, in __init__
> self.build_graph()
> File "C:\Python36\lib\site-packages\django\db\migrations\loader.py", line 210, in build_graph
> self.applied_migrations = recorder.applied_migrations()
> File "C:\Python36\lib\site-packages\django\db\migrations\recorder.py", line 65, in applied_migrations
> self.ensure_schema()
> File "C:\Python36\lib\site-packages\django\db\migrations\recorder.py", line 52, in ensure_schema
> if self.Migration._meta.db_table in self.connection.introspection.table_names(self.connection.cursor()):
> File "C:\Python36\lib\site-packages\django\db\backends\base\base.py", line 254, in cursor
> return self._cursor()
> File "C:\Python36\lib\site-packages\django\db\backends\base\base.py", line 229, in _cursor
> self.ensure_connection()
> File "C:\Python36\lib\site-packages\django\db\backends\base\base.py", line 213, in ensure_connection
> self.connect()
> File "C:\Python36\lib\site-packages\django\db\utils.py", line 94, in __exit__
> six.reraise(dj_exc_type, dj_exc_value, traceback)
> File "C:\Python36\lib\site-packages\django\utils\six.py", line 685, in reraise
> raise value.with_traceback(tb)
> File "C:\Python36\lib\site-packages\django\db\backends\base\base.py", line 213, in ensure_connection
> self.connect()
> File "C:\Python36\lib\site-packages\django\db\backends\base\base.py", line 189, in connect
> self.connection = self.get_new_connection(conn_params)
> File "C:\Python36\lib\site-packages\sql_server\pyodbc\base.py", line 314, in get_new_connection
> timeout=timeout)
> django.db.utils.InterfaceError: ('28000', "[28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'qatrack'. (18456) (SQLDriverConnect); [28000] [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute (0); [28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'qatrack'. (18456); [28000] [Microsoft][ODBC SQL Server Driver]Invalid connection string attribute (0)")
>
> --
> You received this message because you are subscribed to the Google Groups "QATrack+" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to qatrack+u...@googlegroups.com.
> To post to this group, send email to qat...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/qatrack/4a10fa34-5188-47e6-b0fe-4c7f45d4914f%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Randle Taylor]

Hi Rachid,

As Kym said (thanks Kym!), this is likely an issue with not having enabled SQL Server Authentication enabled. Instructions for that are here: https://www.dundas.com/support/learning/documentation/installation/how-to-enable-sql-server-authentication

Randy

To view this discussion on the web visit https://groups.google.com/d/msgid/qatrack/34C79A8F-ED97-44EF-A77F-69E078CAFAC5%40icloud.com.

[Luka Komar]

Hi,

i am sorry to open an old thread again but i have the same problem:
django.db.utils.InterfaceError: ('28000', "[28000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Login failed for user 'qatrack'. (18456) (SQLDriverConnect); [28000] [Microsoft][ODBC Driver 17 for SQL Server]Invalid connection string attribute (0); [28000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Login failed for user 'qatrack'. (18456); [28000] [Microsoft][ODBC Driver 17 for SQL Server]Invalid connection string attribute (0)")

I did confirm that i have selected SQL Server and Windows Authentication mode and i've restarted the server.

I tried copying the local settings file multiple times. I've only changed the timezone.

If i leave user and password empty, then i get another error that might be connected:
django.db.utils.InterfaceError: ('28000', '[28000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Login failed for user \'ONKO-QATRACK\\luka.komar\'. (18456) (SQLDriverConnect); [28000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Cannot open database "qatrackplus31" requested by the login. The login failed. (4060); [28000] [Microsoft][ODBC Driver 17 for SQL Server]Invalid connection string attribute (0); [28000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Login failed for user \'ONKO-QATRACK\\luka.komar\'. (18456); [28000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Cannot open database "qatrackplus31" requested by the login. The login failed. (4060); [28000] [Microsoft][ODBC Driver 17 for SQL Server]Invalid connection string attribute (0)').

Is the error from setting up the local server or something? I have windows server 2019.

Thank you for your time,

Luke

četrtek, 16. maj 2019 ob 15:19:16 UTC+2 je oseba Randle Taylor napisala:

[Luka Komar]

I've successfully fixed after a couple of hours: i've had multiple sql servers on, i've specified directly which one i wanted with 'HOST': 'COMPUTERNAME\QATRACKPLUS3_1'.

Thank you anyway.

Have a nice day,

Luke

torek, 9. april 2024 ob 10:44:44 UTC+2 je oseba Luka Komar napisala: