Dear Sir,

We have a parent domain and child domain , all users and resources are part of the child domain , We have extended the forest at the root level and schema log file show that the schema updated successfully.

We have created the system management container in both the Parent and child domain and added the sccmserver with full control on object and its descendent.

When we trying to install the sccm server on a machine (in child domain) it is giving the below error in ConfigMgrSetupWizard

8/26/2013 5:32:18 PM: ConfigMgrSetupWizard Information: 1 : Cannot detect SMS Type because either SiteServer, SqlServer or SiteServerName is empty.
8/26/2013 5:33:51 PM: ConfigMgrSetupWizard Information: 1 : Creating SQL connection to database master on server 2k8-ho-dbclus.exch1.XXX.YYY.com.
8/26/2013 5:33:51 PM: ConfigMgrSetupWizard Error: 1 : Exception message: [The value's length for key 'data source' exceeds it's limit of '128'.], Exception details: [System.ArgumentException: The value's length for key 'data source' exceeds it's limit of '128'.

We have so far done the following

1) Check all the pre-requisites

2) Run the setup with a user having all the permissions on the domain.

3) SQL : SQL Server 2008 R2 on Cluster with SP2

4) http://social.technet.microsoft.com/Forums/en-US/a8e1e624-10d1-413e-910e-932bf6624ba9/install-issue-sccm2012

5) Changed the media source files

6) Tried doing a ODBC to SQL Server : work all fine .

Need help ,

Regards,

Hasan Reza

• Edited by Hasan Reza Tuesday, August 27, 2013 8:08 AM
• Moved by Andreas BaumgartenMVP Tuesday, August 27, 2013 9:03 PM This question is related to System Center 2012 Configuration Manager

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

BTW it is NOT recommend to install SQL remotely from CM12 site server. Additionally, it is not recommend to install CM12 SQL's on a Share server.

Dear All,

We found the error with MS Support ticket after sending some 100 mb of program execution debur report , below was the finding,

The SQL Administrator had added some 20 ports in addition to the 1433 in tcp port parameter , in that case each time the application tried creating SQL Connection it would exceed the 128 limit,

We removed the number of ports and the issues was sorted,

Apologies for the delayed answer,

Hasan Reza,

• Marked as answer by Hasan Reza 19 hours 3 minutes ago