rsItemNotFound for Report Models

I have a Sharepoint integrated Reporting Services server. I have created Report models based on Data Sources. I then created Report Builder Reports to make some BI Charts and Graphs. They look great and work fine for a few days then all of a sudden I get a rsItemNotFound error saying it cannot find the Report Model which is clearly there.

An error has occurred during report processing. (rsProcessingAborted)

The item 'IT Reports/PWPDB_Prod_Model.smdl' cannot be found. (rsItemNotFound)

If I open the Report Model from Report Builder it loads the data fields, but also fails to run reports with the same error

If I try to regenerate the model from the library I get an error stating that the model needs to be a generated model.

The model specified must be a generated model.

(rsModelNotGenerated)

Even after rebooting all of the servers in the farm I get the same messages. I can regenerate a model from the data source and it doesn't work. I am seeing no errors in the logs of my app server at all regarding reporting services.

It looks as though I will have to de-integrate Reporting Services as it is not viable for a business critical application.

Please for th elove of Zeus tell me you were able to solve this?

I am getting the exact same error. I have tried everything under the sun to make this work. Any advice?

rsItemNotFound for Report Models

I have a Sharepoint integrated Reporting Services server. I have created Report models based on Data Sources. I then created Report Builder Reports to make some BI Charts and Graphs. They look great and work fine for a few days then all of a sudden I get a rsItemNotFound error saying it cannot find the Report Model which is clearly there.

An error has occurred during report processing. (rsProcessingAborted)

The item 'IT Reports/PWPDB_Prod_Model.smdl' cannot be found. (rsItemNotFound)

If I open the Report Model from Report Builder it loads the data fields, but also fails to run reports with the same error

If I try to regenerate the model from the library I get an error stating that the model needs to be a generated model.

The model specified must be a generated model.

(rsModelNotGenerated)

Even after rebooting all of the servers in the farm I get the same messages. I can regenerate a model from the data source and it doesn't work. I am seeing no errors in the logs of my app server at all regarding reporting services.

It looks as though I will have to de-integrate Reporting Services as it is not viable for a business critical application.

Please for th elove of Zeus tell me you were able to solve this?

I am getting the exact same error. I have tried everything under the sun to make this work. Any advice?

RS report integrated with .Net web app

I am trying to integrate a Reporting Services report within a .Net web
application. The easiest way to do this is to create a frame from within the
web application and link to the Reporting Services report. That way it
appears to be part of the application. But how can it be setup so that the
user doesn't have to log in twice? Once for the web application and then
again after they click on the link that goes to the Reporting Servies report.
How can I turn off the login prompt that comes up when the user clicks on
the link to the RS report but still lock down Report Manager? Also, how can
the roles be shared that is used from within the web application and the
reporting services report?Hi,
If you haven't resolved this issue first implement and install the Custom
Authentication Forms Authentication Example:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/ufairs.asp
and then see the following:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconformsauthenticationacrossapplications.asp
Its actually quite simple to setup once you have configured and set up the
Custom Authentication Forms Authentication Example.
Good luck,
Nick @. INDATA
"David" wrote:
> I am trying to integrate a Reporting Services report within a .Net web
> application. The easiest way to do this is to create a frame from within the
> web application and link to the Reporting Services report. That way it
> appears to be part of the application. But how can it be setup so that the
> user doesn't have to log in twice? Once for the web application and then
> again after they click on the link that goes to the Reporting Servies report.
> How can I turn off the login prompt that comes up when the user clicks on
> the link to the RS report but still lock down Report Manager? Also, how can
> the roles be shared that is used from within the web application and the
> reporting services report?|||Did you get this to work? I am trying to do the same thing.
"David" wrote:
> I am trying to integrate a Reporting Services report within a .Net web
> application. The easiest way to do this is to create a frame from within the
> web application and link to the Reporting Services report. That way it
> appears to be part of the application. But how can it be setup so that the
> user doesn't have to log in twice? Once for the web application and then
> again after they click on the link that goes to the Reporting Servies report.
> How can I turn off the login prompt that comes up when the user clicks on
> the link to the RS report but still lock down Report Manager? Also, how can
> the roles be shared that is used from within the web application and the
> reporting services report?|||This is most likely a double hop issue. Windows NT Challenge Response does
not support double hop (in that once passed to the IIS server, the same
credentials cannot be passed to a back-end server for authentication). Do do
this you need to be using Kerberos. As far as Active Directory and Kerberos,
other than knowing you can do this, I don't know any more than that.
Another option, is to have RS on the same server as your app. The database
can be on a different machine. This does mean that you need to have a
license for SQL Server wherever RS is installed.
The other option is to implement Forms based authentication (i.e. you
provide the user authentication). This is non-trivial but is the method that
is used by people using RS over the internet.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Katie" <Katie@.discussions.microsoft.com> wrote in message
news:6A87F447-C852-4668-9542-3C7A19571C6D@.microsoft.com...
> Did you get this to work? I am trying to do the same thing.
> "David" wrote:
>> I am trying to integrate a Reporting Services report within a .Net web
>> application. The easiest way to do this is to create a frame from within
>> the
>> web application and link to the Reporting Services report. That way it
>> appears to be part of the application. But how can it be setup so that
>> the
>> user doesn't have to log in twice? Once for the web application and then
>> again after they click on the link that goes to the Reporting Servies
>> report.
>> How can I turn off the login prompt that comes up when the user clicks
>> on
>> the link to the RS report but still lock down Report Manager? Also, how
>> can
>> the roles be shared that is used from within the web application and the
>> reporting services report?

RS integrated with MOSS - Internal Error - AdjustTokenPrivileges

I'm running MOSS 2007 Enterprise, SQL 2005 SP2, RS integrated with MOSS and have a number of reports deployed to a Reports Library in MOSS. 3 out of 10 times I run a report I get a error message stating that 'An internal error occured on the report server.' Just hitting Apply on the parameter panel will fix the problem and render the report as expected.

Previous entries to the forum about this error hints at an error that supposedly was fixed in SP2; since I'm running SP2 something else must be the problem.

Any insight to what might cause the problem ?

Regards,

Trond

Relevant content from the RS error log included below:

04/26/07 11:42:21, ERROR , SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () failed (00000514)

04/26/07 11:42:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied

04/26/07 11:42:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,ProcessID = 7008

04/26/07 11:42:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,ThreadId = 0

04/26/07 11:42:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,Flags = 0x0

04/26/07 11:42:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,MiniDumpFlags = 0x0

04/26/07 11:42:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,SqlInfoPtr = 0x47405860

04/26/07 11:42:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,DumpDir = <NULL>

04/26/07 11:42:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,ExceptionRecordPtr = 0x00000000

04/26/07 11:42:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,ContextPtr = 0x00000000

04/26/07 11:42:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,ExtraFile = <NULL>

04/26/07 11:42:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,InstanceName = <NULL>

04/26/07 11:42:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,ServiceName = <NULL>

04/26/07 11:42:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used

04/26/07 11:42:21, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used

04/26/07 11:42:23, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used

04/26/07 11:42:23, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\SQLDmpr0147.mdmp

04/26/07 11:42:23, ACTION,w3wp.exe, Watson Invoke: No

w3wp!processing!1!4/26/2007-11:42:21:: a ASSERT: Assertion failed!Call stack:

Microsoft.ReportingServices.ReportProcessing.ReportProcessing.UpdateTimingInformation(RunningJobContext jobContext, Int64 totalDurationMs, Int64 reportDataRetrievalDurationMs, Int64 reportRenderingDurationMs)

Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(IRenderingExtension renderer, DateTime executionTimeStamp, GetReportChunk getCompiledDefinitionCallback, ProcessingContext pc, RenderingContext rc, CreateReportChunk cacheDataCallback, Boolean& dataCached)

Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderReport(DateTime executionTimeStamp, GetReportChunk getCompiledDefinitionCallback, ProcessingContext pc, RenderingContext rc)

Microsoft.ReportingServices.Library.RSService.RenderAsLive(CatalogItemContext reportContext, ItemProperties properties, ParameterInfoCollection effectiveParameters, Guid reportId, ClientRequest session, String description, ReportSnapshot intermediateSnapshot, DataSourceInfoCollection thisReportDataSources, Boolean cachingRequested, Boolean isLinkedReport, Warning[]& warnings, ReportSnapshot& resultSnapshotData, DateTime& executionDateTime, RuntimeDataSourceInfoCollection& alldataSources, UserProfileState& usedUserProfile)

Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(CatalogItemContext reportContext, ClientRequest session, Warning[]& warnings, ParameterInfoCollection& effectiveParameters)

Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext reportContext, ClientRequest session, Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]& secondaryStreamNames)

Microsoft.ReportingServices.Library.RenderFirstCancelableStep.Execute()

Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()

Microsoft.ReportingServices.Library.RenderFirstCancelableStep.RenderFirst(RSService rs, CatalogItemContext reportContext, ClientRequest session, JobType type, Warning[]& warnings, ParameterInfoCollection& effectiveParameters, String[]& secondaryStreamNames)

Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderReport(HttpResponseStreamFactory streamFactory)

Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.DoStreamedOperation(StreamedOperation operation)

Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderItem(ItemType itemType)

Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPageContent()

Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.RenderPage()

Microsoft.ReportingServices.WebServer.ReportServiceHttpHandler.ProcessRequest(HttpContext context)

System.Web.HttpApplication+CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

System.Web.HttpApplication.ResumeSteps(Exception error)

System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)

System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)

System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr)

System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType)

w3wp!library!1!4/26/2007-11:42:21:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., un-named assertion fired for component processing;

Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details.

Reapplying SP2, rebooting and then reapplying SP2 once more because I got frustrated beyond what's good for my health, seems to have fixed this issue.

