April 6, 2009 at 4:56 pm
Environment:
Windows 2003
Development environmet
SQL Installations;
The following have been installed and uninstalled multiple times
SQL 2000
SQL 2005
SQL 2008
Current environment:
SQL2005 Enterprise with SP 3
Reports
Error Message:
The page cannot be displayed
There is a problem with the page you are trying to reach and it cannot be displayed.
--------------------------------------------------------------------------------
Please try the following:
Open the localhost home page, and then look for links to the information you want.
Click the Refresh button, or try again later.
Click Search to look for information on the Internet.
You can also see a list of related sites.
HTTP 500 - Internal server error
Internet Explorer
Report Server
http://localhost/reportsserver$
No Error message
localhost/ReportServer$ - /
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Microsoft SQL Server Reporting Services Version 9.00.3077.00
Accounts:
SQLServer2005ReportingServicesWebServiceUser$
NT\AUTHORITY
ASPNET
FOLDER SECURITY
SQLServer2005ReportingServicesWebServiceUser$
Full
April 7, 2009 at 7:55 am
If you used the default install you should not need the "$" at the end of the URL. Try http://localhost/reports
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
April 11, 2009 at 12:21 pm
I was able to resolve my Reporting service error message:
Brief Review:
Url: http://localhost
IIS web site up and running
Url: http://localhost/ReportingServer
Report Server up and running
Server not found - 500
I reviewed Reporting Services Logs:
Locatin: :\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\LogFiles
Opened the current reporting services log:
Noticed the following entry:
w3wp!ui!1!4/11/2009-11:04:22:: e ERROR: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
w3wp!ui!1!4/11/2009-11:04:22:: e ERROR: HTTP status code --> 500
-------Details--------
System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at System.Security.Cryptography.RijndaelManaged..ctor()
at System.Web.Configuration.MachineKeySection.ConfigureEncryptionObject()
at System.Web.Configuration.MachineKeySection.EnsureConfig()
at System.Web.Configuration.MachineKeySection.EncryptOrDecryptData(Boolean fEncrypt, Byte[] buf, Byte[] modifier, Int32 start, Int32 length, IVType ivType, Boolean useValidationSymAlgo)
at System.Web.UI.Page.EncryptStringWithIV(String s, IVType ivType)
at System.Web.Handlers.AssemblyResourceLoader.FormatWebResourceUrl(String assemblyName, String resourceName, Int64 assemblyDate, Boolean htmlEncoded)
at System.Web.Handlers.AssemblyResourceLoader.GetWebResourceUrlInternal(Assembly assembly, String resourceName, Boolean htmlEncoded)
at System.Web.Handlers.AssemblyResourceLoader.GetWebResourceUrl(Type type, String resourceName, Boolean htmlEncoded)
at System.Web.UI.ClientScriptManager.GetWebResourceUrl(Page owner, Type type, String resourceName, Boolean htmlEncoded)
at System.Web.UI.ClientScriptManager.RegisterClientScriptResource(Type type, String resourceName)
at System.Web.UI.WebControls.BaseValidator.RegisterValidatorCommonScript()
at System.Web.UI.WebControls.BaseValidator.OnPreRender(EventArgs e)
at System.Web.UI.Control.PreRenderRecursiveInternal()
In response to this I disabled the FLIPS Compliance:
Start | Administrative Tools | Local Security Policy | Local Policies | Security Options | System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing
I re-started my server and verified reporting server.
Everything is fine. At some point I will have to re-enable FIPS Compliance.
Any thoughts would be appreciated.
MJS
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply