Hopefully this will be a simple question.
Where is the error log located? I am looking in
program files\microsoft sql server\mssql\reporting services\LogFile
at a file called ReportServer__09_27_2005_11_38_23.log inside that file is a
message:
e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details., ;
Where can I fine the error log it refers to? Everything has been installed
to default locations.
ThanksYou are looking at the error log. The log contains the text that is
displayed to users so it is a little misleading when seeing it in the log
itself. Can you include the entire call stack?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Nicola Jones" <NicolaJones@.discussions.microsoft.com> wrote in message
news:83BFFE98-BBF5-4CD6-9D71-CAC85D4E3228@.microsoft.com...
> Hopefully this will be a simple question.
> Where is the error log located? I am looking in
> program files\microsoft sql server\mssql\reporting services\LogFile
> at a file called ReportServer__09_27_2005_11_38_23.log inside that file is
> a
> message:
> e ERROR: Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for
> more
> details., ;
> Where can I fine the error log it refers to? Everything has been
> installed
> to default locations.
> Thanks|||Thanks for that. I am getting different errors in the log at different times
from the same problem. The problem in detailed in my post "Login Prompt
after ~3min timeout".
I am reguarly getting out memory errors, but I have looked at the machine
and it is only using ~1/3 of available memory and CPU so I think that is a
red herring.
The report runs fine if the data allows it to complete before 2.5 - 3mins -
this seems to be 2.5mins on the test server I am using and 3mins on the live
environment.
The following messages are the only consistant ones I am seeing in the log:
w3wp!runningjobs!1568!28/09/2005-09:46:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!1568!28/09/2005-09:46:45:: w WARN:
RunningJobContext.Cancel; failed
w3wp!runningjobs!1568!28/09/2005-09:47:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!15f0!28/09/2005-09:48:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!15f0!28/09/2005-09:49:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!15f0!28/09/2005-09:50:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!fe4!28/09/2005-09:51:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
w3wp!runningjobs!15f0!28/09/2005-09:52:45:: i INFO:
RunningJobContext.IsClientConnected; found orphaned request
Any thoughts, pointers or suggestions will be gratefully received.
"Daniel Reib [MSFT]" wrote:
> You are looking at the error log. The log contains the text that is
> displayed to users so it is a little misleading when seeing it in the log
> itself. Can you include the entire call stack?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Nicola Jones" <NicolaJones@.discussions.microsoft.com> wrote in message
> news:83BFFE98-BBF5-4CD6-9D71-CAC85D4E3228@.microsoft.com...
> > Hopefully this will be a simple question.
> >
> > Where is the error log located? I am looking in
> >
> > program files\microsoft sql server\mssql\reporting services\LogFile
> >
> > at a file called ReportServer__09_27_2005_11_38_23.log inside that file is
> > a
> > message:
> >
> > e ERROR: Throwing
> > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> > An internal error occurred on the report server. See the error log for
> > more
> > details., ;
> >
> > Where can I fine the error log it refers to? Everything has been
> > installed
> > to default locations.
> >
> > Thanks
>
>|||The orphaned requests means that the client is disconnected from the server.
In this case RS will stop processing the job.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Nicola Jones" <NicolaJones@.discussions.microsoft.com> wrote in message
news:E2F9A42E-C173-4B35-8BA3-749239454E90@.microsoft.com...
> Thanks for that. I am getting different errors in the log at different
> times
> from the same problem. The problem in detailed in my post "Login Prompt
> after ~3min timeout".
> I am reguarly getting out memory errors, but I have looked at the machine
> and it is only using ~1/3 of available memory and CPU so I think that is a
> red herring.
> The report runs fine if the data allows it to complete before 2.5 -
> 3mins -
> this seems to be 2.5mins on the test server I am using and 3mins on the
> live
> environment.
> The following messages are the only consistant ones I am seeing in the
> log:
> w3wp!runningjobs!1568!28/09/2005-09:46:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!1568!28/09/2005-09:46:45:: w WARN:
> RunningJobContext.Cancel; failed
> w3wp!runningjobs!1568!28/09/2005-09:47:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!15f0!28/09/2005-09:48:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!15f0!28/09/2005-09:49:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!15f0!28/09/2005-09:50:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!fe4!28/09/2005-09:51:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> w3wp!runningjobs!15f0!28/09/2005-09:52:45:: i INFO:
> RunningJobContext.IsClientConnected; found orphaned request
> Any thoughts, pointers or suggestions will be gratefully received.
> "Daniel Reib [MSFT]" wrote:
>> You are looking at the error log. The log contains the text that is
>> displayed to users so it is a little misleading when seeing it in the log
>> itself. Can you include the entire call stack?
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Nicola Jones" <NicolaJones@.discussions.microsoft.com> wrote in message
>> news:83BFFE98-BBF5-4CD6-9D71-CAC85D4E3228@.microsoft.com...
>> > Hopefully this will be a simple question.
>> >
>> > Where is the error log located? I am looking in
>> >
>> > program files\microsoft sql server\mssql\reporting services\LogFile
>> >
>> > at a file called ReportServer__09_27_2005_11_38_23.log inside that file
>> > is
>> > a
>> > message:
>> >
>> > e ERROR: Throwing
>> > Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
>> > An internal error occurred on the report server. See the error log for
>> > more
>> > details., ;
>> >
>> > Where can I fine the error log it refers to? Everything has been
>> > installed
>> > to default locations.
>> >
>> > Thanks
>>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment