It doesn’t make sense to have both - you can only use one. Check your DATABASES setting to which one you’re using - I suspect it’s mssql-django, since it’s newer (mssql-django is a fork of django-mssql-backend, now maintained by microsoft).
As to the error: Django provides the inspectdb command, but it’s up to the database backend to ensure that it works. Therefore this is a bug with django-mssql-backend or mssql-django. Report the bug there, they won’t see it on the forums. I’m sure they will ask for more details regarding the tables in question - perhaps you can show them the SQL CREATE TABLE statements.
To make things work for yourself, you can proceed by using inspectdb on the tables that it does work for (inspectdb table1 table2), then writing models by hand for the two failing tables. inspectdb is ultimately just a shortcut for generating some code - the end result is still your code that you’re responsible for, so you shouldn’t be afraid of writing your own.
Hi @Boomesshv not sure if this will help, but i used this site when i started a few months ago to get an idea of the different Engines Django could use. However not all of them. There are links to Repo’s at the bottom as well, which Adam already referenced as well.
inspectDB can be tricky especially if you have multiple databases configured and if your SCHEMA is not the default one but a custom schema. These might pop up in the future as well :-).