none
Error when i try to start mirroring RRS feed

Answers

  • Hi

    To resolve the issue, please take the following steps.
    1 By default, Microsoft Windows XP Service Pack 2 and Windows Vista block all ports. 
    2  check the following
  • Make sure that that name and port of the mirror server instance are correct.
  • Make sure that the destination mirror server instance is not behind a firewall.
  • Make sure that the principal server instance is not behind a firewall.
  • Verify that the endpoints are started on the partners by using the state or state_desc column the of the sys.database_mirroring_endpoints catalog view. If either endpoint is not started, execute an ALTER ENDPOINT statement to start it.
  • Make sure that the principal server instance is listening on the port assigned to its database mirroring endpoint and that and the mirror server instance is listening on its port. For more information, see "Verifying Port Availability," later in this topic. If a partner is not listening on its assigned port, modify the database mirroring endpoint to listen on a different port.

    3 Verifying Port Availability

    When you are configuring the network for a database mirroring session, make sure the database mirroring endpoint of each server instance is used by only the database mirroring process. If another process is listening on the port assigned to a database mirroring endpoint, the database mirroring processes of the other server instances cannot connect to the endpoint.

    To display all the ports on which a Windows-based server is listening, use the netstat command-prompt utility. The syntax for netstat depends on the version of the Windows operating system. For more information, see the operating system documentation.

    Windows Server 2003 Service Pack 1 (SP1)
    To list listening ports and the processes that have those ports opened, enter the following command at the Windows command prompt: netstat -abn

    Besides, there is an article to share with you:http://msdn.microsoft.com/en-us/library/aa337361(SQL.90).aspx

    Regards

Thursday, September 3, 2009 6:26 AM

All replies

  • Are both your sql services runnning under the same account ? Aslo what do you mean by TEST in your explanation??

    In BOL there is a section that deals explicitly with setup errors for database mirroring.Search for "troubleshooting database mirroring."


    Thanks, Leks
    Wednesday, September 2, 2009 11:40 PM
    Answerer
  • Hi

    To resolve the issue, please take the following steps.
    1 By default, Microsoft Windows XP Service Pack 2 and Windows Vista block all ports. 
    2  check the following
  • Make sure that that name and port of the mirror server instance are correct.
  • Make sure that the destination mirror server instance is not behind a firewall.
  • Make sure that the principal server instance is not behind a firewall.
  • Verify that the endpoints are started on the partners by using the state or state_desc column the of the sys.database_mirroring_endpoints catalog view. If either endpoint is not started, execute an ALTER ENDPOINT statement to start it.
  • Make sure that the principal server instance is listening on the port assigned to its database mirroring endpoint and that and the mirror server instance is listening on its port. For more information, see "Verifying Port Availability," later in this topic. If a partner is not listening on its assigned port, modify the database mirroring endpoint to listen on a different port.
  • 3 Verifying Port Availability

    When you are configuring the network for a database mirroring session, make sure the database mirroring endpoint of each server instance is used by only the database mirroring process. If another process is listening on the port assigned to a database mirroring endpoint, the database mirroring processes of the other server instances cannot connect to the endpoint.

    To display all the ports on which a Windows-based server is listening, use the netstat command-prompt utility. The syntax for netstat depends on the version of the Windows operating system. For more information, see the operating system documentation.

    Windows Server 2003 Service Pack 1 (SP1)
    To list listening ports and the processes that have those ports opened, enter the following command at the Windows command prompt: netstat -abn

    Besides, there is an article to share with you:http://msdn.microsoft.com/en-us/library/aa337361(SQL.90).aspx

    Regards

Thursday, September 3, 2009 6:22 AM
  • Hi

    To resolve the issue, please take the following steps.
    1 By default, Microsoft Windows XP Service Pack 2 and Windows Vista block all ports. 
    2  check the following
  • Make sure that that name and port of the mirror server instance are correct.
  • Make sure that the destination mirror server instance is not behind a firewall.
  • Make sure that the principal server instance is not behind a firewall.
  • Verify that the endpoints are started on the partners by using the state or state_desc column the of the sys.database_mirroring_endpoints catalog view. If either endpoint is not started, execute an ALTER ENDPOINT statement to start it.
  • Make sure that the principal server instance is listening on the port assigned to its database mirroring endpoint and that and the mirror server instance is listening on its port. For more information, see "Verifying Port Availability," later in this topic. If a partner is not listening on its assigned port, modify the database mirroring endpoint to listen on a different port.

    3 Verifying Port Availability

    When you are configuring the network for a database mirroring session, make sure the database mirroring endpoint of each server instance is used by only the database mirroring process. If another process is listening on the port assigned to a database mirroring endpoint, the database mirroring processes of the other server instances cannot connect to the endpoint.

    To display all the ports on which a Windows-based server is listening, use the netstat command-prompt utility. The syntax for netstat depends on the version of the Windows operating system. For more information, see the operating system documentation.

    Windows Server 2003 Service Pack 1 (SP1)
    To list listening ports and the processes that have those ports opened, enter the following command at the Windows command prompt: netstat -abn

    Besides, there is an article to share with you:http://msdn.microsoft.com/en-us/library/aa337361(SQL.90).aspx

    Regards

  • Thursday, September 3, 2009 6:26 AM

  • Now I got it, Thanks for your instruction!
    Saturday, February 26, 2011 10:31 PM