Thursday, January 30, 2014

Blank page for SQL 2008 Reporting Services management site

Finally figured this out.  The Windows 2008 R2 image we use had the described setting enabled by default.  Had to disable in order for the Reporting services management page to work/display.
 

*** Report Manager fails after you enable FIPS compliant algorithms in Local Security Policy

After you enable the Local Security Policy "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing", you are not able to use Report Manager. When you open Report Manager, your browser will be empty or show an "HTTP 500 Internal Server Error". A SQL Server 2008 R2 or later version of the report server will add an error message similar to the following in the report server service log file:

ui!ReportManager_0-1!1708!02/27/2010-08:02:03:: e ERROR: System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

To work around this issue: At this time, there is no known work around. Report Manager does not support the Local Security Policy "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing". If you want to use Report Manager you need to disable the setting and restart the report server service.

This issue applies to: SQL Server 2008 Reporting Services and SQL Server 2008 R2 Reporting Services.

Reference:

Monday, June 24, 2013

Adding Mgt Network to IE Local Intranet Zone

  1. Open GPEDIT.MSC as administrator
  2. Go to Computer Configuration/Administrative Templates/Windows components/Internet Explorer/Internet Control Panel/Security Page.
  3. Enable Site to Zone Assignment List
  4. Add IP segment, ie. 192.168.0.* with value = 1 (for local intranet, 2=trusted sites).
  5. Close all browser session, then test.

Thursday, June 20, 2013

Troubleshooting SQL server RESOURCE_SEMAPHORE Wait Type

Application users were complaining that web applications were slow.  Turned out there were some bad queries that were requesting up to 1GB of SQL RAM to execute.  It's no wonder SQL was suspending queries waiting for memory...

Reference:
http://www.mssqltips.com/sqlservertip/2827/troubleshooting-sql-server-resourcesemaphore-waittype-memory-issues/
http://blogs.msdn.com/b/sqlqueryprocessing/archive/2010/02/16/understanding-sql-server-memory-grant.aspx

Friday, June 14, 2013

WSUS client options

Reference below includes definitions of the regkeys that can be set for different options on the a WSUS client server.

Reference:
http://technet.microsoft.com/en-us/library/cc708449(v=ws.10).aspx

Thursday, May 23, 2013