Reporting services and microsoft exchange on the same computer

could u say if there would be a problem with reporting services and
microsoft exchange running on the same computerThere is no reason this shouldn't work, but just evaluate whether your
server can cope with the expected loads from the two apps.
Chris
Dale wrote:
> could u say if there would be a problem with reporting services and
> microsoft exchange running on the same computer|||Just keep on eye on the resource usage - see if CPU is consistently high, or
there is lots of paging.
Basically it depends on usage of both applications.
"Dale" wrote:
> could u say if there would be a problem with reporting services and
> microsoft exchange running on the same computer|||Thank you. Are there any known issues with Windows Server 2003 SP1?
"Mary Bray [SQL Server MVP]" wrote:
> Just keep on eye on the resource usage - see if CPU is consistently high, or
> there is lots of paging.
> Basically it depends on usage of both applications.
>
> "Dale" wrote:
> > could u say if there would be a problem with reporting services and
> > microsoft exchange running on the same computer

Reporting Services affected by a server name change?

We are running 64-bit SQL Server 2005 build 3200 on a 64-bit Windows 2003
operating system. We had Reporting Services installed and configured but we
did not use it. A couple of weeks ago the server name was changed. I ran
sp_dropserver and then sp_addserver.
Since then our client want to utilize Reporting Services. Although
configured it is not working. I cannot even access Reporting Services
through SQL Server Management Studio. Could this be the result of the server
name change? What should be done with Reporting Services in the event of a
server name change?Go to RS Config Manager (Start Menu\Programs\Microsoft SQL Server
2005\Configuration Tools)
-Database Setup:
-Change the name in the "Server Name" field to your server's new name
-Click on "Connect"
-Click on "Apply"
-Encryption keys
-Click on "Delete" and Ok (deleting this can give you problems on an
active production server)
-Open the file C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\rsreportserver.config
and change the line
<UrlRoot>http://OldServerName/reportserver</UrlRoot>
to
<UrlRoot>http://NewServerName/reportserver</UrlRoot>
-In MSIE, check the following addresses:
http://localhost/reports
http://localhost/reportserver
-Try to connect to Reporting Services through Management Studio
--
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Loren Z" <anonymous@.discussions.microsoft.com> wrote in message
news:e$M4P4ThIHA.2268@.TK2MSFTNGP02.phx.gbl...
> We are running 64-bit SQL Server 2005 build 3200 on a 64-bit Windows 2003
> operating system. We had Reporting Services installed and configured but
> we did not use it. A couple of weeks ago the server name was changed. I
> ran sp_dropserver and then sp_addserver.
> Since then our client want to utilize Reporting Services. Although
> configured it is not working. I cannot even access Reporting Services
> through SQL Server Management Studio. Could this be the result of the
> server name change? What should be done with Reporting Services in the
> event of a server name change?
>

Reporting Services affected by a server name change?

We are running 64-bit SQL Server 2005 build 3200 on a 64-bit Windows 2003
operating system. We had Reporting Services installed and configured but we
did not use it. A couple of weeks ago the server name was changed. I ran
sp_dropserver and then sp_addserver.
Since then our client want to utilize Reporting Services. Although
configured it is not working. I cannot even access Reporting Services
through SQL Server Management Studio. Could this be the result of the server
name change? What should be done with Reporting Services in the event of a
server name change?Go to RS Config Manager (Start Menu\Programs\Microsoft SQL Server
2005\Configuration Tools)
-Database Setup:
-Change the name in the "Server Name" field to your server's new name
-Click on "Connect"
-Click on "Apply"
-Encryption keys
-Click on "Delete" and Ok (deleting this can give you problems on an
active production server)
-Open the file C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\rsreportserver.config
and change the line
<UrlRoot>http://OldServerName/reportserver</UrlRoot>
to
<UrlRoot>http://NewServerName/reportserver</UrlRoot>
-In MSIE, check the following addresses:
http://localhost/reports
http://localhost/reportserver
-Try to connect to Reporting Services through Management Studio
--
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Loren Z" <anonymous@.discussions.microsoft.com> wrote in message
news:e$M4P4ThIHA.2268@.TK2MSFTNGP02.phx.gbl...
> We are running 64-bit SQL Server 2005 build 3200 on a 64-bit Windows 2003
> operating system. We had Reporting Services installed and configured but
> we did not use it. A couple of weeks ago the server name was changed. I
> ran sp_dropserver and then sp_addserver.
> Since then our client want to utilize Reporting Services. Although
> configured it is not working. I cannot even access Reporting Services
> through SQL Server Management Studio. Could this be the result of the
> server name change? What should be done with Reporting Services in the
> event of a server name change?
>sql

Reporting Services affected by a server name change?

We are running 64-bit SQL Server 2005 build 3200 on a 64-bit Windows 2003
operating system. We had Reporting Services installed and configured but we
did not use it. A couple of weeks ago the server name was changed. I ran
sp_dropserver and then sp_addserver.
Since then our client want to utilize Reporting Services. Although
configured it is not working. I cannot even access Reporting Services
through SQL Server Management Studio. Could this be the result of the server
name change? What should be done with Reporting Services in the event of a
server name change?
Go to RS Config Manager (Start Menu\Programs\Microsoft SQL Server
2005\Configuration Tools)
-Database Setup:
-Change the name in the "Server Name" field to your server's new name
-Click on "Connect"
-Click on "Apply"
-Encryption keys
-Click on "Delete" and Ok (deleting this can give you problems on an
active production server)
-Open the file C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\rsreportserver.config
and change the line
<UrlRoot>http://OldServerName/reportserver</UrlRoot>
to
<UrlRoot>http://NewServerName/reportserver</UrlRoot>
-In MSIE, check the following addresses:
http://localhost/reports
http://localhost/reportserver
-Try to connect to Reporting Services through Management Studio
Alain Quesnel
alainsansspam@.logiquel.com
www.logiquel.com
"Loren Z" <anonymous@.discussions.microsoft.com> wrote in message
news:e$M4P4ThIHA.2268@.TK2MSFTNGP02.phx.gbl...
> We are running 64-bit SQL Server 2005 build 3200 on a 64-bit Windows 2003
> operating system. We had Reporting Services installed and configured but
> we did not use it. A couple of weeks ago the server name was changed. I
> ran sp_dropserver and then sp_addserver.
> Since then our client want to utilize Reporting Services. Although
> configured it is not working. I cannot even access Reporting Services
> through SQL Server Management Studio. Could this be the result of the
> server name change? What should be done with Reporting Services in the
> event of a server name change?
>

Reporting Services Access Problem

I have one problem that must deal with security and I have tried everything to no avail. Reporting Services is running fine, I can deploy, I can see the link to the report in the browser. When I click the link I get Access Denied. All my IIS settings are as RS set them during the install. I am the administrator of the computer. I have given full control to all the folders that I think RS needs. If anyone has a suggestion please reply, thank you

GerryAre you connected to the Database??
|||In IIS, try unchecking the option to allow anonymous access and then click the link logged in as the local administrator (or add yourself to the local admins). If that works add the other credentials to RS security. Let me know if this helps.

