Showing posts with label reportserver. Show all posts
Showing posts with label reportserver. Show all posts

Wednesday, March 21, 2012

RS2005 Date parameter - JScript error

I have a RS2005 report that was deployed to a ReportServer and has been running for over 1 month. I personally have not run this report in the past month, however, today when I tried to run it I got an error trying to select a date parameter. I can't paste samples of the windows displayed, so I'll do my best to explain. When I click on the report, it goes to the View window and displays 2 date parameter fields. When I click the icon next to one of the parameter fields, I get an error window that says

A Runtime Error has occurred.

Do you wish to Debug?

Line: 383

Error: 'resultfield.id' is null or not an object

I click Yes and get a VS Just-in-Time Debugger window, where I choose New instance of VS 2005. When VS2005 opens, then I get this error:

Microsoft JScript runtime error: 'resultfield.id' is null or not an object

The Continue option just keeps displaying this error, when I click Break it shows me the code below and has highlighted the line I show in BOLD:

function ClickDay(date)

{

var win = document.parentWindow;

if (!win) win = document.contentWindow;

if (!win) win = document.defaultView;

if (!win) return true;

var ifrm=win.frameElement;

if (ifrm==null)

{

return MoveToDate(date, false);

}

var eltValidator=win.parent.document.getElementById(ifrm.resultfield.id+g_strDatePickerRangeValidatorID);

if (eltValidator !=null)

{

eltValidator.style.display="none";

}

var OnSelectDateCallback=ifrm.OnSelectDateCallback;

OnSelectDateCallback(ifrm.resultfield, date);

var resultfunc=ifrm.resultfunc;

resultfunc(ifrm.resultfield);

return true;

}

To make this more confusing, after I get this error a few times, eventually it lets me choose a date and run the report. Another quirk of my PC is that I often get runtime errors that ask me if I want to Debug when I'm in IExplorer.

Any idea what is going on and how to fix it?

Thanks in advance!Hi! I have the same problem!!
Do you have fix it?
Thanks in advance!|||Unfortunately, no. Not long after I posted this, I got pulled to another project. I will probably start working on this project again some time next week, so if I figure out how to fix this I will post it. Good luck!|||thanks!
If I find the solution I'll post it!|||

I also have this error when two date controls are in use, it seems to be a timing issue. When I click the calendar icon for one date, and it is posting back, if I manage to click the 2nd calendar icon during the postback I get the error.

Not sure if there is any possible solution for this ?

|||

I was experiencing the same problem with the calendar controls until I figured out that it was my McAfee "on access" scanner causing the problems. Once I disabled the scanner, everything worked fine. Enable it, and the problem returns. You can also wait about 5 seconds after the page loads and the controls should work. It makes since, because these "on access" scans always increase page loading times. For once, it's not a Microsoft problem. I know...shocking, isn't it?

Hope this helps with your prob.

Later....

|||Definitely sounds like a possible solution, we do have McAfee and the 'wait about 5 seconds' explains why I was able to get it to work later. I haven't deployed this to too many users yet, so maybe I'll feel more comfortable deploying it now if it looks like this is the problem. Thanks for the response!

RS2005 Date parameter - JScript error

I have a RS2005 report that was deployed to a ReportServer and has been running for over 1 month. I personally have not run this report in the past month, however, today when I tried to run it I got an error trying to select a date parameter. I can't paste samples of the windows displayed, so I'll do my best to explain. When I click on the report, it goes to the View window and displays 2 date parameter fields. When I click the icon next to one of the parameter fields, I get an error window that says

A Runtime Error has occurred.

Do you wish to Debug?

Line: 383

Error: 'resultfield.id' is null or not an object

I click Yes and get a VS Just-in-Time Debugger window, where I choose New instance of VS 2005. When VS2005 opens, then I get this error:

Microsoft JScript runtime error: 'resultfield.id' is null or not an object

The Continue option just keeps displaying this error, when I click Break it shows me the code below and has highlighted the line I show in BOLD:

function ClickDay(date)

{

var win = document.parentWindow;

if (!win) win = document.contentWindow;

if (!win) win = document.defaultView;

if (!win) return true;

var ifrm=win.frameElement;

if (ifrm==null)

{

return MoveToDate(date, false);

}

var eltValidator=win.parent.document.getElementById(ifrm.resultfield.id+g_strDatePickerRangeValidatorID);

if (eltValidator !=null)

{

eltValidator.style.display="none";

}

var OnSelectDateCallback=ifrm.OnSelectDateCallback;

OnSelectDateCallback(ifrm.resultfield, date);

var resultfunc=ifrm.resultfunc;

resultfunc(ifrm.resultfield);

return true;

}

To make this more confusing, after I get this error a few times, eventually it lets me choose a date and run the report. Another quirk of my PC is that I often get runtime errors that ask me if I want to Debug when I'm in IExplorer.

Any idea what is going on and how to fix it?

Thanks in advance!Hi! I have the same problem!!
Do you have fix it?
Thanks in advance!
|||Unfortunately, no. Not long after I posted this, I got pulled to another project. I will probably start working on this project again some time next week, so if I figure out how to fix this I will post it. Good luck!|||thanks!
If I find the solution I'll post it!
|||

I also have this error when two date controls are in use, it seems to be a timing issue. When I click the calendar icon for one date, and it is posting back, if I manage to click the 2nd calendar icon during the postback I get the error.

Not sure if there is any possible solution for this ?

|||

I was experiencing the same problem with the calendar controls until I figured out that it was my McAfee "on access" scanner causing the problems. Once I disabled the scanner, everything worked fine. Enable it, and the problem returns. You can also wait about 5 seconds after the page loads and the controls should work. It makes since, because these "on access" scans always increase page loading times. For once, it's not a Microsoft problem. I know...shocking, isn't it?

Hope this helps with your prob.

Later....

|||Definitely sounds like a possible solution, we do have McAfee and the 'wait about 5 seconds' explains why I was able to get it to work later. I haven't deployed this to too many users yet, so maybe I'll feel more comfortable deploying it now if it looks like this is the problem. Thanks for the response!sql

RS2005 Date parameter - JScript error

I have a RS2005 report that was deployed to a ReportServer and has been running for over 1 month. I personally have not run this report in the past month, however, today when I tried to run it I got an error trying to select a date parameter. I can't paste samples of the windows displayed, so I'll do my best to explain. When I click on the report, it goes to the View window and displays 2 date parameter fields. When I click the icon next to one of the parameter fields, I get an error window that says

A Runtime Error has occurred.

Do you wish to Debug?

Line: 383

Error: 'resultfield.id' is null or not an object

I click Yes and get a VS Just-in-Time Debugger window, where I choose New instance of VS 2005. When VS2005 opens, then I get this error:

Microsoft JScript runtime error: 'resultfield.id' is null or not an object

The Continue option just keeps displaying this error, when I click Break it shows me the code below and has highlighted the line I show in BOLD:

function ClickDay(date)

