 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussion Groups Database Servers DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybaseDesktop Databases FileMakerFoxProMS AccessParadoxGeneral General DB TopicsDatabase TheoryRelated Topics Java Development.NET DevelopmentVB DevelopmentMore Topics ... |
Database Forum / DB2 Topics / March 2005SQL22201N - I am unable to Proceed further
All: This is becoming a big problem for us. Whenever we are using control center it asks for the userid/passwd and when we provide the admin userid/passwd we get a error "Administrative Server failed to authenticate SQL22201N with reason code 6." We are unable to use the GUI.. Any help???? The database in on Windows 2000 box. We tried creating new user ids on Windows box and gave dbadm to it and tried, but gave the same error. Thanks. Does your userid/passwd work locally...ie is this password error ONLY with control center or do you see it in other places? -B db2s...@yahoo.com wrote: > All: > [quoted text clipped - 12 lines] > > Thanks. when I use control center or other things, the userid/password works fine. Well, there are limitations on the length of the password in DB2...8 characters is the max in DB2...I ran into this not to long ago on Linux. But this wouldn't explain why it works in other places. How long is the passwd? User id is: 8 characters Password is: 7 characters When I use Control Center and connect to the database it throws me this error, and If I cancel the error message, I am able to proceed, till the next command and once again get it. > User id is: 8 characters > Password is: 7 characters > > When I use Control Center and connect to the database it throws me this > error, and If I cancel the error message, I am able to proceed, till > the next command and once again get it. I've encountered this problem before and the reason was believed to be a security setting within Windows. We never solved this condition because we ended up using terminal services and CC on that machine so stopped encountering the problem. I believe it has to do with being able to run services as a different user or something along those lines.  SignatureRob Wilson |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.