This fix to the issue was to set the database to "Trustworthy"

alter database DatabaseName set Trustworthy on

I renamed the folder that was WAY long to something shorter and simpler then mapped the drive. That fixed the problem.

I tried that. Thanks.

So here's what did and did not work:

Didn't work:

1. Add full backup

2. Restore with NoRecovery

3. Add differential backup

What did work:

1. ...

I was able to successfully restore a smaller database (12GB). I'll have to wait to try this larger one (about 300GB) when we have to do another refresh. I...

The header file on each backup contains the LSN numbers. Querying the msdb database also produces matching LSN numbers.

Thanks to everyone who replied. Our system administrators are looking into the SPN issue. The SPN is not registering correctly.

My guess was also the SPN being registered. I do have our System Admin looking into that option.

I am using a completly different service account that is a local administrator on the windows server and is a member of the SQL Administrators group that has sysadmin on...

The problem turned out to be really simple. I did not enable TCP/IP on the SQL Express Server.

When I tried to install the Service Pack, I received the same error. Our System Admins did the following to rebuild the WMI database. This corrected all of...

I'll try that. My only problem is that this a PROD system so I need to schedule an outage. Also, I just realized that I have tested SP3...

I looked at the file. All of the documentation I have found on this error said that there would be two report instances in the mof file and that...

No it is a default instance. The server recently received all Windows Updates and the latest Service Pack. I believe that's when it broke.

No. When I open Reporting Services Configuration Manager, and attempt to connect to the Report Server, I get the error and the application closes.