Reporting Services 2005 Report Builder

Does anyone know if RS 2005 report builder will work on databases other than SQL Server 2005?

In other words, say I have SQL Server 2005 running Reporting Service 2005 and want to allow the end users to build their own ad-hoc reports against a SQL Server 2000 application database... would this be possible?
Thanks,
-KirkYes, Report Builder will work against both SQL Server (2000 and 2005) and Analysis Services 2005. We are working on support for additional databases.|||So does it mean Report Builder will be supporting other databases such as Oracle or OLE DB datasources? What about supporting a custom data provider (as in Report Designer)?

Thanks!|||I think it depends on the report model that you created.sql

Reporting Services 2005 Report Builder

Does anyone know if RS 2005 report builder will work on databases other than SQL Server 2005?

In other words, say I have SQL Server 2005 running Reporting Service 2005 and want to allow the end users to build their own ad-hoc reports against a SQL Server 2000 application database... would this be possible?
Thanks,
-KirkYes, Report Builder will work against both SQL Server (2000 and 2005) and Analysis Services 2005. We are working on support for additional databases.|||So does it mean Report Builder will be supporting other databases such as Oracle or OLE DB datasources? What about supporting a custom data provider (as in Report Designer)?

Thanks!|||I think it depends on the report model that you created.

Reporting Services 2005 on Windows 2000 SP4 Domain Controller

Hi all,

I'm experiencing a problem with Reporting Services 2005 running on a Windows 2000 AD Domain Controller.

Installation has been done correctly, SQL 2005 and SSRS 2005 are running correctly (I've followed Microsoft KB911846 to solve the "not dtarting after installation" problem).

Accessing reports virtual folder (http://machinename/reports) from localhost, logged on with user Administrator Report Builder option displays correctly. Also accessing from LAN, but with user Administrator, displys Report Builder Option.

Report Builder button is not displayed with other users (i.e. user Dave)

I've given user Dave same permission as Administrator (Content Manager, in SSRS) but Report Buildr still can't be viewed.

If it can be userful to understand this strange behaviour, looking in "Reporting Services Configuration" tool I can see that Web Service Identity is reported as Not configured, with a beautiful red X besides.

Can someone please help me?

Thank you very much for any suggestion.

Regards,

Dave

Solved! :-)

Just had to set domain users as "System Users" in Report Server Management

Dave

Reporting Services 2005 on Windows 2000 server

Hi,

I successfully got SQL 2005 Express with reporting services running under VISTA. Developed some reports in the VISTA environment. However, my target system is a Windows 2000 server. We installed SQL 2005 w/reporting services onto the Windows 2000 server. SQL2005 Database is up and running. Reporting Services are running, IIS RRS virtual directories are built, RRS databases are built. I can do everything except deploy reports from Business Intelligent Studio. I can preview reports, just cannot deploy. The Reporting Services indicate 1 failure in its configuration; the Web Service Identity. It is loaded with <server>\ASPNET. I cannot get rid of this error. I assume this is the problem. After digging around I found that Windows 2000 does not have an ASPNET user, it uses the IWAM user instead. Reporting services did not run at all till I changed the rs config file and put the IWAM user in as <WebServiceAccount>.

Does anyone have Reporting services 2005 running on Windows 2000 server? Anyone know how to fix the Web Service Identity error I am getting?

Thanks

Could you please post the whole error message ?|||

I have the same problem too...

I can't change the value of ASP .NET Service Account in the text box and when I try to apply what is proposed (MACHINENAME\ASPNET - that don't exists), I receive the following error:

ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 8007056B

at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)

I hope in a solution ....

|||

Hi Matteo and rodgerst,

Could you, please, connect to your Report Server instance using the config tool, choose Report Server and Report Manager virtual directories tabs, check Apply Default Settings, and then press Apply?

If the previous workaround was not working, could you, please, go to this registry key corresponding to the RS instance:

HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL.x\Setup

and look for this key: ReportManagerIdentityConfigured. Please change its value to what you want to have for your web service identity (the IWAM user).

I hope it helps. Please let me know how this is working for you.

Mihaela

|||

Hi Mihaela

I've tried the first workaround, close and open RS Config Manager but ....nothing: a red X on web service identity and a locked textbox with the same wrong value.

The value specified in the second workaround don't exists in the registry key, and in entire registry... I've tried to create it, close and reopen Config Manager but .... nothing ....

If can be useful at this link i've saved a screenshot of registry

http://www.matteodistefano.it/public/registrySS.gif

Thanks in advance

Matteo

|||

Matteo,

I see from your screenshot that you have SQL Express Advanced SP1 installed on the Windows 2000 machine, which is your Reporting Services server. I would suggest to try to install SP2 and see if this is working.

Thank you,

Mihaela

|||

Hi Mihaela

Thanks for your answer,

For the moment I can't access directly to it, so I won't risk to install a service pack remotely on a production server.

I'll do it after 6 weeks.

Any other suggestions are appreciate.

Thanks

|||

Tried applying default settings; did not help. Tried regedit; ReportManagerIdentityConfigured is not a key in either MSSQL.1 or MSSQL.2. Should I try adding it to MSSQL.2\Setup?

|||My registry looks like Matteo's snapshot except we are running the Enterprise Evaluation Edition.

Reporting Services 2005 on Windows 2000 server

Hi,

I successfully got SQL 2005 Express with reporting services running under VISTA. Developed some reports in the VISTA environment. However, my target system is a Windows 2000 server. We installed SQL 2005 w/reporting services onto the Windows 2000 server. SQL2005 Database is up and running. Reporting Services are running, IIS RRS virtual directories are built, RRS databases are built. I can do everything except deploy reports from Business Intelligent Studio. I can preview reports, just cannot deploy. The Reporting Services indicate 1 failure in its configuration; the Web Service Identity. It is loaded with <server>\ASPNET. I cannot get rid of this error. I assume this is the problem. After digging around I found that Windows 2000 does not have an ASPNET user, it uses the IWAM user instead. Reporting services did not run at all till I changed the rs config file and put the IWAM user in as <WebServiceAccount>.

Does anyone have Reporting services 2005 running on Windows 2000 server? Anyone know how to fix the Web Service Identity error I am getting?

Thanks

Could you please post the whole error message ?|||

I have the same problem too...

I can't change the value of ASP .NET Service Account in the text box and when I try to apply what is proposed (MACHINENAME\ASPNET - that don't exists), I receive the following error:

ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 8007056B

at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)

I hope in a solution ....

|||

Hi Matteo and rodgerst,

Could you, please, connect to your Report Server instance using the config tool, choose Report Server and Report Manager virtual directories tabs, check Apply Default Settings, and then press Apply?

If the previous workaround was not working, could you, please, go to this registry key corresponding to the RS instance:

HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL.x\Setup

and look for this key: ReportManagerIdentityConfigured. Please change its value to what you want to have for your web service identity (the IWAM user).

I hope it helps. Please let me know how this is working for you.

Mihaela

|||

Hi Mihaela

I've tried the first workaround, close and open RS Config Manager but ....nothing: a red X on web service identity and a locked textbox with the same wrong value.

