Error 1920. Service 'ReportServer' (ReportServer) failed to start

Hello, I cannot install Reporting Services Developer Version, at the end of
the setup I got a message like:
Error 1920. Service 'ReportServer' (ReportServer) failed to start. Verify
that you have sufficient privileges to start system services.
I have SQL SP3a, IIS, .NET 2003 all in the same computer.
Just cannot find how to solve the problem, seems to be something with the
account used to start the service, but with neither the built in account, not
a computer admin account can continue. Have no problem creating the database,
just to start the service.
Help pleaseMy problem is solved; I think you only need to change the installation path
of RS during the setup, but the following are the steps I follow:
1. Uninstall RS
2. Clean all signs of RS in the registry, the service and components
Delete in the registry the entries in
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RS Rep..
Delete the service from the command prompt
sc delete ReportServer
Delete the components in Component Services in
the control panel Administrative Tools in the COM+ Applications for the ISS
3. Install RS in a different path
I install RS in C:\Program Files\Microsoft SQL ServerRS
Also i rename the services in the setup to MSReportService, MSReports for
the
IIS part.
I have Windows XP with all in one box; I use a domain account, for the
services
and for the SQL login.

Error 17883

The SQL Server is 32 bit - 2000 and I have applied SP3a with hot patch 815495. So it is up to version 818 but I am still getting errors sporadically which are the Process 53:0 (19f8) UMS Context 0x0D2123E8 appears to be non-yielding on Scheduler 0. They
are server errors and appear to be happening in the early morning and trying to search the microsoft web site, indicates that these should be corrected.
Are there additional hot patches to correct this problem? Thanks.
Cynthia,
Here is an article which seems to outline your problem.
http://support.microsoft.com/default...b;en-us;810885
The circumstances for this are fairly specific and there is no hot-patch
according to the article. Do you fit the profile of this article?
Russell Fields
"Cynthia" <anonymous@.discussions.microsoft.com> wrote in message
news:803D34D5-99BD-408F-B767-A29FE8FC112C@.microsoft.com...
> The SQL Server is 32 bit - 2000 and I have applied SP3a with hot patch
815495. So it is up to version 818 but I am still getting errors
sporadically which are the Process 53:0 (19f8) UMS Context 0x0D2123E8
appears to be non-yielding on Scheduler 0. They are server errors and
appear to be happening in the early morning and trying to search the
microsoft web site, indicates that these should be corrected.
> Are there additional hot patches to correct this problem? Thanks.
>
|||Hi,
Thanks for the reply. Yes I do have autogrow on all the servers and this one that is giving the error. But there is nothing exceptional about this server compared to the other servers. No high speed disk system or anything unusual. This is the only s
erver that has this error and the error 17883 and Q815056 seems to identify what the problem is but the hotfix 815495 didn't resolve the problem. I am wondering if the error is informational only?
|||Cynthia,
Although this error is "informational" in that there is no direct action
that you can take, I would view the message as the harbinger of problems
that may hurt you more in the future.
Inside 810885 there is a reference to:
http://support.microsoft.com/default.aspx?kbid=319892
That makes the following comment: If you cannot determine the root cause
immediately, consult the error log for problems and engage in extended
support efforts.
Sounds like Microsoft feels that you should be concerned.
Russell Fields
"cynthia" <anonymous@.discussions.microsoft.com> wrote in message
news:BA5E143F-A0EE-486B-97D7-756D71893984@.microsoft.com...
> Hi,
> Thanks for the reply. Yes I do have autogrow on all the servers and this
one that is giving the error. But there is nothing exceptional about this
server compared to the other servers. No high speed disk system or anything
unusual. This is the only server that has this error and the error 17883
and Q815056 seems to identify what the problem is but the hotfix 815495
didn't resolve the problem. I am wondering if the error is informational
only?
|||In the absence of a specific bug, this is likely going to be best-handled and troubleshot by Microsoft support. I'd recommend that you engage them as soon as possible.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message news:exv7IzyTEHA.2464@.TK2MSFTNGP10.phx.gbl...
Cynthia,
Although this error is "informational" in that there is no direct action
that you can take, I would view the message as the harbinger of problems
that may hurt you more in the future.
Inside 810885 there is a reference to:
http://support.microsoft.com/default.aspx?kbid=319892
That makes the following comment: If you cannot determine the root cause
immediately, consult the error log for problems and engage in extended
support efforts.
Sounds like Microsoft feels that you should be concerned.
Russell Fields
"cynthia" <anonymous@.discussions.microsoft.com> wrote in message
news:BA5E143F-A0EE-486B-97D7-756D71893984@.microsoft.com...
> Hi,
> Thanks for the reply. Yes I do have autogrow on all the servers and this
one that is giving the error. But there is nothing exceptional about this
server compared to the other servers. No high speed disk system or anything
unusual. This is the only server that has this error and the error 17883
and Q815056 seems to identify what the problem is but the hotfix 815495
didn't resolve the problem. I am wondering if the error is informational
only?
|||Thanks Ryan and Russell. You're both right and I have run out of troubleshooting tools for this.

Error 17883

The SQL Server is 32 bit - 2000 and I have applied SP3a with hot patch 81549
5. So it is up to version 818 but I am still getting errors sporadically wh
ich are the Process 53:0 (19f8) UMS Context 0x0D2123E8 appears to be non-yie
lding on Scheduler 0. They
are server errors and appear to be happening in the early morning and trying
to search the microsoft web site, indicates that these should be corrected.
Are there additional hot patches to correct this problem? Thanks.Cynthia,
Here is an article which seems to outline your problem.
http://support.microsoft.com/defaul...kb;en-us;810885
The circumstances for this are fairly specific and there is no hot-patch
according to the article. Do you fit the profile of this article?
Russell Fields
"Cynthia" <anonymous@.discussions.microsoft.com> wrote in message
news:803D34D5-99BD-408F-B767-A29FE8FC112C@.microsoft.com...
> The SQL Server is 32 bit - 2000 and I have applied SP3a with hot patch
815495. So it is up to version 818 but I am still getting errors
sporadically which are the Process 53:0 (19f8) UMS Context 0x0D2123E8
appears to be non-yielding on Scheduler 0. They are server errors and
appear to be happening in the early morning and trying to search the
microsoft web site, indicates that these should be corrected.
> Are there additional hot patches to correct this problem? Thanks.
>|||Hi,
Thanks for the reply. Yes I do have autogrow on all the servers and this o
ne that is giving the error. But there is nothing exceptional about this se
rver compared to the other servers. No high speed disk system or anything u
nusual. This is the only s
erver that has this error and the error 17883 and Q815056 seems to identify
what the problem is but the hotfix 815495 didn't resolve the problem. I am
wondering if the error is informational only'|||Cynthia,
Although this error is "informational" in that there is no direct action
that you can take, I would view the message as the harbinger of problems
that may hurt you more in the future.
Inside 810885 there is a reference to:
http://support.microsoft.com/default.aspx?kbid=319892
That makes the following comment: If you cannot determine the root cause
immediately, consult the error log for problems and engage in extended
support efforts.
Sounds like Microsoft feels that you should be concerned.
Russell Fields
"cynthia" <anonymous@.discussions.microsoft.com> wrote in message
news:BA5E143F-A0EE-486B-97D7-756D71893984@.microsoft.com...
> Hi,
> Thanks for the reply. Yes I do have autogrow on all the servers and this
one that is giving the error. But there is nothing exceptional about this
server compared to the other servers. No high speed disk system or anything
unusual. This is the only server that has this error and the error 17883
and Q815056 seems to identify what the problem is but the hotfix 815495
didn't resolve the problem. I am wondering if the error is informational
only'|||In the absence of a specific bug, this is likely going to be best-handled an
d troubleshot by Microsoft support. I'd recommend that you engage them as s
oon as possible.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message news:exv7
IzyTEHA.2464@.TK2MSFTNGP10.phx.gbl...
Cynthia,
Although this error is "informational" in that there is no direct action
that you can take, I would view the message as the harbinger of problems
that may hurt you more in the future.
Inside 810885 there is a reference to:
http://support.microsoft.com/default.aspx?kbid=319892
That makes the following comment: If you cannot determine the root cause
immediately, consult the error log for problems and engage in extended
support efforts.
Sounds like Microsoft feels that you should be concerned.
Russell Fields
"cynthia" <anonymous@.discussions.microsoft.com> wrote in message
news:BA5E143F-A0EE-486B-97D7-756D71893984@.microsoft.com...
> Hi,
> Thanks for the reply. Yes I do have autogrow on all the servers and this
one that is giving the error. But there is nothing exceptional about this
server compared to the other servers. No high speed disk system or anything
unusual. This is the only server that has this error and the error 17883
and Q815056 seems to identify what the problem is but the hotfix 815495
didn't resolve the problem. I am wondering if the error is informational
only'|||Thanks Ryan and Russell. You're both right and I have run out of troubleshoo
ting tools for this.sql

