Share this

Error “Server is not found or not accessible” while executing bts_ConfigureBizTalkLogShipping on SQL Server 2012 for BTS 2013

Log shipping provides standby server capabilities, which reduces downtime in the event of a system failure. Log shipping allows you to automatically send transaction logs from the source system to the destination system. At the destination system the transaction logs are restored to the BizTalk Server databases, keeping them closely synchronized with the source databases. Couple of times I found this error “Server is not found or not accessible” while configuring the DR site by executing the stored procedure bts_ConfigureBizTalkLogShippingLog

exec bts_ConfigureBizTalkLogShipping @nvcDescription = '<MyLogShippingSolution>', @nvcMgmtDatabaseName = '<BizTalkServerManagementDatabaseName>', @nvcMgmtServerName = '<BizTalkServerManagementDatabaseServer>', @SourceServerName = null, -- null indicates that this destination server restores all databases @fLinkServers = 1 -- 1 automatically links the server to the management database

Reasons:

1. DTC Connectivity between LIVE and DR SQL Instance.

2. There might be some firewall issue where only a particular port has been open to access the LIVE database server. In that case create an alias with same name as LIVE SQL database and then run the stored procedure.

Also refer the MSDN forum link

https://social.msdn.microsoft.com/Forums/en-US/a2fd8aa3-6f58-4b80-b2de-25df111684cc/error-while-executing-btsconfigurebiztalklogshipping-with-sql-server-2012-and-bts-2013?forum=biztalkgeneral

Loved this? Spread the word


Gautam

Follow me here

About the Author

My name is Gyanendra Kumar Gautam. I am Solution Consultant, who basically works to hook the stuff together using Microsoft technologies like Azure PaaS, Azure Serverless Services, Microsoft BizTalk Server, and Azure DevOps Services.

You may also like

The source was not found, but some or all event logs could not be searched. To create the source, you need permission to read all event logs to make sure that the new source name is unique. Inaccessible logs: Security.

Yesterday this error came for one of the deployment on production. But the same deployment was working fine on staging environment. A message received by adapter “MSMQ” on receive location “RL_XYZ_RES_09” with URI “FORMATNAME:DIRECT=OS:.\PRIVATE$\XYZ_RES_09” is suspended. Error details: There was a failure executing the receive pipeline: “BTSHttpDecoder.DecoderPipeline, BTSHttpDecoder, Version=1.0.0.0, Culture=neutral, PublicKeyToken=5793a821957af7d1” Source: “MessageDecoderPipelineComponent_F09” Receive Port:

Read More

BizTalk Project Template is missing in Visual Studio 2012

I ran couple of times into this issue so thought of documenting it here. So first of all development of BizTalk Server 2013 application is only supported on Visual Studio 2012. In short, to get BizTalk Project Template do the following steps: Install Visual Studio 2012 Install SQLServer2012 or SQLServer2008R2 SP1 Install BizTalk Server 2013  – Select (mark

Read More

There is no value associated with the property ‘BTS.MessageID’ in the message.

In the following orchestration (This is the HelloWorld sample application at C:\Program Files (x86)\Microsoft BizTalk Server 2013\SDK\Samples\Orchestrations\HelloWorld\)     Inside the message assignment shape I have added the following code. System.Diagnostics.EventLog.WriteEntry(“HelloWorld”,InvoiceMessage(BTS.MessageID)); Now when I deploy and test the HelloWorld application, I get the following error xlang/s engine event log entry: Uncaught exception (see the ‘inner exception’ below)

Read More

Never miss a good story!

 Subscribe to my blog to keep up with the latest news!