Tried versions 7.x-1.3 and 7.x-2.x-dev and received the following fatal error when module is enabled:

PDOException: SQLSTATE[42S02]: [Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid object name 'password_policy_force_change'.: SELECT p.[force_change] AS [force_change] FROM {password_policy_force_change} p WHERE ( ([uid] = :db_condition_placeholder_0) ); Array ( [:db_condition_placeholder_0] => 1 ) in password_policy_user_load() (line 237 of D:\wwwroot\drupal7\sites\all\modules\password_policy\password_policy.module).

Suspect this is actually a problem with the SQL Server driver (e.g., \sqlsrv\database.inc or \sqlsrv\select.inc), but am wondering if this is a known issue or if anyone has found a workaround to get Password policy working on SQL Server implementations.

Thanks,

Kerry

Comments

erikwebb’s picture

erikwebb commented
Issue tags: +mssql sqlsrv

I'm not a SQL Server expert, but the error appears to say that the "password_policy_force_change" table is missing. I don't believe this functionality has been reproduced for 7.x-2.x yet, so it explains that problem. Can you confirm that the table exists in your 7.x-1.3 installation?

khalligan’s picture

khalligan commented

Thanks for the reply. I am actually running Drupal 7.12, so that may be the problem. I don't have a password_policy_force_change table. I tried the 7.x-1.x version of password policy as well and got the same result. I will upgrade to Drupal 7.13 and re-try with 7.x-1.3 but that will likely be a few days before I can implement the upgrade. Is password_policy_force_change table create/implemented as a part of Drupal 7.13, or is it created when password_policy is enabled? Thanks.

erikwebb’s picture

erikwebb commented

It should be automatically created by Password Policy 7.x-1.x (I wouldn't test 7.x-2.x right now). Can you try with a fresh install and Password Policy 7.x-1.x installed?

erikwebb’s picture

erikwebb commented
Status: Active » Postponed (maintainer needs more info)
khalligan’s picture

khalligan commented

This was the straw that broke the camel's back. After running up against issue after issue with contributed modules on my SQL Server implementation, I switched to MySQL and everything is working perfectly. This is a fantastic module, exactly what I needed. Thanks! Consider this closed, but it should be noted that at least one user (me) couldn't make this work on a SQL Server implementation.

erikwebb’s picture

erikwebb commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Unfortunately SQL Server is not as well supported by Drupal as it probably should be. I'd like to take Password Policy off of that list of incompatibilities if we can work things out, but obviously in the long-term MySQL will be much better supported and tested.