Error 17883

The SQL Server is 32 bit - 2000 and I have applied SP3a with hot patch 815495. So it is up to version 818 but I am still getting errors sporadically which are the Process 53:0 (19f8) UMS Context 0x0D2123E8 appears to be non-yielding on Scheduler 0. They are server errors and appear to be happening in the early morning and trying to search the microsoft web site, indicates that these should be corrected.
Are there additional hot patches to correct this problem? Thanks.Cynthia,
Here is an article which seems to outline your problem.
http://support.microsoft.com/default.aspx?scid=kb;en-us;810885
The circumstances for this are fairly specific and there is no hot-patch
according to the article. Do you fit the profile of this article?
Russell Fields
"Cynthia" <anonymous@.discussions.microsoft.com> wrote in message
news:803D34D5-99BD-408F-B767-A29FE8FC112C@.microsoft.com...
> The SQL Server is 32 bit - 2000 and I have applied SP3a with hot patch
815495. So it is up to version 818 but I am still getting errors
sporadically which are the Process 53:0 (19f8) UMS Context 0x0D2123E8
appears to be non-yielding on Scheduler 0. They are server errors and
appear to be happening in the early morning and trying to search the
microsoft web site, indicates that these should be corrected.
> Are there additional hot patches to correct this problem? Thanks.
>|||Hi
Thanks for the reply. Yes I do have autogrow on all the servers and this one that is giving the error. But there is nothing exceptional about this server compared to the other servers. No high speed disk system or anything unusual. This is the only server that has this error and the error 17883 and Q815056 seems to identify what the problem is but the hotfix 815495 didn't resolve the problem. I am wondering if the error is informational only'|||Cynthia,
Although this error is "informational" in that there is no direct action
that you can take, I would view the message as the harbinger of problems
that may hurt you more in the future.
Inside 810885 there is a reference to:
http://support.microsoft.com/default.aspx?kbid=319892
That makes the following comment: If you cannot determine the root cause
immediately, consult the error log for problems and engage in extended
support efforts.
Sounds like Microsoft feels that you should be concerned.
Russell Fields
"cynthia" <anonymous@.discussions.microsoft.com> wrote in message
news:BA5E143F-A0EE-486B-97D7-756D71893984@.microsoft.com...
> Hi,
> Thanks for the reply. Yes I do have autogrow on all the servers and this
one that is giving the error. But there is nothing exceptional about this
server compared to the other servers. No high speed disk system or anything
unusual. This is the only server that has this error and the error 17883
and Q815056 seems to identify what the problem is but the hotfix 815495
didn't resolve the problem. I am wondering if the error is informational
only'|||This is a multi-part message in MIME format.
--=_NextPart_000_001C_01C44EFA.1D839650
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
In the absence of a specific bug, this is likely going to be =best-handled and troubleshot by Microsoft support. I'd recommend that =you engage them as soon as possible.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"Russell Fields" <RussellFields@.NoMailPlease.Com> wrote in message =news:exv7IzyTEHA.2464@.TK2MSFTNGP10.phx.gbl...
Cynthia,
Although this error is "informational" in that there is no direct =action
that you can take, I would view the message as the harbinger of =problems
that may hurt you more in the future.
Inside 810885 there is a reference to:
http://support.microsoft.com/default.aspx?kbid=3D319892
That makes the following comment: If you cannot determine the root =cause
immediately, consult the error log for problems and engage in extended
support efforts.
Sounds like Microsoft feels that you should be concerned.
Russell Fields
"cynthia" <anonymous@.discussions.microsoft.com> wrote in message
news:BA5E143F-A0EE-486B-97D7-756D71893984@.microsoft.com...
> Hi,
>
> Thanks for the reply. Yes I do have autogrow on all the servers =and this
one that is giving the error. But there is nothing exceptional about =this
server compared to the other servers. No high speed disk system or =anything
unusual. This is the only server that has this error and the error =17883
and Q815056 seems to identify what the problem is but the hotfix =815495
didn't resolve the problem. I am wondering if the error is =informational
only'
--=_NextPart_000_001C_01C44EFA.1D839650
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&

---

In the absence of a specific bug, this is likely =going to be best-handled and troubleshot by Microsoft support. I'd recommend =that you engage them as soon as possible.
Thanks,
Ryan Stonecipher
Microsoft SQL Server Storage Engine.
"Russell Fields" wrote in message news:exv7IzyTEHA.2464=@.TK2MSFTNGP10.phx.gbl...Cynthia,Although this error is "informational" in that there is no direct =actionthat you can take, I would view the message as the harbinger of =problemsthat may hurt you more in the future.Inside 810885 there is a reference = to:http://support.microsoft.com/default.aspx?kbid=3D319892">http://s=upport.microsoft.com/default.aspx?kbid=3D319892That makes the following comment: If you cannot determine the root causeimmediately, consult the error log for problems and engage in = extendedsupport efforts.Sounds like Microsoft feels that =you should be concerned.Russell Fields"cynthia" wrote in messagenews:BA5=E143F-A0EE-486B-97D7-756D71893984@.microsoft.com...> Hi,>> Thanks for the reply. Yes I do have =autogrow on all the servers and thisone that is giving the error. But =there is nothing exceptional about thisserver compared to the other servers. No high speed disk system or anythingunusual. =This is the only server that has this error and the error 17883and Q815056 =seems to identify what the problem is but the hotfix 815495didn't =resolve the problem. I am wondering if the error is informationalonly'

---

--=_NextPart_000_001C_01C44EFA.1D839650--|||Thanks Ryan and Russell. You're both right and I have run out of troubleshooting tools for this.

Error (bug?) when hiding subtotals in Report Builder report from AS2005 cube

I consequently get an error

message in Report Builder (version 9.0.2047.0) when I make a report

without subtotals when I have the Key attribute of a dimension in

combination with a measure.

The following Report is OK, but when I unselect Show Subtotals, I get an error message.
Date | Count Result
-
10-10-2003 | 200000
-
Total | 200000

The error message is:
For more information about this error navigate to the report server on the local server machine, or enable remote errors
-
Semantic query execution failed.
-
Query execution failed for data set 'dataSet'.
-
An error has occurred during report processing.

I

have tried experimenting with the GroupingBehaviour on

EncourageGrouping or DiscourageGrouping, but without success. I seem to

be the only one with this problem.

I am using Reporting Services 2005 in combination with Analysis Services 2005 (9.00.2153.00)

Because I don't know if the issue is related to Reporting Services or Analysis Services I posted in both forums.

This is probably Reporting Services problem.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.