Oh, I have 2012 R2 already setup. I am trying to configure a migration in the ConfigMgr 2012 console and the source ConfigMgr 2007 database runs on a custom port. There is no way that I can tell in the Source Hierarchy setup to specify database connection info. Jeff
From: [email protected] To: [email protected] Subject: RE: [mssms] CM07 - CM12 Migration Error Date: Thu, 29 Jan 2015 14:59:14 +0000 Think it was on the server name, or was it on the instance? Can’t really remember, but I put in into the setup.exe. Can dig it up I think if needed. //A From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Poling Sent: den 29 januari 2015 15:55 To: [email protected] Subject: RE: [mssms] CM07 - CM12 Migration Error Do you remember how you include the port? I can't seem to find anywhere in the setup of the source hierarchy to specify the database port Thanks, Jeff From: [email protected] To: [email protected] Subject: RE: [mssms] CM07 - CM12 Migration Error Date: Thu, 29 Jan 2015 14:48:49 +0000 Yeah… I have! J Seems to remember that I had to include the port, even though it was standard. //A From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Poling Sent: den 29 januari 2015 15:34 To: [email protected] Subject: RE: [mssms] CM07 - CM12 Migration Error I confirmed that configuring the source hierarchy is failing due to the CM07 database server using an instance configured with a custom port. Based on some research and community feedback, I tested connectivity using UDL (see http://blogs.technet.com/b/michaelgriswold/archive/2014/01/06/the-easy-way-to-test-sql-connectivity.aspx). If I specify the SQL Server instance with the port (like this, SERVER\INSTANCE,1542), the test succeeds without issue. If I specify it without the port, like the migration tool does, it fails. The migration tool tries the connection like this (note the data source does not include the port): Connection string = Data Source=SERVER\INSTANCE;Initial Catalog=SMS_ABC;Integrated Security=True;Persist Security Info=False;MultipleActiveResultSets=True;Encrypt=True;TrustServerCertificate=True;Application Name="Migration Manager". The SQL Browser service is running on the SQL server, so I thought that would allow clients to automatically determine the port? Has anyone run into this before? Thanks! Jeff To: [email protected] From: [email protected] Subject: RE: [mssms] CM07 - CM12 Migration Error Date: Wed, 28 Jan 2015 19:18:52 -0600 Actually, yeah. I forgot to include that they have SQL on a non-standard port. Sorry, I hurriedly sent the initial email. Is there a way to specify the SQL port when configuring the source hierarchy? Thanks, Jeff Sent from my Windows Phone From: Andreas Hammarskjöld Sent: 1/28/2015 5:29 PM To: [email protected] Subject: RE: [mssms] CM07 - CM12 Migration Error Rings a bell… I would say it’s the binding/port info, weird SQL port or TCP/IP net pipe issue with a non-default instance name? Can you connect with SQL Admin studio? //A From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Poling Sent: den 28 januari 2015 23:57 To: [email protected] Subject: [mssms] CM07 - CM12 Migration Error I posted this to the TechNet forum as well, but I thought I would see if anyone on this list has encountered this. . . When setting up the migration job, the initial data gathering returns an error related to finding the SQL instance: ERROR: [MigrationManager]: Microsoft.ConfigurationManagement.Migration.MigrationException: Error occurred when trying to make sql connection to SERVER. Contact product support for help. Error Information -2146232060, A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) The ConfigMgr 2007 database is hosted remotely on an SQL Server cluster. The DBA configured the migration account to have both read and execute permissions on the COnfigMgr 2007 database. The 2007 environment uses a remote SQL cluster to host the database. I worked with the DBA to assign read and execute permissions on the 2007 database for the account I am using to migrate the data. Even after the permission changes, we still get the error. Has anyone experienced this or have any suggestions? Thanks, Jeff