Why the initial and the second SP2 didn't help is beyond my understanding.

Trond

RS 2005 SP2 in Sharepoint integrated mode

Up until an hour ago, I was using the Sql Server Reporting Services Report Viewer webpart in Sharepoint with forms authentication, and was not having an issue. The only thing that I did (or remember doing) before things went sour was upload a new report to the document list and since then whenever I try to access a report, manage the data source on a report, change the report URL in the webpart, I get the following message:

An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode. --> The request failed with the error message:
--
<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="/_layouts/login.aspx?ReturnUrl=%2f_vti_bin%2fReportServer%2fReportService2006.asmx">here</a>.</h2>
</body></html>

--.

I found some related posts and have tried the following, but none have helped:

Removed all reports and reuploaded only the one that was definitely working.

I changed the application pool for the report server to be the same app pool as Sharepoint (runs under domain admin account).

I changed the application pool for the report server back to it's original (which the Reporting Services Configuration prefers - was running under Network Service acct before the problem started, now running under domain admin acct)

I can browse to http://server/reportserver.

I'm running under forms authentication, which had been working.

I can access the three configs for Reporting Services under Application Management in Central Admin - I've tried changing the settings.

I can access http://server/_vti_bin/reportserver/reportservice2006.asmx as well as http://server/_vti_bin/reportserver/reportserviceauthentication.asmx (that was suggested in one post)

I've restarted IIS numerous times, and also finally rebooted the server.

I've created a new document list and set it for report content, just like the other list.

I also just noticed that even though I've set up my admin account as a site collection administrator, I now no longer see my report options under the New button in the document library (both the old and new). I don't know if this is related.

I'm sure that this is a case of something minor that I did that I forgot about. Any suggestions or other troubleshooting that I can do?

Thanks!

daw

Has anyone seen an error like this? Do I need to reinstall reporting services?

Thanks for any advice that you can give me!

daw

|||Hi Daw,

This is just a shot in the dark but have you tried the last step in http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1170221&SiteID=1 :

3. If you've run the

installer multiple times, there may be duplicate entries in the

web.config file. Open web.config which by default should be in

C:\Inetpub\wwwroot\wss\VirtualDirectories\80 . In that file make sure

there is only one entry for "ReportServiceAuthentication.asmx". If

there is more than one entry, delete the extra tag.

Thanks,
Josh
|||

Thanks, Josh! I checked, and there is only one entry in the web.config.

I have determined that it must be something to do with forms authentication. When I changed the authentication provider back to Windows and logged into the site, I'm able to use the report viewer and access the reports. I can also add New data sources in the document library. No permissions have been changed that I'm aware of, so I'm not sure where to check. I've looked at the security on some of the folders, but it appears to be correct. Do you know why forms authentication would not work? It had been working just fine. The forms authentication user is set up as the site administrator, and is in the owners Sharepoint group which has full control.

Thanks!!

daw

|||

It looks like it may not even be related to the RS add-in, unless it's related to SP2. I removed the add-in and I still have the problem in document libraries under forms authentication. I can see the New, Upload, Actions and Settings buttons in the document libraries, but I do not have an option to create a new document (or other content type), however I have the option and can create a new folder. I have the option to upload one document at a time, but not multiple. It's almost like I have partial permissions. This user is the site collection administrator, is in the Owners Sharepoint group which has full control, and I even added the user with full control.

Any ideas on where this permissions issue could be stemming from? Windows authentication works just fine.

daw

|||

<html><head><title>Object moved</title></head><body>
<h2>Object moved to <a href="/_layouts/login.aspx?ReturnUrl=%2f_vti_bin%2fReportServer%2fReportService2006.asmx">here</a>.</h2>
</body></html>

The above error message happened when you acccess a web site configured with forms auth but your request does not carry the forms auth cookie. Usually browser will automatically add it in after you log in. Did you see frequent timeout happneing?

It should not related to report server itself because the request has not got to report server yet. Can you create a new web app and try to see whether it still repros?

|||

No timeouts, no prompts to login again.

I ran a repair on Sharepoint, but no change. It looks like I may need to uninstall and reinstall Sharepoint since I can't find an answer. I'm just concerned that it may happen again.

Thanks for the help!

daw

|||

The issue with not being able to add a new document or other content type was related to the Authentication Provider setup in Central Admin. By default, the Enable Client Integration? for forms authentication is set to No. When I changed it to Yes, I saw the New Document, etc.

I'm still getting the error when accessing the Reporting Services add-in. I've uninstalled and reinstalled Sharepoint, as well as Reporting Services and the add-in. No change. Has anyone else come across this error?

daw

|||

Reporting Services and Sharepoint both support forms authentication, but they are not compatible. See the Note in this document, http://msdn2.microsoft.com/en-us/library/bb283324.aspx

I'm not sure how it was ever working in the first place.

Hope this helps someone else!

daw