This content has been marked as final. Show 6 replies
It is TCP port 1433 you have configured in SQL config manager then?
on the sql server, run the util called svrnetcn , choose the \eposerver instance from the drop down list, and check that tcpip is listed as available on the right hand side, and look at the properties of it. it will list its TCP port.
Did you check that the SQL server is accepting remote connections?
Also make sure that it is allowed through the firewall, it may be basic but the windows firewall has forgotten exceptions on me in the past.
Yes, confirmed on SQL that instance is listening on tcp port 1433, and accepting remote connections. no network firewall rules blocking yet as this is new network setup.
I was able to create an odbc (system DSN) successfully on epo server to EPODB.XYZ.COM\EPOSERVER using the same credential I keyed in for epo installation. thus confirmed not windows firewall blocking
could it be a bug on epo 4.0 installation or incompatibility with remote SQL2005 enterprise edition? I have logged a support call this morning.
Is there MDAC 2.8 installed on the remote SQL ?
I managed to find out what's wrong, with the help of the log files generated.
I had keyed in the FQDN of the DB server "EPODB.XYZ.COM\EPOSERVER" since that was how it was registered in DNS, & I was able to connect to the DB via odbc.
but the installer somehow discovered only "EPODB" without the domain postfix, hence the discrepancy with what I keyed in, and it returned this port mismatch error.
The installer went thru after I changed to "EPODB\EPOSERVER"
Thanks for all your help!