A weird problem of Reporting Service

My company is using SQL 2000, Reporting Service SP2, Server 2003, .NET framework 1.1.

We have an ASP.NET application, working properly on one of our test machine, but when we test on another test machine, it would have the following problem:

When we want to view the PDF or EXCEL report generated by Reporting Services, we get prompted to download an ASPX file. If we choose [Open], it will use Visual Studio.NET to open it. But if we choose [Save], and change the extenstion name, it's actually the correct report file.

That means, the report is generated correctly, but we can't open it.

We have added the Content-Disposition to indicate a correct extension name, but that machine still have this weird problem. Frustrately, it works perfectly on our another machine, even without Content-Disposition.

So, we are thinking probably it's related some file system security configuration. Could anyone give me a little hint about it?

Thank you very much!

Hi, we have the same problem. Did you get anywhere with this?|||are u still looking for answer of it?

that's because the server turns on the http compression, stupid IE doesn't understand it.

one thing to work it around is, turn off the compression for aspx, it might affect too much. If that's a concern, change your report generator file from ASPX to another extension, then that extension file won't have compression on. And you can enable asp.net to handle that new extension, which is only used to generate report.

this just works fine for us

A weird problem of Reporting Service

My company is using SQL 2000, Reporting Service SP2, Server 2003, .NET framework 1.1.

We have an ASP.NET application, working properly on one of our test machine, but when we test on another test machine, it would have the following problem:

When we want to view the PDF or EXCEL report generated by Reporting Services, we get prompted to download an ASPX file. If we choose [Open], it will use Visual Studio.NET to open it. But if we choose [Save], and change the extenstion name, it's actually the correct report file.

That means, the report is generated correctly, but we can't open it.

We have added the Content-Disposition to indicate a correct extension name, but that machine still have this weird problem. Frustrately, it works perfectly on our another machine, even without Content-Disposition.

So, we are thinking probably it's related some file system security configuration. Could anyone give me a little hint about it?

Thank you very much!

Hi, we have the same problem. Did you get anywhere with this?|||are u still looking for answer of it?

that's because the server turns on the http compression, stupid IE doesn't understand it.

one thing to work it around is, turn off the compression for aspx, it might affect too much. If that's a concern, change your report generator file from ASPX to another extension, then that extension file won't have compression on. And you can enable asp.net to handle that new extension, which is only used to generate report.

this just works fine for us

A weird problem of Reporting Service

My company is using SQL 2000, Reporting Service SP2, Server 2003, .NET framework 1.1.

We have an ASP.NET application, working properly on one of our test machine, but when we test on another test machine, it would have the following problem:

When we want to view the PDF or EXCEL report generated by Reporting Services, we get prompted to download an ASPX file. If we choose [Open], it will use Visual Studio.NET to open it. But if we choose [Save], and change the extenstion name, it's actually the correct report file.

That means, the report is generated correctly, but we can't open it.

We have added the Content-Disposition to indicate a correct extension name, but that machine still have this weird problem. Frustrately, it works perfectly on our another machine, even without Content-Disposition.

So, we are thinking probably it's related some file system security configuration. Could anyone give me a little hint about it?

Thank you very much!

Hi, we have the same problem. Did you get anywhere with this?|||are u still looking for answer of it?

that's because the server turns on the http compression, stupid IE doesn't understand it.

one thing to work it around is, turn off the compression for aspx, it might affect too much. If that's a concern, change your report generator file from ASPX to another extension, then that extension file won't have compression on. And you can enable asp.net to handle that new extension, which is only used to generate report.

this just works fine for us
sql

A way to control the # of Transport connections

Is there a configuration parameter that allows me to control the number of Transport connections used by service broker? Right now it seems that it just uses one.

There is no such configuration parameter. The only reason to use more than one TCP connection would be if there were multiple NICs having routes to the destination. But since Service Broker does not really bottleneck on the NIC, there was no reaon to add support for multiple TCP connections. However, we may add this support for other reasons.

Rushi

|||

Ok so what should I do if it feels like I am being constrained at around 100 - 150 messages per second through this transport piece? I have done a couple of tests and at one point it seemed if I enqueued more than 100 messages/sec then they would back up into the sys.transmission_queue on the source side. I realize that is by design, but I have been led to believe that I should get something closer to 1,000 messages/sec of throughput between the 2 instances?

Any thoughts?

sql

A stupid question

