![]() | ![]() |
Home |
|
|
Troubleshooting and Error Messages Guide |
|
| Chapter 3 Error Message Writeups |
|
| Initialization Errors |
|
| Error 1623 |
21
Warning: dataserver -p option fails. Please check for state '%d' to see where it fails.
This error occurs when Adaptive Server is unable to create a new password for a user with "sso" role in response to the dataserver command with the -p option.
There are three possible states:
State | Meaning |
1 | Login passed with the -p option does not exist in syslogins. |
2 | Login exists but does not have the "sso" (system security officer) role. |
3 | Call to the routine that sets the passwords failed. This routine generates its own errors to help you diagnose the problem. |
The actions for recovering from Error 1623 are listed below, by state.
If you did not remove "sso" role from the "sa" login, use "sa" in your dataserver command in your runserver file. If you did remove "sso" role from the "sa" login, choose the appropriate option below.
If you can, log into Adaptive Server as any user.
Determine which login names have "sso" role:
1> use master 2> go
1> select l.name, s.name from sysloginroles slr, 2> syslogins l,syssrvroles s 3> where slr.srid = 1 and slr.suid = l.suid and 4> slr.srid = s.srid 5> go
If you cannot log into Adaptive Server as any user, and you have a historical dump of the master database that includes a user with the "sso" role and for which you know the password, create a new master device, load that dump and determine whether you can log into it. Refer to "master Database Is Corrupt and Adaptive Server Starts" and read "Valid Dump of the master Database Exists"for instructions on how to re-create your master database.
If you cannot log into Adaptive Server as any user and do not have a historical dump of the master database, refer to "master Database Is Corrupt and Adaptive Server Starts" in the System Database Recovery chapter and read "Valid Dump of the master Database Does Not Exist" for instructions on how to re-create your master database.
Other error messages will be listed. Follow the directions in this manual for recovering from those errors. If no directions exist, call Sybase Technical Support.
All versions
|
|