SQL RS 2000 problem with web service/Virtual directory

We're having a problem which appears to affect 5-10 clients using SQL RS
2000.

It seems randomly, the reporting services web service will stop responding.
We get timeout errors when trying to run reports through our web based
application, and the http://localhost/reportserver virtual directory becomes

unavailable.

We've narrowed the fix down to restarting the reporting services web
service, and doing an IIS reset. We've tried using a separate app pool
within IIS and while it cuts the number a bit, the problem persists.

Other VD's on IIS are not affected, so I'm leaning towards the problem being
with RS 2000. Does anyone know of a particular configuration/update that
might cause this ? We have dozens of people using this config (sql 2000, w/
sql rs 2000) and only a handful are having the issue. I've googled my
brains out...

Any help would be appreciated.

Re: SQL RS 2000 problem with web service/Virtual directory

What does the log files say? The event log? Any error message returned to
the client?

If you think this is a problem with RS 2000 i would recommend you to post
this question in a newsgroup related to SQL Server (and RS 2000). We do
not see this kind of questions often, so the experts of SQL Server does
not visit this newsgroup.



--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


AJPLeBlancTSS wrote:

>We're having a problem which appears to affect 5-10 clients using SQL RS
>2000.
>
>It seems randomly, the reporting services web service will stop responding.
>We get timeout errors when trying to run reports through our web based
>application, and the http://localhost/reportserver virtual directory
>becomes
>
>unavailable.
>
>We've narrowed the fix down to restarting the reporting services web
>service, and doing an IIS reset. We've tried using a separate app pool
>within IIS and while it cuts the number a bit, the problem persists.
>
>Other VD's on IIS are not affected, so I'm leaning towards the problem
>being
>with RS 2000. Does anyone know of a particular configuration/update that
>might cause this ? We have dozens of people using this config (sql 2000,
>w/
>sql rs 2000) and only a handful are having the issue. I've googled my
>brains out...
>
>Any help would be appreciated.

Re: SQL RS 2000 problem with web service/Virtual directory

Thanks Kristofer,

I actually cross posted this message to both groups.
I'd hoped to make sure that I wasn't missing something.
I welcome any suggestions from anyone who might be able
to help us with this issue.

Thanks again.
~Andy

"Kristofer Gafvert" wrote:

> What does the log files say? The event log? Any error message returned to
> the client?
>
> If you think this is a problem with RS 2000 i would recommend you to post
> this question in a newsgroup related to SQL Server (and RS 2000). We do
> not see this kind of questions often, so the experts of SQL Server does
> not visit this newsgroup.
>
>
>
> --
> Regards,
> Kristofer Gafvert
> http://www.gafvert.info/iis/ - IIS Related Info
>
>
> AJPLeBlancTSS wrote:
>
> >We're having a problem which appears to affect 5-10 clients using SQL RS
> >2000.
> >
> >It seems randomly, the reporting services web service will stop responding.
> >We get timeout errors when trying to run reports through our web based
> >application, and the http://localhost/reportserver virtual directory
> >becomes
> >
> >unavailable.
> >
> >We've narrowed the fix down to restarting the reporting services web
> >service, and doing an IIS reset. We've tried using a separate app pool
> >within IIS and while it cuts the number a bit, the problem persists.
> >
> >Other VD's on IIS are not affected, so I'm leaning towards the problem
> >being
> >with RS 2000. Does anyone know of a particular configuration/update that
> >might cause this ? We have dozens of people using this config (sql 2000,
> >w/
> >sql rs 2000) and only a handful are having the issue. I've googled my
> >brains out...
> >
> >Any help would be appreciated.
>

Re: SQL RS 2000 problem with web service/Virtual directory

I think you multiposted (two individually posts that are not related to
each other), that is why i cannot see that you posted to the other
newsgroup. Otherwise i would see the other newsgroup's name in my news
reader (and replies made here would show up in both newsgroups).

I hope the SQL Server experts can give you some specific help on this
product. If not, we can help you with some general troubleshooting by
checking the logs and see if we can understand the problem (it usually
however often requires some knowledge about the product that is failing).

--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


AJPLeBlancTSS wrote:

>Thanks Kristofer,
>
>I actually cross posted this message to both groups.
>I'd hoped to make sure that I wasn't missing something.
>I welcome any suggestions from anyone who might be able
>to help us with this issue.
>
>Thanks again.
>~Andy
>
>"Kristofer Gafvert" wrote:
>
>>What does the log files say? The event log? Any error message returned to
>>the client?
>>
>>If you think this is a problem with RS 2000 i would recommend you to post
>>this question in a newsgroup related to SQL Server (and RS 2000). We do
>>not see this kind of questions often, so the experts of SQL Server does
>>not visit this newsgroup.
>>
>>
>>
>>--
>>Regards,
>>Kristofer Gafvert
>>http://www.gafvert.info/iis/ - IIS Related Info
>>
>>
>>AJPLeBlancTSS wrote:
>>
>>>We're having a problem which appears to affect 5-10 clients using SQL RS
>>>2000.
>>>
>>>It seems randomly, the reporting services web service will stop
>>>responding.
>>>We get timeout errors when trying to run reports through our web based
>>>application, and the http://localhost/reportserver virtual directory
>>>becomes
>>>
>>>unavailable.
>>>
>>>We've narrowed the fix down to restarting the reporting services web
>>>service, and doing an IIS reset. We've tried using a separate app pool
>>>within IIS and while it cuts the number a bit, the problem persists.
>>>
>>>Other VD's on IIS are not affected, so I'm leaning towards the problem
>>>being
>>>with RS 2000. Does anyone know of a particular configuration/update that
>>>might cause this ? We have dozens of people using this config (sql 2000,
>>>w/
>>>sql rs 2000) and only a handful are having the issue. I've googled my
>>>brains out...
>>>
>>>Any help would be appreciated.
>>