My sql mail stops responding periodically. I did my
research and I have to restart the SQL Server Service.
Will this affect people using the db if i restart it
whilst they are connections to db. Or do i have to stop
users from connecting to the db and restart it? Sorry for
the silly question.Stopping the SQL Service will kill any DB connections you may have. Stopping
the SQL Server agent will only stop any currently running jobs.
Your research concluded you have to restart the SQL Service, have you
located the root-cause? Do you start getting errors when it stops
responding?
HTH
--
Ray Higdon MCSE, MCDBA, CCNA
--
"Naz" <Milnaz@.hotmail.com> wrote in message
news:0cf601c38357$b9608610$a001280a@.phx.gbl...
> My sql mail stops responding periodically. I did my
> research and I have to restart the SQL Server Service.
> Will this affect people using the db if i restart it
> whilst they are connections to db. Or do i have to stop
> users from connecting to the db and restart it? Sorry for
> the silly question.

a strange issue after installing SP3a (SP3a Issue)

when installing "SQL Server Service Pack 3a" on my "SQL Server Personal
Edition", something strange happened to the windows view data in the Tables
and Views, they are showing RightToLeft!!!!?
how can i fix this? and why did it happen?
please help. and if possible email me the solution to ay_tech@.yahoo.com
Thanks!
Ayman
Message posted via http://www.sqlmonster.com
Would Any One help plese on the Issue ?
Message posted via http://www.sqlmonster.com
|||On Wed, 16 Feb 2005 11:05:43 GMT, Ayman AM via SQLMonster.com wrote:

>when installing "SQL Server Service Pack 3a" on my "SQL Server Personal
>Edition", something strange happened to the windows view data in the Tables
>and Views, they are showing RightToLeft!!!!?
>how can i fix this? and why did it happen?
Hi Ayman,
Is this in Enterprise Manager?
Try this: when displaying tables or views, select "Details" from the
"View" menu (I hope that's the English equivalent - I'm using a Dutch
verwion of Windows). Check the left-most heading above the list of table
names - my guess is that you'll find an upward pointing arrowhead in it,
denoting reverse sort on table- or view-name. Click this header once to
select normal sort (the arrowhead will change to point down). Then, use
the "View" menu again to restore your favorite setting (I think, from your
message, that you're using large pictograms - I always have the details
view selected, but that's just personal preference).
Best, Hugo
(Remove _NO_ and _SPAM_ to get my e-mail address)

a strange issue after installing SP3a (SP3a Issue)

when installing "SQL Server Service Pack 3a" on my "SQL Server Personal
Edition", something strange happened to the windows view data in the Tables
and Views, they are showing RightToLeft!!!!?
how can i fix this? and why did it happen?
please help. and if possible email me the solution to ay_tech@.yahoo.com
Thanks!
Ayman
--
Message posted via http://www.sqlmonster.comWould Any One help plese on the Issue ?
--
Message posted via http://www.sqlmonster.com|||On Wed, 16 Feb 2005 11:05:43 GMT, Ayman AM via SQLMonster.com wrote:
>when installing "SQL Server Service Pack 3a" on my "SQL Server Personal
>Edition", something strange happened to the windows view data in the Tables
>and Views, they are showing RightToLeft!!!!?
>how can i fix this? and why did it happen?
Hi Ayman,
Is this in Enterprise Manager?
Try this: when displaying tables or views, select "Details" from the
"View" menu (I hope that's the English equivalent - I'm using a Dutch
verwion of Windows). Check the left-most heading above the list of table
names - my guess is that you'll find an upward pointing arrowhead in it,
denoting reverse sort on table- or view-name. Click this header once to
select normal sort (the arrowhead will change to point down). Then, use
the "View" menu again to restore your favorite setting (I think, from your
message, that you're using large pictograms - I always have the details
view selected, but that's just personal preference).
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)

a strange issue after installing SP3a (SP3a Issue)

when installing "SQL Server Service Pack 3a" on my "SQL Server Personal
Edition", something strange happened to the windows view data in the Tables
and Views, they are showing RightToLeft!!!!?
how can i fix this? and why did it happen?
please help. and if possible email me the solution to ay_tech@.yahoo.com
Thanks!
Ayman
Message posted via http://www.droptable.comWould Any One help plese on the Issue ?
Message posted via http://www.droptable.com|||On Wed, 16 Feb 2005 11:05:43 GMT, Ayman AM via droptable.com wrote:

>when installing "SQL Server Service Pack 3a" on my "SQL Server Personal
>Edition", something strange happened to the windows view data in the Tables
>and Views, they are showing RightToLeft!!!!?
>how can i fix this? and why did it happen?
Hi Ayman,
Is this in Enterprise Manager?
Try this: when displaying tables or views, select "Details" from the
"View" menu (I hope that's the English equivalent - I'm using a Dutch
verwion of Windows). Check the left-most heading above the list of table
names - my guess is that you'll find an upward pointing arrowhead in it,
denoting reverse sort on table- or view-name. Click this header once to
select normal sort (the arrowhead will change to point down). Then, use
the "View" menu again to restore your favorite setting (I think, from your
message, that you're using large pictograms - I always have the details
view selected, but that's just personal preference).
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)

A significant part of sql server process memory has been paged out

On a SQL Server 2005 x64 Standard Edition cluster I get the error listed below and then the SQL server service restarts. The SQL server is unavailable for 5-10 minutes during that time. Any ideas?

Error:

A significant part of sql server process memory has been paged out. This may result in a performance degradation. Duration: 647 seconds. Working set (KB): 11907776, committed (KB): 28731732, memory utilization: 41%%.

This means that Windows has decided to move SQL Server memory out of RAM and stored it in disk until it's needed again. This article has some more information on how to avoid this:

http://support.microsoft.com/kb/918483/en-us

You also mentioned that SQL Server has restarted after this. Could you please post the last 10 lines or so of errorlog when this occurred?

Thanks,

Fabricio.

|||

I did look at that article but I don't think that will work for SQL Standard Edition.

Note SQL Server 2005 Enterprise Edition is the only edition that is designed to use lock pages in memory.

|||

In that case, try to identify what's causing Windows to page SQL Server out to disk. SQL Server tries to fill up the available memory on the machine. When you have other apps running on the same machine, they may use a lot of memory and push SQL Server out to the swap file. SQL Server will detect this and trim its memory, but in some rare cases it can't release enough memory or can't release fast enough and may end up being swapped out. This message is to notify you that such event happened and that SQL Server's memory is being fetched from disk, causing some temporary slowness.

Please, let me know if you need help figuring out what app is using memory on the machine.

Thanks,

Fabricio.

|||

I believe the KB article is incorrect stating it’s only valid for x64 Enterprise Edition. I encountered the same problem you reported and the Lock Pages In Memory policy work just fine with x64 standard edition.

|||

This article explains the problem I was having:

http://blogs.technet.com/askperf/archive/2007/05/18/sql-and-the-working-set.aspx

The system was running Windows 2003 SP1. Have upgraded to Windows 2003 SP2 and have not had the problem since.

|||

Kmoskal,

The KB article is correct. Only SQL Server Enterprise will lock pages in memory. You may set the priviledge with any other edition, but it will have no effect in SQL Server. I guess you just have been lucky (and SQL Server has been doing a great job keeping itself in RAM) :-)

