Internal Error 1367 In Module 19
Recent Discussions Activity Best Of... Unanswered Categories 62.5K All Categories73 General 73 Announcements 57K Microsoft Dynamics NAV 11.3K NAV Three Tier 37.1K NAV/Navision Classic Client 3.6K Navision Attain 2.2K Navision Financials 107 Navision DOS 828 Navision e-Commerce 528 NAV Tips & Tricks 728 NAV Dutch speaking only 580 NAV Courses, Exams & Certification 1.8K Microsoft Dynamics-Other 1.4K Dynamics AX 195 Dynamics CRM 96 Dynamics GP 5 Dynamics SL 1.4K Other 928 SQL General 354 SQL Performance 24 SQL Tips & Tricks 17 Design Patterns (General & Best Practices) 0 Architectural Patterns 6 Design Patterns 2 Implementation Patterns 28 3rd Party Products, Services & Events 860 General 860 General Chat 1.5K Website 73 Testing 1.1K Download section 23 How Tos section 231 Feedback 12 NAV TechDays 2013 Sessions 13 NAV TechDays 2012 Sessions internal error 1367 in module 19 danial Member Posts: 2 2007-02-21 edited 2014-04-01 in NAV/Navision Classic Client Hi When i try to compile form 21 (customer card) i get the message "internal error 1367 in module 19" Anyone got an idea what to do to solve this problem? 0 Comments Timo_Lässer Member Posts: 481 2007-02-21 Internal Error 1367 in Module 19 Module 19 = Database-Errors (see also Module 34) Errorcode: 1246551 Description: #Err_DB_TableNotSpecified (Possible) Reason(s): Table not defined or not specified. Timo Lässer Microsoft Dynamics NAV Developer since 1997 MSDynamics.de - German Microsoft Dynamics Community - member of [clip]0 AntidotE Member Posts: 56 2009-06-06 Sorry for upping so old topic, maybe, someone find it helpful... I got the same error when tried to compile form. The cause of this problem was in absence of another form. options in one of MenuItems: RunObject=Form
Date 2010-2-18 3:30 AM Replies 1 reply Subscribers 338 subscribers Views 2282 views Options Share RSS Tags More Cancel Click here to login or become a member to ask questions and reply in our fourms. Internal error 1367 in module 19. Hello... I couldn't compile the table because of this error... help me, please. Ariuka http://forum.mibuso.com/discussion/16692/internal-error-1367-in-module-19 Cancel Dhan Raj Bansal 0 2010-2-18 8:17 AM I do not know the real solution for this, but following may help: 1. Delete the ZUP file and then re-run the client. 2. If the above doesn't resolve the issue, then re-install NAV on that client https://dynamicsuser.net/forums/p/8478/31388.aspx machine. Dhan Raj Bansal Click here to login or join to be able to reply and post new questions. Related DUG Home Contact DUG Dynamics AX Users Forums Blogs Events Documentation, videos and downloads AX Partners Group Dynamics NAV Users Forums Blogs Wikipedia Events Books NAV partners group NAV freelancers group Dynamics CRM Users Forums Blogs Dynamics GP Users Forums Blogs Dynamics 365 Users Forums Blogs Documentation, videos and downloads Jobs and careers Jobs and Careers Forum Dynamics Jobs Offered Dynamics Jobs Wanted About DUG Announcements Frequently asked questions about DUG Suggestions to DUG Membership service Advertise on DUG Become a DUG sponsor Follow us on LinkedIn Follow us on Facebook Follow us on Twitter More Cancel © 1995-2016 Dynamics User Group, all rights reserved. Terms of use| Privacy|Contact us|Powered by Telligent Community
365 for Enterprise Skype for business Microsoft Dynamics Microsoft Dynamics Sales Service Marketing Social Enterprise Resource Planning Small and Midsize Business Windows Windows 10 for business Windows 10 for Internet of Things Windows devices Data and analytics Data management https://community.dynamics.com/nav/f/34/t/121897 and analytics Microsoft SQL Server Microsoft Power BI Microsoft Cortana Intelligence Suite Operations management Operations Management Suite System Center Sign in Search Microsoft Search Dynamics Community Participate Ask a Question Get Started Badges Earn http://techblog.byllemos.com/2008/10/internal-error-1247-in-module-19/ Badges View Badges Leaderboards Compete on Leaderboards View Leaderboards Become an Expert Recommend a Blog Introduce Yourself Provide Feedback Communities Microsoft Dynamics AX Microsoft Dynamics CRM Dynamics 365, Business Edition Dynamics 365, Enterprise Edition internal error Microsoft Dynamics GP Microsoft Dynamics NAV Partner Community Other Products Dynamics Community Microsoft Dynamics NAV Forum Blogs Videos Experts Support Wiki Dynamics Community Participate Ask a Question Get Started Badges Earn Badges View Badges Leaderboards Compete on Leaderboards View Leaderboards Become an Expert Recommend a Blog Introduce Yourself Provide Feedback Communities Microsoft Dynamics AX Microsoft Dynamics CRM Dynamics 365, Business Edition Dynamics 365, Enterprise Edition Microsoft Dynamics GP Microsoft internal error 1367 Dynamics NAV Partner Community Other Products Microsoft Dynamics NAV Forum Blogs Videos Experts Support Wiki NAS Fileadapter error "Internal error 1247 in module 19" Sign In Share Twitter LinkedIn Facebook Email Print RSS Ekaterina Putintseva Question Status Unanswered Ekaterina Putintseva asked a question on 25 Feb 2014 12:57 AM Dear All, I have the following problem. Please help me with a good advice. NAS Fileadapter server keeps collapsing from time to time with the following error message in the Event Viewer "Internal error 1247 in module 19". Not very informative... and the consequences are crucial as it stops working. No other error messages were found. And practice shows server collapses always after getting this error (it is actually Warning message in Event Viewer). Is there any hotfix I can try to apply for nassql.exe? Some additional information on the system: Client Dynamics NAV 5.0 SP1 running on Microsoft SQL Server 2008. The server where NAS is installed is Microsoft Windows Server 2003 R2 Standard Edition Service Pack 2. Reply All Responses (2) Mohana Yadav Works In Hyderabad, India @mohana_cse06 LinkedIn YouTube Blog My Badges Mohana Yadav responded on 25 Feb 2014 1:02 AM Did you try this post www.mibuso.com/.../viewtopic.php Reply Ekaterina Putin
Post Tags: Deadlock, Internal Error 1247, Navision I did meet this error for the first time several years ago. Today some of my colleagues saw the message for the first time and did not know what to do about it. Internal Error 1247 in module 19 is equal to #Err_DB_NewWTAMissing DB_Err(1247), where WTA is short for Write TransAction. This error can occur if two or more users run into a deadlock. The first user, that run into the deadlock will recieve this message and will, by clicking ok to the window message, cancel his transaction (The Navision Client will Crash). The second user will thereby not notice there has been a deadlock and will therefor continue his transaction. This again means, that it will be difficult to find the area where the deadlock has occured. So what to do? If you can recreate the deadlock - then its great, because this mean that you can do something against it All you have to do - is looking through the code and remove possible deadlock situations. One way to do, this could be using the Client Monitor, it can predict possible deadlocks in the C/AL code. A second way, if you are using sql, would be using the sql profiler. It can log your steps, which could help you pin point where there might be a issue. If you have pin pointed the area where the deadlocks can occur, that you have to go through you code. A good idea could also be to optimize indexes and sift's on the tables. Good luck with your deadlock search! Share:Click to email this to a friend (Opens in new window)Click to print (Opens in new window)Share on Facebook (Opens in new window)Click to share on Google+ (Opens in new window)Click to share on Twitter (Opens in new window)Click to share on LinkedIn (Opens in new window)Click to share on Pinterest (Opens in new window)Click to share on Tumblr (Opens in new window)Click to share on Reddit (Opens in new window) « Writing an automation for Navision in C# Prevent Copy in Navision » You can leave a response, or trackback from your own site. 5 Responses to "Internal Error 1247 in module 19" iby says: October 23, 2008 at 18:25 I just found out, that the Navision 5 SP1 client also h