hmatthews 0 Posted December 19, 2014 Share Posted December 19, 2014 HI, I am having ODBC connection error when trying to install ERA version 6 on my win server 2003, 32x, domaine controller. - Unable to connect to the database ( error 0) - selected database driver is not correct. If I change to another ODBC driver: - Unable to connect to the database ( error 65535) - PLease check all connection information and check if selected ODBC driver is installed correctly. Can you please poste the solution for this, Regards, M.H Link to comment Share on other sites More sharing options...
Arakasi 549 Posted December 24, 2014 Share Posted December 24, 2014 (edited) Already thread here : https://forum.eset.com/topic/3805-remote-administrator-install-odbc-error/ Edited December 24, 2014 by Arakasi Link to comment Share on other sites More sharing options...
Chadh 45 Posted December 30, 2014 Share Posted December 30, 2014 Hello hmatthews, If you encounter this error, you will need to ensure your existing SQL instance is listening on port 1433. To enable the instance to listen on port 1433, please use the following steps: On the Start menu, point to All Programs, point to Microsoft SQL Server, point to Configuration Tools, and then click SQL Server Configuration Manager. Navigate to SQL Server Network Configuration -> Protocols for %YOUR_INSTANCE_NAME% (the default is MSSQLServer or SQLEXPRESS) Double-click the TCP/IP protocol Locate the Enabled field and change the drop-down box to Yes Select the IP Addresses tab Navigate to the IPAll section In the IPAll section, delete any information in the field "TCP Dynamic Ports" In the IPAll section, change the field for TCP Port to 1433 Click OK Select the SQL Server Services entry in the list on the left In the pane on the right, right-click SQL Server (%YOUR_INSTANCE_NAME%) and select Restart Thank you,ChadH Link to comment Share on other sites More sharing options...
latinkreationz 0 Posted January 22, 2015 Share Posted January 22, 2015 Hello hmatthews, If you encounter this error, you will need to ensure your existing SQL instance is listening on port 1433. To enable the instance to listen on port 1433, please use the following steps: On the Start menu, point to All Programs, point to Microsoft SQL Server, point to Configuration Tools, and then click SQL Server Configuration Manager. Navigate to SQL Server Network Configuration -> Protocols for %YOUR_INSTANCE_NAME% (the default is MSSQLServer or SQLEXPRESS) Double-click the TCP/IP protocol Locate the Enabled field and change the drop-down box to Yes Select the IP Addresses tab Navigate to the IPAll section In the IPAll section, delete any information in the field "TCP Dynamic Ports" In the IPAll section, change the field for TCP Port to 1433 Click OK Select the SQL Server Services entry in the list on the left In the pane on the right, right-click SQL Server (%YOUR_INSTANCE_NAME%) and select Restart Thank you, ChadH I've tried this solution but did not work for me. Is there something else I can try? I'm running Server 2012 R2. Link to comment Share on other sites More sharing options...
Blackspear 0 Posted March 4, 2015 Share Posted March 4, 2015 Where is this on a 2003 SBS Server? Link to comment Share on other sites More sharing options...
Blackspear 0 Posted March 4, 2015 Share Posted March 4, 2015 I have MS Windows Server 2003 for SBS, Service Pack 2, fully up to date. It uses a Domain Controller I have installed SQLServer2005_SSMSEE.msi I can’t locate where to open Port 1433 Assistance would be appreciated please. Link to comment Share on other sites More sharing options...
jimwillsher 64 Posted March 4, 2015 Share Posted March 4, 2015 1433 is the default port for sql. However I don't think sql2005 is supported for ERA I think it's 2008 or later Link to comment Share on other sites More sharing options...
Blackspear 0 Posted March 5, 2015 Share Posted March 5, 2015 (edited) Thanks Jim, so given that I am stopped at the next screen with the attached error, what driver or software do I need to have installed to complete the installation? It seemed to be missing SQL, so I installed SQL2005, and still receive the same error. The solution to others was to change/open port 1433, so I was thinking that I was in the same boat... Cheers Edited March 5, 2015 by Blackspear Link to comment Share on other sites More sharing options...
jimwillsher 64 Posted March 5, 2015 Share Posted March 5, 2015 Again, you can't use SQL 2005, it must be 2008 or later. I think you can install SQL 2008 R2 Express onto your SBS box. You won't need to open 1433 as everythign will be on the same box (I assume?), but if you're installing 2008R2 as a separate SQL instance then you'll need to specify that in the connection properties. Link to comment Share on other sites More sharing options...
Former ESET Employees Timos 8 Posted March 6, 2015 Former ESET Employees Share Posted March 6, 2015 jimwilsher is right, supported vesions of SQL Server are 2008 and newer Link to comment Share on other sites More sharing options...
Blackspear 0 Posted March 10, 2015 Share Posted March 10, 2015 Your own Knowlegebase now shows that you can use SQL 2005hxxp://kb.eset.com/esetkb/index?page=content&id=SOLN3671&actp=RSS Link to comment Share on other sites More sharing options...
ESET Staff CB530 70 Posted March 10, 2015 ESET Staff Share Posted March 10, 2015 Blackspear, Thank you for pointing this out. The screenshot in that article is incorrect and will be updated. Link to comment Share on other sites More sharing options...
Recommended Posts