请高手啊。。。sa密码忘记了，用网上说的方法，有一台成功了，另一台不成功。
本帖最后由 小凌子 于 2011-09-08 13:21 编辑各位大侠：
公司一台服务器数据库sa密码忘记了，用网上说的方法，在RUN_SERVER文件中加参数-psa ，在一台测试服务器上成功了，
但在另一台失败了，不知道什么原因(两台服务器唯一的区别是数据库版本不一样，成功是sybase 11.92，失败的是sybase 12.56的)，请各位先辈们帮忙。
部份日志具体如下：
00:00000:00000:2010/11/18 11:39:18.03 kernelRegistry keys for event logging are missing.
00:00000:00000:2010/11/18 11:39:18.07 kernelUse license file C:\sybase\\SYSAM-1_0\licenses\license.dat.
00:00000:00000:2010/11/18 11:39:18.09 kernelFailed to log the current message in the Windows NT event log
00:00000:00000:2010/11/18 11:39:18.09 kernelChecked out license ASE_SERVER
00:00000:00000:2010/11/18 11:39:18.09 kernelFailed to log the current message in the Windows NT event log
00:00000:00000:2010/11/18 11:39:18.09 kernelAdaptive Server Enterprise Edition
00:00000:00000:2010/11/18 11:39:18.09 kernelFailed to log the current message in the Windows NT event log
00:00000:00000:2010/11/18 11:39:36.51 kernelUsing config area from primary master device.
00:00000:00000:2010/11/18 11:39:36.73 serverConfiguration Error: Configuration file, 'C:\sybase\NG.cfg', does not exist.
00:00000:00000:2010/11/18 11:39:36.75 kernelFailed to log the current message in the Windows NT event log
00:00000:00000:2010/11/18 11:39:36.76 kernelWarning: A configuration file was not specified and the default file 'C:\sybase\NG.cfg' does not exist. SQL Server creates the default file with the default configuration.
00:00000:00000:2010/11/18 11:39:36.76 kernelFailed to log the current message in the Windows NT event log
00:00000:00000:2010/11/18 11:39:36.79 kernelWarning: Using default file 'C:\sybase\NG.cfg' since a configuration file was not specified. Specify a configuration file name in the RUNSERVER file to avoid this message.
00:00000:00000:2010/11/18 11:39:36.79 kernelFailed to log the current message in the Windows NT event log
00:00000:00000:2010/11/18 11:39:36.93 kernelUsing 100000 file descriptors.
00:00000:00000:2010/11/18 11:39:37.00 kernelAdaptive Server Enterprise/12.5.2/EBF 11798/P/NT (IX86)/OS 4.0/ase1252/1831/32-bit/OPT/Fri Apr 09 04:15:03 2004
00:00000:00000:2010/11/18 11:39:37.00 kernelConfidential property of Sybase, Inc.
00:00000:00000:2010/11/18 11:39:37.00 kernelCopyright 1987, 2004
00:00000:00000:2010/11/18 11:39:37.00 kernelSybase, Inc.All rights reserved.
00:00000:00000:2010/11/18 11:39:37.00 kernelUnpublished rights reserved under U.S. copyright laws.
00:00000:00000:2010/11/18 11:39:37.00 kernel
00:00000:00000:2010/11/18 11:39:37.00 kernelThis software contains confidential and trade secret information of Sybase,
00:00000:00000:2010/11/18 11:39:37.00 kernelInc. Use,duplication or disclosure of the software and documentation by
00:00000:00000:2010/11/18 11:39:37.00 kerneltheU.S.Governmentissubjecttorestrictions set forth in a license
00:00000:00000:2010/11/18 11:39:37.00 kernelagreementbetweentheGovernmentandSybase,Inc.orotherwritten
00:00000:00000:2010/11/18 11:39:37.00 kernelagreementspecifyingtheGovernment's rights to use the software and any
00:00000:00000:2010/11/18 11:39:37.00 kernelapplicable FAR provisions, for example, FAR 52.227-19.
00:00000:00000:2010/11/18 11:39:37.00 kernelSybase, Inc. One Sybase Drive, Dublin, CA 94568, USA
00:00000:00000:2010/11/18 11:39:37.00 kernelASE booted on Windows 2000 build 2195 Service Pack 4.
00:00000:00000:2010/11/18 11:39:37.00 kernelUsing 'C:\sybase\NG.cfg' for configuration information.
00:00000:00000:2010/11/18 11:39:37.00 kernelFailed to log the current message in the Windows NT event log
00:00000:00000:2010/11/18 11:39:37.00 kernelLogging ASE messages in file 'C:\sybase\ASE-12_5\install\NG.log'.
00:00000:00000:2010/11/18 11:39:37.01 kernelInitializing MSDTC Connection
00:00000:00000:2010/11/18 11:39:37.01 kernelFailed to log the current message in the Windows NT event log
00:00000:00000:2010/11/18 11:39:38.06 kernelMSDTC Initialization succeeded
00:00000:00000:2010/11/18 11:39:38.06 kernelFailed to log the current message in the Windows NT event log
00:00000:00000:2010/11/18 11:39:38.06 kernelPlatform TCP network is forced to IPv4-only.
00:00000:00000:2010/11/18 11:39:38.06 kernelFailed to log the current message in the Windows NT event log
00:00000:00000:2010/11/18 11:39:38.06 kernelSQL Server booted with TCP_NODELAY enabled.
00:00000:00000:2010/11/18 11:39:38.06 kernelFailed to log the current message in the Windows NT event log
00:00000:00000:2010/11/18 11:39:38.06 kernel*** WARNING ******************
00:00000:00000:2010/11/18 11:39:38.06 kernelFailed to log the current message in the Windows NT event log
00:00000:00000:2010/11/18 11:39:38.06 kernelOperating system may favor the system cache when memory is at a premium.
To disable this warning, set the registry parameter 'LargeSystemCache' to 0 in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management.
00:00000:00000:2010/11/18 11:39:38.06 kernelFailed to log the current message in the Windows NT event log
00:00000:00000:2010/11/18 11:39:38.06 kernelSQL Server NT process id is 0x910.
00:00000:00000:2010/11/18 11:39:38.06 kernelSQL Server was started as a Service.
00:00000:00000:2010/11/18 11:39:38.09 kernelSSL Plus v3.1.5 security modules loaded successfully.
00:00000:00000:2010/11/18 11:39:38.09 kernelFailed to log the current message in the Windows NT event log
00:00000:00000:2010/11/18 11:39:38.09 kernelNetwork and device connection limit is 99992.
00:00000:00000:2010/11/18 11:39:38.17 serverNumber of blocks left for proc headers: 3232.
00:00000:00000:2010/11/18 11:39:38.17 serverProc header memory allocated 1616 pages for each per engine cache
00:00000:00000:2010/11/18 11:39:38.18 serverSize of the 8K memory pool: 8192 Kb
0000:00001:2011/09/07 09:55:34.96 serverRecovery has restored the value of 'local async prefetch limit' for '64K' pool in 'default data cache' from '80' to 'DEFAULT'.
00:00000:00001:2011/09/07 09:55:34.96 kernelFailed to log the current message in the Windows NT event log
00:00000:00001:2011/09/07 09:55:34.96 serverRecovery has restored the value of 'local async prefetch limit' for '8K' pool in 'default data cache' from '80' to 'DEFAULT'.
00:00000:00001:2011/09/07 09:55:34.96 kernelFailed to log the current message in the Windows NT event log
00:00000:00001:2011/09/07 09:55:35.89 serverRecovery has restored the original size for '64K' pool and '8K' pool in 'default data cache'.
00:00000:00001:2011/09/07 09:55:35.89 kernelFailed to log the current message in the Windows NT event log
00:00000:00001:2011/09/07 09:55:35.90 serverRecovery complete.
00:00000:00001:2011/09/07 09:55:35.90 kernelFailed to log the current message in the Windows NT event log
00:00000:00001:2011/09/07 09:55:35.90 kernelReenlistment of DTC Transactions Complete
00:00000:00001:2011/09/07 09:55:35.90 kernelFailed to log the current message in the Windows NT event log
00:00000:00001:2011/09/07 09:55:35.90 serverSQL Server's default unicode sort order is 'binary'.
00:00000:00001:2011/09/07 09:55:35.90 kernelFailed to log the current message in the Windows NT event log
00:00000:00001:2011/09/07 09:55:35.92 serverSQL Server's default sort order is:
00:00000:00001:2011/09/07 09:55:35.92 server 'noaccents_iso_1' (ID = 54)
00:00000:00001:2011/09/07 09:55:35.92 serveron top of default character set:
00:00000:00001:2011/09/07 09:55:35.92 server 'iso_1' (ID = 1).
00:00000:00001:2011/09/07 09:55:35.92 kernelFailed to log the current message in the Windows NT event log
00:00000:00001:2011/09/07 09:55:35.92 serverMaster device size: 120 megabytes, or 61440 virtual pages. (A virtual page is 2048 bytes.)
00:00000:00001:2011/09/07 09:55:35.92 kernelFailed to log the current message in the Windows NT event log
00:00000:00004:2011/09/07 09:55:43.54 kernelshutdownproc: shutting down SQL Server!
00:00000:00004:2011/09/07 09:55:43.54 kernelFailed to log the current message in the Windows NT event log
00:00000:00004:2011/09/07 09:55:43.59 kernelXP Server is not running.
00:00000:00004:2011/09/07 09:55:43.59 kernelFailed to log the current message in the Windows NT event log
00:00000:00004:2011/09/07 09:55:43.62 serverSQL Server shutdown by request.
00:00000:00004:2011/09/07 09:55:43.62 kernelFailed to log the current message in the Windows NT event log
00:00000:00004:2011/09/07 09:55:43.62 kernelueshutdown: exiting
00:00000:00004:2011/09/07 09:55:43.62 kernelFailed to log the current message in the Windows NT event log 光见shutdown没见启动 本帖最后由 小凌子 于 2011-09-07 14:28 编辑
回复 2# Eisen
运行后一直停止在这个状态，以上日志是前部分和后部分，太大无法上传，中间部分。
在”服务”，是没有启动，手工启动后报错“1067错误，服务无法启动”
把原来备份的RUN_server文件拷到原目录下后，服务又可以启动了。这是怎么回事？
请教各路高手，具体怎么办呢？
通过另外一个用户登录查看系统表syslogins,发现sa前后前后两个密码是发生了变化，这样看来，新密码是随机产生了，但就是看不到。
而且在服务器上“服务”里查看SERVER没有启动，但我通过数据库的客户端怎么可以连接数据库呢？ 不是SA密码可以修改的吗， 回复 4# wfcjz
就是sa密码不记得了啊 嗯。看样子是Win平台，你不要通过Service的方式去启动，走dos窗口命令行的方式去启动，就能看见了。 本帖最后由 小凌子 于 2011-09-07 16:58 编辑
回复 6# Eisen
dos窗口命令行的方式去启动？
具体怎么写？
是运行bin下的sqlsrvr.exe 文件吗？
这样操作了，但还是不行
具体如下：
C:\sybase\ASE-12_5\bin>sqlsrvr.exe -sng
00:00000:00000:2011/09/07 16:57:54.87 kernelUse license file C:\sybase\SYSAM-1
_0\licenses\license.dat.
00:00000:00000:2011/09/07 16:57:54.87 kernelFailed to log the current message
in the Windows NT event log
00:00000:00000:2011/09/07 16:57:54.87 kernelChecked out license ASE_SERVER
00:00000:00000:2011/09/07 16:57:54.87 kernelFailed to log the current message
in the Windows NT event log
00:00000:00000:2011/09/07 16:57:54.89 kernelAdaptive Server Enterprise Edition
00:00000:00000:2011/09/07 16:57:54.90 kernelFailed to log the current message
in the Windows NT event log
00:00000:00000:2011/09/07 16:57:54.93 kernelbasis_dlock: file 'C:\sybase\data\
master.dat' already in use by a SQL Server
00:00000:00000:2011/09/07 16:57:54.93 kernelFailed to log the current message
in the Windows NT event log
00:00000:00000:2011/09/07 16:57:54.95 kernelkdconfig: unable to read primary m
aster device
00:00000:00000:2011/09/07 16:57:54.96 kernelFailed to log the current message
in the Windows NT event log
00:00000:00000:2011/09/07 16:57:54.98 serverkiconfig: read of config block fai
led
00:00000:00000:2011/09/07 16:57:55.00 kernelFailed to log the current message
in the Windows NT event log
C:\sybase\ASE-12_5\bin> 直接用鼠标双击那个run什么什么的bat。 本帖最后由 小凌子 于 2011-09-07 17:10 编辑
回复 8# Eisen
前辈，我开始就是运行那个run_***.bat的啊，出现如问题所示的情况啊，一直没有显示密码啊
总是提示Failed to log the current message in the Windows NT event log
这是什么怎么回事啊
通过客户端可以连接，应该是启动了，是不是操作系统的问题啊 哦。windows的event log满了，你去"My computer"上点右键，选"Manage"，然后在里面找到event log清掉，应该就可以了……