The value specified in the second workaround don't exists in the registry key, and in entire registry... I've tried to create it, close and reopen Config Manager but .... nothing ....

If can be useful at this link i've saved a screenshot of registry

http://www.matteodistefano.it/public/registrySS.gif

Thanks in advance

Matteo

|||

Matteo,

I see from your screenshot that you have SQL Express Advanced SP1 installed on the Windows 2000 machine, which is your Reporting Services server. I would suggest to try to install SP2 and see if this is working.

Thank you,

Mihaela

|||

Hi Mihaela

Thanks for your answer,

For the moment I can't access directly to it, so I won't risk to install a service pack remotely on a production server.

I'll do it after 6 weeks.

Any other suggestions are appreciate.

Thanks

|||

Tried applying default settings; did not help. Tried regedit; ReportManagerIdentityConfigured is not a key in either MSSQL.1 or MSSQL.2. Should I try adding it to MSSQL.2\Setup?

|||My registry looks like Matteo's snapshot except we are running the Enterprise Evaluation Edition.sql

Reporting Services 2005 on Vista

Hi All
When I go to http://localhost/reports on my laptop running Vista and SQL
Server Reporting Services 2005 SP2 I recive the following error:
HTTP Error 401.1 - Unauthorized
Description: You do not have permission to view this directory or page using
the credentials that you supplied.
Does anyone know how to resolve this?
Thanks
- DavidNot sure if this is to do with you having to be logged in to the machine as
Admin or someone with admin rights.
"David" wrote:
> Hi All
> When I go to http://localhost/reports on my laptop running Vista and SQL
> Server Reporting Services 2005 SP2 I recive the following error:
> HTTP Error 401.1 - Unauthorized
> Description: You do not have permission to view this directory or page using
> the credentials that you supplied.
> Does anyone know how to resolve this?
> Thanks
> - David
>|||I don't run Vista but here is a post I saved that might help you:
>>>>>
1) Control Panel / User Accounts / Turn User Account Control - off
2) run "%windir%\Microsoft.NET\Framework\version\aspnet_regiis.exe" -i
>>>>>>
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"David" <David@.discussions.microsoft.com> wrote in message
news:90D7717A-5883-4EB8-BFDF-A97EE9E5FE40@.microsoft.com...
> Hi All
> When I go to http://localhost/reports on my laptop running Vista and SQL
> Server Reporting Services 2005 SP2 I recive the following error:
> HTTP Error 401.1 - Unauthorized
> Description: You do not have permission to view this directory or page
> using
> the credentials that you supplied.
> Does anyone know how to resolve this?
> Thanks
> - David
>

Reporting Services 2005 BestPractises Question

Hi,

We're starting to migrate from Crystal Enterprise to SSRS2005, and had some performance-related questions in relation to complex reports running against large tables.

Scenario:

. We have fairly large source tables, some greater than 5 million rows

. We use fairly complex stored procs which use dynamic sql based on about 10-15 search criterias entered on web page

. Currently our web middle tier calls a stored proc which inserts into a report table. Then UI calls the report which has SQL query to filter the report table on the UserId and shows only the rows for that user.

Question:

. Is this method - running stored proc in app which inserts into table, then asking report to filter the table based on UserID - considered the best way for designing and running complex SSRS2005 reports with lots of data?

(or)

. Is it better to directly run the stored proc from the report and return the resultset directly to the report?

Advantages or disadvantages of either method, useful articles, best practises...all are appreciated.

Thanks,

JGP

In general, only feed the data you want to present into the report. It's much faster to filter data out on the back end than it is to package it up (even if it's not going across the wire) and send it to Report Server.

You can replace the default parameter handling (by using the WebForms control or Url Access) if you don't like the way our parameters are shown (with 10-15 search criteria, this is probably a good idea).

Why not have the report itself call your stored procedure directly w/o the need for the intermediate table? If the number of rows returned is reasonable (ie, criterial + userid is passed to the stored proc) then this should be fine. How many rows per criteria/userid will be returned? How many KB? Query Analyzer will tell you this.

I would make sure to test whatever choices you make. Don't take anyone elses word for how your machines will perform. Use Microsoft ACT or Visual Studio 2005 and validate all assumptions. Please.

Thanks, Donovan.

|||

I must have a misunderstanding on this. I thought it was better to package it up and send it over to RS and use filters so that RS could cache the result set. Do I have a disconnect here?

R

|||

Sending 5m rows across the wire is slow. Filtering/aggregating in SQL is much faster than the overhead of serializing/deserializing and hitting the wire with a bunch of data a particular rendering isn't going to use. Live reports work much better if the only data RS has to deal with is the data it actualy displays. This isn't just true of RS but any application that deals with a database backend.

Of course, I'm generalizing and simplifying and the real answer is more of an "it depends on your report and your usage". But hopefully this explains my comment better.

Thanks, Donovan.

|||

I think the value in cache is negated by the potentially large recordsets that RS must sift through for grouping/sorting. Use procs for everything, we use temp tables rathen than real table with each temp table being called from a perspective proc and destroyed at connection close. For example, we have reports that return a weeks worth of data(40,000 rows), I organize it by day/product by selecting from the base table into a temp and then returning the 7 rows for the day report to RS.

I also find manging paramters in RS beteer than procs. For example, I ask for one date parameter and the derive all the others from it where I can. For example, a report will show this week, last week and last six months turn around time for a product(s). By managing the parameters in RS, I can just pass the different params to the same sproc although they are set up a different datasets. I've toyed with the idea of adding another input parameter to the procs to push the date manipulation back into the backend.

My general philosphy is to use RS(or any other tool) as a presentation layer and do all calcs except for basic summing, avergaing, etc.. in the DB.

sql

Reporting Services 2005 BestPractises Question

Hi,

We're starting to migrate from Crystal Enterprise to SSRS2005, and had some performance-related questions in relation to complex reports running against large tables.

Scenario:

. We have fairly large source tables, some greater than 5 million rows

. We use fairly complex stored procs which use dynamic sql based on about 10-15 search criterias entered on web page

. Currently our web middle tier calls a stored proc which inserts into a report table. Then UI calls the report which has SQL query to filter the report table on the UserId and shows only the rows for that user.

Question:

. Is this method - running stored proc in app which inserts into table, then asking report to filter the table based on UserID - considered the best way for designing and running complex SSRS2005 reports with lots of data?

(or)

. Is it better to directly run the stored proc from the report and return the resultset directly to the report?

Advantages or disadvantages of either method, useful articles, best practises...all are appreciated.

Thanks,

JGP

In general, only feed the data you want to present into the report. It's much faster to filter data out on the back end than it is to package it up (even if it's not going across the wire) and send it to Report Server.

You can replace the default parameter handling (by using the WebForms control or Url Access) if you don't like the way our parameters are shown (with 10-15 search criteria, this is probably a good idea).

Why not have the report itself call your stored procedure directly w/o the need for the intermediate table? If the number of rows returned is reasonable (ie, criterial + userid is passed to the stored proc) then this should be fine. How many rows per criteria/userid will be returned? How many KB? Query Analyzer will tell you this.

