This seems like a bug:
I created a "jump to report" action on a TABLE in my report.
It works fine. But - when the table becomes long, and exceeds one
page on the HTML viewer, the "Jump to report" doesn't work anymore.
It keep throwing up blank pages.
Has anyone else encountered this?One question, is this from the IDE or from a deployed report. I have had a
variety of funky oddities that are only in the IDE, the deployed report
works fine.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Harsh" <harsh.vb@.gmail.com> wrote in message
news:1e70ecdd.0411130717.8685260@.posting.google.com...
> This seems like a bug:
> I created a "jump to report" action on a TABLE in my report.
> It works fine. But - when the table becomes long, and exceeds one
> page on the HTML viewer, the "Jump to report" doesn't work anymore.
> It keep throwing up blank pages.
> Has anyone else encountered this?
Showing posts with label second. Show all posts
Showing posts with label second. Show all posts
Thursday, February 16, 2012
Monday, February 13, 2012
[324] SQLAgent is not allowed to run.
I have two instances of SQL 2000 installed. SQLAgent on
one starts ok. However SQLAgent on the second instance
does NOT start. The one that does not work is for
SHAREPOINT. I am running SBS 2003. Both MSSQL servers
start ok.
Originally the SHAREPOINT server was MSDE but I upgraded
it to SQL 2000.That's not much to go on. What is the error msg? You might want to check
to ensure the account and password SQL Agent is running under are valid.
--
Andrew J. Kelly SQL MVP
"Dennis Cullen" <anonymous@.discussions.microsoft.com> wrote in message
news:070301c3d793$1657e810$a501280a@.phx.gbl...
> I have two instances of SQL 2000 installed. SQLAgent on
> one starts ok. However SQLAgent on the second instance
> does NOT start. The one that does not work is for
> SHAREPOINT. I am running SBS 2003. Both MSSQL servers
> start ok.
> Originally the SHAREPOINT server was MSDE but I upgraded
> it to SQL 2000.|||I have a similar problem; running SPS 2003. Took the box out of the network and when booted, SQLAgent$SHAREPOINT died. After much research, the setting in the registry was somehow truncated (the DependsOn Service was truncated to MSSQL$SHAREPOINT to MSSQL$SHA) - no idea how THAT happened.
At any rate, while I've corrected the above, any attempt to start SQLAgent (even on the command line) simply returns "SQLAgent is not allowed to run". Only error message I can see is "StartServiceCtrlDispatcher failed (error 6)".
NO info anywhere so far on this type of problem; NOTE: Recently applied the Security patch however, I am skeptical about that being the problem as all other Databases are working fine.
Any ideas?|||After Much Much searching, I located the information on Google (!); this relates the SHAREPOINT ONLY that I know of...In the registry, find
HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/MICROSOFT SQL SERVER/SHAREPOINT/SQLSERVERAGEN
and delete the GUID entry - this corrects the problem. This was posted by chrisfez is the DBForum as the solution provided by Microsoft Support. ALSO NOTE: There is a similar problem with UDDI, though I am just now investigating it (start up of the Sql Agent for UDDI fails the same as SharePoint).|||Thanks, this solved my problem
Google (!); this relates the SHAREPOINT ONLY that I know
of...In the registry, find:
>HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/MICROSOFT SQL
SERVER/SHAREPOINT/SQLSERVERAGENT
>and delete the GUID entry - this corrects the problem.
This was posted by chrisfez is the DBForum as the solution
provided by Microsoft Support.
one starts ok. However SQLAgent on the second instance
does NOT start. The one that does not work is for
SHAREPOINT. I am running SBS 2003. Both MSSQL servers
start ok.
Originally the SHAREPOINT server was MSDE but I upgraded
it to SQL 2000.That's not much to go on. What is the error msg? You might want to check
to ensure the account and password SQL Agent is running under are valid.
--
Andrew J. Kelly SQL MVP
"Dennis Cullen" <anonymous@.discussions.microsoft.com> wrote in message
news:070301c3d793$1657e810$a501280a@.phx.gbl...
> I have two instances of SQL 2000 installed. SQLAgent on
> one starts ok. However SQLAgent on the second instance
> does NOT start. The one that does not work is for
> SHAREPOINT. I am running SBS 2003. Both MSSQL servers
> start ok.
> Originally the SHAREPOINT server was MSDE but I upgraded
> it to SQL 2000.|||I have a similar problem; running SPS 2003. Took the box out of the network and when booted, SQLAgent$SHAREPOINT died. After much research, the setting in the registry was somehow truncated (the DependsOn Service was truncated to MSSQL$SHAREPOINT to MSSQL$SHA) - no idea how THAT happened.
At any rate, while I've corrected the above, any attempt to start SQLAgent (even on the command line) simply returns "SQLAgent is not allowed to run". Only error message I can see is "StartServiceCtrlDispatcher failed (error 6)".
NO info anywhere so far on this type of problem; NOTE: Recently applied the Security patch however, I am skeptical about that being the problem as all other Databases are working fine.
Any ideas?|||After Much Much searching, I located the information on Google (!); this relates the SHAREPOINT ONLY that I know of...In the registry, find
HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/MICROSOFT SQL SERVER/SHAREPOINT/SQLSERVERAGEN
and delete the GUID entry - this corrects the problem. This was posted by chrisfez is the DBForum as the solution provided by Microsoft Support. ALSO NOTE: There is a similar problem with UDDI, though I am just now investigating it (start up of the Sql Agent for UDDI fails the same as SharePoint).|||Thanks, this solved my problem
Google (!); this relates the SHAREPOINT ONLY that I know
of...In the registry, find:
>HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/MICROSOFT SQL
SERVER/SHAREPOINT/SQLSERVERAGENT
>and delete the GUID entry - this corrects the problem.
This was posted by chrisfez is the DBForum as the solution
provided by Microsoft Support.
[324] SQLAgent is not allowed to run.
I have two instances of SQL 2000 installed. SQLAgent on
one starts ok. However SQLAgent on the second instance
does NOT start. The one that does not work is for
SHAREPOINT. I am running SBS 2003. Both MSSQL servers
start ok.
Originally the SHAREPOINT server was MSDE but I upgraded
it to SQL 2000.That's not much to go on. What is the error msg? You might want to check
to ensure the account and password SQL Agent is running under are valid.
Andrew J. Kelly SQL MVP
"Dennis Cullen" <anonymous@.discussions.microsoft.com> wrote in message
news:070301c3d793$1657e810$a501280a@.phx.gbl...
and when booted, SQLAgent$SHAREPOINT died. After much research, the setting
in the registry was somehow truncated (the DependsOn Service was truncated t
o MSSQL$SHAREPOINT to MSSQL
$SHA) - no idea how THAT happened.
At any rate, while I've corrected the above, any attempt to start SQLAgent (
even on the command line) simply returns "SQLAgent is not allowed to run". O
nly error message I can see is "StartServiceCtrlDispatcher failed (error 6)"
.
NO info anywhere so far on this type of problem; NOTE: Recently applied the
Security patch however, I am skeptical about that being the problem as all o
ther Databases are working fine.
Any ideas?|||After Much Much searching, I located the information on Google (!); this rel
ates the SHAREPOINT ONLY that I know of...In the registry, find:
HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/MICROSOFT SQL SERVER/SHAREPOINT/SQLSER
VERAGENT
and delete the GUID entry - this corrects the problem. This was posted by ch
risfez is the DBForum as the solution provided by Microsoft Support. ALSO NO
TE: There is a similar problem with UDDI, though I am just now investigating
it (start up of the Sql Ag
ent for UDDI fails the same as SharePoint).|||Thanks, this solved my problem
Google (!); this relates the SHAREPOINT ONLY that I know
of...In the registry, find:
SERVER/SHAREPOINT/SQLSERVERAGENT
This was posted by chrisfez is the DBForum as the solution
provided by Microsoft Support.
one starts ok. However SQLAgent on the second instance
does NOT start. The one that does not work is for
SHAREPOINT. I am running SBS 2003. Both MSSQL servers
start ok.
Originally the SHAREPOINT server was MSDE but I upgraded
it to SQL 2000.That's not much to go on. What is the error msg? You might want to check
to ensure the account and password SQL Agent is running under are valid.
Andrew J. Kelly SQL MVP
"Dennis Cullen" <anonymous@.discussions.microsoft.com> wrote in message
news:070301c3d793$1657e810$a501280a@.phx.gbl...
quote:|||I have a similar problem; running SPS 2003. Took the box out of the network
> I have two instances of SQL 2000 installed. SQLAgent on
> one starts ok. However SQLAgent on the second instance
> does NOT start. The one that does not work is for
> SHAREPOINT. I am running SBS 2003. Both MSSQL servers
> start ok.
> Originally the SHAREPOINT server was MSDE but I upgraded
> it to SQL 2000.
and when booted, SQLAgent$SHAREPOINT died. After much research, the setting
in the registry was somehow truncated (the DependsOn Service was truncated t
o MSSQL$SHAREPOINT to MSSQL
$SHA) - no idea how THAT happened.
At any rate, while I've corrected the above, any attempt to start SQLAgent (
even on the command line) simply returns "SQLAgent is not allowed to run". O
nly error message I can see is "StartServiceCtrlDispatcher failed (error 6)"
.
NO info anywhere so far on this type of problem; NOTE: Recently applied the
Security patch however, I am skeptical about that being the problem as all o
ther Databases are working fine.
Any ideas?|||After Much Much searching, I located the information on Google (!); this rel
ates the SHAREPOINT ONLY that I know of...In the registry, find:
HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/MICROSOFT SQL SERVER/SHAREPOINT/SQLSER
VERAGENT
and delete the GUID entry - this corrects the problem. This was posted by ch
risfez is the DBForum as the solution provided by Microsoft Support. ALSO NO
TE: There is a similar problem with UDDI, though I am just now investigating
it (start up of the Sql Ag
ent for UDDI fails the same as SharePoint).|||Thanks, this solved my problem
Google (!); this relates the SHAREPOINT ONLY that I know
of...In the registry, find:
quote:
>HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/MICROSOFT SQL
SERVER/SHAREPOINT/SQLSERVERAGENT
quote:
>and delete the GUID entry - this corrects the problem.
This was posted by chrisfez is the DBForum as the solution
provided by Microsoft Support.
Subscribe to:
Posts (Atom)