SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


2008 Subscription Error


2008 Subscription Error

Author
Message
Joey Braaten
Joey Braaten
SSC Journeyman
SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)

Group: General Forum Members
Points: 77 Visits: 137
Recently, we migrated two instances of RS 2005 to RS 2008. In one of the instances we encounter the following error when clicking 'OK' to create/modify a report subscription.

An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database. (rsReportServerDatabaseError) Get Online Help Invalid object name 'ReportServerTESTTempDB.dbo.ExecutionCache'.

Note: We have change the name of this instance. Thus, the object referred to above, is from the 2005 database. Whatever action is occuring to use this object, it should be looking for 'ReportServerStagingTempDB.dbo.ExecutionCache'

Was it a mistake to change the names? How might we be able to resolve this?

I'm more than willing to provide more information if necessary. Any help provided will be much appreciated. I thank you in advance.

Joey
Joey Braaten
Joey Braaten
SSC Journeyman
SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)

Group: General Forum Members
Points: 77 Visits: 137
We found the root cause of the problem and a solution.

There exists a trigger, Schedule_UpdateExpiration, on the ReportServer.Schedule table that references the "TempDB" dbo.ExecutionCache table. We altered the trigger to point to the table with the appropriate fully qualified name.

So far we have yet to notice any other objects that point to the old db name, thus everything is working properly. However, we will keep our fingers crossed.

The thread at the following link was a big help.

http://www.sqlservercentral.com/Forums/Topic553765-147-1.aspx#bm670251
Ananth Hegde
Ananth Hegde
Forum Newbie
Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: General Forum Members
Points: 5 Visits: 26
Thanks Soo Much. I had a similar issue and got around it using the above approach
WebTechie
WebTechie
Right there with Babe
Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)Right there with Babe (743 reputation)

Group: General Forum Members
Points: 743 Visits: 973
Excellent!!!!

I had the same issue and just found this thread. I changed the name in the trigger to reference the new server and I am back in business.
ProKelly
ProKelly
SSC-Enthusiastic
SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)SSC-Enthusiastic (165 reputation)

Group: General Forum Members
Points: 165 Visits: 588
Frustrating. Reading through this thread a smile grew on my face as I realised I had found the resolution to my issues.

Alas not. I have exactly the same problem as those mentioned here, but not the same reason. I have not changed instance names etc. Indeed this has occured on a deployment that has been working for months before. I left to go on paternity leave for 2 weeks, returned to find that I could not amend any subscriptions, and whilst the job in SA appeared to be running properly, no reports were being emailed out.

I get the same message as others here. I did check, for happenstance, to see if my triggers had changed, but mine do reference the correct locations etc.

I don't hold out much hope, but if anyone can help with that i'd be eternally greatful.

thanks.
Dattatrey SIndol
Dattatrey SIndol
Grasshopper
Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)Grasshopper (14 reputation)

Group: General Forum Members
Points: 14 Visits: 186
Hi There,

We had a similar problem and when we analyzed the issue we found that there were two different SQL Agent Jobs with the same name assiciated with the same schedule. When we deleted those SQL Agent Jobs & Re-Created the Schedule, it solved the problem.

Hope it helps!

Dattatrey Sindol
Blog: Datta's Ramblings on Business Intelligence 'N' Life

This information is provided "AS IS" with no warranties, and confers no rights.
mbenish245
mbenish245
Forum Newbie
Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)Forum Newbie (8 reputation)

Group: General Forum Members
Points: 8 Visits: 56
Thanks. The database on our 2005 server was RSDB and RSDBTemp, and we renamed the ReportServer and ReportServerTempDB on 2008, and we got this problem. It worked. Thanks!
fcortezs-781196
fcortezs-781196
Forum Newbie
Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: General Forum Members
Points: 5 Visits: 53
Thanks so much!!!
jmapledoram
jmapledoram
Grasshopper
Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)Grasshopper (11 reputation)

Group: General Forum Members
Points: 11 Visits: 34
Completely different cause and resolution to this problem for me:


When I grant sysadmin to my SSRS login it resolves the issue (obviously not a solution). Double-triple-quadruple checked all RSExec role permissions. All correct. Grasping at straws for hours. Finally noticed the ownership on all of the subscription jobs was odd. It was owned by a domain user account that no longer exists.


Several weeks ago we had switched the service account for SSRS to a new AD account (new naming convention, old account deleted). I cannot find any documentation from MS regarding updating ownership of subscription / jobs when modifying the SSRS Service account. Regardless, changing the ownership to = the new AD account resolves the issue.


Seems to me, this is a deficiency in SSRS config manager or to say the least, lacking / undocumented feature. Maybe I'm just a silly DBA and this should be a no-brainer. Seems to me when you log into the config manager and change the user account, you should be forced to do this via a dbo / sys admin user on the SQL Server. It should then automatically change the ownership for you. Angry
malokej 15917
malokej 15917
Grasshopper
Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)

Group: General Forum Members
Points: 13 Visits: 14
Did you set the account you want to use to set the subscription in Reporting Services Configurations Manager, if not do so. It worked for me
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search