{

var win = document.parentWindow;

if (!win) win = document.contentWindow;

if (!win) win = document.defaultView;

if (!win) return true;

var ifrm=win.frameElement;

if (ifrm==null)

{

return MoveToDate(date, false);

}

var eltValidator=win.parent.document.getElementById(ifrm.resultfield.id+g_strDatePickerRangeValidatorID);

if (eltValidator !=null)

{

eltValidator.style.display="none";

}

var OnSelectDateCallback=ifrm.OnSelectDateCallback;

OnSelectDateCallback(ifrm.resultfield, date);

var resultfunc=ifrm.resultfunc;

resultfunc(ifrm.resultfield);

return true;

}

To make this more confusing, after I get this error a few times, eventually it lets me choose a date and run the report. Another quirk of my PC is that I often get runtime errors that ask me if I want to Debug when I'm in IExplorer.

Any idea what is going on and how to fix it?

Thanks in advance!Hi! I have the same problem!!
Do you have fix it?
Thanks in advance!
|||Unfortunately, no. Not long after I posted this, I got pulled to another project. I will probably start working on this project again some time next week, so if I figure out how to fix this I will post it. Good luck!|||thanks!
If I find the solution I'll post it!
|||

I also have this error when two date controls are in use, it seems to be a timing issue. When I click the calendar icon for one date, and it is posting back, if I manage to click the 2nd calendar icon during the postback I get the error.

Not sure if there is any possible solution for this ?

|||

I was experiencing the same problem with the calendar controls until I figured out that it was my McAfee "on access" scanner causing the problems. Once I disabled the scanner, everything worked fine. Enable it, and the problem returns. You can also wait about 5 seconds after the page loads and the controls should work. It makes since, because these "on access" scans always increase page loading times. For once, it's not a Microsoft problem. I know...shocking, isn't it?

Hope this helps with your prob.

Later....

|||Definitely sounds like a possible solution, we do have McAfee and the 'wait about 5 seconds' explains why I was able to get it to work later. I haven't deployed this to too many users yet, so maybe I'll feel more comfortable deploying it now if it looks like this is the problem. Thanks for the response!

RS2005 Date parameter - JScript error

I have a RS2005 report that was deployed to a ReportServer and has been running for over 1 month. I personally have not run this report in the past month, however, today when I tried to run it I got an error trying to select a date parameter. I can't paste samples of the windows displayed, so I'll do my best to explain. When I click on the report, it goes to the View window and displays 2 date parameter fields. When I click the icon next to one of the parameter fields, I get an error window that says

A Runtime Error has occurred.

Do you wish to Debug?

Line: 383

Error: 'resultfield.id' is null or not an object

I click Yes and get a VS Just-in-Time Debugger window, where I choose New instance of VS 2005. When VS2005 opens, then I get this error:

Microsoft JScript runtime error: 'resultfield.id' is null or not an object

The Continue option just keeps displaying this error, when I click Break it shows me the code below and has highlighted the line I show in BOLD:

function ClickDay(date)

{

var win = document.parentWindow;

if (!win) win = document.contentWindow;

if (!win) win = document.defaultView;

if (!win) return true;

var ifrm=win.frameElement;

if (ifrm==null)

{

return MoveToDate(date, false);

}

var eltValidator=win.parent.document.getElementById(ifrm.resultfield.id+g_strDatePickerRangeValidatorID);

if (eltValidator !=null)

{

eltValidator.style.display="none";

}

var OnSelectDateCallback=ifrm.OnSelectDateCallback;

OnSelectDateCallback(ifrm.resultfield, date);

var resultfunc=ifrm.resultfunc;

resultfunc(ifrm.resultfield);

return true;

}

To make this more confusing, after I get this error a few times, eventually it lets me choose a date and run the report. Another quirk of my PC is that I often get runtime errors that ask me if I want to Debug when I'm in IExplorer.

Any idea what is going on and how to fix it?

Thanks in advance!Hi! I have the same problem!!
Do you have fix it?
Thanks in advance!|||Unfortunately, no. Not long after I posted this, I got pulled to another project. I will probably start working on this project again some time next week, so if I figure out how to fix this I will post it. Good luck!|||thanks!
If I find the solution I'll post it!|||

I also have this error when two date controls are in use, it seems to be a timing issue. When I click the calendar icon for one date, and it is posting back, if I manage to click the 2nd calendar icon during the postback I get the error.

Not sure if there is any possible solution for this ?

|||

I was experiencing the same problem with the calendar controls until I figured out that it was my McAfee "on access" scanner causing the problems. Once I disabled the scanner, everything worked fine. Enable it, and the problem returns. You can also wait about 5 seconds after the page loads and the controls should work. It makes since, because these "on access" scans always increase page loading times. For once, it's not a Microsoft problem. I know...shocking, isn't it?

Hope this helps with your prob.

Later....

|||Definitely sounds like a possible solution, we do have McAfee and the 'wait about 5 seconds' explains why I was able to get it to work later. I haven't deployed this to too many users yet, so maybe I'll feel more comfortable deploying it now if it looks like this is the problem. Thanks for the response!

RS2005 - Response Time

