How to Install SQL 2005 Reporting on Windows Server 2008

  • Comments 4
  • Likes
A new paper has been posted on the OpsManJam site on the pre-requisites for SQL 2005 Reporting on Windows Server 2008.

How to Install SQL 2005 Reporting on Windows Server 2008

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • PingBack from

  • I have installed Win2008 (x64) with SQL 2005 Ent SP2 (x64) and use this for SCOM Databases.

    The RMS server and Management Servers running Win2003 Server.

    I will use one Managament server for SCOM Reporting and have installed IIS and SQL Reporting Services SP2.

    I have run Reporting Services Configurator Manager and all steps are green. Report Site (http://servername/Reports) is OK.

    But when I tried to install SCOM Reporting the installastion stop after it try to connect the RMS server. I got the folliwing message:

    "Could not verify if the current user is in Sysadmin role. The user running setup is not in sysadmin role in the OM database or we are unable to connect to OM database, please verify if you can connect to OM database from this computer"

    The user account that I use are local administrator on both the SQL server and the OM Reporting server. The account are "owner" to alle OM databases and are Sysadmin to.

    Does anyone have some suggestion what I should do?

  • hi

    Unfortunately, I got several problems of the same kind with 64bits on windows 2008. Even though i gave accounts domain admin, local admin, sysadmin rights on Scom and Sql servers, i get 'account verification failed'. I think this is due to some problem with 64 bits as i don't have any problem on 32 bits platform (i think this is not due to the account but to the check made by the application, as whatever you put there will fail anyway). I checked several times that everything has been configured properly but it won't install. As it works on 32 bits i think a call might be addressed to 32bits subsystem instead of 64bits and fails for this reason. Unfortunately the verbose logs and process monitor do not bring any info about the failure.

  • The first thing you’ll probably want to do in preparation for your callback is gather up any relevant