"Unable to connect to target server" when restoring bacpac file to SQL Server 2014 CTP2

Question

I'm getting the following error message when trying to restore a (known good) .bacpac file to a new SQL Server 2014 (Express) instance through the "Import Data-tier Application" wizard:

===================================

Unable to connect to target server. (Microsoft.Data.Tools.Schema.Sql)

---

Program Location:

at Microsoft.Data.Tools.Schema.Sql.Deployment.SqlDeploymentEndpointServer.OnInit(ErrorManager errors, String targetDBName) at Microsoft.Data.Tools.Schema.Sql.Deployment.SqlDeployment..ctor(SqlDeploymentConstructor constructor) at Microsoft.Data.Tools.Schema.Sql.Deployment.SqlDeploymentConstructor.ConstructServiceImplementation() at Microsoft.SqlServer.Dac.DacServices.CreatePackageToDatabaseDeployment(String connectionString, IPackageSource packageSource, String targetDatabaseName, DacAzureDatabaseSpecification creationDefaults, DacDeployOptions options, ErrorManager errorManager) at Microsoft.SqlServer.Dac.DeployOperation.<>c__DisplayClass3.<>c__DisplayClass5.b__1() at Microsoft.Data.Tools.Schema.Sql.Dac.OperationLogger.Capture(Action action) at Microsoft.SqlServer.Dac.DeployOperation.<>c__DisplayClass3.b__0(Object operation, CancellationToken token) at Microsoft.SqlServer.Dac.Operation.Microsoft.SqlServer.Dac.IOperation.Run(OperationContext context) at Microsoft.SqlServer.Dac.ReportMessageOperation.Microsoft.SqlServer.Dac.IOperation.Run(OperationContext context) at Microsoft.SqlServer.Dac.OperationExtension.CompositeOperation.Microsoft.SqlServer.Dac.IOperation.Run(OperationContext context) at Microsoft.SqlServer.Dac.OperationExtension.CompositeOperation.Microsoft.SqlServer.Dac.IOperation.Run(OperationContext context) at Microsoft.SqlServer.Dac.DeployOperation.Microsoft.SqlServer.Dac.IOperation.Run(OperationContext context)

The error specifically doesn't make sense because it successfully creates the database, as reported here (and manually confirmed). It just doesn't import the data.

Googling hasn't turned up anything. Anybody else run into this? Any workarounds? Give up and go back to 2012?

Answer 1

I never did figure this out, but uninstalling 2014 and dropping back to 2012 seemed to fix it. For now, I'm chalking it up to a bug in 2014. It's not even at the beta stage yet, so I suppose it's not surprising that there are still significant bugs. (Still, isn't it interesting how so many other companies manage to release software on a much more aggressive schedule than MS, with each release being so much more stable?)