When running a report in VS, the report run fast but when running the same
report via the browser (<servername>\reportserver), the report runs slow.
How can I increase the response time in running the report via the browser?
Thank you.One thing to remember, in VS it caches the data (look in your directory and
you will see a .data file). So sometimes this can give you an erroneous idea
of the time required.
Also, if it is the first time that RS has run in awhile you will get a big
delay. So run any report to make sure RS is up and active and then run your
report you are concerned about.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Terry" <Terry@.discussions.microsoft.com> wrote in message
news:BB36DBF2-4F3C-4BF7-8850-6CCC9639FE7C@.microsoft.com...
> When running a report in VS, the report run fast but when running the same
> report via the browser (<servername>\reportserver), the report runs slow.
> How can I increase the response time in running the report via the
> browser?
> Thank you.|||Do you know what 'awhile' is? Is it possible to run a schedule report
just to keep RS 'alive'?
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
news:uRucKBj3FHA.3708@.TK2MSFTNGP10.phx.gbl:
> One thing to remember, in VS it caches the data (look in your
> directory and you will see a .data file). So sometimes this can give
> you an erroneous idea of the time required.
> Also, if it is the first time that RS has run in awhile you will get a
> big delay. So run any report to make sure RS is up and active and then
> run your report you are concerned about.
>|||I have a simple report I keep open on my desktop that autoexecutes every 5
minutes. You could also try Chris' suggestion posted below:
>>>>>>>>>>
If you are running Windows 2003 server for your IIS reportserver, then this
is a simple issue - I'll explain what happens:
The report service engine, once it is idle for more than the default 20
minutes, the worker process is shutdown.
This is controlled by IIS.
Open up the Internet Information Services (IIS) Manager
Expand the server node then the application pools.
On my IIS machine, I created an application pool dedicated to the
reportserver & reportmanager virtual webs.
But anyways, for the application pool that the reportserver is pointing to
if you left everything to their defaults will be the DefaultAppPool.
Right click the default app pool and select properties.
There are two things that are checked by default - On the recycling tab
there is a checkbox for recycling worker processes - it is currently set to
1740 minutes (29 hours). Leave it.
The other one is on the performance tab - which is the one you are
interested in changing...
See the "Idle Timeout" section and increase the number of minutes to be 8
hours a typical working day - 8*60 = 480 minutes.
Next, to be sure the "morning person" that runs the first report doesn't get
the delay, set up a schedule for either a dummy or adhoc report to fire off
like at 6am so that the report component worker processes get loaded.
I hope this helps you.
There is no need to have a report fire off every minute to keep things
alive - it is just that the report service was "unloaded" and needed to load
back up.
=-Chris
>>>>>>>>>>
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Asher_N" <compguy666@.hotmail.com> wrote in message
news:Xns97009891877C1compguy666hotmailcom@.207.46.248.16...
> Do you know what 'awhile' is? Is it possible to run a schedule report
> just to keep RS 'alive'?
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
> news:uRucKBj3FHA.3708@.TK2MSFTNGP10.phx.gbl:
>> One thing to remember, in VS it caches the data (look in your
>> directory and you will see a .data file). So sometimes this can give
>> you an erroneous idea of the time required.
>> Also, if it is the first time that RS has run in awhile you will get a
>> big delay. So run any report to make sure RS is up and active and then
>> run your report you are concerned about.
>>
>|||"Bruce L-C [MVP]" <brucelc@.newsgroup.nospam> wrote in
news:#wuXBil3FHA.3292@.tk2msftngp13.phx.gbl:
> I have a simple report I keep open on my desktop that autoexecutes
> every 5 minutes. You could also try Chris' suggestion posted below:
>>>>>>>>>>
> If you are running Windows 2003 server for your IIS reportserver, then
> this
> is a simple issue - I'll explain what happens:
> The report service engine, once it is idle for more than the default
> 20
> minutes, the worker process is shutdown.
> This is controlled by IIS.
> Open up the Internet Information Services (IIS) Manager
> Expand the server node then the application pools.
> On my IIS machine, I created an application pool dedicated to the
> reportserver & reportmanager virtual webs.
> But anyways, for the application pool that the reportserver is
> pointing to
> if you left everything to their defaults will be the DefaultAppPool.
> Right click the default app pool and select properties.
> There are two things that are checked by default - On the recycling
> tab
> there is a checkbox for recycling worker processes - it is currently
> set to
> 1740 minutes (29 hours). Leave it.
> The other one is on the performance tab - which is the one you are
> interested in changing...
> See the "Idle Timeout" section and increase the number of minutes to
> be 8
> hours a typical working day - 8*60 = 480 minutes.
> Next, to be sure the "morning person" that runs the first report
> doesn't get
> the delay, set up a schedule for either a dummy or adhoc report to
> fire off
> like at 6am so that the report component worker processes get loaded.
> I hope this helps you.
> There is no need to have a report fire off every minute to keep things
> alive - it is just that the report service was "unloaded" and needed
> to load
> back up.
> =-Chris
>>>>>>>>>>
>
Thanks

RS2005 - Backend database SQL 2000

Hi,

Is it possible to have RS2005 with the backend as SQL Server 2000 (may be on a remote machine)?

I.e. the Reportserver and ReportServerTempDb will reside on SQL Server 2000.

With which edition of SQL Server 2005 is it possible?

TIA,
Tanmaya

Dear,

U can link a datasource from sqlserver2000.But u cannot have a reportserver and reportservertempdatabase on sqlserver2000.

No edition of sqlserver2005 support this.

HTH

sufian

|||

Yes, this is possible and supported. For example, you can install RS 2005 Enterprise Edition with the metadata being stored on a SQL Server 2000 Enterprise Edition.

-- Robert

|||Thanks,

RS2005 enterprise edition works with backend as SQL 2000.

In Reporting Services configuration manager -> database set, I connected to the machine having SQL 2000 and successfully created the Reportserver and ReportServerTempDb.

However, am getting an error at 'Create Grants Right Script'. I am giving the credentials of system adminstrator (i.e. sa)

Am I going wrong in giving the credentials? Which User's credentials am I suppose to enter there?

Has anyone tried this scenario?

Thanks
Tanmaya|||Please be careful in doing this as it does change some things on that backend. I messed up our backup software by doing this. In short the backup software does not support 2005 server yet and the things that report service installs, installed something that our back software was using....sql

RS2000: Subscriptions "Logon Failed"

