No reason

  • Every attempt I've made to link two servers has failed, and I cannot think of any plausible reason. The production server is SS 2005 Ent Ed 64 bit SP2 and I am trying to link it to a SQL Express that is (successfully) functioning as the mirror witness server.

    Whether I try creating a linked server via Enterprise Manager, or via sp_addlinkedserver, the connection test always fails. The error message is "Connection timed out; Check to see that Remote Access is enabled".

    To rub salt in the wound, I have another almost identical Sql Server (2005 SP2, 64bit) that does have a successful link to the SQLExpress server. And the SQLExpress server has a successful link back to the production server.

    I've used Configuration Manager to make sure that both servers had the network protocols enabled, and I've repeatedly enabled Remote Access in Surface Area Mgr and re-started the SQL service.

    Any expert opinions on how to diagnose the cause of this?

  • Have you given any alias name for the Servers???

  • [font="Verdana"]Try creating an alias in the source server to point destination server with correct port and then try creating the linked server.[/font]

  • vidhya sagar (7/20/2008)


    [font="Verdana"]Try creating an alias in the source server to point destination server with correct port and then try creating the linked server.[/font]

    what is an alias server??

  • [font="Verdana"]Check out the below KB article to create an alias for the destination server.

    http://msdn.microsoft.com/en-us/library/ms190445.aspx[/font]

  • vidhya sagar (7/21/2008)


    [font="Verdana"]Check out the below KB article to create an alias for the destination server.

    http://msdn.microsoft.com/en-us/library/ms190445.aspx[/font]

    thanks a lot, I had a look and seems interesting..

    btw..do you have any idea of how to find the login properties of a particular login, ie do you have a script that could be executed against a particular login and that script would give the properties of that login??

    thanks in advance!

  • Creating an alias seems like it would add another dimension to the problem. I would like to simply create a linked server for use in T-SQL commands within SQL Server. I am not trying to reach a linked server using a 3rd party application, so it doesn't seem that an alias would really address the connection problem here.

    That said, the issue seems to a failure of connection during the set up of a linked server. But this makes no sense because I was able to easily created a link between a similar SQL Server and the instance of SQL Express. What could be different?

    Thanks,

    Elliott

  • If you hit problems between 64 bit and 32 bit, run instcat.sql from a query window.

    If you have further problems, check the security on MSDTC:

    1. Go into admin tools

    2. Open component services

    3. Double click on component services from there - this will take a minute to populate

    4. Double click on computers

    5. Right click on my computer.

    6. Select properties

    7. Click on the MSDTC tab at the top

    8. Click on security configuration at the bottom

    9. Check

    A. Network DTC access

    B. Allow remote clients

    C. Allow inbound

    D. Allow outbound

    E. Enable transaction internet protocol (TIP) transactions

    10. Click on OK. You will want to restart the protocol

    11. save and exit

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply