Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 309 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Dynamic NAV2018 Could not find prepared statement with handle 6046
muqfiy
Member Posts: 1
Hello all,
I use NAV2018 get an "Could not find prepared statement with handle 6046".
Sometimes once a month, sometimes every week one time.
Than you can only restart SQL Server services / NAV service to solve the problem
Are there other solution centers outside with the same problem and do have a fix for this.
In the internet I do not find solid information about this failure.
Best wishes
Muq
I use NAV2018 get an "Could not find prepared statement with handle 6046".
Sometimes once a month, sometimes every week one time.
Than you can only restart SQL Server services / NAV service to solve the problem
Are there other solution centers outside with the same problem and do have a fix for this.
In the internet I do not find solid information about this failure.
Best wishes
Muq
0
Answers
I am working for a NAV customer using NAV 2016 right now. We also get this error every now and then. We also restart the service tiers, when the error occurs. I too haven't found any helpful information regarding this error and NAV (for it is an error with the source SQL Server, it also can occur with other programs, there it is provoked by programming errors). We monitor the SQL statements for the first occurence of the error (Windows event log on service tier machine) trying to find a pattern, but up to now, we have no clue... too many different statements, no pattern here. When the error started to show up, it was often related to reading BLOB data (traffic light pictures). So we tried to reduce tha database access that reads pictures (reading once in the page into global variables, then using these and so on). It seemed to help a bit, but didn't stop the error showing up. I think it has to do with system or network loads / timeouts. Our solution center also has no information and no idea up to now.
We decided to live with it, hoping that the pending Upgrade to BC will help.
Best Regards,
Thomas