Hi,
We get an "Logon Failed" message when running subscriptions;
ReportServer service runs using an domain account. Domain account has
run-as-a-service, logon-locally and "impersonate a client after
authentication" and the apprioriate database rights.
What is the "required privilege" (see below) the reportserver is requiring?
Regards,
Erik Tamminga
ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
Logon failed., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
Logon failed. --> System.Runtime.InteropServices.COMException (0x80070522):
A required privilege is not held by the client.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
errorCode, IntPtr errorInfo)
at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
String pDomain, String pPassword, Boolean bTryRemote, IntPtr& pImpToken)
at
Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
userName, String userPwd, String domain)From here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0lmh.asp
Hope it helps
1.. Decide which accounts to use for Report Server services. Reporting
Services requires three accounts:
2.. Report Server Windows service requires an account to log on to the
local system. Microsoft recommends that you use Local System if you are
installing on Windows 2000. For more information about this recommendation,
see Service Account.
3.. Report Server Web service requires an account to log on to the local
system. Because it is an ASP.NET application, it runs using the ASPNET
account. If you are running Windows 2000, you cannot specify a different
account to use during Setup; you must use the account that is defined for
ASP.NET. If you are running Windows Server 2003, the default is Network
Service, but you can choose to run the service as Local System.
4.. Report Server Web service requires an account to log on to the SQL
Server instance that hosts the report server database. You can specify a
domain account, a SQL Server login, or Local System. You can also use the
credentials that the Report Server Web service uses to log on to the system.
For more information, see Report Server Database Setup.
"Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in message
news:OcR0JGqQGHA.3896@.TK2MSFTNGP15.phx.gbl...
> Hi,
> We get an "Logon Failed" message when running subscriptions;
> ReportServer service runs using an domain account. Domain account has
> run-as-a-service, logon-locally and "impersonate a client after
> authentication" and the apprioriate database rights.
> What is the "required privilege" (see below) the reportserver is
> requiring?
> Regards,
> Erik Tamminga
> ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR:
> Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> Logon failed., ;
> Info:
> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> Logon failed. --> System.Runtime.InteropServices.COMException
> (0x80070522): A required privilege is not held by the client.
> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> errorCode, IntPtr errorInfo)
> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
> String pDomain, String pPassword, Boolean bTryRemote, IntPtr& pImpToken)
> at
> Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
> userName, String userPwd, String domain)
>|||Thanks Beth,
But; RS is able to start, login to the databases. RS WebApplication works as
expected but only the Subscriptions give me a logon failed when they're
scheduled to run. It seems to have something to do with RS not being able to
render the reports using the account used for subscriptions. Any idears on
how to fix this?
Erik
"Beth" <scratchbakery@.msn.com> wrote in message
news:%23ClUKBtQGHA.3916@.TK2MSFTNGP11.phx.gbl...
> From here:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0lmh.asp
> Hope it helps
> 1.. Decide which accounts to use for Report Server services. Reporting
> Services requires three accounts:
> 2.. Report Server Windows service requires an account to log on to the
> local system. Microsoft recommends that you use Local System if you are
> installing on Windows 2000. For more information about this
> recommendation, see Service Account.
> 3.. Report Server Web service requires an account to log on to the local
> system. Because it is an ASP.NET application, it runs using the ASPNET
> account. If you are running Windows 2000, you cannot specify a different
> account to use during Setup; you must use the account that is defined for
> ASP.NET. If you are running Windows Server 2003, the default is Network
> Service, but you can choose to run the service as Local System.
> 4.. Report Server Web service requires an account to log on to the SQL
> Server instance that hosts the report server database. You can specify a
> domain account, a SQL Server login, or Local System. You can also use the
> credentials that the Report Server Web service uses to log on to the
> system. For more information, see Report Server Database Setup.
> "Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in
> message news:OcR0JGqQGHA.3896@.TK2MSFTNGP15.phx.gbl...
>> Hi,
>> We get an "Logon Failed" message when running subscriptions;
>> ReportServer service runs using an domain account. Domain account has
>> run-as-a-service, logon-locally and "impersonate a client after
>> authentication" and the apprioriate database rights.
>> What is the "required privilege" (see below) the reportserver is
>> requiring?
>> Regards,
>> Erik Tamminga
>> ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR:
>> Throwing
>> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
>> Logon failed., ;
>> Info:
>> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
>> Logon failed. --> System.Runtime.InteropServices.COMException
>> (0x80070522): A required privilege is not held by the client.
>> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
>> errorCode, IntPtr errorInfo)
>> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
>> String pDomain, String pPassword, Boolean bTryRemote, IntPtr& pImpToken)
>> at
>> Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
>> userName, String userPwd, String domain)
>|||Hi Erik,
i think for the subscription to work you need to have Credentials stored
securely in the report server. Subscription will not work for reports which
dont have this stored credentials. When you run the report it will work, but
subscription will not work. The reason is DataSources for that report does
not have stored credentials i.e it has either have windows credential or no
credential. in order that reports have subscrpiton enabled you have to check
the "Credentials stored securely in the report server" and enter the user
name and pwd. you can either enter a sql login or windows login based on the
authentication type. and finally click Apply button to store it. Then do the
subscrpion it will work.
Bava
"Erik Tamminga" wrote:
> Thanks Beth,
> But; RS is able to start, login to the databases. RS WebApplication works as
> expected but only the Subscriptions give me a logon failed when they're
> scheduled to run. It seems to have something to do with RS not being able to
> render the reports using the account used for subscriptions. Any idears on
> how to fix this?
> Erik
> "Beth" <scratchbakery@.msn.com> wrote in message
> news:%23ClUKBtQGHA.3916@.TK2MSFTNGP11.phx.gbl...
> > From here:
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0lmh.asp
> > Hope it helps
> > 1.. Decide which accounts to use for Report Server services. Reporting
> > Services requires three accounts:
> > 2.. Report Server Windows service requires an account to log on to the
> > local system. Microsoft recommends that you use Local System if you are
> > installing on Windows 2000. For more information about this
> > recommendation, see Service Account.
> > 3.. Report Server Web service requires an account to log on to the local
> > system. Because it is an ASP.NET application, it runs using the ASPNET
> > account. If you are running Windows 2000, you cannot specify a different
> > account to use during Setup; you must use the account that is defined for
> > ASP.NET. If you are running Windows Server 2003, the default is Network
> > Service, but you can choose to run the service as Local System.
> > 4.. Report Server Web service requires an account to log on to the SQL
> > Server instance that hosts the report server database. You can specify a
> > domain account, a SQL Server login, or Local System. You can also use the
> > credentials that the Report Server Web service uses to log on to the
> > system. For more information, see Report Server Database Setup.
> > "Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in
> > message news:OcR0JGqQGHA.3896@.TK2MSFTNGP15.phx.gbl...
> >> Hi,
> >>
> >> We get an "Logon Failed" message when running subscriptions;
> >>
> >> ReportServer service runs using an domain account. Domain account has
> >> run-as-a-service, logon-locally and "impersonate a client after
> >> authentication" and the apprioriate database rights.
> >>
> >> What is the "required privilege" (see below) the reportserver is
> >> requiring?
> >>
> >> Regards,
> >>
> >> Erik Tamminga
> >>
> >> ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR:
> >> Throwing
> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> >> Logon failed., ;
> >> Info:
> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> >> Logon failed. --> System.Runtime.InteropServices.COMException
> >> (0x80070522): A required privilege is not held by the client.
> >> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> >> errorCode, IntPtr errorInfo)
> >> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
> >> String pDomain, String pPassword, Boolean bTryRemote, IntPtr& pImpToken)
> >> at
> >> Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
> >> userName, String userPwd, String domain)
> >>
> >
> >
>
>|||Hi,
Thanks for the reply, but all of my data sources already use stored
credentials (sql-server's sa user, ..., yeah I know ...). So I still think
it has something to do with the win2000 environment and rs supplied
credentials. Have another look at the reported error, it talks about
impersonation, tokens and the windows user/password/domain combo wich are
not used by SQL authenticating data sources.
Regads,
Erik
"Bava Mani" <BavaMani@.discussions.microsoft.com> wrote in message
news:5F64E059-6709-4881-85ED-D9612700BB3B@.microsoft.com...
> Hi Erik,
> i think for the subscription to work you need to have Credentials stored
> securely in the report server. Subscription will not work for reports
> which
> dont have this stored credentials. When you run the report it will work,
> but
> subscription will not work. The reason is DataSources for that report does
> not have stored credentials i.e it has either have windows credential or
> no
> credential. in order that reports have subscrpiton enabled you have to
> check
> the "Credentials stored securely in the report server" and enter the user
> name and pwd. you can either enter a sql login or windows login based on
> the
> authentication type. and finally click Apply button to store it. Then do
> the
> subscrpion it will work.
> Bava
> "Erik Tamminga" wrote:
>> Thanks Beth,
>> But; RS is able to start, login to the databases. RS WebApplication works
>> as
>> expected but only the Subscriptions give me a logon failed when they're
>> scheduled to run. It seems to have something to do with RS not being able
>> to
>> render the reports using the account used for subscriptions. Any idears
>> on
>> how to fix this?
>> Erik
>> "Beth" <scratchbakery@.msn.com> wrote in message
>> news:%23ClUKBtQGHA.3916@.TK2MSFTNGP11.phx.gbl...
>> > From here:
>> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0lmh.asp
>> > Hope it helps
>> > 1.. Decide which accounts to use for Report Server services. Reporting
>> > Services requires three accounts:
>> > 2.. Report Server Windows service requires an account to log on to the
>> > local system. Microsoft recommends that you use Local System if you are
>> > installing on Windows 2000. For more information about this
>> > recommendation, see Service Account.
>> > 3.. Report Server Web service requires an account to log on to the
>> > local
>> > system. Because it is an ASP.NET application, it runs using the ASPNET
>> > account. If you are running Windows 2000, you cannot specify a
>> > different
>> > account to use during Setup; you must use the account that is defined
>> > for
>> > ASP.NET. If you are running Windows Server 2003, the default is Network
>> > Service, but you can choose to run the service as Local System.
>> > 4.. Report Server Web service requires an account to log on to the SQL
>> > Server instance that hosts the report server database. You can specify
>> > a
>> > domain account, a SQL Server login, or Local System. You can also use
>> > the
>> > credentials that the Report Server Web service uses to log on to the
>> > system. For more information, see Report Server Database Setup.
>> > "Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in
>> > message news:OcR0JGqQGHA.3896@.TK2MSFTNGP15.phx.gbl...
>> >> Hi,
>> >>
>> >> We get an "Logon Failed" message when running subscriptions;
>> >>
>> >> ReportServer service runs using an domain account. Domain account has
>> >> run-as-a-service, logon-locally and "impersonate a client after
>> >> authentication" and the apprioriate database rights.
>> >>
>> >> What is the "required privilege" (see below) the reportserver is
>> >> requiring?
>> >>
>> >> Regards,
>> >>
>> >> Erik Tamminga
>> >>
>> >> ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR:
>> >> Throwing
>> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
>> >> Logon failed., ;
>> >> Info:
>> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
>> >> Logon failed. --> System.Runtime.InteropServices.COMException
>> >> (0x80070522): A required privilege is not held by the client.
>> >> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
>> >> errorCode, IntPtr errorInfo)
>> >> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
>> >> String pDomain, String pPassword, Boolean bTryRemote, IntPtr&
>> >> pImpToken)
>> >> at
>> >> Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
>> >> userName, String userPwd, String domain)
>> >>
>> >
>> >
>>|||Hi,
Are you using any custom dataset extension or custom assemblie?
why cant you give a domain\windowuser and pwd and click the check box below
"Use as Windows credentials when connecting to the data source" in the
datasource and try running the report. see if its work.
Bava
"Erik Tamminga" wrote:
> Hi,
> Thanks for the reply, but all of my data sources already use stored
> credentials (sql-server's sa user, ..., yeah I know ...). So I still think
> it has something to do with the win2000 environment and rs supplied
> credentials. Have another look at the reported error, it talks about
> impersonation, tokens and the windows user/password/domain combo wich are
> not used by SQL authenticating data sources.
> Regads,
> Erik
> "Bava Mani" <BavaMani@.discussions.microsoft.com> wrote in message
> news:5F64E059-6709-4881-85ED-D9612700BB3B@.microsoft.com...
> > Hi Erik,
> > i think for the subscription to work you need to have Credentials stored
> > securely in the report server. Subscription will not work for reports
> > which
> > dont have this stored credentials. When you run the report it will work,
> > but
> > subscription will not work. The reason is DataSources for that report does
> > not have stored credentials i.e it has either have windows credential or
> > no
> > credential. in order that reports have subscrpiton enabled you have to
> > check
> > the "Credentials stored securely in the report server" and enter the user
> > name and pwd. you can either enter a sql login or windows login based on
> > the
> > authentication type. and finally click Apply button to store it. Then do
> > the
> > subscrpion it will work.
> >
> > Bava
> >
> > "Erik Tamminga" wrote:
> >
> >> Thanks Beth,
> >>
> >> But; RS is able to start, login to the databases. RS WebApplication works
> >> as
> >> expected but only the Subscriptions give me a logon failed when they're
> >> scheduled to run. It seems to have something to do with RS not being able
> >> to
> >> render the reports using the account used for subscriptions. Any idears
> >> on
> >> how to fix this?
> >>
> >> Erik
> >>
> >> "Beth" <scratchbakery@.msn.com> wrote in message
> >> news:%23ClUKBtQGHA.3916@.TK2MSFTNGP11.phx.gbl...
> >> > From here:
> >> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0lmh.asp
> >> > Hope it helps
> >> > 1.. Decide which accounts to use for Report Server services. Reporting
> >> > Services requires three accounts:
> >> > 2.. Report Server Windows service requires an account to log on to the
> >> > local system. Microsoft recommends that you use Local System if you are
> >> > installing on Windows 2000. For more information about this
> >> > recommendation, see Service Account.
> >> > 3.. Report Server Web service requires an account to log on to the
> >> > local
> >> > system. Because it is an ASP.NET application, it runs using the ASPNET
> >> > account. If you are running Windows 2000, you cannot specify a
> >> > different
> >> > account to use during Setup; you must use the account that is defined
> >> > for
> >> > ASP.NET. If you are running Windows Server 2003, the default is Network
> >> > Service, but you can choose to run the service as Local System.
> >> > 4.. Report Server Web service requires an account to log on to the SQL
> >> > Server instance that hosts the report server database. You can specify
> >> > a
> >> > domain account, a SQL Server login, or Local System. You can also use
> >> > the
> >> > credentials that the Report Server Web service uses to log on to the
> >> > system. For more information, see Report Server Database Setup.
> >> > "Erik Tamminga" <agnimmate@.muimetca.ln_revese_the_previous> wrote in
> >> > message news:OcR0JGqQGHA.3896@.TK2MSFTNGP15.phx.gbl...
> >> >> Hi,
> >> >>
> >> >> We get an "Logon Failed" message when running subscriptions;
> >> >>
> >> >> ReportServer service runs using an domain account. Domain account has
> >> >> run-as-a-service, logon-locally and "impersonate a client after
> >> >> authentication" and the apprioriate database rights.
> >> >>
> >> >> What is the "required privilege" (see below) the reportserver is
> >> >> requiring?
> >> >>
> >> >> Regards,
> >> >>
> >> >> Erik Tamminga
> >> >>
> >> >> ReportingServicesService!library!968!03/08/2006-11:19:11:: e ERROR:
> >> >> Throwing
> >> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> >> >> Logon failed., ;
> >> >> Info:
> >> >> Microsoft.ReportingServices.Diagnostics.Utilities.LogonFailedException:
> >> >> Logon failed. --> System.Runtime.InteropServices.COMException
> >> >> (0x80070522): A required privilege is not held by the client.
> >> >> at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32
> >> >> errorCode, IntPtr errorInfo)
> >> >> at RSRemoteRpcClient.RemoteLogon.GetRemoteImpToken(String pUserName,
> >> >> String pDomain, String pPassword, Boolean bTryRemote, IntPtr&
> >> >> pImpToken)
> >> >> at
> >> >> Microsoft.ReportingServices.Diagnostics.DatasourceRuntimeContext.MakeUserToken(String
> >> >> userName, String userPwd, String domain)
> >> >>
> >> >
> >> >
> >>
> >>
> >>
>
>

