The password does not meet Windows policy requirements because it is too short.

[John_Anderson4]

Some users (presumably new workstations) are getting this error when logging in to OnBase (thick client or config).

Native Error: 15116 (0x00003b0c)
SQL State: [37000]
SQL Error: [[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet Windows policy requirements because it is too short.]
SQL: [ csp_AddDMUser WORKSTATIONNAME ]
Source File: []
Line Number: 8538
Function Call: [::SQLExecDirect( m_hStatement, (unsigned char *)szSQL, SQL_NTS )]
Software Build: [9.2.0.536]

Is there any workaround to this? I see a setting in config called "Disable workstation account creation" but I don't think we want to go that way if we can help it.

Thanks.

[#2]

Are they using integrated login? Are they logged on to the machine as themselves? If they're new workstations, have they been registered correctly? Can any of these users log on at another machine and not encounter the error?

[Ansley_Ingram]

Hi John,

Did you recently upgrade the database server from SQL Server 2000 to a newer version? If so, you may need to drop the dbo.csp_AddDMUser stored procedure from the database. It will be recreated on the next new workstation login and should correct this issue.

The "Disable workstation account creation" option will prevent workstation level logins from being created in the database. Instead, all Thick Client activity will be performed with the 'HSI' account. Setting that option would prevent the error you are seeing but it would just be masking the real issue.

Ansley

[John_Anderson4]

Yes we did upgrade it fairly recently from SQL 2000 to 2005. We'll give that a shot. Thanks!

[John_Anderson4]

We dropped that stored proc and it did get re-created. But now it doesn't even get to the login screen when we try to log in. On the database server we see an error log like this:

Login failed for user 'WORKSTATIONNAME'. [CLIENT: xx.xx.xx.xx]   Error: 18456, Severity: 14, State: 5. Password missmatch

But there's no user created for that workstation in SQL. We're going to reboot the server, but is there anything else we might need to do?

Thanks!