Skip to main content

RTC Error The Microsoft Dynamics NAV Server cannot connect the Change Listener to SQL Server because of the following error: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.


Hi all,

Which doing a implentation i found a error, and i thought of sharing same so that others who face this issue can reslove same without spending time which i did.

Everything done, from syncronization, change listener but the error remains same as shown in screenshot below.















After searching i found out at MSDN that this is due to SQL Server and Firewall.

For SQL Server the ports used is 1433.

Steps to Resolve Error -

1) On the Start menu, click Run, type WF.msc, and then click OK.

2) In the Windows Firewall with Advanced Security, in the left pane, right-click Inbound Rules, and then click New Rule in the action pane.

3) In the Rule Type dialog box, select Port, and then click Next.

4) In the Protocol and Ports dialog box, select TCP. Select Specific local ports, and then type the port number of the instance of the Database Engine, such as 1433 for the default instance. Click Next.

5) In the Action dialog box, select Allow the connection, and then click Next.

6) In the Profile dialog box, select any profiles that describe the computer connection environment when you want to connect to the Database Engine, and then click Next.

7) In the Name dialog box, type a name and description for this rule, and then click Finish.

After this restart the service and try to connect to Role Tailored Client. You should be able to connect as i did.

Thanks & Regards,
Saurav Dhyani

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.