You’re offline. This is a read only version of the page.
Hello:
We are on GP 2013 R2 (12.00.1920) and Management Reporter 2012 CU13 with the Legacy Provider.
Last night, our ManagementReporter database was taking up too much space on our SQL server. So, our DBA either moved the database to a new drive on the same server or to a different server.
Anyway, after I turned off the two services for the app on our main Terminal Server, he was able to conduct this move just fine. He, then, told me that everything should be fine.
In fact, this morning, I logged on to the Terminal Server where the app's Configuration Console exists, using the Windows credentials of the app's Service Account.
I was able to get into the Configuration Console, without issues. Afterward, I was able to get into Report Designer and Report Viewer and review reports without issues.
It is true that, when I first went into the Report Designer, I was prompted for credentials to use to choose a default company. Since I'm a Management Reporter Administrator, I usually use "sa" on such rare occasions. In any case, I was able to login to the default company and even login to a reporting tree that references all of our companies by entering the sa credentials once again.
Here's the problem. After logging off of the Terminal Server as the Management Reporter service account "user", I logged back on to the Terminal Server using my own Windows credentials.
Again, I'm both a Management Reporter administrator and an administrator on the Terminal Server. When I opened Report Designer, I was prompted for credentials for accessing the default company. This prompt was expected.
So, I entered the sa credentials, which I always use. But, upon doing so, I was told that there was an error upon logging in and that I needed to contact the system administrator. In fact, the sa account became locked out, because of this. I could not even log in to GP, afterward, as sa.
I, then, had to contact the DBA and get the "sa" account unlocked, which he did.
I don't dare try logging into the app as "sa", until I can figure out why this happened.
Why did this happen? In order for Report Designer to acknowledge my Windows user's entry of sa credentials in light of the database issue, do I need to open the Configuration Console and do something?
I'm pretty shocked that this happened. Why would the sa credentials work for one user but not for another?
Thank you! Much appreciated!
John
*This post is locked for comments
I have the same question (0)
Hello:
I figured this out. I did have to go into the Configuration Console and re-run the import of companies. Prior to this import, the Console prompted me for the "sa" credentials which I successfully entered.
Anyway, after conducting this import in the Console, I was able to afterward open Management Reporter's Report Designer with my own Windows credentials, rather than those of the app's Service Account.
In fact, the app did not even prompt me for any credentials. As normal, it simply let me in. :)
John
Share
Report
All responses (
Answers (
2