SQLServer2000 FAQs and Solutions

I. Solve the Problem of file suspension during SQL installation: (1) Click start to run, enter regedit, open the Registry (2), find the directory HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSessionManager (3) delete PendingFileRenameOperations 2: The system prompts that the user logs on

I. Solve the Problem of file suspension during SQL installation: (1) Click start to run, enter regedit, and open the Registry (2) find the HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Session Manager (3) directory, delete PendingFileRenameOperations 2: prompt due to login at SQL server startup

I:SolutionFiles suspended during SQL InstallationProblem:

(1) Click start to run and enter regedit to open the registry.

(2) Locate the HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/Session Manager directory.

(3) Delete "PendingFileRenameOperations"

Ii. When SQL server is started, the system prompts that the service cannot be started due to login failure.

When installing SQL Server, the default logon user is used as the account for starting the SQL Server service (for standalone that you use, it is usually administrator ), when the user changes the user name (for example, someone prefers to change administrator to admin) or the password, the server is started again, the error "cannot start the service due to logon Failure" occurs.

SolutionSolution: 1. Change the user password back to the original one, then start service 2, use the service manager of the control panel, find the MSSQLSERVER service, change the startup account information, change it to the changed one, and then start service 3, it is also recommended to create a new user dedicated to starting the SQL Server service. This user is used to start SQL Server when installing SQL Server, this avoids the 1069 error caused by frequent changes to the administrator password. If you have installed SQL Server, you can also change the service account information of the MSSQLSERVER service under the service manager of the Control Panel to a user dedicated to SQL service.

Iii. Connection Failed. Check SQL SERVER Registration attributes.

Register again! Right-click your SQLserver group to create SQLserver registration. It turns out that you can delete it !~