ISQL Invalid Password: Password is not long enough

Asked By 1430 points N/A Posted on -
qa-featured

Hi,

I am having a problem with my query to the database.

I was using ISQL to do some queries,

When I got this error that says Invalid password: Password is not long enough.

I pasted below the complete screen shot.

ISQL Error

Could not execute the statement.
Invalid password: Password is not long enough.
SQLCODE=-1044, ODBC 3 State=”28000”
Line 1, Column 1
grant connect to demo identified by deM0

I wonder why I encountered such an error since I used a correct password. I remember days ago there was some database re-structuring, after which we experienced no problem in connecting to the database.

We presumed every thing is running great since no complaint was received, but now an error occurred. I am wondering if the database re-structuring has anything to do with this error.

Please help me with this issue.

SHARE
Best Answer by Santons
Best Answer
Best Answer
Answered By 0 points N/A #123401

ISQL Invalid Password: Password is not long enough

qa-featured
  • Password expiration at SQL Server Native Client OLE DB provider is supported when DBPROPSET_SQLSERVERDBINIT property set and SSPROP_AUTH_OLD_PASSWORD property (type VT_BSTR) are added.
  • Existing "Password" property looks at DBPROP_AUTH_PASSWORD and where new password is stored.
  • Value of property has not been persisted by the provider.  First connection is not used because second connection is made. Connection pool is not used by the provider when property is set. Provider will not use current connection if password is changed successfully.  Old password is stilled existed but becomes invalid.  This property is also cleared by the provider after a new logon.  If old password is retrieved, VT_EMPTY will be returned.
  • You shall change password and if the error still appears, the user account shall be recreated.
Answered By 0 points N/A #123403

ISQL Invalid Password: Password is not long enough

qa-featured

Restructuring of the databases might have caused some information to be misplaced or some configuration settings to be lost.

First try to solve the problem by restarting the database server. If the problem remains the same, get in to the database and check that the user has been given permissions to use the database. For this you can use the command;

Show grant;

The output shows the set of permissions assigned to the relevant user. If the user is not granted proper permissions, this type of error messages come. Simply you can grant all privileges to the user by the command,

Grant all on database_name to user_name.

 

Login/Register to Answer

Related Questions