Unable to fetch result from linked server

  • Narine M - Thursday, March 16, 2017 11:09 AM

    Yes, i looked in to the post, whether the uninstallation and reinstallation of DTC services can be done by dba or should be done by it- admin

    Depends on your work environment.  Where I work, the DBA handles all of the stuff related to SQL.  This includes the installation and configuration of DTC.

    Did you check your event logs for anything useful?  The link I posted said that after they verified that DTC looked correct, they checked the event log and found:
    The local MS DTC detected that the MS DTC on ServerName has the same unique identity as the local MS DTC.

    And possibly a dumb question, but the username for connecting to SAO is likely different than other servers (or at least I would HOPE you don't reuse the same username and password for all of your cloud servers... that sounds scary).  Are you sure the username and password pair are configured correctly?

    If you are certain that is all good and that the problem is NOT on your end, then I agree with Lynn: contacting AWS for support will be the next step.

    Is there a reason you cannot provide the SQL?  Does it help if you put your query into an explicitly defined distributed transaction?

    Are all of the SQL servers the same version and have similar configuration setups?

    And, although I don't expect this to help, does making a new linked server connection to SAO work?  If so, you could drop the existing one and make a new connection?  I expect that to fail though in the same way things are now, but just a thought.

    The above is all just my opinion on what you should do. 
    As with all advice you find on a random internet forum - you shouldn't blindly follow it.  Always test on a test server to see if there is negative side effects before making changes to live!
    I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.

  • The SAO server in different domain , whether it may cause any issue.?????

  • Narine M - Thursday, March 16, 2017 3:23 PM

    The SAO server in different domain , whether it may cause any issue.?????

    Depends on how your authentication is set up.  If you are using SQL Authentication, you should have no issues.  If you are using windows authentication, I imagine so.  Or at least, it does add some complexity and that is beyond my knowledge on how to configure for sure.

    But if all of the other servers are on the same domain EXCEPT SAO and you can't get that link working, I'd be willing to bet the different domain is what is making this more complicated and fail. 

    EDITED because I hit submit too soon.  Fingers are slower than my brain.

    The above is all just my opinion on what you should do. 
    As with all advice you find on a random internet forum - you shouldn't blindly follow it.  Always test on a test server to see if there is negative side effects before making changes to live!
    I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.

Viewing 3 posts - 16 through 17 (of 17 total)

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