I have a thread on StackExchange I need help with.
It seems that SQL Server 2012 requires the default port 1433 be specified when connecting to it a requirment that does not exist in earlier versions. I think this is causing connection issues with the SharePoint powershell cmdlets.
For instance, when connecting to SLQ 2012, the function CheckSQLAccess had to be altered by adding ',1433' to connection string like so:
$objSQLConnection.ConnectionString = "Server=$sqlServer,1433;....
This issue is causing the New-SPContentDatabase to fail during SP2010 farm setup.
See the link below for the error messages I am seeing.
http://stackoverflow.com/questions/18558952/sql-server-2012-remote-connection-setup
Any help that could find a work-around would be greatly appreciated.
Thanks
It seems that SQL Server 2012 requires the default port 1433 be specified when connecting to it a requirment that does not exist in earlier versions. I think this is causing connection issues with the SharePoint powershell cmdlets.
For instance, when connecting to SLQ 2012, the function CheckSQLAccess had to be altered by adding ',1433' to connection string like so:
$objSQLConnection.ConnectionString = "Server=$sqlServer,1433;....
This issue is causing the New-SPContentDatabase to fail during SP2010 farm setup.
See the link below for the error messages I am seeing.
http://stackoverflow.com/questions/18558952/sql-server-2012-remote-connection-setup
Any help that could find a work-around would be greatly appreciated.
Thanks