"key not valid for use in the specified state"

I upgraded to Windows 2003 SP1, and now I keep getting the message: "Key not
valid for use in the specified state" on any page of the Report Manager that
I try to access.
I've tried deleting and recreating the keys with no success. The search that
I've done in the MS Site have all pointed me to EFS errors. Anybody have any
ideas where I should go next?
Thanks.
DerrickI had that problem 6 months ago. After opening a support call with MS
and after many attempts to fix it, in the end the only process that
worked was to completely erase all traces of RS from the system and then
do a fresh install. Below is a list of the steps to take (note
especially step 5 - this was the deciding factor for me on the reinstall
fixing the problem)
1. Backup your existing solution files, such as .sln, .rdl, .rds files.
2. If the machine is a domain controller, do not install Reporting
Service on it. Use another machine instead.
3. Run Setup.exe of the SQL Server 2000 Reporting Services to launch the
Setup window.
4. Click "Remove Microsoft SQL Server 2000 Reporting Service" button in
the Setup window.
5. From Explorer, navigate to x:\Documents and Settings\<service
account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20 and delete all
files located in this folder.
6. Delete all Reporting services related files under this folder
"x:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services" if present
7. Delete all Reporting Services Virtual Directories (ReportServer and
Reports) from IIS Manager if present.
8. Delete all Reporting Services Databases (ReportServer and
ReportServerTempDB) from SQL Server Enterprise Manager if present.
9. Re-boot the machine and log on using an Administrators group account.
10. Reinstall SQL Server 2000 Reporting Service on the machine.
brian smith
Derrick Powell wrote:
> I upgraded to Windows 2003 SP1, and now I keep getting the message: "Key not
> valid for use in the specified state" on any page of the Report Manager that
> I try to access.
> I've tried deleting and recreating the keys with no success. The search that
> I've done in the MS Site have all pointed me to EFS errors. Anybody have any
> ideas where I should go next?
> Thanks.
> Derrick
>

"Failed to generate a user instance of SQL Server" - Redux

I have SQL Server 2005 SP1 Dev Edition installed on my laptop along with Visual Web Developer 2005. I installed SQL Server Express 2005 SP1. I then created a new web site using the Club Web Site template.

I did the recommended initial build to get the Membership database installed and got an error page (http://localhost:1667/WebSitesVB2/):

SQLExpress database file auto-creation error:
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.

There were 4 recomme4ndations from the error page. I have met three of them: (1) the AppDaa folder that was created when I used the Club Web Site template; (2) my machine's ASPNET user set up with full control permissions on the APP Data Folder; (3) SQL Server Express successfully installed on my machine.

The 4th recommendation from the error page is "The process identity for the web server account must have a local user profile. See the readme document for details on how to create a local user profile for both machine and domain accounts. ". I have no idea of how to do this or how/where to find the elusive the "readme" file.

I am at a loss as to what to do next. I have spent the day going over forums on this error and none seem to provide consistent or relevant answers.

Try to remove User Instance=true from your connection string, if you don't need to generate a user instance at runtime. For more information about the user instance attribute, you can refer to:

http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring(VS.80).aspx|||

Changed userinstance = TRUE to userinstance=FALSE. Same result - failure to generate userinstance.

Is it possible that there is some setting in VWD that provides a connection string for the ASPNET db that is to be created? The only connection string in the WebConfig from the original template is the one for the ClubSite DB. There is none for the ASPNET db (because the template does not provide the ASPNET DB.

After 2 tries, I still get this error and when I look at the database explorer, there is only one DB file: Club.MDF.

Anyone else have any answers?

|||

I probably should have included this stack trace:

Stack Trace:

[SqlException (0x80131904): Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +115 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +346 System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +3244 System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +56 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +1084 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +272 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +355 System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +91 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +115 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +122 System.Data.SqlClient.SqlConnection.Open() +229 System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +110[HttpException (0x80004005): Unable to connect to SQL Server database.] System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +181 System.Web.Management.SqlServices.SetupApplicationServices(String server, String user, String password, Boolean trusted, String connectionString, String database, String dbFileName, SqlFeatures features, Boolean install) +167 System.Web.Management.SqlServices.Install(String database, String dbFileName, String connectionString) +46 System.Web.DataAccess.SqlConnectionHelper.CreateMdfFile(String fullFileName, String dataDir, String connectionString) +681

---

|||Sorry I forgot to mention: there is a connection string named LocalSqlServer, which is used by .NET 2.0 built-in providers (Profile, Membership, RoleManager, etc.). You can override it and try again, for details you can refer to:
Configuring ASP.NET 2.0 Application Services to use SQL Server 2000 or SQL Server 2005