I would make sure to test whatever choices you make. Don't take anyone elses word for how your machines will perform. Use Microsoft ACT or Visual Studio 2005 and validate all assumptions. Please.

Thanks, Donovan.

|||

I must have a misunderstanding on this. I thought it was better to package it up and send it over to RS and use filters so that RS could cache the result set. Do I have a disconnect here?

R

|||

Sending 5m rows across the wire is slow. Filtering/aggregating in SQL is much faster than the overhead of serializing/deserializing and hitting the wire with a bunch of data a particular rendering isn't going to use. Live reports work much better if the only data RS has to deal with is the data it actualy displays. This isn't just true of RS but any application that deals with a database backend.

Of course, I'm generalizing and simplifying and the real answer is more of an "it depends on your report and your usage". But hopefully this explains my comment better.

Thanks, Donovan.

|||

I think the value in cache is negated by the potentially large recordsets that RS must sift through for grouping/sorting. Use procs for everything, we use temp tables rathen than real table with each temp table being called from a perspective proc and destroyed at connection close. For example, we have reports that return a weeks worth of data(40,000 rows), I organize it by day/product by selecting from the base table into a temp and then returning the 7 rows for the day report to RS.

I also find manging paramters in RS beteer than procs. For example, I ask for one date parameter and the derive all the others from it where I can. For example, a report will show this week, last week and last six months turn around time for a product(s). By managing the parameters in RS, I can just pass the different params to the same sproc although they are set up a different datasets. I've toyed with the idea of adding another input parameter to the procs to push the date manipulation back into the backend.

My general philosphy is to use RS(or any other tool) as a presentation layer and do all calcs except for basic summing, avergaing, etc.. in the DB.

Reporting Services 2000, VS2005 and SQL Server 2000

I am running MS SQL 2000 and VS .Net 2005.

Is it possible to run Microsoft Reporting Services 2000 with VS2005 or am I required to upgrade the SQL server and reporting services to 2005 just to produce a few WEB reports ? This would be too costly both in money and time.

I have just finished developing a solution using the version of Crystal Reports which is built into VS 2005. However I now believe that I require costly licenses to deploy the solution on the live WEB server. Can anyone confirm this assumption (in simple terms).

There really does to be a lack of a descent, reasonable cost, solution for generating WEB reports against an MS SQL 2000 database whilst using the VS 2005 development environment. Maybe I am wrong ?

Any suggestions would be appreciated.

Cheers

George

Please help ...

In simple terms, I have VS2005 and am limited to MSSQL 2000 and want to generate some WEB reports. Can I use Reporting Services 2000 services to do this ?

Upgrading to SQL 2005 is NOT an option and I have a large WEB project built using VS2005 (VB).

This now all seems to be so difficult. Any help would be appreciated.

Cheers

George

Reporting Services 2000 RSClientPrint

For some reason I am not seeing the Printer Icon on my RS tool bar when
running a report off of the report server. I looked in my add-ons for
Internet Explorer and RSPrintClient.DLL is installed and active. However, it
says that it is not verified.
How do I correct this problem? Do I have to uninstall the RSPrintClient.DLL
file manually and let reporting services prompt me to install it when I run a
report?
Thanks!Hi there,
you got to instal the service pack1.
Ricardo Bessa
> For some reason I am not seeing the Printer Icon on my RS tool bar
> when running a report off of the report server. I looked in my
> add-ons for Internet Explorer and RSPrintClient.DLL is installed and
> active. However, it says that it is not verified.
> How do I correct this problem? Do I have to uninstall the
> RSPrintClient.DLL file manually and let reporting services prompt me
> to install it when I run a report?
> Thanks!
>|||I believe SP1 it is installed. I don't think it is a service pack issue.
The strange thing is that there are users on Reporting Services server that
run reports and see the printer Icon. Just my user ID that doesn't for some
reason. It is probably releated to the way the RSPrintClient.DLL is
installed on my machine.
I need to know how to coreect
"Ricardo Bessa" wrote:
> Hi there,
> you got to instal the service pack1.
>
> Ricardo Bessa
> > For some reason I am not seeing the Printer Icon on my RS tool bar
> > when running a report off of the report server. I looked in my
> > add-ons for Internet Explorer and RSPrintClient.DLL is installed and
> > active. However, it says that it is not verified.
> >
> > How do I correct this problem? Do I have to uninstall the
> > RSPrintClient.DLL file manually and let reporting services prompt me
> > to install it when I run a report?
> >
> > Thanks!
> >
>
>

Reporting Services 2000 broke by installing .NET 2.0 redistributable runtime files

We have RS 2000 running in our lab environment where I recently installed the .NET Framework 2.0 Redistributable Package. After installation, reporting services stopped working with the following error:

Security Exception

Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.

Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

I noticed the Version=2.0.0.0 part and went into the IIS properties for the /Reports directory and verified that 1.1 was selected and not 2.0.

Not sure why it appears 2.0 is being referenced when the site should be pointing to 1.1 libraries.

Any ideas would be appreciated.

Make sure you check both virtual folders: /Reports and /ReportServer. When you go to the properties of these virtual folders, go to application configuration and check all script maps. Make sure there's no v2.0 DLLs in the script maps.|||If you are running Windows XP or you have Reporting Services installed in the same application pool as an ASP.NET 2.0 application, then this will happen. You can't run two version of the .NET Framework in the same IIS process.|||I tried both posted solutions and neither worked, although they were good ideas. Both the /Reports and /ReportServer directores have the 1.1 binaries in the Application Mappings tab in IIS. Of interest is the /Reports directory has many application extensions listed and no wildcard maps. The /ReportServer directory has the opposite, no application extensions and one wildcard mapping. Regardless, they all point to 1.1 binaries.

I created a new application pool and put the /Reports and /ReportServer in that pool and am getting the same error.
|||In addition, this event was logged in the Application Events. Still appears to be using the 2.0 libraries yet I don't know why:

Event code: 4010
Event message: An unhandled security exception has occurred.
Event time: 12/1/2005 4:54:28 PM
Event time (UTC): 12/1/2005 9:54:28 PM
Event ID: 37a8c59bd4d14536ac63fdd0b43185d3
Event sequence: 7
Event occurrence: 2
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/Root/Reports-1-127779471911380892
Trust level: RosettaMgr
Application Virtual Path: /Reports
Application Path: C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager\
Machine name: TLCB1
Process information:
Process ID: 1864
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Request information:
Request URL: http://tlcb1/reports/Pages/Folder.aspx
Request path: /reports/Pages/Folder.aspx
User host address: 10.125.124.17
User: xxxx\yyyyy
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE
Custom event details:

