ASP. NET SQL serverinstallation wizard aspnet_regsql.exe Error

This program is used to register the database of the website, so as to provide Membership, Role, Profile and other functions and the use of control for managing permissions. Try this tool today. First, a database named TESTDB is created in the database, and then a new Login Name (testdb) is created, specifying testdb as the default database of TESTDB. Then the configuration starts.

The configuration process refers to 《aspnet_regsql.exe, but when you select the server and database, enter the correct server name, select SQL server authentication, and enter the new testdb user name and password, click the drop-down box to select the target database. An error message is displayed: (the list of database names in SQL Server cannot be queried. The user's default database cannot be opened, logon fails, and user 'testdb' logon fails)

Oh, by the way, I forgot to authorize this user. This user does not have the logon permission. To ensure that the configuration will not fail due to permission issues, I will grant this user the highest permission for sysadmin. Then run the command again, but the following error is still reported: (the list of database names in SQL Server cannot be queried. The object name 'sysdatabases' is invalid)

This is strange. If I try to use sa, there is no problem. I can display the names of all the databases in the database. Is there still insufficient permissions ?? I know that sysdatabases is a view in the system table and is used to read all database names. So I use testdb to log on to the database and try to execute this command:

Select * from sys. sysdatabases

No problem. The table names can be displayed. This should not be the access permission problem. What should we do?

Solution:With a try attitude, I entered my database name TESTDB in the database drop-down box shown in the figure above, and clicked next. It actually passed ~~~, After the configuration is successful, go to the database and check the 11 tables that are automatically generated starting with asp _ and the attempts and stored procedures.

Conclusion: I don't know where the problem is. Although the problem has not been solved, it is a problem with the configuration tool.