Sorry folks for reposting this if it's been posted; a general search didn't find the answer I was looking for.

Here's the setup:

• Windows Server 2008 R2
• IIS 7.5
• SQL 2008 R2 (default instance)

Here's the situation:

Lost my host server a while back, and had to rebuild my VMs.  I had a backup of the .mdf and .log files as well as the directory structure for the website.

I added the .mdf/.log file to SQL 2008 R2, and created a new website in IIS 7.5.

SQL seems to be acting fine (i can log onto it just fine, it's not throwing errors)
IIS seems fine, no errors.

However, when I launch http://www.mysite.com/setup/default.aspx, I'm getting the following errors:

Probing system...
File system permissions ok.

The system cannot connect to the MSSQL database. Please check your connection string.

System.Data.SqlClient.SqlException: Login failed for user 'mpuser'. at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at mojoPortal.Data.DBPortal.DatabaseHelperGetConnectionError(String overrideConnectionInfo)

What I've done:

The mpuser is a local user account on my server.  In SQL, I've created a Login for that user "SERVER\mpuser" and added him to the database security and given him the default schema of [dbo].

I've tried using sa, tried using a domain account.  I've tried all sorts of combinations of the roles and schemas to grant permissions.

Looking at the docs, I only saw that you had to give [dbo] access, but nothing really calls out any differences with 2008R2 (if there are any).

Am I missing something? Is there another log where I could provide further info?

Thanks,

Chris