locked
error in wsus installation of other site locaton RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Dear All,

    below error getting when installing secondary wsus server at remote location.

    please help out me.

    Regards

    jitendra singh

    9871615296


    Rajesh Khabar

    Thursday, July 3, 2014 9:36 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    this might be due to a firewall blocking the SQL tcp port (default 1433) if you are using a remote db, or the local instance not running/available if you are using a local or remote database.

    Also check if teh account used to access the database has teh resuired permissions.

    MCP/MCSA/MCTS/MCITP

    • Marked as answer by Daniel JiSun Tuesday, July 8, 2014 6:53 AM
    Thursday, July 3, 2014 12:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    this might be due to a firewall blocking the SQL tcp port (default 1433)

    The connection attempt is to a Named Instance, so it won't be occurring over port 1433.

    Also check if teh account used to access the database has teh resuired permissions.

    This is definitely relevant. Also, since the connection IS to a named instance, ensure that the SQL Browser service is running and that port 1434 is accessible. This, of course, assumes there actually is a database instance installed at wherever it is (the image is so small I cannot read the text).

    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Daniel JiSun Tuesday, July 8, 2014 6:53 AM
    Thursday, July 3, 2014 8:06 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    this might be due to a firewall blocking the SQL tcp port (default 1433) if you are using a remote db, or the local instance not running/available if you are using a local or remote database.

    Also check if teh account used to access the database has teh resuired permissions.

    MCP/MCSA/MCTS/MCITP

    • Marked as answer by Daniel JiSun Tuesday, July 8, 2014 6:53 AM
    Thursday, July 3, 2014 12:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    this might be due to a firewall blocking the SQL tcp port (default 1433)

    The connection attempt is to a Named Instance, so it won't be occurring over port 1433.

    Also check if teh account used to access the database has teh resuired permissions.

    This is definitely relevant. Also, since the connection IS to a named instance, ensure that the SQL Browser service is running and that port 1434 is accessible. This, of course, assumes there actually is a database instance installed at wherever it is (the image is so small I cannot read the text).

    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    • Marked as answer by Daniel JiSun Tuesday, July 8, 2014 6:53 AM
    Thursday, July 3, 2014 8:06 PM