Thanks,

Fabricio.

a service pack question...

background: sql2k
I have a quick question about sql sp3a.
when i apply the sp3a, is that just for the sql or for analysis service
as well?
if i have ananlysis services installed, do you need to apply the sp3
for analysis service seperately (in MSOLAP|install|setup on the sp3a
CD) or sql sp3a will take care of it? thank you.> I have a quick question about sql sp3a.
> when i apply the sp3a, is that just for the sql or for analysis service
> as well?
No.

> if i have ananlysis services installed, do you need to apply the sp3
> for analysis service seperately (in MSOLAP|install|setup on the sp3a
> CD)
Yes.

> or sql sp3a will take care of it? thank you.
No.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com

'A required privilege is not held by the client' when re-initalization

Hi all,
the sys admin has changed the service a/c to another admin. id. But now, i can't start the replication jobs even re-created the publication and subscription with the new admin. id. Any advise? Thanks in advance!

'Executed as user: test.com\admin. A required privilege is not held by the client. The step failed.'

Hi Stephaine,

How do your admin change the service account? He/she might use Windows Service Control Manager to change account. To solve the issue, please refer to this KB article (http://support.microsoft.com/kb/911305/en-us).

Thanks,

Peng

|||an issue i found was that sql server agent and ssis had been changed to not use the local system account. this caused me to continually get the dreaded --> "A required privilege is not held by the client" error. i fought with it all afternoon and eventually updated the services to use the local system account and it worked. perhaps this will save some other as much time as i wasted.

'A required privilege is not held by the client' when re-initalization

Hi all,
the sys admin has changed the service a/c to another admin. id. But now, i can't start the replication jobs even re-created the publication and subscription with the new admin. id. Any advise? Thanks in advance!

'Executed as user: test.com\admin. A required privilege is not held by the client. The step failed.'

Hi Stephaine,

How do your admin change the service account? He/she might use Windows Service Control Manager to change account. To solve the issue, please refer to this KB article (http://support.microsoft.com/kb/911305/en-us).

Thanks,

Peng

|||an issue i found was that sql server agent and ssis had been changed to not use the local system account. this caused me to continually get the dreaded --> "A required privilege is not held by the client" error. i fought with it all afternoon and eventually updated the services to use the local system account and it worked. perhaps this will save some other as much time as i wasted.