Actually, here's an interesting update. I can successfully login to the company in MR in the test environment if I use the production "sa" password! Now, just to make sure that the test environment's MR is not pointing to the production SQL instance, I afterward opened MR in production and created a "dummy" report. Then, I logged back in to MR in test, where I did not see that new dummy report. So, MR in test is obviously not pointing to SQL in production. Before all of this, as I was in the Configuration Console on test, I was prompted for credentials in case I needed to import companies. It would not let me use my Windows Authenticated sysadmin credentials. So, I successfully used the test environment's "sa" credentials where the password for "sa" in test is different from that in production. So, there must be something in the restored ManagementReporter database in test that contains credentials used in production. Is there another script in test that I need to run against this database? Thanks! John
↧