Skip to main content

Posts

Navision List of Hidden Tables

Hi all, Most of time we try to figure out the Hidden Tables in Navision. I required the same list, it took a long time to find all hidden tables, so i thought that it might be useful to others too. This list if for Microsoft Dynamics NAV 2009 R2. 2000000001 Object 2000000007 Date 2000000009 Session 2000000010 Database File 2000000020 Drive 2000000022 File 2000000024 Monitor 2000000026 Integer 2000000028 Table Information 2000000029 System Object 2000000037 Performance 2000000038 AIIObj 2000000039 Printer 2000000040 License Information 2000000041 Field 2000000042 OLE Control 2000000043 License Permission 2000000044 Permission Range 2000000045 Windows Language 2000000046 Automation Servers 2000000047 Server 2000000048 Database 2000000049 Code Coverage 2000000050 Windows Object 2000000052 Windows Group Member 2000000053 Windows Access Control 2000000055 SID - Account ID 2000000056 User SID 2000000058 AllObjWithCaption 2000000059 Breakpoints 2000000063

Copy Navision Data Between Databases using SQL Server

Hi all, Microsoft SQL Server has an import and export wizard that assists you in copying Navision data from one database to another. This import and export wizard is available in any version of SQL Server, and it lets you copy tables, data, functions and other database objects. This is beneficial when you want to move your Navision data to a faster server for better querying performance.

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