Issue#1: VS 2015 cannot load BizTalk projects
Resolution: The BizTalk 2016 projects with .net Framework set to 4.6 & above had this issue. The .net framework 4.7 Developer pack had to be installed.
Issue#2: SQL Agent disabled on DB servers
Resolution: The alias name for SQL Instance had to be updated to <ServerName>.<domain>\<InstanceName> in SQL Agent Properties.
Issue#3: BizTalk group could not be configured
Resolution: The App & DB servers were cloned, which resulted in the same set of MSDTC CID values in the registry. To overcome this, MSDTC had to be reinstalled on each App server.
Issue#4: BizTalk Migration tool import failed to connect to remote BizTalk Server.
Resolution: The Firewall on Destination Server had to be turned off for Domain, private & public profiles.
Issue#5: SQL Server Configuration Manager:
Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager.
Resolution:
Execute following Command in command prompt with Administrative privileges:
mofcomp “%programfiles(x86)%\Microsoft SQL Server\130\Shared\sqlmgmproviderxpsp2up.mof”
Reference here.
Issue#6: SQL Server agent job- PurgeBackupPlan.Subplan1 job error log: SQL Server blocked access to procedure ‘sys.xp_cmdshell’ of component ‘xp_cmdshell’ because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of ‘xp_cmdshell’ by using sp_configure. For more information about enabling ‘xp_cmdshell’, search for ‘xp_cmdshell’ in SQL Server Books Online.
Resolution:
Enable xp_cmdshell on Listener server using the script:
— To allow advanced options to be changed.
EXEC sp_configure ‘show advanced options’, 1;
GO
— To update the currently configured value for advanced options.
RECONFIGURE;
GO
— To enable the feature.
EXEC sp_configure ‘xp_cmdshell’, 1;
GO
— To update the currently configured value for this feature.
RECONFIGURE;
GO
Reference here.
Issue#7: Error while executing custom view on a different listener.
Could not find server ‘<ServerName> in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers.
Resolution:
As a workaround, a linked server with name ‘<ServerName>’ is added on the listener and a remote login user is added to connect to the server.
EXEC master.dbo.sp_addlinkedserver
@server = N'<ServerName>’,
@srvproduct=N’SQLSERVER’,
@provider=N’SQLNCLI’,
@datasrc=N'<BizTalkListenerName\InstanceName>’
EXEC master.dbo.sp_addlinkedsrvlogin
@rmtsrvname=N'<ServerName>’,
@useself=N’False’,
@locallogin=NULL,
@rmtuser=N'<sa Login>’,
@rmtpassword='<sa Password>’