The ScopeSET Support and Community Portal
View all tags
Tags:    No tags associated yet.
First off, you can log in as any SSO role user and have them reset the 'sa' password for you.

Being life and life being not always so simple we may not always have an SSO role handy (or configured)

So, we resort to the following:.

  1. Edit the 'runserver' file. By default it's in the $SYBASE_HOME/install directory
  2. Add "-psa" (for password 'sa') to the end of the command line. (I have noticed that this DOES NOT work in windows unless it's the FIRST param on the command line)
  3. Save file and reboot server. You 'may' have to use Unix 'kill' or Windows 'End Task' but I suggest that as a last resort.
  4. While server is restarting, watch the console. You will see something like. "New SSO Password for sa:akshentneksla". If you miss it in the console, check the error logs. It will also be written there.
  5. Re-Edit the runserver file once the server has 'booted' and remove the "-psa". If you don't, the next time the server is restarted it will RESET the sa password again and you're screwed all over. :)
  6. Login as 'sa' using the new password (In this case: akshentneksla).
  7. use sp_password to change the password to something you will remember.
  8. (OPTIONAL) reboot server to make sure all is nice and neat. (See Note #2 below!).

Some Notes:

1- People have claimed that they are still not able to login with this new password. If that is the case make sure that the 'sa' account is not locked. You can do this by setting a TRACEFLAG to "4044". This is a boot time traceflag that allows 'sa' to login even if his/her account is locked.

2- Windows services do not always call the proper .bat file when they startup your service. What happens is that you may edit the 'runserver' .bat file and yet not have your password reset if you stop/start the service. This is because the sybase installer references the 'sqlsvr.exe' executable with parameters DIRECTLY. (I have not, as of this writing been able to figure out how to change this.) So, stop the service, do all the edits/steps I mention above, but make sure you take STEP 8 and restart the server VIA THE SERVICES WINDOWS, then you will be sure that your server will start properly on subsequent executions.