Report with SSIS package having Indirect Package Configuration setup

Deployed Report having SSIS package as source do not work when Indirect Package configuration is used in ETL package. It seems ETL package when called/executed from Report manager does not recognize environment variable to pick up the dtsconfig file.

The Report works when Direct package configuration is used to same dtsconfig file.

What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod very difficult.

IIS needs to be reset to pickup the new system environment variable.

Also the variable should be of type System.

Thanks

sql

report viewer web part error

I'm having problems with the SharePoint configuration on a REport Viewer web
part. When Report Explorer and Report Viewer are used together, all is fine.
This is just trying to configure Report Viewer as a stand alone web part.
My direct URL path to a report is:
http://server01/Reports/Pages/Report.aspx?ItemPath=%2fCorporate+Applications%2fOpen+Requests+By+Priority
In the Report Manager URL box, I have http://server01/Reports.
In the Report Path box I have:
/Pages/Report.aspx?ItemPath=%2fCorporate+Applications%2fOpen+Requests+By+Priority.
I get the Reporting Services Error in the Report Viewer web part:
"The path of the item
'/reportserver?%2fCorporate+Applications%2fOpen+Requests+By+Priority&rs:Command=Render'
is not valid. The full path must be less than 260 characters long, must start
with slash; other restrictions apply. Check the documentation for complete
set of restrictions. (rsInvalidItemPath) "
Of course the doc just tells me my path is too long, which it's not.
Any ideas?
Thanks,
PaulI have the same problem...did you figure out a solution? If so, can
you send it to me at ram.pisipati@.lmco.com
Thanks
Ram|||Hi,
I got the same error !
solution:
just enter the folder name from reporting service
i.e. /AD+Site+Reports
Torsten
ram.pisipati@.lmco.com schrieb:
> I have the same problem...did you figure out a solution? If so, can
> you send it to me at ram.pisipati@.lmco.com
> Thanks
> Ram|||Not sure I understand you correctly. Where do you want me to enter the
folder name?
the report viewer web part takes two parameters and this is what I am
entering for each of the parameters
Report Server path: http://www.myserver.com/Reports/?
Report path: /TestFolder/TestReport
Thanks in advance
Ram

Report Services Instance not found

after re-installing sql server 2005 server reporting services when i start the Reporting Services Configuration Manager a message pops up saying "Not Found", at the instance selection screen. when i type in the name of the server and click find i get the same message.. what am i doing wrong?

THe next steps would be:

