Loading ...
Sorry, an error occurred while loading the content.

Unable to login to SQL after domain change and uninstall/re-install

Expand Messages
  • rosab99
    Ok. For those of you who were at the SQL Users group meeting last night....Apparently the issue was the Browser service. It had somehow retained the password
    Message 1 of 1 , Jan 16, 2008
    • 0 Attachment
      Ok. For those of you who were at the SQL Users group meeting last
      night....Apparently the issue was the Browser service. It had somehow
      retained the password from the first domain and was not starting.
      Once the correct id and pw were entered the server started with no
      problem. I did not know that you could not log into a named instance
      without the browser service running. It would have worked if I were
      using a default instance and default port.

      Here is some additional info if you are interested.

      Using SQL Server Browser
      If the SQL Server Browser service is not running, you are still able
      to connect to SQL Server if you provide the correct port number or
      named pipe. For instance, you can connect to the default instance of
      SQL Server with TCP/IP if it is running on port 1433.

      However, if the SQL Server Browser service is not running, the
      following connections do not work:

      Any component that tries to connect to a named instance without fully
      specifying all the parameters (such as the TCP/IP port or named pipe).

      Any component that generates or passes server\instance information
      that could later be used by other components to reconnect.

      Connecting to a named instance without providing the port number or
      pipe.

      DAC to a named instance or the default instance if not using TCP/IP
      port 1434.

      - Rosa :)
    Your message has been successfully submitted and would be delivered to recipients shortly.