locked
problems activating Monitor Server RRS feed

  • Question

  • I am unable to activate the monitor server because it can't find the SQL server instance.  I preloaded a full version of SQL 2005 but when I enter the servername\instance field with the servername only, it is unable to find the default instance.   I need guidance as I am not a SQL person.  How does one find the SQL instance? Please help.  Thanks.
    Monday, August 10, 2009 10:35 PM

Answers

All replies

  • If you open the SQL management Studio you can find out the Instance name.
    Jithendranath Reddy
    Tuesday, August 11, 2009 10:00 AM
  • If you installed a named instance in SQL then the proper format would be "ServerName\InstanceName" but if you installed a default instance of SQL then try using the path of "ServerName\MSSQLSERVER".  MSSQLSERVER is the default SQL instance name.
    Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
    Tuesday, August 11, 2009 1:15 PM
    Moderator
  • when i open management studio and I browse for instance it doesn't find the just installed version of SQL Svr 2005.  That is one of the issues.
    Tuesday, August 11, 2009 9:56 PM
  • I also found that a pre-requisite for Monitoring server is to have SQL DMO installed.  It states to load this from SQL disk but I can't find this.  How do we load this?  Just reiterating that I am not a SQL person at all and this is very helpful.  THanks.
    Tuesday, August 11, 2009 9:59 PM
  • I don't recall getting prompted to set the instance name.  Is there some configuration after the install had completed?
    Tuesday, August 11, 2009 10:05 PM
  • Hi

    Per your description, when you activated the monitor server, you coundnt find the SQL instance.

    Here are some suggestions for you to make a troubleshooting.

    1.     Before you deploy the monitor server, you must install the SQL firstly, and ensure that you have either SQL Server 2008 (32-bit or 64-bit) or SQL Server 2005 with Service Pack 2 (32-bit or 64-bit). So make sure what version of the SQL you have installed. You can refer to below link:

    http://technet.microsoft.com/en-us/library/dd425286(office.13).aspx

    2.     Ensure you have installed the SQL successfully and configure everything properly. About how to install SQL server 2005 you can refer to below link:

    http://technet.microsoft.com/en-us/library/ms942986.aspx

    Ensure you have installed the SP2 for SQL 2005 server; you can refer to below link:

    http://technet.microsoft.com/en-us/library/aa545440.aspx  

    You can download the SP2 refer to below link:

    http://www.microsoft.com/downloads/details.aspx?FamilyId=d07219b2-1e23-49c8-8f0c-63fa18f26d3a&DisplayLang=en

    3.     The Monitoring Server Report Pack can generate detailed reports using Monitoring Server. This is an optional feature. To view these reports, you must install SQL Server Reporting Services. You can refer to below link:

    http://technet.microsoft.com/en-us/library/dd425337(office.13).aspx  

    4.     Do you have use the same computer that runs Monitoring Server, or a dedicated database server? If Monitoring Server and the Monitoring Server database will be located on separate computers, SQL-DMO for SQL Server 2005 must be installed on the Monitoring Server computer. If it is not already installed, the OCS deployment tool will install it when you deploy Monitoring Server. You can refer to below link:

    http://technet.microsoft.com/en-us/library/dd425102(office.13).aspx

    5.     About how to deploy the monitoring server detail procedures you can refer to below link:

    http://technet.microsoft.com/en-us/library/dd441379(office.13).aspx

     

    Hope this helpful!

    Regards!

    • Marked as answer by trothstein Wednesday, August 26, 2009 2:49 PM
    Monday, August 17, 2009 5:50 AM
    Moderator
  • Hello,

    did you install SQL Server on a Windows Server 2008?
    If so, you need to open port 1433 (default SQL Server port) on Windows Firewall settings, as SQL2005 does not automatically open the required ports on Windows Server 2008.

    Try "telnet servername 1433"
    If your request times out then SQL Server is not listening on the default port.
    If this is not a firewall issue, maybe SQL Server Browser is not running or needs to be setup.

    Hope this helps.

    Regards,
    George

    Monday, August 17, 2009 8:28 AM