My end users want me to post 2 versions of my 2005 Reporting Services
reports. One that when they click on it automatically opens in Excel w/o
grouping...sort of a data dump. Then a second that is grouped, formatted and
pretty.
I know that I can have them export the report once run into Excel, but they
don't want that. (of course...;) So, does anyone know how to publish in
straight Excel in Reporting Services?
thanks in advance for any help!
MachelleYou didn't say if you are using Report Manager or not. The best way is to
use jump to URL and render in CSV ASCII format. The default for CSV is
unicode which Excel opens up with all the data in its own column.
Depending on your report you may or may not want to have a duplicate report
that you have cleaned up and call that one rather than the pretty one.
Regardless, if you have any data size at all URL is much faster.
If you are using Report Manager you could have a report that has no data,
just the parameters and then textboxes, one for pretty, one for Data Export
(I call it that in my link to differentiate that it is a data export, not
the pretty Excel export).
Note, the fields texboxes of the report have a name property that is set
during design to the name of the field. You can give it friendlier names if
you want.
Here is an example of a Jump to URL link I use. This causes Excel to come up
with the data in a separate window:
="javascript:void(window.open('" & Globals!ReportServerUrl &
"?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
"&rs:Format=CSV&rc:Encoding=ASCII','_blank'))"
Very nice and very fast.
Bruce Loehle-Conger
"Machelle" <Machelle@.discussions.microsoft.com> wrote in message
news:A5360BDE-440C-4AAF-8D07-46A9D3472567@.microsoft.com...
> My end users want me to post 2 versions of my 2005 Reporting Services
> reports. One that when they click on it automatically opens in Excel w/o
> grouping...sort of a data dump. Then a second that is grouped, formatted
> and
> pretty.
> I know that I can have them export the report once run into Excel, but
> they
> don't want that. (of course...;) So, does anyone know how to publish in
> straight Excel in Reporting Services?
> thanks in advance for any help!
> Machelle
Showing posts with label automatically. Show all posts
Showing posts with label automatically. Show all posts
Tuesday, March 6, 2012
Thursday, February 9, 2012
2005 Agent doesn't start automatically on reboot
We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
machine is rebooted, the SQL Server agent is not automatically started.
It is set to start automatically in the Windows Services dialog. I
see a safe shutdown prior to the reboot, but no messages like it's even
trying to start up. I can start it manually with no problems.
Any ideas what to check or where to go from here?Hi
Have you checked the sql server agent log file in Management studio? Also
check what SQL Server Configuration Manager has for the service and check
that error reporting is selected on the advanced tab.
John
"PSPDBA" wrote:
> We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> machine is rebooted, the SQL Server agent is not automatically started.
> It is set to start automatically in the Windows Services dialog. I
> see a safe shutdown prior to the reboot, but no messages like it's even
> trying to start up. I can start it manually with no problems.
> Any ideas what to check or where to go from here?
>|||Agent log shows:
Message
[241] Startup error: Unable to initialize error reporting system
(reason: The EventLog service has not been started)
However, The EventLog service is also set to automatic.
John Bell wrote:
> Hi
> Have you checked the sql server agent log file in Management studio? Also
> check what SQL Server Configuration Manager has for the service and check
> that error reporting is selected on the advanced tab.
> John
> "PSPDBA" wrote:
> > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > machine is rebooted, the SQL Server agent is not automatically started.
> > It is set to start automatically in the Windows Services dialog. I
> > see a safe shutdown prior to the reboot, but no messages like it's even
> > trying to start up. I can start it manually with no problems.
> >
> > Any ideas what to check or where to go from here?
> >
> >|||Hi
I assume that the EventLog has started correctly?
Making SQL Agent dependent on the EventLog service would ensure that it has
started before SQL Agent starts.
If the service is running as LOCALSYSTEM you could change it to an domain
account.
John
"PSPDBA" wrote:
> Agent log shows:
> Message
> [241] Startup error: Unable to initialize error reporting system
> (reason: The EventLog service has not been started)
> However, The EventLog service is also set to automatic.
> John Bell wrote:
> > Hi
> >
> > Have you checked the sql server agent log file in Management studio? Also
> > check what SQL Server Configuration Manager has for the service and check
> > that error reporting is selected on the advanced tab.
> >
> > John
> >
> > "PSPDBA" wrote:
> >
> > > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > > machine is rebooted, the SQL Server agent is not automatically started.
> > > It is set to start automatically in the Windows Services dialog. I
> > > see a safe shutdown prior to the reboot, but no messages like it's even
> > > trying to start up. I can start it manually with no problems.
> > >
> > > Any ideas what to check or where to go from here?
> > >
> > >
>|||Yep, it sure has. I was thinking of doing both of those things. I'll
give it a try.
John Bell wrote:
> Hi
> I assume that the EventLog has started correctly?
> Making SQL Agent dependent on the EventLog service would ensure that it has
> started before SQL Agent starts.
> If the service is running as LOCALSYSTEM you could change it to an domain
> account.
> John
> "PSPDBA" wrote:
> > Agent log shows:
> >
> > Message
> > [241] Startup error: Unable to initialize error reporting system
> > (reason: The EventLog service has not been started)
> >
> > However, The EventLog service is also set to automatic.
> >
> > John Bell wrote:
> > > Hi
> > >
> > > Have you checked the sql server agent log file in Management studio? Also
> > > check what SQL Server Configuration Manager has for the service and check
> > > that error reporting is selected on the advanced tab.
> > >
> > > John
> > >
> > > "PSPDBA" wrote:
> > >
> > > > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > > > machine is rebooted, the SQL Server agent is not automatically started.
> > > > It is set to start automatically in the Windows Services dialog. I
> > > > see a safe shutdown prior to the reboot, but no messages like it's even
> > > > trying to start up. I can start it manually with no problems.
> > > >
> > > > Any ideas what to check or where to go from here?
> > > >
> > > >
> >
> >|||Hi
You didn't say if the service was running under local system or not'
Looking at other posts http://tinyurl.com/rvql2 the service account seems to
be a prime reason for this failure. To change this manually check out
http://support.microsoft.com/?id=283811
John
"PSPDBA" wrote:
> Yep, it sure has. I was thinking of doing both of those things. I'll
> give it a try.
>
> John Bell wrote:
> > Hi
> >
> > I assume that the EventLog has started correctly?
> >
> > Making SQL Agent dependent on the EventLog service would ensure that it has
> > started before SQL Agent starts.
> >
> > If the service is running as LOCALSYSTEM you could change it to an domain
> > account.
> >
> > John
> >
> > "PSPDBA" wrote:
> >
> > > Agent log shows:
> > >
> > > Message
> > > [241] Startup error: Unable to initialize error reporting system
> > > (reason: The EventLog service has not been started)
> > >
> > > However, The EventLog service is also set to automatic.
> > >
> > > John Bell wrote:
> > > > Hi
> > > >
> > > > Have you checked the sql server agent log file in Management studio? Also
> > > > check what SQL Server Configuration Manager has for the service and check
> > > > that error reporting is selected on the advanced tab.
> > > >
> > > > John
> > > >
> > > > "PSPDBA" wrote:
> > > >
> > > > > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > > > > machine is rebooted, the SQL Server agent is not automatically started.
> > > > > It is set to start automatically in the Windows Services dialog. I
> > > > > see a safe shutdown prior to the reboot, but no messages like it's even
> > > > > trying to start up. I can start it manually with no problems.
> > > > >
> > > > > Any ideas what to check or where to go from here?
> > > > >
> > > > >
> > >
> > >
>
machine is rebooted, the SQL Server agent is not automatically started.
It is set to start automatically in the Windows Services dialog. I
see a safe shutdown prior to the reboot, but no messages like it's even
trying to start up. I can start it manually with no problems.
Any ideas what to check or where to go from here?Hi
Have you checked the sql server agent log file in Management studio? Also
check what SQL Server Configuration Manager has for the service and check
that error reporting is selected on the advanced tab.
John
"PSPDBA" wrote:
> We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> machine is rebooted, the SQL Server agent is not automatically started.
> It is set to start automatically in the Windows Services dialog. I
> see a safe shutdown prior to the reboot, but no messages like it's even
> trying to start up. I can start it manually with no problems.
> Any ideas what to check or where to go from here?
>|||Agent log shows:
Message
[241] Startup error: Unable to initialize error reporting system
(reason: The EventLog service has not been started)
However, The EventLog service is also set to automatic.
John Bell wrote:
> Hi
> Have you checked the sql server agent log file in Management studio? Also
> check what SQL Server Configuration Manager has for the service and check
> that error reporting is selected on the advanced tab.
> John
> "PSPDBA" wrote:
> > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > machine is rebooted, the SQL Server agent is not automatically started.
> > It is set to start automatically in the Windows Services dialog. I
> > see a safe shutdown prior to the reboot, but no messages like it's even
> > trying to start up. I can start it manually with no problems.
> >
> > Any ideas what to check or where to go from here?
> >
> >|||Hi
I assume that the EventLog has started correctly?
Making SQL Agent dependent on the EventLog service would ensure that it has
started before SQL Agent starts.
If the service is running as LOCALSYSTEM you could change it to an domain
account.
John
"PSPDBA" wrote:
> Agent log shows:
> Message
> [241] Startup error: Unable to initialize error reporting system
> (reason: The EventLog service has not been started)
> However, The EventLog service is also set to automatic.
> John Bell wrote:
> > Hi
> >
> > Have you checked the sql server agent log file in Management studio? Also
> > check what SQL Server Configuration Manager has for the service and check
> > that error reporting is selected on the advanced tab.
> >
> > John
> >
> > "PSPDBA" wrote:
> >
> > > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > > machine is rebooted, the SQL Server agent is not automatically started.
> > > It is set to start automatically in the Windows Services dialog. I
> > > see a safe shutdown prior to the reboot, but no messages like it's even
> > > trying to start up. I can start it manually with no problems.
> > >
> > > Any ideas what to check or where to go from here?
> > >
> > >
>|||Yep, it sure has. I was thinking of doing both of those things. I'll
give it a try.
John Bell wrote:
> Hi
> I assume that the EventLog has started correctly?
> Making SQL Agent dependent on the EventLog service would ensure that it has
> started before SQL Agent starts.
> If the service is running as LOCALSYSTEM you could change it to an domain
> account.
> John
> "PSPDBA" wrote:
> > Agent log shows:
> >
> > Message
> > [241] Startup error: Unable to initialize error reporting system
> > (reason: The EventLog service has not been started)
> >
> > However, The EventLog service is also set to automatic.
> >
> > John Bell wrote:
> > > Hi
> > >
> > > Have you checked the sql server agent log file in Management studio? Also
> > > check what SQL Server Configuration Manager has for the service and check
> > > that error reporting is selected on the advanced tab.
> > >
> > > John
> > >
> > > "PSPDBA" wrote:
> > >
> > > > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > > > machine is rebooted, the SQL Server agent is not automatically started.
> > > > It is set to start automatically in the Windows Services dialog. I
> > > > see a safe shutdown prior to the reboot, but no messages like it's even
> > > > trying to start up. I can start it manually with no problems.
> > > >
> > > > Any ideas what to check or where to go from here?
> > > >
> > > >
> >
> >|||Hi
You didn't say if the service was running under local system or not'
Looking at other posts http://tinyurl.com/rvql2 the service account seems to
be a prime reason for this failure. To change this manually check out
http://support.microsoft.com/?id=283811
John
"PSPDBA" wrote:
> Yep, it sure has. I was thinking of doing both of those things. I'll
> give it a try.
>
> John Bell wrote:
> > Hi
> >
> > I assume that the EventLog has started correctly?
> >
> > Making SQL Agent dependent on the EventLog service would ensure that it has
> > started before SQL Agent starts.
> >
> > If the service is running as LOCALSYSTEM you could change it to an domain
> > account.
> >
> > John
> >
> > "PSPDBA" wrote:
> >
> > > Agent log shows:
> > >
> > > Message
> > > [241] Startup error: Unable to initialize error reporting system
> > > (reason: The EventLog service has not been started)
> > >
> > > However, The EventLog service is also set to automatic.
> > >
> > > John Bell wrote:
> > > > Hi
> > > >
> > > > Have you checked the sql server agent log file in Management studio? Also
> > > > check what SQL Server Configuration Manager has for the service and check
> > > > that error reporting is selected on the advanced tab.
> > > >
> > > > John
> > > >
> > > > "PSPDBA" wrote:
> > > >
> > > > > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > > > > machine is rebooted, the SQL Server agent is not automatically started.
> > > > > It is set to start automatically in the Windows Services dialog. I
> > > > > see a safe shutdown prior to the reboot, but no messages like it's even
> > > > > trying to start up. I can start it manually with no problems.
> > > > >
> > > > > Any ideas what to check or where to go from here?
> > > > >
> > > > >
> > >
> > >
>
2005 Agent doesn't start automatically on reboot
We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
machine is rebooted, the SQL Server agent is not automatically started.
It is set to start automatically in the Windows Services dialog. I
see a safe shutdown prior to the reboot, but no messages like it's even
trying to start up. I can start it manually with no problems.
Any ideas what to check or where to go from here?Hi
Have you checked the sql server agent log file in Management studio? Also
check what SQL Server Configuration Manager has for the service and check
that error reporting is selected on the advanced tab.
John
"PSPDBA" wrote:
> We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> machine is rebooted, the SQL Server agent is not automatically started.
> It is set to start automatically in the Windows Services dialog. I
> see a safe shutdown prior to the reboot, but no messages like it's even
> trying to start up. I can start it manually with no problems.
> Any ideas what to check or where to go from here?
>|||Agent log shows:
Message
[241] Startup error: Unable to initialize error reporting system
(reason: The EventLog service has not been started)
However, The EventLog service is also set to automatic.
John Bell wrote:[vbcol=seagreen]
> Hi
> Have you checked the sql server agent log file in Management studio? Also
> check what SQL Server Configuration Manager has for the service and check
> that error reporting is selected on the advanced tab.
> John
> "PSPDBA" wrote:
>|||Hi
I assume that the EventLog has started correctly?
Making SQL Agent dependent on the EventLog service would ensure that it has
started before SQL Agent starts.
If the service is running as LOCALSYSTEM you could change it to an domain
account.
John
"PSPDBA" wrote:
> Agent log shows:
> Message
> [241] Startup error: Unable to initialize error reporting system
> (reason: The EventLog service has not been started)
> However, The EventLog service is also set to automatic.
> John Bell wrote:
>|||Yep, it sure has. I was thinking of doing both of those things. I'll
give it a try.
John Bell wrote:[vbcol=seagreen]
> Hi
> I assume that the EventLog has started correctly?
> Making SQL Agent dependent on the EventLog service would ensure that it ha
s
> started before SQL Agent starts.
> If the service is running as LOCALSYSTEM you could change it to an domain
> account.
> John
> "PSPDBA" wrote:
>|||Hi
You didn't say if the service was running under local system or not'
Looking at other posts http://tinyurl.com/rvql2 the service account seems to
be a prime reason for this failure. To change this manually check out
http://support.microsoft.com/?id=283811
John
"PSPDBA" wrote:
> Yep, it sure has. I was thinking of doing both of those things. I'll
> give it a try.
>
> John Bell wrote:
>
machine is rebooted, the SQL Server agent is not automatically started.
It is set to start automatically in the Windows Services dialog. I
see a safe shutdown prior to the reboot, but no messages like it's even
trying to start up. I can start it manually with no problems.
Any ideas what to check or where to go from here?Hi
Have you checked the sql server agent log file in Management studio? Also
check what SQL Server Configuration Manager has for the service and check
that error reporting is selected on the advanced tab.
John
"PSPDBA" wrote:
> We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> machine is rebooted, the SQL Server agent is not automatically started.
> It is set to start automatically in the Windows Services dialog. I
> see a safe shutdown prior to the reboot, but no messages like it's even
> trying to start up. I can start it manually with no problems.
> Any ideas what to check or where to go from here?
>|||Agent log shows:
Message
[241] Startup error: Unable to initialize error reporting system
(reason: The EventLog service has not been started)
However, The EventLog service is also set to automatic.
John Bell wrote:[vbcol=seagreen]
> Hi
> Have you checked the sql server agent log file in Management studio? Also
> check what SQL Server Configuration Manager has for the service and check
> that error reporting is selected on the advanced tab.
> John
> "PSPDBA" wrote:
>|||Hi
I assume that the EventLog has started correctly?
Making SQL Agent dependent on the EventLog service would ensure that it has
started before SQL Agent starts.
If the service is running as LOCALSYSTEM you could change it to an domain
account.
John
"PSPDBA" wrote:
> Agent log shows:
> Message
> [241] Startup error: Unable to initialize error reporting system
> (reason: The EventLog service has not been started)
> However, The EventLog service is also set to automatic.
> John Bell wrote:
>|||Yep, it sure has. I was thinking of doing both of those things. I'll
give it a try.
John Bell wrote:[vbcol=seagreen]
> Hi
> I assume that the EventLog has started correctly?
> Making SQL Agent dependent on the EventLog service would ensure that it ha
s
> started before SQL Agent starts.
> If the service is running as LOCALSYSTEM you could change it to an domain
> account.
> John
> "PSPDBA" wrote:
>|||Hi
You didn't say if the service was running under local system or not'
Looking at other posts http://tinyurl.com/rvql2 the service account seems to
be a prime reason for this failure. To change this manually check out
http://support.microsoft.com/?id=283811
John
"PSPDBA" wrote:
> Yep, it sure has. I was thinking of doing both of those things. I'll
> give it a try.
>
> John Bell wrote:
>
Subscribe to:
Posts (Atom)