Report viewer send print job with a large memory

i am using reporting service 2005 and report viewer from vs.net 2005.

when i send a print job from report view to HP Laserjet 1320, there print job is actually abt 20MB for 20 pages.

it happends that the printer will hav problem printing the print job or just hang there..

is there any way to resolve it?

There was an issue with 2005 that the print control did not get updated correctly if you had the 2000 print control. Is it possible that you have the 2000 print control on the client? If so, you can clear the control from the client by going to Tools->Internet Options->Settings->View Objects in IE, then delete the RSPrintControl. The next time you go to use the print control a new one should be downloaded.

Report Server Subscriptions - Job Owner

Hi,
I am trying to setup a subscription but I keep running into problems.
I setup the subscription fine, I see that it creates a job in SQL
Server. It shows a specific domain account as the owner and I can't
figure out why. The problem is that this account is in a different
domain and it's having problems authenticating when it runs. I did use
this account for the services and whatnot when I originally set it up,
but I've changed the account that SQL Server and SQL Server Agent run
under, but it still uses this account as the owner. The only other
thing I can think of is that the database owner of
SystemCenterReporting is still this account. Is this why it's listing
this account as the owner of the job? Where else could it be?
Thanks,
Bill"zinck74" <zinck74@.hotmail.com> wrote in message
news:1105995617.343495.223770@.f14g2000cwb.googlegr oups.com...
> Hi,
> I am trying to setup a subscription but I keep running into problems.
> I setup the subscription fine, I see that it creates a job in SQL
> Server. It shows a specific domain account as the owner and I can't
> figure out why. The problem is that this account is in a different
> domain and it's having problems authenticating when it runs. I did use
> this account for the services and whatnot when I originally set it up,
> but I've changed the account that SQL Server and SQL Server Agent run
> under, but it still uses this account as the owner. The only other
> thing I can think of is that the database owner of
> SystemCenterReporting is still this account. Is this why it's listing
> this account as the owner of the job? Where else could it be?
> Thanks,
> Bill

I have no idea about Reporting Services, but the SQL job owner is the SQL
login which creates the job. If RS is running under a certain domain account
to access MSSQL, then I guess that would be the account which owns the
subscription job.

The MS RS Deployment Guide is a bit vague - it seems to recommend a domain
account for the RS service, but doesn't say exactly what permissions it
needs:

http://www.microsoft.com/technet/pr...oy/rsdepgd.mspx

You might get a better response in microsoft.public.sqlserver.reportingsvcs.

Simon|||Thanks. The answer ended up being running the rsconfig.exe utility.
Didn't know this existed, but the account used with this is who the
owner is of the job.

Report Server job failed

