Windows Server 2003 And Reporting Services Error: For Security Reasons DTD Is Prohibited In This XML Document.
Mar 29, 2007
I do a clean install of SQL Server + RS + SP1 with standard setup on Windows Server 2003. I create a simple report (select * from aTable). This report (actually any report) shows the error message "For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method."
This has to do with security settings in Windows Server 2003. On Windows XP everything works fine.
Any help would be greatly appreciated. Thanks!
Edit: The reports do work in the preview tab in BIDS.
View 5 Replies
ADVERTISEMENT
Oct 9, 2007
After viewing many reports in reportviewer, I sporadically get the following error message. Each attempt to access any report in report viewer after the error message first appears results in the same error message for a bit of time until it appears to reset itself. I have read that this may be related to running out of memory for report processing... We have 2GB of RAM. How can I prevent this from happening or force the system to free up some memory if it is exhausing the available memory?
For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method.
View 1 Replies
View Related
Apr 4, 2006
I have seen one other post about this and using IP addressing rather that DNS names - I am using DNS.
I have a large report that runs fine in report manager, but as soon as I try and export it to Excel it takes an age to run and I get the above error.
Any ideas anyone?
Oh, and I export loads of other reports to Excel with no problems on the same server.
View 18 Replies
View Related
May 1, 2007
I am getting this error while running a very large dataset. Please help..
The full description of the error is : "For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method."
I am having hard time figuring out a solution for this. I am using sql 05, SSRS 05, Report viewer
View 3 Replies
View Related
Jan 10, 2007
When we develop with the Microsoft SQL Server 2005 Reporting Service.
We got the exception on some reports.
For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on
XmlReaderSettings to false and pass the settings into XmlReader.Create method.
Ther report renders well first time, but if we click the title to sort the report, it will throw the exception.
And It occurred that we use IE6 and IE7 to view the report at same time, but if we use the same version brower, there are no exception.
Can somebody help me?
My development€™s environment :
Windows XP English Professional + SP2
Microsoft SQL Server 2005 Development version + SP 1 + SP 2
Microsoft Visual Studio 2005 Professional Version 8.0.50727.51 (QFE.050727-5100) + SP1
Microsoft .NET Framework Version 2.0.50727
View 3 Replies
View Related
Aug 10, 2007
This error comes up in the print preview and nothing prints.
We are using VS-2005, SQL 2005 and SSRS 2005.
We had the same problem yesterday , so we have reinstalled IIS, .Net Framework 2.0 and Reporting Services, then reconfigured RS security, uploaded all the reports and enabled remote errors. After doing everything this error was gone and we were operating pretty fine.
Suddenly just we started getting the same annoying message."ROOT ELEMENT MISSING" from Report Server and from Report Manager we have "
For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method. "
Please Help. I need to fix this ASAP.
View 8 Replies
View Related
Jan 8, 2007
I have aspx page which uses Reportviewer object to execute/display reporting services report on the page based on the parameters passed by the aspx page.
It works fine. I have a problem when I try to use import option on that page. It throws the following error. Can anybody help me to resolve this issue?
Advanct thanks for your help and support
Thanks,
Sundar
Here is the error message when I export the report to any format (Excel, pdf, csv or text)
For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Xml.XmlException: For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method.
Here is the code:
ASPX Code:
<rsweb:ReportViewer ID="ReportViewer1" runat="server" Font-Names="Verdana" Font-Size="8pt" Height="100%" ProcessingMode="Remote" Width="100%" ShowFindControls="false" ShowPageNavigationControls="true" ShowPromptAreaButton="false" AsyncRendering="false" EnableViewState="true" ShowParameterPrompts="false" Visible="false">
<ServerReport ReportServerUrl="http://miscsql1/ReportServer" ReportPath="/webreports/POS Commission Report"></ServerReport>
</rsweb:ReportViewer>
ASPX.VB Code
Dim RptParameters(2) As Microsoft.Reporting.WebForms.ReportParameter
RptParameters(0) = New Microsoft.Reporting.WebForms.ReportParameter("Repcode", objCommon.RepSite.ToString, False)
RptParameters(1) = New Microsoft.Reporting.WebForms.ReportParameter("StartDate", txtStartDate.Text.ToString)
RptParameters(2) = New Microsoft.Reporting.WebForms.ReportParameter("EndDate", txtEndDate.Text.ToString)
ReportViewer1.ServerReport.SetParameters(RptParameters)
ReportViewer1.ServerReport.Refresh()
ReportViewer1.Visible = True
objCommon = Nothing
View 5 Replies
View Related
Dec 13, 2007
SQL Server Reporting Services 2005 Service would not Start on windows server 2003. Working great till yesterday and no changes were made to config file.
Here is the error in Event log
Event Type: Error
Event Source: SQL Server Report Service
Event Category: None
Event ID: 0
Date: 12/13/2007
Time: 8:25:59 AM
User: N/A
Computer: XXXXXXXXXXX
Description:
Service cannot be started. Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information.
at Microsoft.ReportingServices.Library.ServiceAppDomainController.Start(Boolean firstTime)
at Microsoft.ReportingServices.NTService.ReportService.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Here is i found in log files
ReportingServicesService!resourceutilities!4!12/13/2007-08:25:59:: i INFO: Running on 0 physical processors, 1 logical processors
ReportingServicesService!servicecontroller!4!12/13/2007-08:25:59:: e ERROR: Exception caught loading and setting code permissions policy level: System.Security.XmlSyntaxException: Invalid syntax on line 158.
at System.Security.Util.Parser.GetRequiredSizes(TokenizerStream stream, Int32& index)
at System.Security.Util.Parser.ParseContents()
at System.Security.Util.Parser..ctor(Tokenizer t)
at System.Security.SecurityManager.LoadPolicyLevelFromStringHelper(String str, String path, PolicyLevelType type)
at System.Security.SecurityManager.LoadPolicyLevelFromString(String str, PolicyLevelType type)
at Microsoft.ReportingServices.Library.ServiceController.SetAppDomainPolicy()
ReportingServicesService!servicecontroller!4!12/13/2007-08:25:59:: e ERROR: Error Starting Service: System.Security.XmlSyntaxException: Invalid syntax on line 158.
at System.Security.Util.Parser.GetRequiredSizes(TokenizerStream stream, Int32& index)
at System.Security.Util.Parser.ParseContents()
at System.Security.Util.Parser..ctor(Tokenizer t)
at System.Security.SecurityManager.LoadPolicyLevelFromStringHelper(String str, String path, PolicyLevelType type)
at System.Security.SecurityManager.LoadPolicyLevelFromString(String str, PolicyLevelType type)
at Microsoft.ReportingServices.Library.ServiceController.SetAppDomainPolicy()
at Microsoft.ReportingServices.Library.ServiceController.StartService(Boolean firstStart)
View 1 Replies
View Related
Jul 24, 2007
I have installed windows server 2003 on one of our test boxes (prior to live) and found that reporting services is now unavailable.
When I browse to the report server I get
Service Unavailable
The event log reports several times
"A process serving application pool 'reportserver' terminated unexpectedly. The process id was '3500'. The process exit code was '0xffffffff'.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
before the worker process is disabled:
"Application pool 'reportserver' is being automatically disabled due to a series of failures in the process(es) serving that application pool.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."
Has anyone seen similar behavior?
Stuart
"
View 1 Replies
View Related
May 14, 2008
Hi all,
i am tring to install and configure reporting services in Windows 2003 SP2- 64 bit machine as part of installing SCE 2007, and i followed the procedure for confiurng all the options in reportingservices config tool,
all the options show green flag and still could not proceed further as the following error is coming
"The Selected Sql server reportin service instance is not configured , please configure to continue" which halts the further process,
I have installed SQL Server 2005 edition and installed Sql server 2005 SP2 also,
any inputs on this issue , i would welcome them,
View 2 Replies
View Related
Oct 26, 2007
CLIENT SIDE:
If the query is reading from large table, (100 columns x 20000 rows)
I have no problem getting results using SQL Query Analyzer on the Client side.
However, I am getting timeout problem from the client side application.
The query failed. The message from the database engine was:
Microsoft OLE DB Provider for SQL Server: Timeout expired.
SERVER SIDE:
I tested the same query on the server using the application. I can get the results.
ENVIRONMENT:
Server machine:
The Server : Windows 2003 Server SP2
Database Server : SQL Server 2000 €“ (8.00.2039 Standard Edition SP 2)
linkserver (OLE DB 9.0.0.3504 ) to FoxPro 9.0 SP1 table
SQL Server Timeout Settings: Query time-out (sec, 0=unlimited)
Client machine:
Windows XP SP2 : Windows Network Authentication
SQL Server 2000 client
For some reason my environment doesn€™t like the outside application to connect to the server long time?
Do you have any idea how to fix this timeout problem? Do I need to configure DCOM or DTC?
View 1 Replies
View Related
May 12, 2008
I know from searching this forum that there have been many variations of the issue I'm currently suffering, but I haven't found anything quite like mine or a solution to solve it. The issue I'm running into is that I am unable to log on to Reporting Services using Management Studio or the web interface when Windows Integrated Security is enabled. I have full functionality using basic security, but the risks involved make it impossible to deploy basic authentication out into production. The error I'm receiving in Management Studio is The request failed with HTTP status 401: Unauthorized. (Microsoft.SqlServer.Management.UI.RSClient). I recieve the same error when I try the web interface.
I've looked the most recent logfile in WindowsSystem32LogFilesW3SVC1 and these entries match up to the time I attempted my authentication.
Code Snippet
2008-05-12 20:30:42 <Edited: Server IP> GET /reports - 80 - <Edited: Server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 2 2148074254
2008-05-12 20:30:42 <Edited: Server IP> GET /reports - 80 DomainUserName <Edited: Server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 301 0 0
2008-05-12 20:30:42 <Edited: Server IP> GET /reports/ - 80 - <Edited: Server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 2 2148074254
2008-05-12 20:30:46 <Edited: Server IP> GET /reports/home.aspx - 80 DomainUserName <Edited: Server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 302 0 0
2008-05-12 20:30:46 <Edited: Server IP> GET /reports/Pages/Folder.aspx - 80 - <Edited: Server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 2 2148074254
2008-05-12 20:30:47 127.0.0.1 POST /ReportServer/ReportService2005.asmx - 80 - 127.0.0.1 - 401 2 2148074254
2008-05-12 20:30:47 127.0.0.1 POST /ReportServer/ReportService2005.asmx - 80 - 127.0.0.1 - 401 1 0
2008-05-12 20:30:47 127.0.0.1 POST /ReportServer/ReportService2005.asmx - 80 - 127.0.0.1 - 401 1 2148074248
2008-05-12 20:30:49 127.0.0.1 POST /ReportServer/ReportService2005.asmx - 80 - 127.0.0.1 - 401 2 2148074254
2008-05-12 20:30:49 127.0.0.1 POST /ReportServer/ReportService2005.asmx - 80 - 127.0.0.1 - 401 1 0
2008-05-12 20:30:49 127.0.0.1 POST /ReportServer/ReportService2005.asmx - 80 - 127.0.0.1 - 401 1 2148074248
2008-05-12 20:30:50 <Edited: Server IP> GET /reports/Pages/Folder.aspx - 80 DomainUserName <Edited: Server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 500 0 0
2008-05-12 20:30:50 <Edited: Server IP> GET /Reports/js/ReportingServices.js - 80 - <Edited: Server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 2 2148074254
2008-05-12 20:30:50 <Edited: Server IP> GET /Reports/js/ReportingServices.js - 80 DomainUserName <Edited: Server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 200 0 0
2008-05-12 20:30:54 <Edited: Server IP> GET /Reports/styles/ReportingServices.css - 80 - <Edited: Server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 2 2148074254
2008-05-12 20:30:54 <Edited: Server IP> GET /Reports/images/blank.gif - 80 - <Edited: Server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 2 2148074254
2008-05-12 20:30:54 <Edited: Server IP> GET /Reports/images/blank.gif - 80 DomainUserName <Edited: Server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 200 0 0
2008-05-12 20:30:54 <Edited: Server IP> GET /Reports/images/48error.jpg - 80 - <Edited: Server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 2 2148074254
2008-05-12 20:30:54 <Edited: Server IP> GET /Reports/styles/ReportingServices.css - 80 DomainUserName <Edited: Server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 200 0 0
2008-05-12 20:30:54 <Edited: Server IP> GET /Reports/images/48error.jpg - 80 DomainUserName <Edited: Server IP> Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 200 0 0
2008-05-12 20:31:07 127.0.0.1 GET /reports/ - 80 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 2 2148074254
2008-05-12 20:31:07 127.0.0.1 GET /reports/ - 80 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 1 0
2008-05-12 20:31:13 127.0.0.1 GET /reports/ - 80 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 2 2148074254
2008-05-12 20:31:13 127.0.0.1 GET /reports/ - 80 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727) 401 1 0
I tried to highlight one of each of the HTTP errors I am getting. 401.2 and 401.1 are the ones I kind of expected, but have no idea why I'm getting them. The 500 0 error is a bit troubling, because unless I'm mistaken thats a server side error.
Here's my current setup. As far as I can tell, I've done everything to set up correctly for Windows Integerated security.
My Specs
The server machine running all SQL 2005 services. It resides in a domain. All Clients are in the same domain.
Intel Dual Processor 3.20 gig Xenon
Windows Server 2003 w/ SP2
Microsoft Sql Server 2005 w/ SP2
Reporting Services Setup
The virtual directories Reports and ReportServer are set to Windows Integrated Security with Anonymous Access disabled. All other checkboxes in Directory Security are unchecked. For permissions in Reports, I have:
Administrators (servernameAdministrators) - Full Control
ASP.NET Machine Account - Modify, Read & Execute, List Folder Contents, Read, Write
Authenticated Users - Modify, Read & Execute, List Folder Contents, Read, Write
Creator Owner - No permissions
Domain Users - Read & Execute, List Folder Contents, Read
SQLServer2005ReportingServices]WebServiceUsers$... - Read & Execute, List Folder Contents, Read
SQLServer2005ReportServerUsers$... - Read & Execute, List Folder Contents, Read
SYSTEM - Full Control
Users (CompNameUsers) - Read & Execute, List Folder Contents, Read
In ReportServer I have the same permissions except Authenticated Users is absent.
At one point, I even added the account Everybody and gave it full control, and I still recieved a HTTP 401 error. Any help at what I might be missing would be a godsend.
Thanks.
View 1 Replies
View Related
Feb 22, 2011
I am trying to fetch the sharepoint list data into the SSRS report.
I have given credentials in shared datasource to access remote datasource.
In preview i m getting the following error:
Data extension supports windows integrated security and no credentials only.
View 3 Replies
View Related
Jul 27, 2005
Hi,I tried to Develop one Report in SQL Reporting Service. I haveinstalled SQL Reporting Serivice in Windows 2003 machine. SQL ServerDatabase is in another machine, running on Windows 2000. I developedand deployed the report and all went fine.When I tried to see the report through the Report Service Manager WebPage it is comming properly. But When I tried to See the report inanother web page, I'm not able to see the images. But the Data isgetting Displayed and only Image is not comming. When I exported thereport to Excel, the Image is comming over there.I am using Report Viewer control (Which came as Sample Program) inthe ASPX Page to render the report. I'm using SQL Server 2000 with SP3aand SQL Server 2000 reporting Service with SP1.I tried setting the Mime Time for the GIF image and even "*.*" inthe Mime Type settings of IIS 6.0. Even then its not displaying theimage.Can any one help me out in solving the problem?Thanks in Advance.With RegdsKrish
View 1 Replies
View Related
Jul 14, 2007
Hello - We have been unable to successfully install Integration Services with an instance of SQL 2005 running on a Windows Small Business Server 2003. Installation proceeds with no errors, but when you attempt to connect to the Integrations Services and browse to where it apparently exists, the SQL Server Managment Studio returns the following error:
TITLE: Connect to Server
------------------------------
Cannot connect to ABDI04.
------------------------------
ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
Connect to SSIS Service on machine "ABDI04" failed:
The specified service does not exist as an installed service.
.
------------------------------
Connect to SSIS Service on machine "ABDI04" failed:
The specified service does not exist as an installed service.
.
------------------------------
BUTTONS:
OK
------------------------------
We have tried uninstalling the Integration Services, then reinstalling it and again applying SP2 with the same results.
Thank you.
View 17 Replies
View Related
May 12, 2004
I am running SQL Server 2000 (clustered server) with Windows 2003. For some reason MSDTC is failing on distributed transactions. I can run code that begins and commits a transaction from query analyzer, or run a stored procedure from Query Analyzer with the same code in it and both work great, but if I call the stored procedure from a DTS job, then the job fails with the following error:
DTSStep_DTSExecuteSQLTask_1, Error = -2147217900 (80040E14) Error string: The operation could not be performed because the OLE DB provider 'MSDASQL' was unable to begin a distributed transaction. Error source: ...... Error string: OLE DB error trace [OLE/DB Provider 'MSDASQL' ITransactionJoin::JoinTransaction returned 0x8004d00a]. Error source: Microsoft OLE DB Provider for SQL Serve. The step failed.
Any help would be appreciated!
View 1 Replies
View Related
Feb 29, 2008
I get and error when installing MS SQL 2005 on Windows 2003 server with SP2. It bombs at the very end of the install and Microsoft notification program generated he message below to be sent to Microsoft. Please help. At a stand still.
-------------------------------------------------------------------------------------------------------------------
EventType : sql90setup P1 : unknown P2 : 0x645 P3 : unknown
P4 : 0x645 P5 : unknown P6 : unknown P7 : sqlserver2005_bc.msi@
Below is the summary.txt
-------------------------------------
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Time : Thu Feb 28 22:52:28 2008
Machine : ESAPPS
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_2.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_2.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_2.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_2.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_3.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_3.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_3.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_BOL_1.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_3.log
--------------------------------------------------------------------------------
Machine : ESAPPS
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLXML4_1.log
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Thu Feb 28 23:01:11 2008
List of log files:
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_Core(Local).log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_BackwardsCompat_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SqlWriter_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_BOL_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_3.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLXML4_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_Datastore.xml
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework 2.0.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_Core.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework 2.0 LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework Upgrade Advisor.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework Upgrade Advisor LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework Windows Installer.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_.NET Framework Windows Installer LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_Support.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SCC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_WI.log
View 2 Replies
View Related
Jun 17, 2005
I have a windows 2003 server with the latest service pack and patches. This server also acts a domain controller.
View 4 Replies
View Related
Mar 28, 2006
I currently have a Vs.Net 2003 Pocket PC application that uses sql server ce 2.0 to push and pull data from Sql Server 2000 to the Pocket PC. The sscesa20.dll isapi agent is installed on a Windows 2000 server and points to another server that hosts the SQL database. In this configuration everything works like a charm. I am in the process of upgrading my application server to Windows 2003 Server but the RDA PULL process does not work, giving an Native Error of 28035 EVERY time. I use the exact same code in the app but when I point to the isapi agent on the 2003 box it does not work. When I connect to the the sscesa20.dll via the Pocket IE it returns the "Sql Server CE Server Agent" message. When I do an RDA.Submit it works and the SQL table is updated as expected.
I have configured IIS 6 with the proper web extensions
I have turned off the firewall and antivirus on the server.
I have reinstalled the server agent several times.
I set up the sscesa20.dll manually.
I removed all file level security.
I opened up the virtual directory.
I verified the ddl versions match.
I'm dead in the water right now. I'm not sure what else to try.
Any help would be greatly appreciated.
View 5 Replies
View Related
Dec 3, 2007
I am attempting to install SQL Server 2005 on a Laptop with Windows 2003 Standard Edition.
The installation fails and the File Summary.txt has the following entries:
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Time : Fri Nov 30 09:36:53 2007
Machine : SAPDEMO
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLSupport_2.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLNCLI_2.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_BOL_1.log
--------------------------------------------------------------------------------
Machine : SAPDEMO
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLXML4_1.log
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Fri Nov 30 09:38:41 2007
List of log files:
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_Core(Local).log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLSupport_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLNCLI_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SqlWriter_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_MSXML6_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLSupport_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLNCLI_2.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_BOL_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SQLXML4_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_Datastore.xml
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework 2.0.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_Core.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework 2.0 LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework Upgrade Advisor.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework Upgrade Advisor LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework Windows Installer.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_.NET Framework Windows Installer LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SNAC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_Support.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0006_SAPDEMO_SCC.log
The Log File, SQLSetup0004_<hostname>_Core.log, has the following entries:
Microsoft SQL Server 2005 Setup beginning at Mon Dec 03 08:54:09 2007
Process ID : 2980
C:SAP_CDCD2x86EnterpriseEditionServerssetup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2007/11/3 8:54:9
Complete: LoadResourcesAction at: 2007/11/3 8:54:9, returned true
Running: ParseBootstrapOptionsAction at: 2007/11/3 8:54:9
Loaded DLL:C:SAP_CDCD2x86EnterpriseEditionServersxmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2007/11/3 8:54:9, returned true
Running: ValidateWinNTAction at: 2007/11/3 8:54:9
Complete: ValidateWinNTAction at: 2007/11/3 8:54:9, returned true
Running: ValidateMinOSAction at: 2007/11/3 8:54:9
Complete: ValidateMinOSAction at: 2007/11/3 8:54:9, returned true
Running: PerformSCCAction at: 2007/11/3 8:54:9
Complete: PerformSCCAction at: 2007/11/3 8:54:9, returned true
Running: ActivateLoggingAction at: 2007/11/3 8:54:9
Complete: ActivateLoggingAction at: 2007/11/3 8:54:9, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__2980" returned false.
Running: PerformSCCAction2 at: 2007/11/3 8:54:9
Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.4042
Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.4042
Complete: PerformSCCAction2 at: 2007/11/3 8:54:9, returned true
Running: PerformDotNetCheck at: 2007/11/3 8:54:9
Complete: PerformDotNetCheck at: 2007/11/3 8:54:9, returned true
Running: ComponentUpdateAction at: 2007/11/3 8:54:9
Complete: ComponentUpdateAction at: 2007/11/3 8:55:6, returned true
Running: DetectLocalBootstrapAction at: 2007/11/3 8:55:6
Complete: DetectLocalBootstrapAction at: 2007/11/3 8:55:6, returned true
Running: LaunchLocalBootstrapAction at: 2007/11/3 8:55:6
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 1605
Aborting queue processing as nested installer has completed
Message pump returning: 1605
Regards
View 1 Replies
View Related
May 23, 2007
hello folks
i have recently started to work with the analysis services and i am having some problems.
i have made a web application that for now just tries to connect to an analysis server.
The server is installed on an xp sp 2 system.
for testing, i used my local computer, which is running also win xp sp2. After deploying, the application can connect to the AS server on the other machine. the problem occurs when i try to deploy the applicatuion on the production server, which is running win 2k3 server on 32 bit. When deploying, i use the same connection string, so it should try to connect to the AS server installed on a win xp sp2 system.
The first thing that came to my mind was to check the MDAC versions, be cause of the message: "Provider cannot be found. It may not be properly installed."
on my computer, where the application worked ok, the version is MDAC 2.8 SP 1 Windows XP SP 2
on the win2k3 server, the MDAC version is : MDAC 2.8 SP2.... i thought it was the version of the service pack, so o searched for the update of MDAC 2.8 SP1, trying to install mdac 2.8 sp2 to see if i was to see the same error, but i found that mdac 2.8 sp2 is only for win2k3 server, and for win xp is mdac 2.8 sp1, according to this link: http://support.microsoft.com/default.aspx/kb/884103
Now i got confused and have no clues how to make this work...
Can anybody give any hint?
View 2 Replies
View Related
Apr 3, 2005
When I try to install SQL Server I get the follwing message when I click on the installation file :
A strong SA password is required for security
reasons.
Please use SAPWD
switch to supply the same. Refer to readme
for more details.
Setup will now exit.
I've checked the readme but can't really find any info on how to fix this.
I don't know what password this SA password is nor how to change it.
Can anyone help me out?
View 6 Replies
View Related
Jul 12, 2007
We just replaced an older Windows 2000 sp4 server with a new Window 2003 Standard Edition sp2 server to run our batch processing. We noticed that when the SQL command times out we now get the following error in the ADO command object error collection.
[DBNETLIB][ConnectionWrite (send()).] General network error. Check you network documentation.
Native Error: 11
SQL State: HY018
msado15.dll version 2.82.3959 is on this server.
On other servers running Windows 2003 Enterprise Edition sp1 the error on the ADO command object is normal with.
Timeout expired
Native Error: 0
SQL State: HYT00
msado15.dll version 2.82.1830 is on this server.
The SQL server they are talking to is on the other side of a firewall. It is SQL 2005 sp2 running on Windows 2000 sp4.
I have also tested this on a Windows 2003 sp2 server that doesn't have to cross a firewall and get the correct Timeout error. It also has the same version of msado15.dll as problem server.
The application is a collection of VB6 Components that are running in COM+ applications. I have isolated the test application to our one SQL interface component and have build a test vbs that can reproduce this on demand. The VB6 Components were not modified in any way for this change and have been working fine for many years prior to this.
All other aspects of our batch processing works as expected. Transactions are working fine. As long as the SQL doesn't timeout everything is normal. DTCPing was used to ensure both servers have correct ports open to allow DTC traffic. Checked the SynAttackProtect setting on SQL and this is not an issue since other clients have no problems.
One point I would like to add is that this new server was initially setup with a temporary server name and then was changed to use the name of the original server on move day. Don't know if this has any impact or not.
View 31 Replies
View Related
Feb 20, 2008
Hi,
How programing add new <CodeGroup> element to SQL Server Reporting Services policy configuration file "rssrvpolicy.config"(location path:"C:Program FilesMicrosoft SQL ServerMSSQLReporting ServicesReportServer")???
Ahead Thanks!
View 5 Replies
View Related
Nov 24, 2015
In a new ssrs 2008 report that uses sql server 2012, I am suppose to create a report that prints on both sides of the same paper. The first side of the report will display custom data with a mailing address for the customer.
The second side (back side of the paper) will contain generic information. The second side of the paper will contain areas for the users within my large company to fill out and return to the user via inter-office mail.
Thus my question is can this happen in an SSRS 2008 report to print in a PDF and/or Word document on both sides of the paper? If this is possible would you tell me if the paper needs to be exported to PDF, Word, or if this can on both format(s)? If so, any reference how to accomplish this goal?
If this is not possible in SSRS 2008, is printing on both sides of the paper possible in ssrs 2008 r2 or ssrs 2012?
What version of ssrs report would work, and if the print (export) needs to be a PDF, Word, or either format?Â
View 5 Replies
View Related
Jun 13, 2006
Hello out there!
I've tried to install all features in the SQL Server 2005 to run on Windows Vista. The Reporting Services failed to install. I think it is because of the IIS 7.0 that 's not recognised by SQL Server.
Is there anyone who have had the same problem and is there anyone who have a suggestion to solve this problem?
View 5 Replies
View Related
Feb 4, 2008
Quick question; is SQL Reporting Services 2005 fully compatible with Windows Server 2008 / IIS 7 that RTM'd today?
View 1 Replies
View Related
Mar 19, 2007
Hi,
I successfully got SQL 2005 Express with reporting services running under VISTA. Developed some reports in the VISTA environment. However, my target system is a Windows 2000 server. We installed SQL 2005 w/reporting services onto the Windows 2000 server. SQL2005 Database is up and running. Reporting Services are running, IIS RRS virtual directories are built, RRS databases are built. I can do everything except deploy reports from Business Intelligent Studio. I can preview reports, just cannot deploy. The Reporting Services indicate 1 failure in its configuration; the Web Service Identity. It is loaded with <server>ASPNET. I cannot get rid of this error. I assume this is the problem. After digging around I found that Windows 2000 does not have an ASPNET user, it uses the IWAM user instead. Reporting services did not run at all till I changed the rs config file and put the IWAM user in as <WebServiceAccount>.
Does anyone have Reporting services 2005 running on Windows 2000 server? Anyone know how to fix the Web Service Identity error I am getting?
Thanks
View 8 Replies
View Related
Feb 28, 2006
Hi,
I've just installed SQL Server Express 2005 on our shiny new Windows Server 2003 R x64 server. It has an Intel 830 D chip that uses x86 and 64EMT.
Problem is that I get the message "64-bit ASP.Net is Registered. Required 32-bit ASP.Net to install Microsoft Reporting Services 2005(32-bit)."
Is there any way that I can remedy this?
Thanks in advance
Robert
View 6 Replies
View Related
Nov 17, 2015
I have a request from the customer to export a report to Word as a read-only document. I am restricted to out-of-the-box SSRS 2008, so I cannot write any custom export functionality.
The customer has the ability to export as PDF, and I suggested that, but before I tell them there's no easy solution, I wanted to get input from other Reporting Services folks.
View 3 Replies
View Related
Mar 12, 2008
Does anyone know how to properly install SQL server 2005 express reporting services on windows server 2008. When ever i try to access the report manager I get an error "Cannot access the remote server" even though the report server is on the local machine. I only have the web server role installed on the server. Im still quite a newbie at managing servers so please keep it as simple as possible.
Thanks
Matthew
View 2 Replies
View Related
Apr 21, 2008
Hi,
I have a Windows 2008 server 64-bit SP1 and I have installed SQL 2005 SP2 Enterprise Edition 64-bit. My current version is 9.00.3042.00. I am trying to configure Reporting Services and I am having lots of trouble getting the Application Pools to work properly. I have followed the Microsoft Technet paper 839480 "How to Install and Configure Reporting Services on Windows Server 2008". In the "Configure Reporting Services" part, I have successfully configured everything (all arrows are green) and have the following setup:
Report Server Virtual dir: ReportServer Default Web Site
Report Manager Virtual dir: Reports Defualt Web Site
Windows Service Identity: ReportServer with a service acct login
Web Service Identity:
Report Server: ReportServer,
Report Manager: DefaultAppPool (I get an error when I try to configure it to anything else: ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 800708AC at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetWebServiceIdentity(String applicationPool)
The one thing I notice in the SQL Server configuration manager is that there is a red dot next to the SQL Reporting Services services even though the green arrow is there to show it is running.
When I look in IIS7, I see the application pools Reports and ReportServer and they are both in Integrated mode. When I try to go to http://localhost/reportserver, it gives an error. It will work if I change both application pools to classic. But then when I try to go to http://localhost/reports, I get an error:
"REQUEST IS NOT AVAILABLE IN THIS CONTEXT".
I have read up on IIS7 and it says that:
"This error is due to a design change in the IIS7 Integrated pipeline that makes the request context unavailable in Application_Start event. When using the Classic mode (the only mode when running on previous versions of IIS), the request context used to be available, even though the Application_Start event has always been intended as a global and request-agnostic event in the application lifetime."
So, how do I configure these application pools to work using IIS7 with SQL 2005 Reporting Services on a Windows 2008 server? I have tried all kinds of different things based on what I am reading on the net and nothing is working. Anybody have any suggestions?
Thanks!
Isabelle
View 3 Replies
View Related
