<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SAS Interface/ACCESS to MS SQL Server in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Interface-ACCESS-to-MS-SQL-Server/m-p/172901#M2203</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've always had to set ODBCHOME as well.&lt;/P&gt;&lt;P&gt;&lt;A href="http://support.sas.com/documentation/installcenter/en/ikfdtnunxcg/66380/PDF/default/config.pdf" title="http://support.sas.com/documentation/installcenter/en/ikfdtnunxcg/66380/PDF/default/config.pdf"&gt;http://support.sas.com/documentation/installcenter/en/ikfdtnunxcg/66380/PDF/default/config.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And to verify SAS always pick it up (for all users), set it - and all the other required variables in !SASROOT/bin/sasenv_local&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 06 Oct 2014 14:23:43 GMT</pubDate>
    <dc:creator>dpage</dc:creator>
    <dc:date>2014-10-06T14:23:43Z</dc:date>
    <item>
      <title>SAS Interface/ACCESS to MS SQL Server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Interface-ACCESS-to-MS-SQL-Server/m-p/172898#M2200</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have installed the unixODBC 2.3.0 and MS SQL Server ODBC Driver msodbcsql-11.0.2270.0. Then I have installed SAS Interface/ACCESS to MS SQL Server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; ODBC.INI:&lt;/P&gt;&lt;P&gt;[mfbs_db]&lt;/P&gt;&lt;P&gt;Description = SQL Server Database&lt;/P&gt;&lt;P&gt;Driver = ODBC Driver 11 for SQL Server&lt;/P&gt;&lt;P&gt;Servername = MFBSSQLP01/XRM&lt;/P&gt;&lt;P&gt;Port = 59714&lt;/P&gt;&lt;P&gt;Trace = Yes&lt;/P&gt;&lt;P&gt;Database = MFBS_MSCRM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ODBCINST.INI:&lt;/P&gt;&lt;P&gt;[ODBC Driver 11 for SQL Server]&lt;/P&gt;&lt;P&gt;Description = Microsoft ODBC Driver 11 for SQL Server&lt;/P&gt;&lt;P&gt;Driver = /opt/odbc_mssql/msodbcsql-11.0.2270.0/lib64/libmsodbcsql-11.0.so.2270.0&lt;/P&gt;&lt;P&gt;Threading = 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;$LD_LIBRARY_PATH:&lt;/P&gt;&lt;P&gt;/opt/odbc_unix:/opt/odbc_unix/lib:/opt/odbc_unix/lib64:/opt/odbc_mssql/msodbcsql-11.0.2270.0/lib:/opt/odbc_mssql/msodbcsql-11.0.2270.0/lib64:/o&lt;/P&gt;&lt;P&gt;pt/sas/SASHome/Secure/sasexe:/opt/sas/SASHome/SASPrivateJavaRuntimeEnvironment/9.4/jre/lib/amd64/server:/opt/sas/SASHome/SASPrivateJavaRuntimeE&lt;/P&gt;&lt;P&gt;nvironment/9.4/jre/lib/amd64:/opt/sas/SASHome/SASFoundation/9.4/sasexe&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;P&gt;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;$ODBCINI:&lt;/P&gt;&lt;P&gt;/etc/odbc.ini&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;$ODBCSYSINI:&lt;/P&gt;&lt;P&gt;/etc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;libname-statement:&lt;/P&gt;&lt;P&gt; libname mydblib sqlsvr&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; noprompt="uid=&amp;lt;user&amp;gt;;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; pwd={SAS002}F560034D1111E5B200B1C5553A6A67744BE8CBB1;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; dsn=mfbs_db;"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; stringdates=yes;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error-Message:&lt;/P&gt;&lt;P&gt;ERROR: CLI error trying to establish connection: [unixODBC][Driver Manager]Data source name not found, and no default driver specified&lt;/P&gt;&lt;P&gt;ERROR: Error in the LIBNAME statement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone help me with this issue? What I am doing wrong in configuration?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Christoph&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Oct 2014 06:59:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Interface-ACCESS-to-MS-SQL-Server/m-p/172898#M2200</guid>
      <dc:creator>rico_ehrlich</dc:creator>
      <dc:date>2014-10-06T06:59:39Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Interface/ACCESS to MS SQL Server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Interface-ACCESS-to-MS-SQL-Server/m-p/172899#M2201</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You&amp;nbsp; have a lot of settings mentioned. What is not mentioned:&lt;/P&gt;&lt;P&gt;Are these settings active in the SAS session that is trying to connect?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As you are mentioning a Unix approach you are most likely using Eguide and a WS-server.&lt;/P&gt;&lt;P&gt;These settings should get activated using SAS configuration files. It does not help when you are doing that in your personal Unix profile settings&lt;/P&gt;&lt;P&gt;When you are using the system profiles for modifications than those can be revoked and reset by your OS system administrator.&lt;/P&gt;&lt;P&gt;You probably are following: &lt;A href="http://technet.microsoft.com/en-us/library/hh568449(v=sql.110).aspx" title="http://technet.microsoft.com/en-us/library/hh568449(v=sql.110).aspx"&gt;Installing the Driver Manager&lt;/A&gt; (&lt;A class="toc_collapsed" href="http://technet.microsoft.com/en-us/library/hh568449(v=sql.110).aspx"&gt;http://technet.microsoft.com/en-us/library/hh568449(v=sql.110).aspx&lt;/A&gt;&lt;A data-tochassubtree="true" href="http://technet.microsoft.com/en-us/library/jj991993(v=sql.110).aspx" id="jj991993_SQL.110_en-us" title="Microsoft ODBC Driver for SQL Server"&gt;Microsoft ODBC Driver for SQL Server&lt;/A&gt; as of MS)&lt;/P&gt;&lt;P&gt;The message is telling you the name mfbs_db is not found.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Troubleshooting:&lt;/P&gt;&lt;P&gt;- &lt;A class="active_link" href="http://blogs.msdn.com/b/sql_protocols/archive/2008/04/30/steps-to-troubleshoot-connectivity-issues.aspx"&gt;http://blogs.msdn.com/b/sql_protocols/archive/2008/04/30/steps-to-troubleshoot-connectivity-issues.aspx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;- unixodbc manual: &lt;A href="http://www.unixodbc.org/doc/UserManual/" title="http://www.unixodbc.org/doc/UserManual/"&gt;http://www.unixodbc.org/doc/UserManual/&lt;/A&gt; is using a graphical interface. You should be able to use a X-server terminal on your desktop.&lt;/P&gt;&lt;P&gt;&amp;nbsp; When the datamanager is working proceed to your SAS interface&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Having installed the ODBC driver you should check the functionality of that one outside of SAS.&lt;/P&gt;&lt;P&gt;Do not trust the pwencode approach. Your userid is not secret you could have left to the real one in your SAS example code.&lt;/P&gt;&lt;P&gt;See: &lt;A _jive_internal="true" href="https://communities.sas.com/thread/61088"&gt;https://communities.sas.com/thread/61088&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Having a demo/check account for just verifying the technical connections is very sensible advice. You can validate that always without worrying to do something with real possible sensitive business production information (data).&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Oct 2014 10:42:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Interface-ACCESS-to-MS-SQL-Server/m-p/172899#M2201</guid>
      <dc:creator>jakarman</dc:creator>
      <dc:date>2014-10-06T10:42:23Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Interface/ACCESS to MS SQL Server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Interface-ACCESS-to-MS-SQL-Server/m-p/172900#M2202</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also - you need to check that the port number is set on the ODBC as defined in your code.&amp;nbsp; We found that even with the port&lt;/P&gt;&lt;P&gt;number in the code, it still had to be set manually.&amp;nbsp; Also - make sure you have the appropriate authority to define the ODBC.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Oct 2014 12:37:33 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Interface-ACCESS-to-MS-SQL-Server/m-p/172900#M2202</guid>
      <dc:creator>OS2Rules</dc:creator>
      <dc:date>2014-10-06T12:37:33Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Interface/ACCESS to MS SQL Server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Interface-ACCESS-to-MS-SQL-Server/m-p/172901#M2203</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've always had to set ODBCHOME as well.&lt;/P&gt;&lt;P&gt;&lt;A href="http://support.sas.com/documentation/installcenter/en/ikfdtnunxcg/66380/PDF/default/config.pdf" title="http://support.sas.com/documentation/installcenter/en/ikfdtnunxcg/66380/PDF/default/config.pdf"&gt;http://support.sas.com/documentation/installcenter/en/ikfdtnunxcg/66380/PDF/default/config.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And to verify SAS always pick it up (for all users), set it - and all the other required variables in !SASROOT/bin/sasenv_local&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Oct 2014 14:23:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Interface-ACCESS-to-MS-SQL-Server/m-p/172901#M2203</guid>
      <dc:creator>dpage</dc:creator>
      <dc:date>2014-10-06T14:23:43Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Interface/ACCESS to MS SQL Server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Interface-ACCESS-to-MS-SQL-Server/m-p/172902#M2204</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What version of SAS?&amp;nbsp; We had to update SAS 9.4 to M2 to get the ODBC &amp;amp; SQLSVR to work together.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Oct 2014 15:01:53 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Interface-ACCESS-to-MS-SQL-Server/m-p/172902#M2204</guid>
      <dc:creator>Doc_Duke</dc:creator>
      <dc:date>2014-10-07T15:01:53Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Interface/ACCESS to MS SQL Server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Interface-ACCESS-to-MS-SQL-Server/m-p/172903#M2205</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SAS 9.4 M1&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Oct 2014 15:04:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Interface-ACCESS-to-MS-SQL-Server/m-p/172903#M2205</guid>
      <dc:creator>rico_ehrlich</dc:creator>
      <dc:date>2014-10-07T15:04:36Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Interface/ACCESS to MS SQL Server</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Interface-ACCESS-to-MS-SQL-Server/m-p/172904#M2206</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;it is working now with sql server authentification. now the last task is to get this running with kerberos and windows authentification via AD.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks for your help and support.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;christoph&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Oct 2014 14:09:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/SAS-Interface-ACCESS-to-MS-SQL-Server/m-p/172904#M2206</guid>
      <dc:creator>rico_ehrlich</dc:creator>
      <dc:date>2014-10-14T14:09:21Z</dc:date>
    </item>
  </channel>
</rss>

