OpsMgr / Microsoft SQL 2005 Reporting Services Issue

Hi Folks,

I found a small bug in Microsoft SQL 2005 Reporting Services where you aren't able to create a report database.

During the "Database Setup" slide of wizard "Reporting Service Configuration Manager" tool you may see on of the these error:

1. First error.

System.Data.SqlClient.SqlException: Could not locate entry in sysdatabases for database '<xxxxxx>'. No entry found with that name. Make sure that the name is entered correctly.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.ReportingServices.Common.DBUtils.ApplyScript(String connectionString, String script)

 2. Second error.

 'Verify Database Version' and 'Setting Connection Info For Reporting Server' are warnings while 'Create grants rights script' task is failing


After during some troubleshooting I discovered that the issue occured everything I used a specific syntax for the report database name.

I've reported the issue to Microsoft and gotten the following reply:


From your description, I understand that you are wondering why we can’t create a reporting database with the specific xxxReportServer name. If I am off the base, please feel free to let me know.


I performed a test in my side and found that we also can’t assign the database to xxxReportServe  without SCOM environment. So, we confirmed it’s a known issue for reporting service. I will report this problem to our product team and hope that they can do some change in the future .  As a workaround, we can use ReportXXXServer as the database name to bypass this bug.  


Let’s have an internal look. In my testing, I use sc3ReportServer for its report database name and generate all the scripts of creating database. I found the below records four copies.


USE sc3[sc3ReportServerTempDB]


These records/statements will make creating database operation failed and block our SCOM installation. To fix this problem, we can do some scripts modify(replace USE sc3[sc3ReportServerTempDB] with  USE [sc3ReportServerTempDB]) and run the generated scripts to create the database manually. After creating, we can point the reporting service configuration database to the new created database and then continue SCOM installation.


Hope it helps you get around the issue.



Blog Upgrade from BlogEngine 1.5 > 1.6


In the last couple of months my blog have gotten a huge amount of comments spam. Yesterday I made a few adjustments and upgrades to get rid of all the comments spam.

I decided to upgrade to Blogengine 1.6.1 due to the new comments moderation features and support for the ReCaptcha.

Blog changes:

- Upgrade from BlogEngine 1.5 > 1.6.1
- Better performance with migration from XML > Microsoft SQL
- Enhanced blog spam security with ReCaptcha (http://www.captcha.net/)



VBS : Create Windows File Share Report

Hi Everyone,

During a large file migration for a customer I found it necessary to compile a list of all security settings for Windows file shares. The customer used share permission in combination with file (NTFS) permissions. I know... GREAT combinationJ. It makes the migration task a bit tricky.

For this reason I deployed a script that can dump all current shares including the shares permissions to report.

Using this report you can modify the file permissions using icacls or just manually.


Running the script


  1. Download the script to the computer where you need to extract the report.

  2. Execute the script by double clicking the icon.
  3. Within the same folder as the script a new text file with the name “ShareLogFile.txt” will be create.
  4. Wait for 2-3 minutes for the report to me finalized. Then you can open the report.


    You should get a file that looks something like this ShareLogFile.txt (3.58 kb)


    The scripts are provided AS IS without warranty of any kind.


    Download Script:  DumpShareWithPermissions.vbs (3.49 kb)


List of tools/management packs for OpsMgr


  1. LocalPortMonitor.zip – A vbs script (as a .txt file) for use in a SCOM unit monitor to locally check the status of a listening TCP port.  Described here.
  2. WSHCheck.zip – A vbs script (as a .txt file) for use in a SCOM unit monitor to check the WSH version on 32-bit Windows agents.  Described here.
  3. PutNodeInPatchMaint.zip - A powershell script to put nodes (and clusters, if applicable) in maintenance mode.  Described here.
  4. DocumentMPs.zip – A powershell script to document unsealed management packs by outputting MP entities to a formatted html file.  Described here.
  5. ListUsers2.zip – A powershell script to recursively list the members of a specified group to the defined recursion depth.  Initially descriped here.  Updates described here.
  6. WebMon.zip – A SCOM 2007 R2 management pack for monitoring of multiple websites controlled by a configuration file.   Described here.
  7. EventLogSearch.zip – A simple Windows Forms application for searching events in a local or remote eventlog, including search by description.  Described here.
  8. CiscoSNMP_R2_v1.0.2.7.zip - Version 1.0.2 of the Cisco Managment Pack for OpsMgr 2007 R2.  Described here and here.  (This has been replaced by the xSNMP Management Packs).
  9. Net-SNMP_v1.01.zip – Version 1.0.1 of the Net-SNMP UNIX/Linx Management Packs.  Described here.
  10. CiscoSNMP_SP1_v1.0.2.7.zip - Version 1.0.2 of the Cisco Managment Pack for OpsMgr 2007 SP1.  Described here.
  11. WSSBackup.zip – A VBS script for automating WSS 3.0 backups and an OpsMgr 2007 Management Pack to schedule and monitor the script.  Described here.
  12. xSNMP Management Pack Suite - Version 1.1.0 (Beta) of the xSNMP Management Pack Suite, introduced here, and updates described here.
  13. UNIX.Custom MP - Example SCOM 2007 R2 management pack for monitoring Defunct/Zombie processes on UNIX/Linux systems.  Described here

Source: http://operatingquadrant.com/downloads/


Microsoft Forefront Unified Access Gateway 2010 Released

Microsoft UAG 2010 has just been released.

It's the first true Microsoft release of the IAG server. Fully rewritten under Microsoft best practices for Secure Code writing.

Take a look: