A network-related or instance-specific error occurred

Home Forums Software Support Call Flow Manager A network-related or instance-specific error occurred

This topic contains 2 replies, has 2 voices, and was last updated by  Site Admin 1 year, 6 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #2034

    Site Admin
    Keymaster

    ”A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified)”

    The above error message may be a result of the following:

      – You haven’t installed the Local Configuration Store – this is step 1 of the Lync/SfB deployment wizard. Querying Response Group information requires this component to be installed
      – A Front End server is not reachable
    • This topic was modified 2 years, 12 months ago by  Site Admin.
    • This topic was modified 2 years, 12 months ago by  Site Admin.
    #3117

    rob.guth
    Participant

    Would it be possible for you to enhance this error message with the server that is being tried? We get a number of these but then our RGS config loads. It would be immensely helpful if this error message (or even a log message before this error) that showed what was trying to be connected. There are no event logs that give us more information on the server either.

    FYI – The SfB RGS application gets the same error but just lists it once.

    #3121

    Site Admin
    Keymaster

    Hi Rob,

    The error message we return is the same that is presented when you run the commands from PowerShell (our app is essentially constructing and passing PowerShell commands to SfB). It sounds like one of the pools cannot be contacted for some reason – permissions, network access, or similar. We are not specifically connecting to any server, this is left up to the PowerShell commandlets. The Response Group commandlets seem to try all servers, and this can also hold up loading- do you find this?

    I will see if we can do anything further to enhance this experience. We have some related performance work already slated.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.