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
- 310 Dynamics CRM
- 110 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
"The system is not accessible, because it requires a schema synchronization." error after restart
RobyR
Member Posts: 39
Hi Everyone,
I'm beginning creazy because of the error in subject, I will explain better the situation:
I deleted with force some table and then re-compiled all object in order to find broken references. After a service restart, when I try to login in NAV, i get the error in object, without any Event Viewer log and the service still run.
If I go into Developer client and then Tools->Sync. schema->with validation, then everything starts working right.
Every time I restart the service I need to redo the Sync.
Anyone have an idea?
Thanks in advance
Roby
I'm beginning creazy because of the error in subject, I will explain better the situation:
I deleted with force some table and then re-compiled all object in order to find broken references. After a service restart, when I try to login in NAV, i get the error in object, without any Event Viewer log and the service still run.
If I go into Developer client and then Tools->Sync. schema->with validation, then everything starts working right.
Every time I restart the service I need to redo the Sync.
Anyone have an idea?
Thanks in advance
Roby
0
Best Answer
-
RobyR
Member Posts: 39
With Microsoft Support we found that is a bug of NAV 2018 solved with CU 8 (is necessary to instal at least the application CU)0
Answers