Hi all,
I'm getting failed Report Server jobs. How do I find out what report it is,
user and, more information?
The only information I see is a Step Name which is a long number and then a
message that says this:
"Executed as user: MyDomain\AdminPass. Could not locate entry
in sysdatabases for database 'SQLReportServer'. No entry found
with that name. Make sure that the name is entered correctly.
[SQLSTATE 08004] [Error 911]. The step failed.
thanks
gvDid you check the log files (or is that where this error came from)
located in C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\LogFiles\?
Devin
gv wrote:
> Hi all,
> I'm getting failed Report Server jobs. How do I find out what report it is,
> user and, more information?
> The only information I see is a Step Name which is a long number and then a
> message that says this:
> "Executed as user: MyDomain\AdminPass. Could not locate entry
> in sysdatabases for database 'SQLReportServer'. No entry found
> with that name. Make sure that the name is entered correctly.
> [SQLSTATE 08004] [Error 911]. The step failed.
> thanks
> gv|||I did, I see nothing there.
I got this message from Agent job history
thanks
gv
"Devin" <dlosee@.granitelp.com> wrote in message
news:1161275847.753301.134330@.i3g2000cwc.googlegroups.com...
> Did you check the log files (or is that where this error came from)
> located in C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\LogFiles\?
> Devin
> gv wrote:
>> Hi all,
>> I'm getting failed Report Server jobs. How do I find out what report it
>> is,
>> user and, more information?
>> The only information I see is a Step Name which is a long number and then
>> a
>> message that says this:
>> "Executed as user: MyDomain\AdminPass. Could not locate entry
>> in sysdatabases for database 'SQLReportServer'. No entry found
>> with that name. Make sure that the name is entered correctly.
>> [SQLSTATE 08004] [Error 911]. The step failed.
>> thanks
>> gv
>|||Is SQLReportServer the name of the database? The default is just
ReportServer. Do any scheduled reports run successfully? Do you have
it setup as shared schedules or are they individually scheduled per
report?
You can probably tell which report(s) are failing by looking at the
scheduled date/time within SQL Agent and then matching it up with the
scheduled report(s) in Report Manager that run at that time.
It sounds like 1 more schedules are corrupt. I would check all the
scheduled jobs (in SQL Agent) and make sure that each is pointed to the
correct database. If they all are, then you may want to delete and
re-create the scheduled jobs that are erroring (assuming you don't have
that many).
Devin
gv wrote:
> I did, I see nothing there.
> I got this message from Agent job history
> thanks
> gv
>
> "Devin" <dlosee@.granitelp.com> wrote in message
> news:1161275847.753301.134330@.i3g2000cwc.googlegroups.com...
> > Did you check the log files (or is that where this error came from)
> > located in C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> > Services\LogFiles\?
> >
> > Devin
> >
> > gv wrote:
> >> Hi all,
> >>
> >> I'm getting failed Report Server jobs. How do I find out what report it
> >> is,
> >> user and, more information?
> >>
> >> The only information I see is a Step Name which is a long number and then
> >> a
> >> message that says this:
> >>
> >> "Executed as user: MyDomain\AdminPass. Could not locate entry
> >> in sysdatabases for database 'SQLReportServer'. No entry found
> >> with that name. Make sure that the name is entered correctly.
> >> [SQLSTATE 08004] [Error 911]. The step failed.
> >>
> >> thanks
> >> gv
> >|||Thanks alot for your help, I'm very new to Report Server and new as a DBA.
No, it is ReportServer. Yes, many run fine.
I think they are setup individually. Not sure. How would I check?
In the Agent it doesn't say what report? Just has a long number.
When you goto properties in the first tab page in box says this:
"This is a Reporting Services job. Modifying this job could result in
database incomptabilities.
Please use the Report Server UI to update this job."
I'm confused on how to research scheduled jobs in Report Server and make
changes?
Other people have created these. At first looking at the error.
I noticed the name of the database had SQL at the beginning of it instead
of just saying ReportServer. I think this is the problem. But how
do I change it? Goes back to first knowing what Report. How?
How do I relate the long number in SQL agent to a report name in Report
Manger?
thanks again for your help
gv
"Devin" <dlosee@.granitelp.com> wrote in message
news:1161282924.264914.265360@.i3g2000cwc.googlegroups.com...
> Is SQLReportServer the name of the database? The default is just
> ReportServer. Do any scheduled reports run successfully? Do you have
> it setup as shared schedules or are they individually scheduled per
> report?
> You can probably tell which report(s) are failing by looking at the
> scheduled date/time within SQL Agent and then matching it up with the
> scheduled report(s) in Report Manager that run at that time.
> It sounds like 1 more schedules are corrupt. I would check all the
> scheduled jobs (in SQL Agent) and make sure that each is pointed to the
> correct database. If they all are, then you may want to delete and
> re-create the scheduled jobs that are erroring (assuming you don't have
> that many).
> Devin
> gv wrote:
>> I did, I see nothing there.
>> I got this message from Agent job history
>> thanks
>> gv
>>
>> "Devin" <dlosee@.granitelp.com> wrote in message
>> news:1161275847.753301.134330@.i3g2000cwc.googlegroups.com...
>> > Did you check the log files (or is that where this error came from)
>> > located in C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
>> > Services\LogFiles\?
>> >
>> > Devin
>> >
>> > gv wrote:
>> >> Hi all,
>> >>
>> >> I'm getting failed Report Server jobs. How do I find out what report
>> >> it
>> >> is,
>> >> user and, more information?
>> >>
>> >> The only information I see is a Step Name which is a long number and
>> >> then
>> >> a
>> >> message that says this:
>> >>
>> >> "Executed as user: MyDomain\AdminPass. Could not locate entry
>> >> in sysdatabases for database 'SQLReportServer'. No entry found
>> >> with that name. Make sure that the name is entered correctly.
>> >> [SQLSTATE 08004] [Error 911]. The step failed.
>> >>
>> >> thanks
>> >> gv
>> >
>|||I always prefer to use shared jobs because they are much easier to
change (as long as you have standard reports which are run
daily/weekly/monthly/etc). Here's how you set up a shared schedule:
- Click "Site Settings" at the top right of Report Manager
- Click "Manage Shared Schedules" on the bottom left
- From here you can add/change/delete shared jobs
- If you see none then obviously you are not using scheduled jobs
Since you said you were the dba, I assume you have access to the
database ReportServer. Run this query, and it should tell you the
basic info:
SELECT S.ScheduleID, S.[Name] AS ScheduleName, S.NextRunTime,
S.LastRunTime,
S.EventType, C.[Path], C.[Name] AS ReportName
FROM [schedule] S
INNER JOIN [ReportSchedule] R ON S.ScheduleID = R.ScheduleID
INNER JOIN [Catalog] C ON R.ReportID = C.ItemID;
You can match up the ScheduleID with the ID you see in the Agent. If
you have a lot of reports, you can even put it in the where clause
(S.ScheduleID = SQL_AGENT_ID). If EventType is "SharedSchedule" then
you are using shared schedules, so the change should just be in 1 place
(unless multiple jobs are failing). If it says "TimedSubscription"
then you will have to go into each report's properties and change the
subscription. Hope this helps.
Devin
gv wrote:
> Thanks alot for your help, I'm very new to Report Server and new as a DBA.
> No, it is ReportServer. Yes, many run fine.
> I think they are setup individually. Not sure. How would I check?
> In the Agent it doesn't say what report? Just has a long number.
> When you goto properties in the first tab page in box says this:
> "This is a Reporting Services job. Modifying this job could result in
> database incomptabilities.
> Please use the Report Server UI to update this job."
> I'm confused on how to research scheduled jobs in Report Server and make
> changes?
> Other people have created these. At first looking at the error.
> I noticed the name of the database had SQL at the beginning of it instead
> of just saying ReportServer. I think this is the problem. But how
> do I change it? Goes back to first knowing what Report. How?
> How do I relate the long number in SQL agent to a report name in Report
> Manger?
> thanks again for your help
> gv
> "Devin" <dlosee@.granitelp.com> wrote in message
> news:1161282924.264914.265360@.i3g2000cwc.googlegroups.com...
> > Is SQLReportServer the name of the database? The default is just
> > ReportServer. Do any scheduled reports run successfully? Do you have
> > it setup as shared schedules or are they individually scheduled per
> > report?
> >
> > You can probably tell which report(s) are failing by looking at the
> > scheduled date/time within SQL Agent and then matching it up with the
> > scheduled report(s) in Report Manager that run at that time.
> >
> > It sounds like 1 more schedules are corrupt. I would check all the
> > scheduled jobs (in SQL Agent) and make sure that each is pointed to the
> > correct database. If they all are, then you may want to delete and
> > re-create the scheduled jobs that are erroring (assuming you don't have
> > that many).
> >
> > Devin
> >
> > gv wrote:
> >> I did, I see nothing there.
> >>
> >> I got this message from Agent job history
> >>
> >> thanks
> >> gv
> >>
> >>
> >> "Devin" <dlosee@.granitelp.com> wrote in message
> >> news:1161275847.753301.134330@.i3g2000cwc.googlegroups.com...
> >> > Did you check the log files (or is that where this error came from)
> >> > located in C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> >> > Services\LogFiles\?
> >> >
> >> > Devin
> >> >
> >> > gv wrote:
> >> >> Hi all,
> >> >>
> >> >> I'm getting failed Report Server jobs. How do I find out what report
> >> >> it
> >> >> is,
> >> >> user and, more information?
> >> >>
> >> >> The only information I see is a Step Name which is a long number and
> >> >> then
> >> >> a
> >> >> message that says this:
> >> >>
> >> >> "Executed as user: MyDomain\AdminPass. Could not locate entry
> >> >> in sysdatabases for database 'SQLReportServer'. No entry found
> >> >> with that name. Make sure that the name is entered correctly.
> >> >> [SQLSTATE 08004] [Error 911]. The step failed.
> >> >>
> >> >> thanks
> >> >> gv
> >> >
> >|||AHHH. Thanks You!!!
That query is exactly what I was looking for. It says
TimedSubscription and gives me the report name.
I think I would like to change it to Shared Schedules
thanks again
gv
"Devin" <dlosee@.granitelp.com> wrote in message
news:1161285823.236151.182020@.m7g2000cwm.googlegroups.com...
>I always prefer to use shared jobs because they are much easier to
> change (as long as you have standard reports which are run
> daily/weekly/monthly/etc). Here's how you set up a shared schedule:
> - Click "Site Settings" at the top right of Report Manager
> - Click "Manage Shared Schedules" on the bottom left
> - From here you can add/change/delete shared jobs
> - If you see none then obviously you are not using scheduled jobs
> Since you said you were the dba, I assume you have access to the
> database ReportServer. Run this query, and it should tell you the
> basic info:
> SELECT S.ScheduleID, S.[Name] AS ScheduleName, S.NextRunTime,
> S.LastRunTime,
> S.EventType, C.[Path], C.[Name] AS ReportName
> FROM [schedule] S
> INNER JOIN [ReportSchedule] R ON S.ScheduleID = R.ScheduleID
> INNER JOIN [Catalog] C ON R.ReportID = C.ItemID;
> You can match up the ScheduleID with the ID you see in the Agent. If
> you have a lot of reports, you can even put it in the where clause
> (S.ScheduleID = SQL_AGENT_ID). If EventType is "SharedSchedule" then
> you are using shared schedules, so the change should just be in 1 place
> (unless multiple jobs are failing). If it says "TimedSubscription"
> then you will have to go into each report's properties and change the
> subscription. Hope this helps.
> Devin
>
> gv wrote:
>> Thanks alot for your help, I'm very new to Report Server and new as a
>> DBA.
>> No, it is ReportServer. Yes, many run fine.
>> I think they are setup individually. Not sure. How would I check?
>> In the Agent it doesn't say what report? Just has a long number.
>> When you goto properties in the first tab page in box says this:
>> "This is a Reporting Services job. Modifying this job could result in
>> database incomptabilities.
>> Please use the Report Server UI to update this job."
>> I'm confused on how to research scheduled jobs in Report Server and make
>> changes?
>> Other people have created these. At first looking at the error.
>> I noticed the name of the database had SQL at the beginning of it instead
>> of just saying ReportServer. I think this is the problem. But how
>> do I change it? Goes back to first knowing what Report. How?
>> How do I relate the long number in SQL agent to a report name in Report
>> Manger?
>> thanks again for your help
>> gv
>> "Devin" <dlosee@.granitelp.com> wrote in message
>> news:1161282924.264914.265360@.i3g2000cwc.googlegroups.com...
>> > Is SQLReportServer the name of the database? The default is just
>> > ReportServer. Do any scheduled reports run successfully? Do you have
>> > it setup as shared schedules or are they individually scheduled per
>> > report?
>> >
>> > You can probably tell which report(s) are failing by looking at the
>> > scheduled date/time within SQL Agent and then matching it up with the
>> > scheduled report(s) in Report Manager that run at that time.
>> >
>> > It sounds like 1 more schedules are corrupt. I would check all the
>> > scheduled jobs (in SQL Agent) and make sure that each is pointed to the
>> > correct database. If they all are, then you may want to delete and
>> > re-create the scheduled jobs that are erroring (assuming you don't have
>> > that many).
>> >
>> > Devin
>> >
>> > gv wrote:
>> >> I did, I see nothing there.
>> >>
>> >> I got this message from Agent job history
>> >>
>> >> thanks
>> >> gv
>> >>
>> >>
>> >> "Devin" <dlosee@.granitelp.com> wrote in message
>> >> news:1161275847.753301.134330@.i3g2000cwc.googlegroups.com...
>> >> > Did you check the log files (or is that where this error came from)
>> >> > located in C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
>> >> > Services\LogFiles\?
>> >> >
>> >> > Devin
>> >> >
>> >> > gv wrote:
>> >> >> Hi all,
>> >> >>
>> >> >> I'm getting failed Report Server jobs. How do I find out what
>> >> >> report
>> >> >> it
>> >> >> is,
>> >> >> user and, more information?
>> >> >>
>> >> >> The only information I see is a Step Name which is a long number
>> >> >> and
>> >> >> then
>> >> >> a
>> >> >> message that says this:
>> >> >>
>> >> >> "Executed as user: MyDomain\AdminPass. Could not locate entry
>> >> >> in sysdatabases for database 'SQLReportServer'. No entry found
>> >> >> with that name. Make sure that the name is entered correctly.
>> >> >> [SQLSTATE 08004] [Error 911]. The step failed.
>> >> >>
>> >> >> thanks
>> >> >> gv
>> >> >
>> >
>|||What table do I use to get SQL Server Agent information?
thanks again!!
gv
"Devin" <dlosee@.granitelp.com> wrote in message
news:1161285823.236151.182020@.m7g2000cwm.googlegroups.com...
>I always prefer to use shared jobs because they are much easier to
> change (as long as you have standard reports which are run
> daily/weekly/monthly/etc). Here's how you set up a shared schedule:
> - Click "Site Settings" at the top right of Report Manager
> - Click "Manage Shared Schedules" on the bottom left
> - From here you can add/change/delete shared jobs
> - If you see none then obviously you are not using scheduled jobs
> Since you said you were the dba, I assume you have access to the
> database ReportServer. Run this query, and it should tell you the
> basic info:
> SELECT S.ScheduleID, S.[Name] AS ScheduleName, S.NextRunTime,
> S.LastRunTime,
> S.EventType, C.[Path], C.[Name] AS ReportName
> FROM [schedule] S
> INNER JOIN [ReportSchedule] R ON S.ScheduleID = R.ScheduleID
> INNER JOIN [Catalog] C ON R.ReportID = C.ItemID;
> You can match up the ScheduleID with the ID you see in the Agent. If
> you have a lot of reports, you can even put it in the where clause
> (S.ScheduleID = SQL_AGENT_ID). If EventType is "SharedSchedule" then
> you are using shared schedules, so the change should just be in 1 place
> (unless multiple jobs are failing). If it says "TimedSubscription"
> then you will have to go into each report's properties and change the
> subscription. Hope this helps.
> Devin
>
> gv wrote:
>> Thanks alot for your help, I'm very new to Report Server and new as a
>> DBA.
>> No, it is ReportServer. Yes, many run fine.
>> I think they are setup individually. Not sure. How would I check?
>> In the Agent it doesn't say what report? Just has a long number.
>> When you goto properties in the first tab page in box says this:
>> "This is a Reporting Services job. Modifying this job could result in
>> database incomptabilities.
>> Please use the Report Server UI to update this job."
>> I'm confused on how to research scheduled jobs in Report Server and make
>> changes?
>> Other people have created these. At first looking at the error.
>> I noticed the name of the database had SQL at the beginning of it instead
>> of just saying ReportServer. I think this is the problem. But how
>> do I change it? Goes back to first knowing what Report. How?
>> How do I relate the long number in SQL agent to a report name in Report
>> Manger?
>> thanks again for your help
>> gv
>> "Devin" <dlosee@.granitelp.com> wrote in message
>> news:1161282924.264914.265360@.i3g2000cwc.googlegroups.com...
>> > Is SQLReportServer the name of the database? The default is just
>> > ReportServer. Do any scheduled reports run successfully? Do you have
>> > it setup as shared schedules or are they individually scheduled per
>> > report?
>> >
>> > You can probably tell which report(s) are failing by looking at the
>> > scheduled date/time within SQL Agent and then matching it up with the
>> > scheduled report(s) in Report Manager that run at that time.
>> >
>> > It sounds like 1 more schedules are corrupt. I would check all the
>> > scheduled jobs (in SQL Agent) and make sure that each is pointed to the
>> > correct database. If they all are, then you may want to delete and
>> > re-create the scheduled jobs that are erroring (assuming you don't have
>> > that many).
>> >
>> > Devin
>> >
>> > gv wrote:
>> >> I did, I see nothing there.
>> >>
>> >> I got this message from Agent job history
>> >>
>> >> thanks
>> >> gv
>> >>
>> >>
>> >> "Devin" <dlosee@.granitelp.com> wrote in message
>> >> news:1161275847.753301.134330@.i3g2000cwc.googlegroups.com...
>> >> > Did you check the log files (or is that where this error came from)
>> >> > located in C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
>> >> > Services\LogFiles\?
>> >> >
>> >> > Devin
>> >> >
>> >> > gv wrote:
>> >> >> Hi all,
>> >> >>
>> >> >> I'm getting failed Report Server jobs. How do I find out what
>> >> >> report
>> >> >> it
>> >> >> is,
>> >> >> user and, more information?
>> >> >>
>> >> >> The only information I see is a Step Name which is a long number
>> >> >> and
>> >> >> then
>> >> >> a
>> >> >> message that says this:
>> >> >>
>> >> >> "Executed as user: MyDomain\AdminPass. Could not locate entry
>> >> >> in sysdatabases for database 'SQLReportServer'. No entry found
>> >> >> with that name. Make sure that the name is entered correctly.
>> >> >> [SQLSTATE 08004] [Error 911]. The step failed.
>> >> >>
>> >> >> thanks
>> >> >> gv
>> >> >
>> >
>|||No problem. Glad I could help.
Devin
gv wrote:
> AHHH. Thanks You!!!
> That query is exactly what I was looking for. It says
> TimedSubscription and gives me the report name.
> I think I would like to change it to Shared Schedules
> thanks again
> gv
> "Devin" <dlosee@.granitelp.com> wrote in message
> news:1161285823.236151.182020@.m7g2000cwm.googlegroups.com...
> >I always prefer to use shared jobs because they are much easier to
> > change (as long as you have standard reports which are run
> > daily/weekly/monthly/etc). Here's how you set up a shared schedule:
> > - Click "Site Settings" at the top right of Report Manager
> > - Click "Manage Shared Schedules" on the bottom left
> > - From here you can add/change/delete shared jobs
> > - If you see none then obviously you are not using scheduled jobs
> >
> > Since you said you were the dba, I assume you have access to the
> > database ReportServer. Run this query, and it should tell you the
> > basic info:
> >
> > SELECT S.ScheduleID, S.[Name] AS ScheduleName, S.NextRunTime,
> > S.LastRunTime,
> > S.EventType, C.[Path], C.[Name] AS ReportName
> > FROM [schedule] S
> > INNER JOIN [ReportSchedule] R ON S.ScheduleID = R.ScheduleID
> > INNER JOIN [Catalog] C ON R.ReportID = C.ItemID;
> >
> > You can match up the ScheduleID with the ID you see in the Agent. If
> > you have a lot of reports, you can even put it in the where clause
> > (S.ScheduleID = SQL_AGENT_ID). If EventType is "SharedSchedule" then
> > you are using shared schedules, so the change should just be in 1 place
> > (unless multiple jobs are failing). If it says "TimedSubscription"
> > then you will have to go into each report's properties and change the
> > subscription. Hope this helps.
> >
> > Devin
> >
> >
> > gv wrote:
> >> Thanks alot for your help, I'm very new to Report Server and new as a
> >> DBA.
> >>
> >> No, it is ReportServer. Yes, many run fine.
> >> I think they are setup individually. Not sure. How would I check?
> >>
> >> In the Agent it doesn't say what report? Just has a long number.
> >>
> >> When you goto properties in the first tab page in box says this:
> >>
> >> "This is a Reporting Services job. Modifying this job could result in
> >> database incomptabilities.
> >> Please use the Report Server UI to update this job."
> >>
> >> I'm confused on how to research scheduled jobs in Report Server and make
> >> changes?
> >> Other people have created these. At first looking at the error.
> >> I noticed the name of the database had SQL at the beginning of it instead
> >> of just saying ReportServer. I think this is the problem. But how
> >> do I change it? Goes back to first knowing what Report. How?
> >> How do I relate the long number in SQL agent to a report name in Report
> >> Manger?
> >>
> >> thanks again for your help
> >> gv
> >>
> >> "Devin" <dlosee@.granitelp.com> wrote in message
> >> news:1161282924.264914.265360@.i3g2000cwc.googlegroups.com...
> >> > Is SQLReportServer the name of the database? The default is just
> >> > ReportServer. Do any scheduled reports run successfully? Do you have
> >> > it setup as shared schedules or are they individually scheduled per
> >> > report?
> >> >
> >> > You can probably tell which report(s) are failing by looking at the
> >> > scheduled date/time within SQL Agent and then matching it up with the
> >> > scheduled report(s) in Report Manager that run at that time.
> >> >
> >> > It sounds like 1 more schedules are corrupt. I would check all the
> >> > scheduled jobs (in SQL Agent) and make sure that each is pointed to the
> >> > correct database. If they all are, then you may want to delete and
> >> > re-create the scheduled jobs that are erroring (assuming you don't have
> >> > that many).
> >> >
> >> > Devin
> >> >
> >> > gv wrote:
> >> >> I did, I see nothing there.
> >> >>
> >> >> I got this message from Agent job history
> >> >>
> >> >> thanks
> >> >> gv
> >> >>
> >> >>
> >> >> "Devin" <dlosee@.granitelp.com> wrote in message
> >> >> news:1161275847.753301.134330@.i3g2000cwc.googlegroups.com...
> >> >> > Did you check the log files (or is that where this error came from)
> >> >> > located in C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> >> >> > Services\LogFiles\?
> >> >> >
> >> >> > Devin
> >> >> >
> >> >> > gv wrote:
> >> >> >> Hi all,
> >> >> >>
> >> >> >> I'm getting failed Report Server jobs. How do I find out what
> >> >> >> report
> >> >> >> it
> >> >> >> is,
> >> >> >> user and, more information?
> >> >> >>
> >> >> >> The only information I see is a Step Name which is a long number
> >> >> >> and
> >> >> >> then
> >> >> >> a
> >> >> >> message that says this:
> >> >> >>
> >> >> >> "Executed as user: MyDomain\AdminPass. Could not locate entry
> >> >> >> in sysdatabases for database 'SQLReportServer'. No entry found
> >> >> >> with that name. Make sure that the name is entered correctly.
> >> >> >> [SQLSTATE 08004] [Error 911]. The step failed.
> >> >> >>
> >> >> >> thanks
> >> >> >> gv
> >> >> >
> >> >
> >|||What do you mean? If you are looking for the SQL Agent ID, that is
just the name of the job (in RS case it is the large string of numbers
and letters (XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX). I'm sure all the
SQL Agent info is in the master database somewhere, but I wouldn't know
where. I was just referring to the job name that you see when you go
to SQL Server Agent -> Jobs in Management Studio.
Devin
gv wrote:
> What table do I use to get SQL Server Agent information?
> thanks again!!
> gv
>
> "Devin" <dlosee@.granitelp.com> wrote in message
> news:1161285823.236151.182020@.m7g2000cwm.googlegroups.com...
> >I always prefer to use shared jobs because they are much easier to
> > change (as long as you have standard reports which are run
> > daily/weekly/monthly/etc). Here's how you set up a shared schedule:
> > - Click "Site Settings" at the top right of Report Manager
> > - Click "Manage Shared Schedules" on the bottom left
> > - From here you can add/change/delete shared jobs
> > - If you see none then obviously you are not using scheduled jobs
> >
> > Since you said you were the dba, I assume you have access to the
> > database ReportServer. Run this query, and it should tell you the
> > basic info:
> >
> > SELECT S.ScheduleID, S.[Name] AS ScheduleName, S.NextRunTime,
> > S.LastRunTime,
> > S.EventType, C.[Path], C.[Name] AS ReportName
> > FROM [schedule] S
> > INNER JOIN [ReportSchedule] R ON S.ScheduleID = R.ScheduleID
> > INNER JOIN [Catalog] C ON R.ReportID = C.ItemID;
> >
> > You can match up the ScheduleID with the ID you see in the Agent. If
> > you have a lot of reports, you can even put it in the where clause
> > (S.ScheduleID = SQL_AGENT_ID). If EventType is "SharedSchedule" then
> > you are using shared schedules, so the change should just be in 1 place
> > (unless multiple jobs are failing). If it says "TimedSubscription"
> > then you will have to go into each report's properties and change the
> > subscription. Hope this helps.
> >
> > Devin
> >
> >
> > gv wrote:
> >> Thanks alot for your help, I'm very new to Report Server and new as a
> >> DBA.
> >>
> >> No, it is ReportServer. Yes, many run fine.
> >> I think they are setup individually. Not sure. How would I check?
> >>
> >> In the Agent it doesn't say what report? Just has a long number.
> >>
> >> When you goto properties in the first tab page in box says this:
> >>
> >> "This is a Reporting Services job. Modifying this job could result in
> >> database incomptabilities.
> >> Please use the Report Server UI to update this job."
> >>
> >> I'm confused on how to research scheduled jobs in Report Server and make
> >> changes?
> >> Other people have created these. At first looking at the error.
> >> I noticed the name of the database had SQL at the beginning of it instead
> >> of just saying ReportServer. I think this is the problem. But how
> >> do I change it? Goes back to first knowing what Report. How?
> >> How do I relate the long number in SQL agent to a report name in Report
> >> Manger?
> >>
> >> thanks again for your help
> >> gv
> >>
> >> "Devin" <dlosee@.granitelp.com> wrote in message
> >> news:1161282924.264914.265360@.i3g2000cwc.googlegroups.com...
> >> > Is SQLReportServer the name of the database? The default is just
> >> > ReportServer. Do any scheduled reports run successfully? Do you have
> >> > it setup as shared schedules or are they individually scheduled per
> >> > report?
> >> >
> >> > You can probably tell which report(s) are failing by looking at the
> >> > scheduled date/time within SQL Agent and then matching it up with the
> >> > scheduled report(s) in Report Manager that run at that time.
> >> >
> >> > It sounds like 1 more schedules are corrupt. I would check all the
> >> > scheduled jobs (in SQL Agent) and make sure that each is pointed to the
> >> > correct database. If they all are, then you may want to delete and
> >> > re-create the scheduled jobs that are erroring (assuming you don't have
> >> > that many).
> >> >
> >> > Devin
> >> >
> >> > gv wrote:
> >> >> I did, I see nothing there.
> >> >>
> >> >> I got this message from Agent job history
> >> >>
> >> >> thanks
> >> >> gv
> >> >>
> >> >>
> >> >> "Devin" <dlosee@.granitelp.com> wrote in message
> >> >> news:1161275847.753301.134330@.i3g2000cwc.googlegroups.com...
> >> >> > Did you check the log files (or is that where this error came from)
> >> >> > located in C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> >> >> > Services\LogFiles\?
> >> >> >
> >> >> > Devin
> >> >> >
> >> >> > gv wrote:
> >> >> >> Hi all,
> >> >> >>
> >> >> >> I'm getting failed Report Server jobs. How do I find out what
> >> >> >> report
> >> >> >> it
> >> >> >> is,
> >> >> >> user and, more information?
> >> >> >>
> >> >> >> The only information I see is a Step Name which is a long number
> >> >> >> and
> >> >> >> then
> >> >> >> a
> >> >> >> message that says this:
> >> >> >>
> >> >> >> "Executed as user: MyDomain\AdminPass. Could not locate entry
> >> >> >> in sysdatabases for database 'SQLReportServer'. No entry found
> >> >> >> with that name. Make sure that the name is entered correctly.
> >> >> >> [SQLSTATE 08004] [Error 911]. The step failed.
> >> >> >>
> >> >> >> thanks
> >> >> >> gv
> >> >> >
> >> >
> >