Monday, March 12, 2012

RS Web Site

All green on my RS Configurations but when I go to
http://localhost/reportserver - it brings up directory instead of RS Web
site.
What else can I check?Got it - s/b - http://localhost/reports
"Joe H" <horton.rj@.g m a i l> wrote in message
news:O6QvObyTIHA.3400@.TK2MSFTNGP03.phx.gbl...
> All green on my RS Configurations but when I go to
> http://localhost/reportserver - it brings up directory instead of RS Web
> site.
> What else can I check?
>|||Just an FYI. Reports is reportmanager, the portal that ships with RS.
ReportServer is the actual reporting application. Report Manager uses
ReportServer via webservices.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Joe H" <horton.rj@.g m a i l> wrote in message
news:uy%23HFiyTIHA.4584@.TK2MSFTNGP03.phx.gbl...
> Got it - s/b - http://localhost/reports
> "Joe H" <horton.rj@.g m a i l> wrote in message
> news:O6QvObyTIHA.3400@.TK2MSFTNGP03.phx.gbl...
>> All green on my RS Configurations but when I go to
>> http://localhost/reportserver - it brings up directory instead of RS Web
>> site.
>> What else can I check?
>>
>

Wednesday, March 7, 2012

RS fails to render a report with changes just made

Scenario: Using VS, I deploy a new version of a report (e.g., change some
text) to ReportServer. When I view the report from the web server using a
browser, the report does not show the change.
I tried deleting the report from the server, and re-deploying. The new
report appears in Reports, with the new datatime stamp, but when it renders,
it still renders the OLD version! Eventually, the new report shows up (e.g.,
hours later).
I also tried using a new session of the browser; it makes no difference.
I tried using both server\Reports and server\ReportServer. Same behavior on
both.
I tried setting "report history" on "Site Settings" and on the properties
page of the report to 1 (the lowest permitted number). Same behavior.
I assume some kind of caching at the server level is the cause, requiring a
new setting in the Web.Config or rssrvpolicy.config, but I don't know what
those settings might be.
I am using RS SP2, and have duplicated the behavior on both W2K3, and XP,
and using both IIS5 and IIS6.
Any help will be very much appreciated!"JohnWoll" <JohnWoll@.discussions.microsoft.com> schrieb im Newsbeitrag
news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@.microsoft.com...
> Scenario: Using VS, I deploy a new version of a report (e.g., change some
> text) to ReportServer. When I view the report from the web server using a
> browser, the report does not show the change.
> I tried deleting the report from the server, and re-deploying. The new
> report appears in Reports, with the new datatime stamp, but when it
> renders,
> it still renders the OLD version! Eventually, the new report shows up
> (e.g.,
> hours later).
> I also tried using a new session of the browser; it makes no difference.
> I tried using both server\Reports and server\ReportServer. Same behavior
> on
> both.
> I tried setting "report history" on "Site Settings" and on the properties
> page of the report to 1 (the lowest permitted number). Same behavior.
> I assume some kind of caching at the server level is the cause, requiring
> a
> new setting in the Web.Config or rssrvpolicy.config, but I don't know what
> those settings might be.
> I am using RS SP2, and have duplicated the behavior on both W2K3, and XP,
> and using both IIS5 and IIS6.
> Any help will be very much appreciated!|||Try reloading the site with STRG+F5 in the browser, if this resolves your
issues, this should be a client side vaching problem.
HTH, Jens SUessmeyer.
--
http://www.sqlserver2005.de
--
"JohnWoll" <JohnWoll@.discussions.microsoft.com> schrieb im Newsbeitrag
news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@.microsoft.com...
> Scenario: Using VS, I deploy a new version of a report (e.g., change some
> text) to ReportServer. When I view the report from the web server using a
> browser, the report does not show the change.
> I tried deleting the report from the server, and re-deploying. The new
> report appears in Reports, with the new datatime stamp, but when it
> renders,
> it still renders the OLD version! Eventually, the new report shows up
> (e.g.,
> hours later).
> I also tried using a new session of the browser; it makes no difference.
> I tried using both server\Reports and server\ReportServer. Same behavior
> on
> both.
> I tried setting "report history" on "Site Settings" and on the properties
> page of the report to 1 (the lowest permitted number). Same behavior.
> I assume some kind of caching at the server level is the cause, requiring
> a
> new setting in the Web.Config or rssrvpolicy.config, but I don't know what
> those settings might be.
> I am using RS SP2, and have duplicated the behavior on both W2K3, and XP,
> and using both IIS5 and IIS6.
> Any help will be very much appreciated!|||I think I have eliminated client side issues as the reason.
Please explain what you mean by "Try reloading the site with STRG+F5 in the
browser", maybe an example.
Thanks for the helping!
"Jens Sü�meyer" wrote:
> Try reloading the site with STRG+F5 in the browser, if this resolves your
> issues, this should be a client side vaching problem.
> HTH, Jens SUessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
> "JohnWoll" <JohnWoll@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@.microsoft.com...
> > Scenario: Using VS, I deploy a new version of a report (e.g., change some
> > text) to ReportServer. When I view the report from the web server using a
> > browser, the report does not show the change.
> >
> > I tried deleting the report from the server, and re-deploying. The new
> > report appears in Reports, with the new datatime stamp, but when it
> > renders,
> > it still renders the OLD version! Eventually, the new report shows up
> > (e.g.,
> > hours later).
> >
> > I also tried using a new session of the browser; it makes no difference.
> >
> > I tried using both server\Reports and server\ReportServer. Same behavior
> > on
> > both.
> >
> > I tried setting "report history" on "Site Settings" and on the properties
> > page of the report to 1 (the lowest permitted number). Same behavior.
> >
> > I assume some kind of caching at the server level is the cause, requiring
> > a
> > new setting in the Web.Config or rssrvpolicy.config, but I don't know what
> > those settings might be.
> >
> > I am using RS SP2, and have duplicated the behavior on both W2K3, and XP,
> > and using both IIS5 and IIS6.
> >
> > Any help will be very much appreciated!
>
>|||When you say you tried to use a new session of the browser what do you mean?
If you close IE and re-open it you should see the new report. I have never
not seen a new report (however I have not specified any caching). If you
have just taken the defaults when creating a report and have not set any
caching option in Report Manager then if you shut IE and re-open it you
should see the new report. Also, usually if you change the parameters and
run the report you should get the new report. Usually if I click on the
refresh of the report (not the IE refresh, you will also get the new
report).
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jens Süßmeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote in
message news:OrAqjykTFHA.3544@.TK2MSFTNGP12.phx.gbl...
> "JohnWoll" <JohnWoll@.discussions.microsoft.com> schrieb im Newsbeitrag
> news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@.microsoft.com...
>> Scenario: Using VS, I deploy a new version of a report (e.g., change some
>> text) to ReportServer. When I view the report from the web server using a
>> browser, the report does not show the change.
>> I tried deleting the report from the server, and re-deploying. The new
>> report appears in Reports, with the new datatime stamp, but when it
>> renders,
>> it still renders the OLD version! Eventually, the new report shows up
>> (e.g.,
>> hours later).
>> I also tried using a new session of the browser; it makes no difference.
>> I tried using both server\Reports and server\ReportServer. Same behavior
>> on
>> both.
>> I tried setting "report history" on "Site Settings" and on the properties
>> page of the report to 1 (the lowest permitted number). Same behavior.
>> I assume some kind of caching at the server level is the cause, requiring
>> a
>> new setting in the Web.Config or rssrvpolicy.config, but I don't know
>> what
>> those settings might be.
>> I am using RS SP2, and have duplicated the behavior on both W2K3, and XP,
>> and using both IIS5 and IIS6.
>> Any help will be very much appreciated!
>|||In answer to what I mean by using a "new session of the browser": I close MS
Internet Explorer, open it, enter the address for Reports, navigate to the
report and run it.
Here is the exact sequence I use:
-Make a change to a report using VS, e.g., change the value of a text box.
-Rebuild and redploy to ReportServer
-Launch IE, enter the url for Reports, navigate to the report, and the
change I made to the textbox value is not there.
-I delete the report completely, using Reports web interface.
-I rebuild and redploy the report. I close IE, open it again, enter the URL,
navigate to the report (which has a new datetime stamp), and run it. The
change is still missing!
- Changing parameters makes no difference.
- I am not using any caching, that I am aware of.
I appreciate the help. Let me know what you suggest I do next.
"Bruce L-C [MVP]" wrote:
> When you say you tried to use a new session of the browser what do you mean?
> If you close IE and re-open it you should see the new report. I have never
> not seen a new report (however I have not specified any caching). If you
> have just taken the defaults when creating a report and have not set any
> caching option in Report Manager then if you shut IE and re-open it you
> should see the new report. Also, usually if you change the parameters and
> run the report you should get the new report. Usually if I click on the
> refresh of the report (not the IE refresh, you will also get the new
> report).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Jens Sü�meyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote in
> message news:OrAqjykTFHA.3544@.TK2MSFTNGP12.phx.gbl...
> >
> > "JohnWoll" <JohnWoll@.discussions.microsoft.com> schrieb im Newsbeitrag
> > news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@.microsoft.com...
> >> Scenario: Using VS, I deploy a new version of a report (e.g., change some
> >> text) to ReportServer. When I view the report from the web server using a
> >> browser, the report does not show the change.
> >>
> >> I tried deleting the report from the server, and re-deploying. The new
> >> report appears in Reports, with the new datatime stamp, but when it
> >> renders,
> >> it still renders the OLD version! Eventually, the new report shows up
> >> (e.g.,
> >> hours later).
> >>
> >> I also tried using a new session of the browser; it makes no difference.
> >>
> >> I tried using both server\Reports and server\ReportServer. Same behavior
> >> on
> >> both.
> >>
> >> I tried setting "report history" on "Site Settings" and on the properties
> >> page of the report to 1 (the lowest permitted number). Same behavior.
> >>
> >> I assume some kind of caching at the server level is the cause, requiring
> >> a
> >> new setting in the Web.Config or rssrvpolicy.config, but I don't know
> >> what
> >> those settings might be.
> >>
> >> I am using RS SP2, and have duplicated the behavior on both W2K3, and XP,
> >> and using both IIS5 and IIS6.
> >>
> >> Any help will be very much appreciated!
> >
> >
>
>|||I confirmed that only if I do ALL of the following will the change to the
report appear consistently:
1. Delete the report from Report Server.
2. Redploy.
3. Change a parameter.
I can live with that.
Thanks, Bruce, for the suggestion of changing the parameter! I had tried
that, but not WITH deleting and redeploying.
"Bruce L-C [MVP]" wrote:
> When you say you tried to use a new session of the browser what do you mean?
> If you close IE and re-open it you should see the new report. I have never
> not seen a new report (however I have not specified any caching). If you
> have just taken the defaults when creating a report and have not set any
> caching option in Report Manager then if you shut IE and re-open it you
> should see the new report. Also, usually if you change the parameters and
> run the report you should get the new report. Usually if I click on the
> refresh of the report (not the IE refresh, you will also get the new
> report).
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Jens Sü�meyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote in
> message news:OrAqjykTFHA.3544@.TK2MSFTNGP12.phx.gbl...
> >
> > "JohnWoll" <JohnWoll@.discussions.microsoft.com> schrieb im Newsbeitrag
> > news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@.microsoft.com...
> >> Scenario: Using VS, I deploy a new version of a report (e.g., change some
> >> text) to ReportServer. When I view the report from the web server using a
> >> browser, the report does not show the change.
> >>
> >> I tried deleting the report from the server, and re-deploying. The new
> >> report appears in Reports, with the new datatime stamp, but when it
> >> renders,
> >> it still renders the OLD version! Eventually, the new report shows up
> >> (e.g.,
> >> hours later).
> >>
> >> I also tried using a new session of the browser; it makes no difference.
> >>
> >> I tried using both server\Reports and server\ReportServer. Same behavior
> >> on
> >> both.
> >>
> >> I tried setting "report history" on "Site Settings" and on the properties
> >> page of the report to 1 (the lowest permitted number). Same behavior.
> >>
> >> I assume some kind of caching at the server level is the cause, requiring
> >> a
> >> new setting in the Web.Config or rssrvpolicy.config, but I don't know
> >> what
> >> those settings might be.
> >>
> >> I am using RS SP2, and have duplicated the behavior on both W2K3, and XP,
> >> and using both IIS5 and IIS6.
> >>
> >> Any help will be very much appreciated!
> >
> >
>
>|||You don't have to delete the report. Try just 2 and 3.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"JohnWoll" <JohnWoll@.discussions.microsoft.com> wrote in message
news:81A637BD-D409-4AD6-9C0E-C55E8334A867@.microsoft.com...
>I confirmed that only if I do ALL of the following will the change to the
> report appear consistently:
> 1. Delete the report from Report Server.
> 2. Redploy.
> 3. Change a parameter.
> I can live with that.
> Thanks, Bruce, for the suggestion of changing the parameter! I had tried
> that, but not WITH deleting and redeploying.
> "Bruce L-C [MVP]" wrote:
>> When you say you tried to use a new session of the browser what do you
>> mean?
>> If you close IE and re-open it you should see the new report. I have
>> never
>> not seen a new report (however I have not specified any caching). If you
>> have just taken the defaults when creating a report and have not set any
>> caching option in Report Manager then if you shut IE and re-open it you
>> should see the new report. Also, usually if you change the parameters and
>> run the report you should get the new report. Usually if I click on the
>> refresh of the report (not the IE refresh, you will also get the new
>> report).
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Jens Süßmeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
>> in
>> message news:OrAqjykTFHA.3544@.TK2MSFTNGP12.phx.gbl...
>> >
>> > "JohnWoll" <JohnWoll@.discussions.microsoft.com> schrieb im Newsbeitrag
>> > news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@.microsoft.com...
>> >> Scenario: Using VS, I deploy a new version of a report (e.g., change
>> >> some
>> >> text) to ReportServer. When I view the report from the web server
>> >> using a
>> >> browser, the report does not show the change.
>> >>
>> >> I tried deleting the report from the server, and re-deploying. The new
>> >> report appears in Reports, with the new datatime stamp, but when it
>> >> renders,
>> >> it still renders the OLD version! Eventually, the new report shows up
>> >> (e.g.,
>> >> hours later).
>> >>
>> >> I also tried using a new session of the browser; it makes no
>> >> difference.
>> >>
>> >> I tried using both server\Reports and server\ReportServer. Same
>> >> behavior
>> >> on
>> >> both.
>> >>
>> >> I tried setting "report history" on "Site Settings" and on the
>> >> properties
>> >> page of the report to 1 (the lowest permitted number). Same behavior.
>> >>
>> >> I assume some kind of caching at the server level is the cause,
>> >> requiring
>> >> a
>> >> new setting in the Web.Config or rssrvpolicy.config, but I don't know
>> >> what
>> >> those settings might be.
>> >>
>> >> I am using RS SP2, and have duplicated the behavior on both W2K3, and
>> >> XP,
>> >> and using both IIS5 and IIS6.
>> >>
>> >> Any help will be very much appreciated!
>> >
>> >
>>|||As well as checking your I.E. settings for caching, you should also check if
the results are being cached at your proxy server.
"JohnWoll" <JohnWoll@.discussions.microsoft.com> wrote in message
news:045033C0-C950-411C-84B9-934D9FC92F4A@.microsoft.com...
> I think I have eliminated client side issues as the reason.
> Please explain what you mean by "Try reloading the site with STRG+F5 in
the
> browser", maybe an example.
> Thanks for the helping!
> "Jens Süßmeyer" wrote:
> > Try reloading the site with STRG+F5 in the browser, if this resolves
your
> > issues, this should be a client side vaching problem.
> >
> > HTH, Jens SUessmeyer.
> >
> > --
> > http://www.sqlserver2005.de
> > --
> >
> >
> > "JohnWoll" <JohnWoll@.discussions.microsoft.com> schrieb im Newsbeitrag
> > news:12A1EE71-64D7-4CD2-9D80-A7CE0CFB846C@.microsoft.com...
> > > Scenario: Using VS, I deploy a new version of a report (e.g., change
some
> > > text) to ReportServer. When I view the report from the web server
using a
> > > browser, the report does not show the change.
> > >
> > > I tried deleting the report from the server, and re-deploying. The new
> > > report appears in Reports, with the new datatime stamp, but when it
> > > renders,
> > > it still renders the OLD version! Eventually, the new report shows up
> > > (e.g.,
> > > hours later).
> > >
> > > I also tried using a new session of the browser; it makes no
difference.
> > >
> > > I tried using both server\Reports and server\ReportServer. Same
behavior
> > > on
> > > both.
> > >
> > > I tried setting "report history" on "Site Settings" and on the
properties
> > > page of the report to 1 (the lowest permitted number). Same behavior.
> > >
> > > I assume some kind of caching at the server level is the cause,
requiring
> > > a
> > > new setting in the Web.Config or rssrvpolicy.config, but I don't know
what
> > > those settings might be.
> > >
> > > I am using RS SP2, and have duplicated the behavior on both W2K3, and
XP,
> > > and using both IIS5 and IIS6.
> > >
> > > Any help will be very much appreciated!
> >
> >
> >

