Why might SQL Server 2008 OLE DB UDL require port 1433 explicitly specified? -


in production environment, found port 1433 must explicitly specified "microsft ole db provider sql server" udl. this:

provider=sqloledb.1;user id=user;data source=ip,1433 

without port specified, error is:

 test connection failed because of error in initializing provider.  [dbnetlib][connectionopen (invalid instance()).]invalid connection. 

same environment, sql native client 10.1, not require 1433 explicitly specified:

provider=sqlncli10.1;integrated security="";persist security info=false; user id=user;data source=ip;... 

same test against development sql server, ole db udl not require default port specified.

under circumstances might necessary explicitly specify default port?

the production system clustered, primary active , secondary passive, , cluster server connections made. development environment single sql server 2008. don't know of other differences. if think plays it, why might matter?

client sql server (where udl created): windows server 2008 r2 standard mdac 2.8

all sql database servers: microsoft sql server 2008 (sp1) - 10.0.2734.0 (x64) windows server enterprise service pack 2

thanks in advance help.

this known problem unique clustering. reason cluster manager answer on 1 ip/port , hand-off communications actual(physical) server, may communicate on different port. looks there might not fix, have found workaround.
more info, check out microsoft technet article: http://support.microsoft.com/kb/318432


Comments

Popular posts from this blog

Unable to remove the www from url on https using .htaccess -