General Consultant Discussion

 View Only

  • 1.  Good grief. I created a SQL backend with a linked

    Posted 09-08-2015 09:33
    Good grief. I created a SQL backend with a linked server to Sage 100. Works great from SQL server manager and the Access Frontend while on the SQL server itself but not from the users desktop or my rdp connection and I'm the db owner. I'm using Windows authentication. The frustrating part is it did work until last week. Is there something environmental that might have changed to cause this?


  • 2.  RE: Good grief. I created a SQL backend with a linked

    Posted 09-08-2015 10:15
    Which part is failing? Are you receiving an error or just #VALUE records?


  • 3.  RE: Good grief. I created a SQL backend with a linked

    Posted 09-08-2015 10:58
    Someone turn on the Windows Firewall blocking port 1433?


  • 4.  RE: Good grief. I created a SQL backend with a linked

    Posted 09-08-2015 11:32
    @SteveIwanowski the message is Cannot initialize the data source object of OLE DB provider ""MSDASQL"" for linked server ""Sage100"". OLE DB provider ""MSDASQL"" for linked server ""Sage100"" returned message ""[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed"".


  • 5.  RE: Good grief. I created a SQL backend with a linked

    Posted 09-08-2015 11:33
    @ScottHickman there's no telling what the IT guys have done. Thanks for arming me with an intelligent question. I'll ask!


  • 6.  RE: Good grief. I created a SQL backend with a linked

    Posted 09-08-2015 12:44
    I think @ScottHickman nailed it, however you also said that you were using Windows Authentication. Are you using the same Windows login on the SQL Server, the user's desktop and RDS for testing?


  • 7.  RE: Good grief. I created a SQL backend with a linked

    Posted 09-08-2015 13:48
    Yes. These are domain logins and I am a domain user. Works from the Access Frontend on the SQL server but not on the rdp connection. Same user in both places.


Related Content