Saturday, February 25, 2012

RS doesn't works under ASP.NET 2.0?

Hi,
when I switch my reportserver virtual folder to the ASp.net2.0 I receive
this error:
"Failed to load expression host assembly"
this error appears only when I try to render a report, I can list reports or
I can access the webservice without any error.
any solution?
thanks.
Jerome.RS 2000 is not a ASP.Net 2.0 app. It uses the 1.1 framework. RS 2005 is a
ASP.Net 2.0 app.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
news:%23ndrIwI9FHA.1332@.tk2msftngp13.phx.gbl...
> Hi,
> when I switch my reportserver virtual folder to the ASp.net2.0 I receive
> this error:
> "Failed to load expression host assembly"
> this error appears only when I try to render a report, I can list reports
> or I can access the webservice without any error.
> any solution?
> thanks.
> Jerome.
>|||I know, but, for example Sharepoint works fine under ASP.NET 2.0 and its a
1.1 software.
but if I switch the reportserver virtual directory from v1.1 to v2.0,
rendering a report stop working.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%232wwe4P9FHA.1248@.TK2MSFTNGP14.phx.gbl...
> RS 2000 is not a ASP.Net 2.0 app. It uses the 1.1 framework. RS 2005 is a
> ASP.Net 2.0 app.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
> news:%23ndrIwI9FHA.1332@.tk2msftngp13.phx.gbl...
>> Hi,
>> when I switch my reportserver virtual folder to the ASp.net2.0 I receive
>> this error:
>> "Failed to load expression host assembly"
>> this error appears only when I try to render a report, I can list reports
>> or I can access the webservice without any error.
>> any solution?
>> thanks.
>> Jerome.
>>
>|||If you want RS to work, leave it alone at 1.1 or upgrade to RS 2005. Note
that you can leave SQL Server as 2000 and still upgrade RS to 2005. You do
need a 2005 license though. Beside additional features I noticed significant
performance improvements with RS 2005.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:OrI6xeR9FHA.500@.TK2MSFTNGP15.phx.gbl...
>I know, but, for example Sharepoint works fine under ASP.NET 2.0 and its a
>1.1 software.
> but if I switch the reportserver virtual directory from v1.1 to v2.0,
> rendering a report stop working.
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:%232wwe4P9FHA.1248@.TK2MSFTNGP14.phx.gbl...
>> RS 2000 is not a ASP.Net 2.0 app. It uses the 1.1 framework. RS 2005 is a
>> ASP.Net 2.0 app.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Jéjé" <willgart@.BBBhotmailAAA.com> wrote in message
>> news:%23ndrIwI9FHA.1332@.tk2msftngp13.phx.gbl...
>> Hi,
>> when I switch my reportserver virtual folder to the ASp.net2.0 I receive
>> this error:
>> "Failed to load expression host assembly"
>> this error appears only when I try to render a report, I can list
>> reports or I can access the webservice without any error.
>> any solution?
>> thanks.
>> Jerome.
>>
>>
>