asp.net SQL Server Setup Wizard (aspnet_regsql.exe) Error Resolution An example _ practical tips

Try this tool to configure yourself today. First, a database is established in the database, named TestDB, and a new SQL Server login name (TESTDB) is created and the default database TestDB TestDB is specified. And then it starts to be configured.

The configuration process is referred to theaspnet_regsql.exe tool registration database , but when you select the server and database, fill in the correct server name, select SQL Server Authentication, fill out the new TestDB username and password, Then click the Drop-down box to select the target database, and an error message appears: ( failed to query the list of database names in SQL Server). Unable to open user default database, Login failed, user ' TestDB ' login failed )

Oh oh, yes, forget the authorization, this user does not have login rights, in order to ensure that not because it is a permission problem caused by configuration failure, I give this user sysadmin the highest privileges. It then runs again, but still reports the following error: ( failed to query the list of database names in SQL Server.) Object name ' sysdatabases ' is invalid )

This is strange, I tried to try SA, there is no problem, you can display the database of all the names of the database, or not enough permissions?? I know sysdatabases is a view in the system table that reads all the database names, and then logs on to the database with TestDB, trying to execute this command:

SELECT * FROM Sys.sysdatabases

No problem, you can show the name of each table ah, it should not be the issue of access rights. Then what?

Solution: Holding a try attitude, I in the diagram above the database that Drop-down box, directly fill out my database name: TestDB, click Next, unexpectedly passed ~ ~ ~, after the successful configuration, to the database to see, there are automatically generated by the 11 to Asp_ The beginning of the table and those attempts and stored procedures.

Conclusion: Do not know where the problem is, although not solve the "problem", but around the past, so it should be the problem of configuration tools.