March 23, 2012 at 5:10 am
I'm a little lost on this one. We got everything to work correctly in our Dev, Test, QC environments, but Production is giving us fits.
We have to implement a password change for our SSRS Account (Domain User Account only used for SSRS services). The Server Guy (TSG) managed it successfully in other environments by going through the Reporting Services Configuration Manager, which is what one is supposed to do. One one of the Prod application servers, he goes to Database, Change Credentials, and hits Apply. It generates the rights scripts, then, when applying the connection rights, it errors out. This is the error:
System.Data.SqlClient.SqlException: User does not have permission to perform this action.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.ReportingServices.Common.DBUtils.ApplyScript(SqlConnection conn, String script, ICommandWrapperFactory commandWrapper)
at Microsoft.ReportingServices.Common.DBUtils.ApplyScript(String connectionString, String script)
at ReportServicesConfigUI.SqlClientTools.SqlTools.ApplyScript(String connectionString, String script)
When he goes to Service Account, this is the error he gets:
The report server cannot open a connection to the report server database. The log on failed. (rsReportServerDatabaseLogonFailed) Get Online Help
The report server cannot open a connection to the report server database. The log on failed. (rsInternalError) Get Online Help
Logon failure: unknown user name or bad password. (Exception from HRESULT: 0x8007052E)
Production has 2 app servers, clustered, and the reporting services database is on a third server. The database is accessible by me via SSMS. We cannot reboot the database server as it is not under our control, plus it needs to be up almost 24 x 7 unless we absolutely can prove to management that a reboot is the only option.
One of the app servers (server A) accepts this change, but not server B. It's the same account on both (and the same account as the "old service account"), we're just giving it a new password. We've tried this change by being logged in as under our individual admin accounts, and as being logged in under the service account. My google-fu only finds solutions for problems that are not quite like ours.
Does anyone have any other suggestions on where I could look for solutions, or what we're doing wrong?
March 23, 2012 at 6:32 am
The Server Guy (TSG) managed it successfully in other environments by going through the Reporting Services Configuration Manager, which is what one is supposed to do. One one of the Prod application servers, he goes to Database, Change Credentials, and hits Apply.
Is you Dev or QC clustered too?
And are both going through going through RS Config?
Typically when I have seen this, I change to completely different account, then back, and it clears up.
I don't think I have seen this on 2008, but remember it from 2005.
Kind of ugly when Production breaks.
Nicer for test to do this so you can figure out what to do if it happens in Production.
Good luck!
March 23, 2012 at 6:36 am
Greg Edwards-268690 (3/23/2012)
The Server Guy (TSG) managed it successfully in other environments by going through the Reporting Services Configuration Manager, which is what one is supposed to do. One one of the Prod application servers, he goes to Database, Change Credentials, and hits Apply.
Sorry. My bad. I was going backwards through our notes when I wrote this. He did the Service change first. That didn't work. I recommended trying the Database change to see what happened. That didn't work.
Is you Dev or QC clustered too?
And are both going through going through RS Config?
All three environments (Dev, Test, QC) go through RS Config. But I have to check on the clustering. I know Dev is not clustered. Not sure about the other two environments.
Typically when I have seen this, I change to completely different account, then back, and it clears up.
Like a different domain account? Or Local / Network?
March 23, 2012 at 6:39 am
Brandie Tarvin (3/23/2012)
Greg Edwards-268690 (3/23/2012)
Is you Dev or QC clustered too?
And are both going through going through RS Config?
All three environments (Dev, Test, QC) go through RS Config. But I have to check on the clustering. I know Dev is not clustered. Not sure about the other two environments.
CRAP. Test and QC are not clustered. Which means this is probably a clustering issue. Thing is, SSRS isn't set up under the clustering services, so we can't make the change on the virtual instance.
Anyone have any other thoughts?
March 23, 2012 at 7:11 am
I would use my domain account, then back to the domain service account.
Wish I had some experience with clusters, but I can't even get a good dev environment.
March 23, 2012 at 8:52 am
Thanks, Greg. I'll pass the word along and see if we'll be allowed to try that.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply