Call to a member function fetchField() on null

I got a similar error after upgrading to Drupal 9.4. We don't use SQL Server for the primary Drupal database -- we use it as a data source for an ongoing migration, so we end up with a long backtrace, starting with:

Error: Call to a member function fetchField() on null in modules/contrib/sqlsrv/src/Driver/Database/sqlsrv/Schema.php on line 765 #0 modules/contrib/sqlsrv/src/Driver/Database/sqlsrv/Connection.php(790): Drupal\sqlsrv\Driver\Database\sqlsrv\Schema->getDefaultSchema()

Error: Call to a member function fetchField() on null in Drupal\sqlsrv\Driver\Database\sqlsrv\Schema->getDefaultSchema() (line 765 of /var/www/html/downtoearthdistributors.com/modules/contrib/sqlsrv/src/Driver/Database/sqlsrv/Schema.php)

I'm guessing the internal database API changed...

I just tracked this down to a change record that did more than deprecate functionality -- it removed a default 'return' option - #3185520: Introduced a Connection::lastInsertId method, deprecating the 'return' query option and the Database::RETURN_* constants.

The specific change is in core/lib/Drupal/Core/Database/Connection.php . In 9.3.x, this function returned an option 'return' => Database::RETURN_STATEMENT. In 9.4.x, this option was removed from default options.

The core Connection Class query method has been changed between 9.3 to 9.4 to make the return option optional. I applied the same change to the \Drupal\sqlsrv\Driver\Database\sqlsrv\Connection class, to the query() and queryDirect() methods, which appears to fix this issue, and should be backward compatible.

I applied #4 successfully with Composer on Drupal 9.4.1. This fixed my issue.

I had been unable to select from a database using code like this:

      $result = $this->database->select('table')
        ->fields('table', ['id', 'description'])
        ->condition('id', $ids, 'IN')
        ->execute();

I confirm, patch #4 worked for me.

On the other hand, I have a site with drupal 9 and sqlserver, but I have had performance problems and I saw that it was solved with wincache but this module has not worked again, I appreciate if you give me some documentation where I can improve this, thanks

I had the same error and #4 fixed it for me also. Thanks

#4 fixes the problem on Drupal core 9.4.2.

Fixed errors for me moving to 9.4 from 9.3.

Fixed error for me after upgrading to drupal 9.4

@freelock, thanks for posting. Patch #4 fixed the error for me as well. v9.4

This bug makes the module completely useless on Drupal 9.4 - it generates fatal errors upon connection to MSSQL DB. The patch #4 fixes the problem, so why the maintainers do not include it into the released code? The project looks abandoned, it has not been updated in a year and has the fatal error that makes it incompatible with the latest released version of Drupal.

Rasising to 'major'

#4 fixes the problem on Drupal core 9.4.12 . This patch need to go in next release

Patch #4 works in Drupal 9.5 as well.

Patch #4 works in my Drupal 9.5.7 new installation.

Patch #4 working for me upgrading to D9.5.7, so another upvote for RTBC here.

Just noting this issue is a side-effect from 3185269, which removed the default value from the options array. THe patch copies over the relevant change that was made in the parent class, so is good to go.