-Is the Reporting Service started properly ?
-Which port is Reporting Manager using ? (see in the IIS configuration)
-Do you have Sharepoint installed on the machine ?
-Is the Report Service available ? (e.g. http://localhost/ReportServer)

HTH, Jens Suessmeyer.

http://www.sqslerver2005.de

|||When i go to sql server 2005 surface area to check if the report service is running i see the service listed under Surface area configuration for Services and Connection and it is started by local system. when i go to Surface Area configuration for features and i click on reporting services a message pops up that says Not Found (System.Management) why is this?

Report Services installation problem

I've installed SQL Express 2005 on an XP Professional machine and I'm trying to configure Report Services. In Reporting Services Configuration Manager, all items are "green" except "Web Service Identity". The value is <machinename>\ASPNET and isn't configurable. I've searched the forums and followed the advice I've found to remove and reinstall .NET, but it hasn't helped. User ASPNET does exist on the machine with a local account, and IIS5 is running. SQL gurus, please help me figure out what to do! Thanks.The Web Service Identity is supposed to be read-only. If everything is grean RS should be already configured and good to go. What's not working?|||

I apologize - I didn't offer full details. I was frustrated!

Clicking "Apply" on the "Web Service Identity" dialogue results in an error. Clicking the link for details reveals this:

---

ReportServicesConfigUI.WMIProvider.WMIProviderException: The account name is not valid. Specify an account in the form domain\alias.

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

---

The ASPNET user does exist however! I don't understand what's wrong. Thanks for your help.

|||

Not sure what's going on. It's seeme like there is something wrong with the ASPNET account. Is ReportServer vroot in IIS running under asp.net 2.0. Are any other web applications on that machine working OK?

|||That's a little over my head, I know little about IIS. Other "web pages" are accessible, such as http://localhost/printers and http://localhost/tsweb. This machine is dedicated to running SQL Server Express, so no other applications are running that I can test for web connectivity. Any direction you can point me in is greatly appreciated! Thanks again for your help.|||

1. Open up Internet Information Services applet in the Administrators group.

2. Right-click on the ReportServer node and choose Properties. Flip to the ASP.NET tab. What's the ASP.NET version?

|||The ASP.NET version is 2.0.50727. Thanks for helping me through this!

Report Services installation problem

I've installed SQL Express 2005 on an XP Professional machine and I'm trying to configure Report Services. In Reporting Services Configuration Manager, all items are "green" except "Web Service Identity". The value is <machinename>\ASPNET and isn't configurable. I've searched the forums and followed the advice I've found to remove and reinstall .NET, but it hasn't helped. User ASPNET does exist on the machine with a local account, and IIS5 is running. SQL gurus, please help me figure out what to do! Thanks.The Web Service Identity is supposed to be read-only. If everything is grean RS should be already configured and good to go. What's not working?|||

I apologize - I didn't offer full details. I was frustrated!

Clicking "Apply" on the "Web Service Identity" dialogue results in an error. Clicking the link for details reveals this:

---

ReportServicesConfigUI.WMIProvider.WMIProviderException: The account name is not valid. Specify an account in the form domain\alias.

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

---

The ASPNET user does exist however! I don't understand what's wrong. Thanks for your help.

|||

Not sure what's going on. It's seeme like there is something wrong with the ASPNET account. Is ReportServer vroot in IIS running under asp.net 2.0. Are any other web applications on that machine working OK?

|||That's a little over my head, I know little about IIS. Other "web pages" are accessible, such as http://localhost/printers and http://localhost/tsweb. This machine is dedicated to running SQL Server Express, so no other applications are running that I can test for web connectivity. Any direction you can point me in is greatly appreciated! Thanks again for your help.|||

1. Open up Internet Information Services applet in the Administrators group.

2. Right-click on the ReportServer node and choose Properties. Flip to the ASP.NET tab. What's the ASP.NET version?

|||The ASP.NET version is 2.0.50727. Thanks for helping me through this!

Report Services Configuration Error

Hello,

I am a complete Newbie with SQL Server 2005. Can someone help with this problem or at least point me in the right directio for diagnosing it correctly.

I'm learning the Standard SQL product on Windows XP Pro, and everything on my computer has the latest updates (from Windows Updates). I had previously installed SQL Express, but removed all products associated with that according to steps listed at Microsoft's site (pre-installation steps for SQL Server 2005 Standard, as they relate to the removal of SQLExpress).

My problem is I can't run "Reporting Services Configuration". When I try to run it, the main window opens with "Report Server Installation Instance Selection" window, and immediately I get an error box that says, "An unknown error has occurred in the WMI Provider. Error Code 80040219". When I click Ok, I'm back at the instance selection window, where my computer name is by default the machine name, but the instance name is greyed out. After the error, Event Viewer/Application gives the info below. I noticed that it refers to MSSQL.2\Reporting Services\ - but that was the directory for SQL Express Reporting Services, according to the mapping in my registry. It shows mssql.4 as the Standard SQL Reporting Services directory

Event Type: Error
Event Source: Report Server
Event Category: (5)
Event ID: 133
Date: 1/3/2007
Time: 11:08:23 AM
User: N/A
Computer: BSDELL
Description:
The description for Event ID ( 133 ) in Source ( Report Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: c:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\RSReportServer.config.

When I try to connect to Report Services through SQL Server Management Studio, I get the following error: Cannot connect to BsDell - with the following technical details...

Program Location:

at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.ParseServerName(String serverName)
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.CreateSqlOlapConnectionInfoBase(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Thanks so much Albert!! It was the Namespace in the config file.

Removed, saved, and immediately connected in management studio.

:)

Brian

|||

The error means that the config tool can't open the config file for the instance "MSSQL.2". Not surprising, since you uninstalled it. However, the instance name is apparently still in the registry. I'm not sure why the config tool is unable to continue after the error, but you may be able to work around it by cleaning the registry. Using Regedit, look for a key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\RS". Under that key, is there a value whose data is "MSSQL.2"? If so, delete the value.

-Albert

|||

Thanks Albert, that was it.

After deleting that key, I was able to run the RS Config. But I'm still not able to pull up the web at http://localhost/Reports or http://localhost/ReportServer and I can't connect to Reporting Services in MS SQL Server Management Studio.

Should I delete the old mssql.2 folder (inside c:\program files\Microsoft SQL Server) that used to be for the SQLEXPRESS instance? And, along those lines, should I delete any other branches or keys in the registry that mention MSSQL.2? I have a branch at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.2 which is almost an exact duplicate of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.4 (mssql.2 for SQLEXPRESS and mssql.4 for MSSQLSERVER standard)

I appreciate your help immensly.

Here's the last part of the SQLDUMPER_ERROR.log from "MSSQL.4\Reporting Services\LogFiles".

It's got about 10 dumps in it, and they are all exactly like what I've pasted in below.

01/04/07 16:39:48, ACTION, aspnet_wp.exe, Watson Invoke: No

01/04/07 16:40:18, ERROR , SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () failed (00000514)

01/04/07 16:40:18, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied

01/04/07 16:40:18, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 1180

01/04/07 16:40:18, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0

01/04/07 16:40:18, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0

01/04/07 16:40:18, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0

01/04/07 16:40:18, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x11EB40D4

01/04/07 16:40:18, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>

01/04/07 16:40:18, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000

01/04/07 16:40:18, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000

01/04/07 16:40:18, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>

01/04/07 16:40:18, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>

01/04/07 16:40:18, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>

01/04/07 16:40:18, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used

01/04/07 16:40:19, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used

01/04/07 16:40:19, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\LogFiles\SQLDmpr0010.mdmp

01/04/07 16:40:19, ACTION, aspnet_wp.exe, Watson Invoke: No

|||

It would not hurt to delete the registry key and files for the MSSQL.2 instance. I don't know if it's causing your problem, though. Can you scan the other log files in MSSQL.4\Reporting Services\LogFiles for error messages?

-Albert

|||

Albert,

I have several logs that appeared in the mssql.4 log folder after trying to connect to report server in MS SQL Management Studio, and I have two "system" event log entries which both say the same thing, recorded with the same time stamp. I'll paste one of the report server error logs, the sql dumper and the system event item below, but first I will just paraphrase the errors from each log.

The system event error log puzzles me. I've looked up the referenced CLSID key in the registry (see below), starting in HKCR\CLSID\ and the clsid has 18 entries. The entries have various names, like Netork Connection Manager, Lan Connection, etc But I don't see any of the named items in the Component Services tool. Apparently the item or items need Local Activation permission. By the way, the Event Log mentions ASPNET as the user.

The ReportServer log makes reference to "Object reference not set to an instance of an object", just before the system event DCOM error, and then the same error again immediately following the system event DCOM error.

Thanks again for your help.

Brian

--System Event DCOM errors- (2 Items, both exactly the same, pasting only one item)

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 1/5/2007
Time: 10:54:29 AM
User: BSDELL\ASPNET
Computer: BSDELL
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{BA126AD1-2166-11D1-B1D0-00805FC1270E}
to the user BSDELL\ASPNET SID (S-1-5-21-1417001333-813497703-725345543-1008). This security permission can be modified using the Component Services administrative tool.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

--ReportServer__01_05_2007_10_54_20.log--

<Header>

<Product>Microsoft SQL Server Reporting Services Version 9.00.2047.00</Product>

<Locale>en-US</Locale>

<TimeZone>Eastern Standard Time</TimeZone>

<Path>C:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\LogFiles\ReportServer__01_05_2007_10_54_20.log</Path>

<SystemName>BSDELL</SystemName>

<OSName>Microsoft Windows NT 5.1.2600 Service Pack 2</OSName>

<OSVersion>5.1.2600.131072</OSVersion>

</Header>

aspnet_wp!webserver!1!1/5/2007-10:54:22:: i INFO: Reporting Web Server started

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing ConnectionType to '0' as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file.

aspnet_wp!configmanager!1!1/5/2007-10:54:22:: w WARN: WebServiceAccount is not specified in the config file. Using default: BSDELL\ASPNET

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing ProcessRecycleOptions to '0' as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.

aspnet_wp!library!1!1/5/2007-10:54:22:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file.

aspnet_wp!resourceutilities!1!1/5/2007-10:54:22:: i INFO: Reporting Services starting SKU: Standard

aspnet_wp!resourceutilities!1!1/5/2007-10:54:22:: i INFO: Evaluation copy: 0 days left

aspnet_wp!resourceutilities!1!1/5/2007-10:54:22:: i INFO: Running on 1 physical processors, 2 logical processors

aspnet_wp!runningjobs!1!1/5/2007-10:54:22:: i INFO: Database Cleanup (Web Service) timer enabled: Next Event: 600 seconds. Cycle: 600 seconds

aspnet_wp!runningjobs!1!1/5/2007-10:54:22:: i INFO: Running Requests Scavenger timer enabled: Next Event: 60 seconds. Cycle: 60 seconds

aspnet_wp!runningjobs!1!1/5/2007-10:54:22:: i INFO: Running Requests DB timer enabled: Next Event: 60 seconds. Cycle: 60 seconds

aspnet_wp!runningjobs!1!1/5/2007-10:54:22:: i INFO: Memory stats update timer enabled: Next Event: 60 seconds. Cycle: 60 seconds

aspnet_wp!library!1!01/05/2007-10:54:22:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ;

Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. > System.NullReferenceException: Object reference not set to an instance of an object.

at Microsoft.ReportingServices.Diagnostics.WebConfigUtil.GetWebConfigAuthenticationAttribute(String attrName)

at Microsoft.ReportingServices.Diagnostics.WebConfigUtil.GetAuthenticationType()

at Microsoft.ReportingServices.Diagnostics.WebConfigUtil.get_UsingWindowsAuth()

at Microsoft.ReportingServices.WebServer.Global.EnableAntiDos()

at Microsoft.ReportingServices.WebServer.Global.ShouldRejectAntiDos()

at Microsoft.ReportingServices.WebServer.Global.Application_AuthenticateRequest(Object sender, EventArgs e)

End of inner exception stack trace

aspnet_wp!library!1!01/05/2007-10:54:28:: i INFO: Exception dumped to: C:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\LogFiles flags= ReferencedMemory, AllThreads, SendToWatson

aspnet_wp!library!1!01/05/2007-10:54:31:: i INFO: Catalog SQL Server Edition = Standard

aspnet_wp!library!1!01/05/2007-10:54:31:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ;

Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. > System.NullReferenceException: Object reference not set to an instance of an object.

at Microsoft.ReportingServices.Diagnostics.WebConfigUtil.GetWebConfigAuthenticationAttribute(String attrName)

at Microsoft.ReportingServices.Diagnostics.WebConfigUtil.GetAuthenticationType()

at Microsoft.ReportingServices.Diagnostics.WebConfigUtil.get_UsingWindowsAuth()

at Microsoft.ReportingServices.WebServer.Global.EnableAntiDos()

at Microsoft.ReportingServices.WebServer.Global.Application_EndRequest(Object sender, EventArgs e)

End of inner exception stack trace

aspnet_wp!library!1!01/05/2007-10:54:32:: i INFO: Exception dumped to: C:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\LogFiles flags= ReferencedMemory, AllThreads, SendToWatson

--SQLDUMPER_ERRORLOG.log--

01/05/07 10:54:27, ERROR , SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () failed (00000514)

01/05/07 10:54:27, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied

01/05/07 10:54:27, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 3976

01/05/07 10:54:27, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0

01/05/07 10:54:27, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0

01/05/07 10:54:27, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0

01/05/07 10:54:27, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x47405860

01/05/07 10:54:27, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>

01/05/07 10:54:27, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000

01/05/07 10:54:27, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000

01/05/07 10:54:27, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>

01/05/07 10:54:27, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>

01/05/07 10:54:27, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>

01/05/07 10:54:27, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used

01/05/07 10:54:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used

01/05/07 10:54:28, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\LogFiles\SQLDmpr0017.mdmp

01/05/07 10:54:28, ACTION, aspnet_wp.exe, Watson Invoke: No

01/05/07 10:54:31, ERROR , SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () failed (00000514)

01/05/07 10:54:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied

01/05/07 10:54:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 3976

01/05/07 10:54:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0

01/05/07 10:54:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0

01/05/07 10:54:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0

01/05/07 10:54:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x47405860

01/05/07 10:54:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>

01/05/07 10:54:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000

01/05/07 10:54:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000

01/05/07 10:54:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>

01/05/07 10:54:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>

01/05/07 10:54:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>

01/05/07 10:54:31, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used

01/05/07 10:54:32, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used

01/05/07 10:54:32, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\MSSQL.4\Reporting Services\LogFiles\SQLDmpr0018.mdmp

01/05/07 10:54:32, ACTION, aspnet_wp.exe, Watson Invoke: No

|||

Check that the MSSQL.4\Reporting Services\ReportServer\web.config file has a configuration/system.web/authentication element. (See this thread). Also, if you have edited the ReportServer web site with VS2005, it may have altered the web.config by adding a namespace attribute to the configuration element. This would cause the exception you saw.

-Albert

report server problem

I have installed SQL 2005 reporting services and I configured it using
Reporting Services Configuration. Now I tried to access to report manager
using http://servername/Reports with login I used to start reporting
services. It doesn't work and keep prompting me for login and password. But
no use and I am sure this login is correct and password correct and it
started the reportings services successfully. Can anyone please help how to
solve this problem. Thanks.On Oct 24, 9:06 pm, "Andrew Backer" <a...@.b.com> wrote:
> I have installed SQL 2005 reporting services and I configured it using
> Reporting Services Configuration. Now I tried to access to report manager
> usinghttp://servername/Reportswith login I used to start reporting
> services. It doesn't work and keep prompting me for login and password. But
> no use and I am sure this login is correct and password correct and it
> started the reportings services successfully. Can anyone please help how to
> solve this problem. Thanks.
If you are using a browser other than Internet Explorer, this is the
default behavior. Otherwise, you will want to make sure that you do
not have the either the Reports or ReportServer virtual directory set
to anonymous access (via: right-click My Computer >> select Manage >>
select Services and Applications >> Internet Information Services >>
Web Sites >> Default Web Site >> right-click Reports/ReportServer >>
select Properties >> select the Directory Security tab >> select the
Edit... button). also, make sure that the login you are using has
Browser rights/privileges in the Report Manager. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Enrique,
In fact, I am using IE. When I use IE in the server, it asked
me to login and always fails me. When I use IE in the client PC, it don't
ask me for login and just gives me "HTTP status 400: Bad reqeust" directly.
Can you please tell me what user login being used in client PC and what in
server? Please help. Thanks.
"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:1193279009.940293.80780@.v23g2000prn.googlegroups.com...
> On Oct 24, 9:06 pm, "Andrew Backer" <a...@.b.com> wrote:
>> I have installed SQL 2005 reporting services and I configured it using
>> Reporting Services Configuration. Now I tried to access to report manager
>> usinghttp://servername/Reportswith login I used to start reporting
>> services. It doesn't work and keep prompting me for login and password.
>> But
>> no use and I am sure this login is correct and password correct and it
>> started the reportings services successfully. Can anyone please help how
>> to
>> solve this problem. Thanks.
>
> If you are using a browser other than Internet Explorer, this is the
> default behavior. Otherwise, you will want to make sure that you do
> not have the either the Reports or ReportServer virtual directory set
> to anonymous access (via: right-click My Computer >> select Manage >>
> select Services and Applications >> Internet Information Services >>
> Web Sites >> Default Web Site >> right-click Reports/ReportServer >>
> select Properties >> select the Directory Security tab >> select the
> Edit... button). also, make sure that the login you are using has
> Browser rights/privileges in the Report Manager. Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||On Oct 24, 9:52 pm, "Andrew Backer" <a...@.b.com> wrote:
> Enrique,
> In fact, I am using IE. When I use IE in the server, it asked
> me to login and always fails me. When I use IE in the client PC, it don't
> ask me for login and just gives me "HTTP status 400: Bad reqeust" directly.
> Can you please tell me what user login being used in client PC and what in
> server? Please help. Thanks.
> "EMartinez" <emartinez...@.gmail.com> wrote in message
> news:1193279009.940293.80780@.v23g2000prn.googlegroups.com...
> > On Oct 24, 9:06 pm, "Andrew Backer" <a...@.b.com> wrote:
> >> I have installed SQL 2005 reporting services and I configured it using
> >> Reporting Services Configuration. Now I tried to access to report manager
> >> usinghttp://servername/Reportswithlogin I used to start reporting
> >> services. It doesn't work and keep prompting me for login and password.
> >> But
> >> no use and I am sure this login is correct and password correct and it
> >> started the reportings services successfully. Can anyone please help how
> >> to
> >> solve this problem. Thanks.
> > If you are using a browser other than Internet Explorer, this is the
> > default behavior. Otherwise, you will want to make sure that you do
> > not have the either the Reports or ReportServer virtual directory set
> > to anonymous access (via: right-click My Computer >> select Manage >>
> > select Services and Applications >> Internet Information Services >>
> > Web Sites >> Default Web Site >> right-click Reports/ReportServer >>
> > select Properties >> select the Directory Security tab >> select the
> > Edit... button). also, make sure that the login you are using has
> > Browser rights/privileges in the Report Manager. Hope this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
Generally speaking, it normally uses the service acct that the
Reporting Services is running under (right-click My Computer >> Manage
>> Services and Applications >> Services >> SQL Server Reporting
Services (MSSQLSERVER) >> right-click the service >> select Properties
>> Logon tab >> look below: Logon as: This account). Also, if you have
the virtual directories security set to Anonymous (via using my
previous posting's directions), you will want to check Properties. It
will say: Anonymous access >> User Account IUSR_... Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

Report Server First Time Configuration: Provider Load Failure

I'm trying to do the above using the Reporting Services Configuration Manager and I can't even connect. I get the error Provider Load Failure.

Anyone got any pointers?

You're using Express?|||Yes|||

Moving to RS forum.

Mike

|||Can anyone help me out on this?|||

This maybe due to issues with the Reporting Services WMI Provider.

Can you make sure you have a ReportingServicesWMI.dll present and of the appropriate version wrt to the config tool?

thanx,
Prash

|||I have the same issue on SQL Server 2005 SP2 - the dll version is correct - I re-installed SQL Server and it's still broken.

WMI service is running - everything else works.|||

Well I figured out my problem, the System PATH variable was missing

C:\windows\system32\wbem

I added it and rebooted and it works properly. It looks like reportingserviceswmi.dll depends on framedyn.dll which is located in the above path.

|||Can you please provide more detail about the solution. I am also facing this problem.|||

Well, there isn't much more to say - make sure %WINDIR%\system32\WBEM is in your PATH. If it is not, the WMI provider library (which depends on FRAMEDYN.DLL) cannot be loaded. (the alternative would be to copy FRAMEDYN.DLL into the directory that has reportingserviceswmi.dll but I would not recommend it)

Some application messed up my PATH variable and the Reporting Services WMI provider would not load. The error handling could be better so we don't have to debug the process to figure it out...

|||

Remill: Thanx, I have spent over half the day looking for the problem, and now it is fixed. You would have thought that MS could have gotten rid of the PATH thing along time ago. Oh Well.

Thanx

Report Server First Time Configuration: Provider Load Failure

I'm trying to do the above using the Reporting Services Configuration Manager and I can't even connect. I get the error Provider Load Failure.

Anyone got any pointers?

You're using Express?|||Yes|||

Moving to RS forum.

Mike

|||Can anyone help me out on this?|||

This maybe due to issues with the Reporting Services WMI Provider.

Can you make sure you have a ReportingServicesWMI.dll present and of the appropriate version wrt to the config tool?

thanx,
Prash

|||I have the same issue on SQL Server 2005 SP2 - the dll version is correct - I re-installed SQL Server and it's still broken.

WMI service is running - everything else works.
|||

Well I figured out my problem, the System PATH variable was missing

C:\windows\system32\wbem

I added it and rebooted and it works properly. It looks like reportingserviceswmi.dll depends on framedyn.dll which is located in the above path.

|||Can you please provide more detail about the solution. I am also facing this problem.|||

Well, there isn't much more to say - make sure %WINDIR%\system32\WBEM is in your PATH. If it is not, the WMI provider library (which depends on FRAMEDYN.DLL) cannot be loaded. (the alternative would be to copy FRAMEDYN.DLL into the directory that has reportingserviceswmi.dll but I would not recommend it)

Some application messed up my PATH variable and the Reporting Services WMI provider would not load. The error handling could be better so we don't have to debug the process to figure it out...

|||

Remill: Thanx, I have spent over half the day looking for the problem, and now it is fixed. You would have thought that MS could have gotten rid of the PATH thing along time ago. Oh Well.

Thanx

Report Server First Time Configuration: Provider Load Failure

I'm trying to do the above using the Reporting Services Configuration Manager and I can't even connect. I get the error Provider Load Failure.

Anyone got any pointers?

You're using Express?|||Yes|||

Moving to RS forum.

Mike

|||Can anyone help me out on this?|||

This maybe due to issues with the Reporting Services WMI Provider.

Can you make sure you have a ReportingServicesWMI.dll present and of the appropriate version wrt to the config tool?

thanx,
Prash

|||I have the same issue on SQL Server 2005 SP2 - the dll version is correct - I re-installed SQL Server and it's still broken.

WMI service is running - everything else works.|||

Well I figured out my problem, the System PATH variable was missing

C:\windows\system32\wbem

I added it and rebooted and it works properly. It looks like reportingserviceswmi.dll depends on framedyn.dll which is located in the above path.

|||Can you please provide more detail about the solution. I am also facing this problem.|||

Well, there isn't much more to say - make sure %WINDIR%\system32\WBEM is in your PATH. If it is not, the WMI provider library (which depends on FRAMEDYN.DLL) cannot be loaded. (the alternative would be to copy FRAMEDYN.DLL into the directory that has reportingserviceswmi.dll but I would not recommend it)

Some application messed up my PATH variable and the Reporting Services WMI provider would not load. The error handling could be better so we don't have to debug the process to figure it out...

|||

Remill: Thanx, I have spent over half the day looking for the problem, and now it is fixed. You would have thought that MS could have gotten rid of the PATH thing along time ago. Oh Well.

Thanx

Report server does not initialize

I am using ms sql 2005 standard edition on windows Nt

Everything is working fine except the report server..

when i run the configuration tool and try to start the report server, it fails to start.. i am using sql on the local machine .

i have set p lmy database on the windows credentials..

i am using my machine name/user name as the account name for the database setup.

i have also used rsconfig utility to configure the report server but nothing happens after that..

pls help

SQL Server 2005 introduces a new inteface for configuring the report server. It is located under Programs --> Microsoft SQL Server 2005 --> Configuration Tools --> Reporting Services Configuration. YOu can reinitialize your report also from here with the graphical UI. If that doens′t solve the problem, try to get the error messages fromt he log directory and the event log to see what is going on behind the scenes.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

|||

Hi

Thanks Jens

I did manage to start my report server.But when i try to build reports in Business intelligence, i get an error saying "out of memory exception".

Everything seems to be running fine in the configuration manager..i even tried to run the service pack 1 but it doesnt work. i get an error which says " setup is not able to access sql with the login details.

I have checked the login details as well.... both RS and SQL server use windows credentials

Please help..what do i do?

|||

That sounds strange. Are you getting the errors while deploying the reports on the server or during the creation of a Reporting Services project ? Although it could be that there is a problem within your SQL Server (you might check the event logs for abnormalities) there is sure a problem with your client if the error occurs during the creation of the reports. Before finding the needle in the hay, deinstall the tools / client components and reinstall them. Afterwards apply Service Pack 1 and the post hotfixes that you will have the current built of 2153. Let see if that helps.

HTH, Jens SUessmeyer.

http://www.sqlserver2005.de

|||

i am getting the error when i click the preview button in report server for generating the reports...

i have checked the error log and everything seems to be running fine. i have done the reistallation but it still it does not help. i applied the service pack 1 but it does not run properly. it gives me the error " setup cannot access the sql server with the login deails".. i have checked the logins as well. i am using windows credentials for both sql server and report server. please help me as our entire business is developing report and sending it to our clients...

Report Server Configuration Manager 100% CPU

SQL2K8 July CTP. After installing and selecting self-configure option openned RS Configuration Manager UI and selected Instance. Report Server Status page appears ok. 10.0.1049.14 in native mode.

Clicked on "Web Service URL" and CPU pegged at 100%. WmiPrvSE.exe consuming approx 85% CPU. Running on Windows Server 2008 Beta 3 within a single VPC 2007 684MB session - hardware is recent Centrino Duo HP laptop with 2GB RAM. After 30 mins Config Manager still unresponsive.

Is this a known bug?

I had exact same problem, but later i found out that Longhorn is not supported with SQL 2008?!! So i installed on a 2003 server and everything seems to be OK. This sure looks like a bug.|||

We are still working out some bugs in LH support and expect this to be supported in the next CTP.

Report Server Configuration Manager 100% CPU

SQL2K8 July CTP. After installing and selecting self-configure option openned RS Configuration Manager UI and selected Instance. Report Server Status page appears ok. 10.0.1049.14 in native mode.

Clicked on "Web Service URL" and CPU pegged at 100%. WmiPrvSE.exe consuming approx 85% CPU. Running on Windows Server 2008 Beta 3 within a single VPC 2007 684MB session - hardware is recent Centrino Duo HP laptop with 2GB RAM. After 30 mins Config Manager still unresponsive.

Is this a known bug?

I had exact same problem, but later i found out that Longhorn is not supported with SQL 2008?!! So i installed on a 2003 server and everything seems to be OK. This sure looks like a bug.|||

We are still working out some bugs in LH support and expect this to be supported in the next CTP.

Report Server Configuration Issues!

I am attemping to configure Reporting Services on my fresh SQL Server 2005 install. I am literally setting all the defaults for the virtual dirs, identities etc. But when I get to Database Setup, I again pick the defaults, and click New.

It creates the DBs fine, but then asks me whether I want to upgrade the DB, which I find amazing seeing as this is a fresh install.

If I click No and move onto Initialization, then the app tells me there was an error switching panels, and says:

The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. The expected version is 'C.0.8.40'. To continue, update the report server database and verify access rights. (rsInvalidReportServerDatabase).

If I click Yes, it attempts to update the database (that it just created!), and bombs out with the following error:

ReportServicesConfigUI.WMIProvider.WMIProviderException: The version does not match a supported version.

at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.GenerateDatabaseUpgradeScript(String databaseName, String serverVersion, String& script)

Does anybody have any ideas on this one? It seems like a authentication issue, but surely if it created the database, it should then have given itself some rights to use it!

This has been driving me up the wall, so all help is very much appreciated :)

I get the same behaviour!? (Upgrade from SQLServer 2000 -> 2005, then installed ReportServer)

Any fixes/solutions yet?

Report Server Configuration

I'm attempting to install and configure Report Server for the first time.

In the "Configure Report Server" dialog box the first 5 tasks are successfully configured with green circles and check marks. ( Server Status, Report Server Virtual Directory, Report Manager Virtual Directory, Windows Service Identity, Web Service Identity)

Database Setup has a red circle with an X.

The following is returned in Task Status:

Verifying Database Edition. The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.

The following error is returned in the Report Server error log:

ReportingServicesService!library!e!4/5/2007-16:52:27:: i INFO: Catalog SQL Server Edition = Workgroup

ReportingServicesService!library!e!4/5/2007-16:52:27:: e ERROR: restricted SKUs: Workgroup Express Developer Evaluation - actual SKU Workgroup

ReportingServicesService!library!e!4/5/2007-16:52:27:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services., ;

Info: Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.

ReportingServicesService!library!e!4/5/2007-16:52:27:: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.

at Microsoft.ReportingServices.Diagnostics.Sku.EnsureCorrectEdition(SqlConnection sqlConn, String connectionString, Boolean checkRestrictedSkus)

We are running SQL Server 2005 Workgroup Edition

9.00.3054.00 SP2 Workgroup Edition

It sounds like the error is saying that Report Server is not compatible with SQL Server 2005 Workgroup Edition?

Any suggestions?

Thank you.

Are you trying to install the Express version on Workgroup? I don't think that's supported. Workgroup does include Reporting Services, but you should install it from the Workgroup installation.|||I'm getting the same error message, have you found a resolution.|||My problem was operator error. I had used the wrong disc when installing SQL Server 2005 on a Small Business Server. I used the SQL Server Standard Edition disc rather than the SQL Server 2005 disc that came with Small Business Server. I uninstalled SQL Server and installed it from the Small Business Server SQL Server disc and everything was fine.

Report Server Configuration

I'm attempting to install and configure Report Server for the first time.

In the "Configure Report Server" dialog box the first 5 tasks are successfully configured with green circles and check marks. ( Server Status, Report Server Virtual Directory, Report Manager Virtual Directory, Windows Service Identity, Web Service Identity)

Database Setup has a red circle with an X.

The following is returned in Task Status:

Verifying Database Edition. The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.

The following error is returned in the Report Server error log:

ReportingServicesService!library!e!4/5/2007-16:52:27:: i INFO: Catalog SQL Server Edition = Workgroup

ReportingServicesService!library!e!4/5/2007-16:52:27:: e ERROR: restricted SKUs: Workgroup Express Developer Evaluation - actual SKU Workgroup

ReportingServicesService!library!e!4/5/2007-16:52:27:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services., ;

Info: Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.

ReportingServicesService!library!e!4/5/2007-16:52:27:: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException: The feature: "Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services.

at Microsoft.ReportingServices.Diagnostics.Sku.EnsureCorrectEdition(SqlConnection sqlConn, String connectionString, Boolean checkRestrictedSkus)

We are running SQL Server 2005 Workgroup Edition

9.00.3054.00 SP2 Workgroup Edition

It sounds like the error is saying that Report Server is not compatible with SQL Server 2005 Workgroup Edition?

Any suggestions?

Thank you.

Are you trying to install the Express version on Workgroup? I don't think that's supported. Workgroup does include Reporting Services, but you should install it from the Workgroup installation.|||I'm getting the same error message, have you found a resolution.|||My problem was operator error. I had used the wrong disc when installing SQL Server 2005 on a Small Business Server. I used the SQL Server Standard Edition disc rather than the SQL Server 2005 disc that came with Small Business Server. I uninstalled SQL Server and installed it from the Small Business Server SQL Server disc and everything was fine.

Report Server (MSSQLSERVER) cannot connect to the report server database

I am running SQL Reporting Services and SQL Server 2005 on a Windows 2003 server. The configuration has been unchanged for approx. 3 weeks. Suddenly today, reports being accessed via an ASP.NET 2.0 application (on Windows 2003 Server with IIS 6) using a SOAP call to the reportserver became inaccessable. End users received the following error:

Message: An error occurred during rendering of the report. >
An error occurred during rendering of the report. >
An error occurred during rendering of the report. >
An error occurred during rendering of the report. >
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Stack Trace: at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at IFA.CAP.SQLReportingService.ReportingService.Render(String Report, String Format, String HistoryID, String DeviceInfo, ParameterValue[] Parameters, DataSourceCredentials[] Credentials, String ShowHideToggle, String& Encoding, String& MimeType, ParameterValue[]& ParametersUsed, Warning[]& Warnings, String[]& StreamIds) in C:\Applications\IFACAP\Web References\SQLReportingService\Reference.vb:line 1319
at IFA.CAP.BusinessObjects.Reports.Certificate(Int32 certificateID, Boolean isDraft, Boolean isCertified) in C:\Applications\IFACAP\BusinessObjects\IFA.CAP.BusinessObjects.Report.vb:line 551
at IFA.CAP.CertificateDetail.PrintCertificate(Object sender, EventArgs e) in C:\Applications\IFACAP\Main\CertificateDetail.aspx.vb:line 2287

Subsequently, the following error is logged on the Report Server/Database server:

Report Server (MSSQLSERVER) cannot connect to the report server database.

I was able to temporarily correct the problem by performing as iisrest on the Report Server/Database server. However, the same problem occured again a couple hours later. I am relatively new to SQL Reporting Services so any help would be appreciated.

MDJ

Well, the "Report Server (MSSQLSERVER) cannot connect to the report server database" error seems to have vanished but I am still receiving the "Message: An error occurred during rendering of the report. >
An error occurred during rendering of the report. >
An error occurred during rendering of the report. >
An error occurred during rendering of the report. >
Attempted to read or write protected memory. This is often an indication that other memory is corrupt." error. Once whatever is causing this problem occurs, all users attempting to access SSRS from our ASP.NET application (using SOAP) receive the aforementioned error.

I have tried the following:

1. increased the MaxActiveReqForOneUser element in the RSWebApplication.config

2. Set the AppPool recycling setting for the ReportServer to run only once at a specified time (thinking perhaps the pool was recycling and corrputing session information).

Things I've noticed:

So far the only resolution for this issue is to perform an iisrest on the ReportServer.

This only seems to be an issue with reports being called using SOAP. Reports being rendering in the .NET Report Viewer control appear unaffected.

Here is some sample code to illustrate how we call some of our reports from ASP.NET through the SSRS web service:

************************************************************************************************************************************

Private callback As New System.Net.Security.RemoteCertificateValidationCallback(AddressOf RemoteCertificateValidationCallback)

Private Function RemoteCertificateValidationCallback(ByVal sender As Object, _
ByVal cert As System.Security.Cryptography.X509Certificates.X509Certificate, _
ByVal chain As System.Security.Cryptography.X509Certificates.X509Chain, _
ByVal sslPolicyErrors As System.Net.Security.SslPolicyErrors) As Boolean

Return True

End Function

Sub RenderReport()
Dim rs As New SQLReportingService.ReportingService
Dim results As [Byte]() = Nothing

System.Net.ServicePointManager.ServerCertificateValidationCallback = callback

rs.Credentials = New System.Net.NetworkCredential("User", "Password", "Domain")

results = rs.Render(String.Concat("TargerFolder", "ReportName"), "PDF", Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing)

Response.Clear()
Response.Buffer = True
Response.Expires = 0
Response.ContentType = "application/pdf"
Response.AppendHeader("Content-Disposition", "attachment; filename=Report.pdf")
Response.BinaryWrite(results)
Response.End()
End Sub

**********************************************************************************************************************************************

Does anyone see a problem with the above code. It has been in production for 3 weeks now and has been working fine until yesterday. Any help would be greatly appreciated!