SIMS SQL 2016 Migration Tool - Blank Destination

[LazyD]

Hi,

 

Have installed SQL 2016 on the server that has had SQL 2012 on it up until now, when I run the migration tool from Capita it does not find any available destination servers, the drop down is blank.

 

I have checked that TCP/IP is enabled in configuration manager. I have checked that remote connections are allowed to the new SQL 2016 server instance. The SQL Browser service is started and set to automatic. I have disabled the firewall and the problem still remains.

 

I can connect to the source of the migration fine, just no option for destination.. ??

 

Thanks.

[tech-man]

Errrrm I think it’s called named pipe in configuration. Have you enabled it?

[LazyD]

Yes I have enabled named pipes in configuration manager. This has not helped.

[Atomic_Zombie]

Hi LazyD, we are seeing the same thing. we've tried the same things as you along with Windows updates etc. It seems to be hit and miss; Sometimes it works, other times it doesn't. I'm installing another instance today and going to be logging a call with Capita if I can't get it to work.

[LazyD]

Hi Atomic_Zombie, thanks for your reply. What Server OS are you on? I am using Server 2016 Standard.

 

I have done everything the documents suggest, the firewall right now to SQL instances is wide open. As mentioned earlier, I doubt this is a straight up FW issue anyway as disabling it completely did not help. I have also logged a call with Capita this morning.

 

Don't know what else to try right now. You say it's hit and miss, so you have done a few of these and found them to randomly behave differently?

[Atomic_Zombie]

Hi LazyD. I work for an LA so we have done a fair few recently, with no apparent difference with settings / process. We have seen the issue on Windows 10 and Server 2016 std.

 

I have a hunch it's to do with Microsoft moving to a more frequent release schedule of SQL. something to do with expceted version numbers and applied service packs but I've not had chance to test this.

Edited August 8, 2018 by Atomic_Zombie

[LazyD]

How has it been resolved when you have seen this issue before?

[Olliesaurus]

Hey, I am experiencing the same issue, did you get anywhere with the problem at all?

 

Its mildly infuriating, got to a point where I am ready to do the SIMS server but I can't actually get anywhere, have contacted Capita also.

[Atomic_Zombie]

Hi, In the past I've just imported the Databases with DBAttach, but this can sometimes cause issues with performance.

[LazyD]

Atomic Zombie, I tried to do that (and tried to restore a backup) but got one of the long errors from dbattach related to a few dll's and other files that were missing from the destination SQL instances BINN folder. This stuff is normally put into the BINN folder by the Capita migration tool but as that obviously wasn't working, it wasn't there. Capita in the end got the script that performs that part of the migration and ran that (which put all the Capita stuff in the SQL 2016 BINN folder) and then a restore from backup worked.

 

It 'seems' to be ok now. Although I have seen a few weird things so far, like some FMS users user ID (login) was blank, so had to recreate, and some other users are claiming that things they normally have permissions to do in SIMS they no longer have. I am also a bit disturbed by your claim that this method can affect performance.

 

Olliesaurus, I would say it's infuriating to a medium level but with potential to become highly infuriating.

Edited August 9, 2018 by LazyD