For more information, see Help and Support Center at
|||After working with Microsoft support for weeks on this (yes overseas support isn't very expeditious), it turns out it was a problem with a content management ISAPI plugin. The plugin was coded to always run in the context of the latest .net framework version. Since the plugin ran in the default application pool, every app in the default pool then would use the 2.0 framework instead of the 1.1 framework, regardless of what was set for each site.

The solution was to put the content management ISAPI plugin in its own app pool with nothing else. That allow the other apps to use the framework of their specification.
|||

I just updated my Windows 2003 server running Reporting Services 2000 with Net 2.0 and had the same error. I solved it by just selecting the old version 1.1.4 from the ASP.Net settings under the properties tab on IIS. Seems it allows you to select which version to run at each level of a Web/Sub Web. Make sure to select the reportserver and the report sub webs.

Hope this helps.

Tim

|||I had this problem when i've installed MSSQL 2005 and tried to use ReportServer. First I've tried to disable .NET 2.0, but it didn't help. so i uninstalled .net 2.0 and restarted IIS server. it worked. after i've downloaded .net 2.0 from microsoft.com, installed it. Everything works perfect. seems like the .net packege that is distributed with SQL 2005 is broken or something like that.

Reporting Services 2000 broke by installing .NET 2.0 redistributable runtime files

We have RS 2000 running in our lab environment where I recently installed the .NET Framework 2.0 Redistributable Package. After installation, reporting services stopped working with the following error:

Security Exception

Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.

Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

I noticed the Version=2.0.0.0 part and went into the IIS properties for the /Reports directory and verified that 1.1 was selected and not 2.0.

Not sure why it appears 2.0 is being referenced when the site should be pointing to 1.1 libraries.

Any ideas would be appreciated.

Make sure you check both virtual folders: /Reports and /ReportServer. When you go to the properties of these virtual folders, go to application configuration and check all script maps. Make sure there's no v2.0 DLLs in the script maps.|||If you are running Windows XP or you have Reporting Services installed in the same application pool as an ASP.NET 2.0 application, then this will happen. You can't run two version of the .NET Framework in the same IIS process.|||I tried both posted solutions and neither worked, although they were good ideas. Both the /Reports and /ReportServer directores have the 1.1 binaries in the Application Mappings tab in IIS. Of interest is the /Reports directory has many application extensions listed and no wildcard maps. The /ReportServer directory has the opposite, no application extensions and one wildcard mapping. Regardless, they all point to 1.1 binaries.

I created a new application pool and put the /Reports and /ReportServer in that pool and am getting the same error.
|||In addition, this event was logged in the Application Events. Still appears to be using the 2.0 libraries yet I don't know why:

Event code: 4010
Event message: An unhandled security exception has occurred.
Event time: 12/1/2005 4:54:28 PM
Event time (UTC): 12/1/2005 9:54:28 PM
Event ID: 37a8c59bd4d14536ac63fdd0b43185d3
Event sequence: 7
Event occurrence: 2
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/Root/Reports-1-127779471911380892
Trust level: RosettaMgr
Application Virtual Path: /Reports
Application Path: C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager\
Machine name: TLCB1
Process information:
Process ID: 1864
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Request information:
Request URL: http://tlcb1/reports/Pages/Folder.aspx
Request path: /reports/Pages/Folder.aspx
User host address: 10.125.124.17
User: xxxx\yyyyy
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE
Custom event details:

For more information, see Help and Support Center at
|||After working with Microsoft support for weeks on this (yes overseas support isn't very expeditious), it turns out it was a problem with a content management ISAPI plugin. The plugin was coded to always run in the context of the latest .net framework version. Since the plugin ran in the default application pool, every app in the default pool then would use the 2.0 framework instead of the 1.1 framework, regardless of what was set for each site.

The solution was to put the content management ISAPI plugin in its own app pool with nothing else. That allow the other apps to use the framework of their specification.
|||

I just updated my Windows 2003 server running Reporting Services 2000 with Net 2.0 and had the same error. I solved it by just selecting the old version 1.1.4 from the ASP.Net settings under the properties tab on IIS. Seems it allows you to select which version to run at each level of a Web/Sub Web. Make sure to select the reportserver and the report sub webs.

Hope this helps.

Tim

|||I had this problem when i've installed MSSQL 2005 and tried to use ReportServer. First I've tried to disable .NET 2.0, but it didn't help. so i uninstalled .net 2.0 and restarted IIS server. it worked. after i've downloaded .net 2.0 from microsoft.com, installed it. Everything works perfect. seems like the .net packege that is distributed with SQL 2005 is broken or something like that.

Reporting Services 2000 broke by installing .NET 2.0 redistributable runtime files

We have RS 2000 running in our lab environment where I recently installed the .NET Framework 2.0 Redistributable Package. After installation, reporting services stopped working with the following error:

Security Exception

Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.

Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

I noticed the Version=2.0.0.0 part and went into the IIS properties for the /Reports directory and verified that 1.1 was selected and not 2.0.

Not sure why it appears 2.0 is being referenced when the site should be pointing to 1.1 libraries.

Any ideas would be appreciated.

Make sure you check both virtual folders: /Reports and /ReportServer. When you go to the properties of these virtual folders, go to application configuration and check all script maps. Make sure there's no v2.0 DLLs in the script maps.|||If you are running Windows XP or you have Reporting Services installed in the same application pool as an ASP.NET 2.0 application, then this will happen. You can't run two version of the .NET Framework in the same IIS process.|||I tried both posted solutions and neither worked, although they were good ideas. Both the /Reports and /ReportServer directores have the 1.1 binaries in the Application Mappings tab in IIS. Of interest is the /Reports directory has many application extensions listed and no wildcard maps. The /ReportServer directory has the opposite, no application extensions and one wildcard mapping. Regardless, they all point to 1.1 binaries.

I created a new application pool and put the /Reports and /ReportServer in that pool and am getting the same error.
|||In addition, this event was logged in the Application Events. Still appears to be using the 2.0 libraries yet I don't know why:

Event code: 4010
Event message: An unhandled security exception has occurred.
Event time: 12/1/2005 4:54:28 PM
Event time (UTC): 12/1/2005 9:54:28 PM
Event ID: 37a8c59bd4d14536ac63fdd0b43185d3
Event sequence: 7
Event occurrence: 2
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/Root/Reports-1-127779471911380892
Trust level: RosettaMgr
Application Virtual Path: /Reports
Application Path: C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportManager\
Machine name: TLCB1
Process information:
Process ID: 1864
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Request information:
Request URL: http://tlcb1/reports/Pages/Folder.aspx
Request path: /reports/Pages/Folder.aspx
User host address: 10.125.124.17
User: xxxx\yyyyy
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE
Custom event details:

For more information, see Help and Support Center at
|||After working with Microsoft support for weeks on this (yes overseas support isn't very expeditious), it turns out it was a problem with a content management ISAPI plugin. The plugin was coded to always run in the context of the latest .net framework version. Since the plugin ran in the default application pool, every app in the default pool then would use the 2.0 framework instead of the 1.1 framework, regardless of what was set for each site.

The solution was to put the content management ISAPI plugin in its own app pool with nothing else. That allow the other apps to use the framework of their specification.
|||

I just updated my Windows 2003 server running Reporting Services 2000 with Net 2.0 and had the same error. I solved it by just selecting the old version 1.1.4 from the ASP.Net settings under the properties tab on IIS. Seems it allows you to select which version to run at each level of a Web/Sub Web. Make sure to select the reportserver and the report sub webs.

Hope this helps.

Tim

|||I had this problem when i've installed MSSQL 2005 and tried to use ReportServer. First I've tried to disable .NET 2.0, but it didn't help. so i uninstalled .net 2.0 and restarted IIS server. it worked. after i've downloaded .net 2.0 from microsoft.com, installed it. Everything works perfect. seems like the .net packege that is distributed with SQL 2005 is broken or something like that.

reporting services 2000 and 2005 - same database server

We have reporting services 2000 running, with the reportserver and
reportservertemp databases on sql server 2005 on another machine. I
wanted to install reporting services 2005 on a separte machine (3rd
machine), but create the system report server databases (with
different names) on the same sql server as the current database
server, where reporting services 2000 system databases are present.
I installed reporting services, and when I use the configuration tool
to make the database setup, I'm getting the error that the databases
cannot be created, probably because I do not have sufficient
permissions. In spite of this message, the databases are created on
the server. I am the local administrator the sql server machine and
the machine on which I am trying to install reporting services 2005.
Also I am sysadmin on sql server.
When I try to set up the reporting services system databases on a
different sql server it works fine. So my question is whether it is
not possible to install system databases of 2000 and 2005 reporting
services on a single sql server 2005 database server? If yes, can you
please recomment some troubleshooting tips?
Thanks,
JohnIt does not seem to be a problem of two different versions of
reporting services databases on the same sql server. On further
testing, I found that I can set the reporting services system
databases on some remote database servers and not on some; whether the
database server already has a reporting service system database
doesn't seem to be causing the error.
Still looking for ways to troubleshoot.
John|||I figured what was the problem. First I used the reporting services
configuration tool to generate the scripts, and then ran the scripts
on the database server. The problem is that the reporting services
2005 sp2 configuration tool created script is not perfect, if the
system database is named other than ReportServer.
Portion of the generated script is attached below. Note that the
system database I specified was ReportServer2005 and so the other db
would be ReportServer2005TempDB. Now towards the end of the script,
note that it is referring to ReportServerTempdb, instead of
ReportServer2005TempDB, and that was really giving the error. Can't
believe Microsoft could had messed up like that!
IF NOT EXISTS (SELECT name FROM master.dbo.sysdatabases WHERE name =N'ReportServer2005') CREATE DATABASE [ReportServer2005] COLLATE
Latin1_General_CI_AS_KS_WS
GO
IF NOT EXISTS (SELECT name FROM master.dbo.sysdatabases WHERE name =N'ReportServer2005TempDB') CREATE DATABASE [ReportServer2005TempDB]
COLLATE Latin1_General_CI_AS_KS_WS
GO
...
ELSE BEGIN
INSERT INTO [ReportServerTempdb].[dbo].[ChunkData] (
ChunkId, SnapshotDataId, ChunkFlags, ChunkName,
ChunkType, Version, MimeType, Content )
SELECT
NEWID(), @.SnapshotId, @.ChunkFlags, @.ChunkName,
@.ChunkType, @.Version, @.MimeType, ISNULL(Linked.Content,
Original.Content)
FROM [Catalog] Original
LEFT OUTER JOIN [Catalog] Linked WITH (INDEX(PK_Catalog)) ON
(Original.LinkSourceId = Linked.ItemId)
WHERE Original.ItemId = @.ItemId AND
NOT EXISTS (
SELECT *
FROM [ReportServerTempdb].[dbo].[ChunkData]
WHERE SnapshotDataId = @.SnapshotId AND
ChunkName = @.ChunkName AND
ChunkType = @.ChunkType )
END

Reporting Services 2000 - Printing Hangs

I am running SQL 2000 SP4 with Reporting Services 2000 SP2. Reporting services hangs when I try to print reports. The reports render okay, and when I click on the print icon, I get the appropriate dialog box. Once I click "OK", I get the "Printing..." dialog that says "Printing Now...", but it never prints, and the window eventually stops responding. As far as I am aware, no changes have been made to the server, and it was working fine approximately 10 days ago. Below is the contents of my RS Client Print Log (%Temp%\LOG56.tmp):

CRSClientPrint::Print - Starting Function.
reportServerUrl = http://reportsrv/ReportServer
reportPath = %2fEngineering%2fRamz+-+Development%2fDEV_Reports%2fContract_Project_By_State&ContractStateDesc=Active
reportName = Contract_Project_By_State
CResourceManager::SetLocaleInfo - Starting Function.
SetUICulture - Starting Function.
Attempted UI LCID = 9
Using UI LCID = 1033
SetUICulture - Ending Function.
CResourceManager::LoadResourceDLL - Starting Function.
CResourceManager::LoadResourceDLL - Ending Function: 0x00000000.
CResourceManager::CanUseCurrentLocale - Starting Function.
CResourceManager::CanUseCurrentLocale - Ending Function.
CResourceManager::LoadGDIPlus - Starting Function.
CResourceManager::LoadGDIPlus - Ending Function: 0x00000000.
Attempted culture = 1033
Using culture = 1033
Culture name = English_United States.1252
CResourceManager::SetLocaleInfo - Ending Function: 0x00000000.
CPrintDlg::Print - Starting Function.
CPrintDlg::InitializePrintDlg - Starting Function.
CPrintDlg::GetDefaultPrinterName - Starting Function.
CPrintDlg::GetDefaultPrinterName - Ending Function: 0x00000000.
CPrintDlg::SetPrinterPaperSize - Starting Function.
CPrintDlg::SetPrinterPaperSize - Ending Function: 0x00000000.
CPrintDlg::InitializePrintDlg - Ending Function: 0x00000000.
CReport::SetReportName - Starting Function.
CReport::SetReportName - Ending Function: 0x00000000.
CPrintDlg::PrintReportPages - Starting Function.
CCancelDlg::StartDialog - Starting Function.
CCancelDlg::StartDialog - Ending Function: 0x00000000.
CReport::Fetch - Starting Function.
CReport::ComparePrintInfo - Starting Function.
Value of diff = 2
CReport::ComparePrintInfo - Ending Function.
CReport::ClearPages - Starting Function.
CReport::ClearFetchedPages - Starting Function.
CReport::ClearFetchedPages - Ending Function.
CReport::ClearPages - Ending Function.
CReport::ResetNextFetch - Starting Function.
Next Fetch set to 1
CReport::ResetNextFetch - Ending Function.
CReport::StartFetchThread - Starting Function.
CReport::GetPageToFetch - Starting Function.
Page to fetch = 1
CReport::GetPageToFetch - Ending Function.
CReport::StartFetchThread - Ending Function: 0x00000000.
CReport::Fetch - Ending Function: 0x00000000.
CReport::GetPage - Starting Function.
Page = 1
CReport::GetPageWrapper - Starting Function.
Page wrapper = 0x00000000
CReport::GetPageWrapper - Ending Function.
CReport::FetchThreadMain - Starting Function.
CReport::GetPageToFetch - Starting Function.
Page to fetch = 1
CReport::GetPageToFetch - Ending Function.
CReport::FetchAllPages - Starting Function.
CReport::PerformFetch - Starting Function.
CReport::GetPaperSize - Starting Function.
Height = 8500, Width = 11000 IsMM = 0
CReport::GetPaperSize - Ending Function.
CResourceManager::SetInvariantCulture - Starting Function.
CResourceManager::SetInvariantCulture - Ending Function: 0x00000000.
CResourceManager::ResetCulture - Starting Function.
CResourceManager::ResetCulture - Ending Function: 0x00000000.
Url = http://reportsrv/ReportServer?%2fEngineering%2fRamz+-+Development%2fDEV_Reports%2fContract_Project_By_State&ContractStateDesc=Active&rs:Command=Render&rs:format=IMAGE&rc:OutputFormat=emf&rc:StartPage=1&rc:EndPage=65535&rc:PageWidth=11.0in&rc:PageHeight=8.500in&rc:MarginTop=6.350mm&rc:MarginBottom=6.350mm&rc:MarginLeft=6.350mm&rc:MarginRight=6.350mm&rs:PersistStreams=True

Can anyone give me any ideas as to how to troubleshoot this issue?

Hi Patrick,

If that is all that is in the log, it looks like the service might be having an issue with rendering the Url. Paste the Url from the print log file into Internet Explorer and see if it renderers an emf image.

Also, you can check the Report Server log files for any exceptions from the rendering. You can find the log directory, Logfiles next to the Report Server installation binaries directory.

Did you change any settings on your server to use Cookieless Sessions? I notice that the SessionID is not stored in the URL.

|||

I have not changed any cookie settings. When I paste the URL into the browser, I get a prompt for credentials, and then an HTTP 401 (Unauthorized) error. I am an Administrator, so my credentials should be valid. The ReportServer log showed the following:

w3wp!webserver!1df0!01/08/2007-12:34:55:: i INFO: Processed folder '/'
w3wp!webserver!1df0!01/08/2007-12:34:56:: i INFO: Processed folder '/Engineering'
w3wp!webserver!1df0!01/08/2007-12:34:58:: i INFO: Processed folder '/Engineering/Ramz - Development'
w3wp!webserver!1df0!01/08/2007-12:34:59:: i INFO: Processed folder '/Engineering/Ramz - Development/DEV_Reports'
w3wp!library!83c!01/08/2007-12:35:01:: i INFO: Initializing ResponseBufferSizeKb to default value of '64' KB because it was not specified in Server system properties.
w3wp!library!83c!01/08/2007-12:35:01:: i INFO: Initializing UseSessionCookies to 'True' as specified in Server system properties.
w3wp!library!83c!01/08/2007-12:35:01:: i INFO: Initializing EnableIntegratedSecurity to 'True' as specified in Server system properties.
w3wp!library!1e4c!01/08/2007-12:35:06:: i INFO: Initializing SessionTimeout to '600' second(s) as specified in Server system properties.
w3wp!library!1e4c!01/08/2007-12:35:06:: i INFO: Initializing EnableClientPrinting to default value of 'True' because it was not specified in Server system properties.
w3wp!library!1e4c!01/08/2007-12:35:06:: i INFO: Call to RenderFirst( '/Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State' )
w3wp!library!1e4c!01/08/2007-12:35:07:: Using folder C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\RSTempFiles for temporary files.
w3wp!library!1e4c!01/08/2007-12:35:08:: i INFO: Initializing EnableExecutionLogging to 'False' as specified in Server system properties.
w3wp!library!1e2c!1/8/2007-12:35:08:: i INFO: Initializing SqlStreamingBufferSize to default value of '64640' Bytes because it was not specified in Server system properties.
w3wp!webserver!1e4c!01/08/2007-12:35:08:: i INFO: Processed report. Report='/Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State', Stream=''
w3wp!library!1e2c!1/8/2007-12:35:08:: i INFO: Initializing SnapshotCompression to 'SQL' as specified in Server system properties.
w3wp!library!1e4c!01/08/2007-12:35:08:: i INFO: Initializing SessionAccessTimeout to default value of '600' seconds because it was not specified in Server system properties.
w3wp!webserver!1e4c!01/08/2007-12:35:08:: i INFO: Processed report. Report='/Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State', Stream='d60bcf42-3d04-4642-8772-8296be509a7b'
w3wp!library!1e2c!01/08/2007-12:35:39:: i INFO: Call to RenderNext( '/Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State' )
w3wp!cache!1e2c!01/08/2007-12:35:39:: i INFO: Item not cacheable: - PersistStreams /Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State
w3wp!chunks!1e2c!01/08/2007-12:35:39:: i INFO: ### GetReportChunk('RenderingInfo_IMAGE', 2), chunk was not found! this=25ac3238-2ba1-4406-befb-f46907e5d068
w3wp!webserver!1df0!01/08/2007-12:35:41:: i INFO: Processed report. Report='/Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State', Stream=''
w3wp!cache!1e2c!01/08/2007-12:36:17:: i INFO: Session live: /Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State
w3wp!library!83c!01/08/2007-12:36:17:: i INFO: Call to RenderNext( '/Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State' )
w3wp!cache!83c!01/08/2007-12:36:17:: i INFO: Item not cacheable: - PersistStreams /Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State
w3wp!chunks!83c!01/08/2007-12:36:17:: i INFO: ### GetReportChunk('RenderingInfo_IMAGE', 2), chunk was not found! this=25ac3238-2ba1-4406-befb-f46907e5d068
w3wp!webserver!1df0!01/08/2007-12:36:18:: i INFO: Processed report. Report='/Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State', Stream=''
w3wp!cache!83c!01/08/2007-12:36:55:: i INFO: Session live: /Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State
w3wp!library!1e4c!01/08/2007-12:37:57:: i INFO: Call to RenderFirst( '/Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State' )
w3wp!webserver!1df0!01/08/2007-12:37:58:: i INFO: Processed report. Report='/Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State', Stream=''
w3wp!cache!1e4c!01/08/2007-12:38:33:: i INFO: Item not cacheable: - PersistStreams /Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State
w3wp!cache!1e4c!01/08/2007-12:38:33:: i INFO: Item not cacheable: - PersistStreams /Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State
w3wp!cache!1e4c!01/08/2007-12:38:33:: i INFO: Item not cacheable: - PersistStreams /Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State
w3wp!cache!1e4c!01/08/2007-12:38:33:: i INFO: Item not cacheable: - PersistStreams /Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State
w3wp!cache!1e4c!01/08/2007-12:38:33:: i INFO: Item not cacheable: - PersistStreams /Engineering/Ramz - Development/DEV_Reports/Contract_Project_By_State

|||

I get the following in the IIS log when I try to render the report:

2007-01-09 15:42:12 XXX.XXX.XXX.XXX GET /ReportServer %2fEngineering%2fRamz+-+Development%2fDEV_Reports%2fContract_Project_By_State&ContractStateDesc=Active&rs:Command=Render&rs:format=IMAGE&rc:OutputFormat=emf&rc:StartPage=1&rc:EndPage=65535&rc:PageWidth=11.0in&rc:PageHeight=8.500in&rc:MarginTop=6.350mm&rc:MarginBottom=6.350mm&rc:MarginLeft=6.350mm&rc:MarginRight=6.350mm&rs:PersistStreams=True 80 DOMAIN\pburcham XXX.XXX.XXX.XXX Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 200
2007-01-09 15:42:49 XXX.XXX.XXX.XXX GET /ReportServer %2fEngineering%2fRamz+-+Development%2fDEV_Reports%2fContract_Project_By_State&ContractStateDesc=Active&rs:Command=Render&rs:format=IMAGE&rc:OutputFormat=emf&rc:StartPage=1&rc:EndPage=65535&rc:PageWidth=11.0in&rc:PageHeight=8.500in&rc:MarginTop=6.350mm&rc:MarginBottom=6.350mm&rc:MarginLeft=6.350mm&rc:MarginRight=6.350mm&rs:PersistStreams=True 80 - XXX.XXX.XXX.XXX Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 401
2007-01-09 15:42:49 XXX.XXX.XXX.XXX GET /ReportServer %2fEngineering%2fRamz+-+Development%2fDEV_Reports%2fContract_Project_By_State&ContractStateDesc=Active&rs:Command=Render&rs:format=IMAGE&rc:OutputFormat=emf&rc:StartPage=1&rc:EndPage=65535&rc:PageWidth=11.0in&rc:PageHeight=8.500in&rc:MarginTop=6.350mm&rc:MarginBottom=6.350mm&rc:MarginLeft=6.350mm&rc:MarginRight=6.350mm&rs:PersistStreams=True 80 DOMAIN\pburcham XXX.XXX.XXX.XXX Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 200
2007-01-09 15:42:49 XXX.XXX.XXX.XXX GET /ReportServer %2fEngineering%2fRamz+-+Development%2fDEV_Reports%2fContract_Project_By_State&ContractStateDesc=Active&rs:Command=Render&rs:format=IMAGE&rc:OutputFormat=emf&rc:StartPage=1&rc:EndPage=65535&rc:PageWidth=11.0in&rc:PageHeight=8.500in&rc:MarginTop=6.350mm&rc:MarginBottom=6.350mm&rc:MarginLeft=6.350mm&rc:MarginRight=6.350mm&rs:PersistStreams=True 80 - XXX.XXX.XXX.XXX Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 401
2007-01-09 15:43:25 XXX.XXX.XXX.XXX GET /ReportServer %2fEngineering%2fRamz+-+Development%2fDEV_Reports%2fContract_Project_By_State&ContractStateDesc=Active&rs:Command=Render&rs:format=IMAGE&rc:OutputFormat=emf&rc:StartPage=1&rc:EndPage=65535&rc:PageWidth=11.0in&rc:PageHeight=8.500in&rc:MarginTop=6.350mm&rc:MarginBottom=6.350mm&rc:MarginLeft=6.350mm&rc:MarginRight=6.350mm&rs:PersistStreams=True 80 DOMAIN\pburcham XXX.XXX.XXX.XXX Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 200
2007-01-09 15:43:25 XXX.XXX.XXX.XXX GET /ReportServer %2fEngineering%2fRamz+-+Development%2fDEV_Reports%2fContract_Project_By_State&ContractStateDesc=Active&rs:Command=Render&rs:format=IMAGE&rc:OutputFormat=emf&rc:StartPage=1&rc:EndPage=65535&rc:PageWidth=11.0in&rc:PageHeight=8.500in&rc:MarginTop=6.350mm&rc:MarginBottom=6.350mm&rc:MarginLeft=6.350mm&rc:MarginRight=6.350mm&rs:PersistStreams=True 80 - XXX.XXX.XXX.XXX Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 401
2007-01-09 15:44:00 XXX.XXX.XXX.XXX GET /ReportServer %2fEngineering%2fRamz+-+Development%2fDEV_Reports%2fContract_Project_By_State&ContractStateDesc=Active&rs:Command=Render&rs:format=IMAGE&rc:OutputFormat=emf&rc:StartPage=1&rc:EndPage=65535&rc:PageWidth=11.0in&rc:PageHeight=8.500in&rc:MarginTop=6.350mm&rc:MarginBottom=6.350mm&rc:MarginLeft=6.350mm&rc:MarginRight=6.350mm&rs:PersistStreams=True 80 DOMAIN\pburcham XXX.XXX.XXX.XXX Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 200
2007-01-09 15:44:00 XXX.XXX.XXX.XXX GET /ReportServer %2fEngineering%2fRamz+-+Development%2fDEV_Reports%2fContract_Project_By_State&ContractStateDesc=Active&rs:Command=Render&rs:format=IMAGE&rc:OutputFormat=emf&rc:StartPage=1&rc:EndPage=65535&rc:PageWidth=11.0in&rc:PageHeight=8.500in&rc:MarginTop=6.350mm&rc:MarginBottom=6.350mm&rc:MarginLeft=6.350mm&rc:MarginRight=6.350mm&rs:PersistStreams=True 80 - XXX.XXX.XXX.XXX Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 401
2007-01-09 15:47:09 XXX.XXX.XXX.XXX GET /ReportServer %2fEngineering%2fRamz+-+Development%2fDEV_Reports%2fContract_Project_By_State&ContractStateDesc=Active&rs:Command=Render&rs:format=IMAGE&rc:OutputFormat=emf&rc:StartPage=1&rc:EndPage=65535&rc:PageWidth=11.0in&rc:PageHeight=8.500in&rc:MarginTop=6.350mm&rc:MarginBottom=6.350mm&rc:MarginLeft=6.350mm&rc:MarginRight=6.350mm&rs:PersistStreams=True 80 - XXX.XXX.XXX.XXX Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 401
2007-01-09 15:47:14 XXX.XXX.XXX.XXX GET /ReportServer %2fEngineering%2fRamz+-+Development%2fDEV_Reports%2fContract_Project_By_State&ContractStateDesc=Active&rs:Command=Render&rs:format=IMAGE&rc:OutputFormat=emf&rc:StartPage=1&rc:EndPage=65535&rc:PageWidth=11.0in&rc:PageHeight=8.500in&rc:MarginTop=6.350mm&rc:MarginBottom=6.350mm&rc:MarginLeft=6.350mm&rc:MarginRight=6.350mm&rs:PersistStreams=True 80 DOMAIN\pburcham XXX.XXX.XXX.XXX Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 200
2007-01-09 15:47:14 XXX.XXX.XXX.XXX GET /ReportServer %2fEngineering%2fRamz+-+Development%2fDEV_Reports%2fContract_Project_By_State&ContractStateDesc=Active&rs:Command=Render&rs:format=IMAGE&rc:OutputFormat=emf&rc:StartPage=1&rc:EndPage=65535&rc:PageWidth=11.0in&rc:PageHeight=8.500in&rc:MarginTop=6.350mm&rc:MarginBottom=6.350mm&rc:MarginLeft=6.350mm&rc:MarginRight=6.350mm&rs:PersistStreams=True 80 - XXX.XXX.XXX.XXX Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322) 401

It appears that SSRS is not passing my credentials all of the time, only sometimes. It also appears that multiple requests are made for the same report. Any ideas as to why this might be?