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
- 304 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
BC140 Start-NAVServerInstance: "The system is currently updating, try to connect later"
Mips
Member Posts: 3
We have four NAV servers. After a restart, we have the following warning on the heavy load NAV servers for about half an hour when we try to connect:
Microsoft Dynamics 365 Business Central
The system is currently updating, try to connect later
OK
Can we make changes in the Configuration, or what is the problem?
Microsoft Dynamics 365 Business Central
The system is currently updating, try to connect later
OK
Can we make changes in the Configuration, or what is the problem?
0
Answers
did you find a reason for this or a solution?
This week a customer complains about the very same thing. They restart NST at 3 am and get the message around 6 am when the first users try to connect. The message disappears after 10 - 30 minutes - but 'til that they can't work...
THX Heinrich
the problem is resolved. It was a bug by Microsoft. They fixed it in CU15.
As workaround you can try this:
1. Change / import table(s) with Sync option choose “Later”.
2. Run the following PS cmdlet: Sync-NAVTenant BC140 -CommitPerTable -Mode Sync
3. At this stage the Database will be in status “OperationalSyncInProgress” and your RTC and Web client will not be able to connect as before.
4. Wait 1 minute and then restart the NAV Service.
5. When the service is available again the database will be showing “Operational” and the table change will be fully synchronized. Users will be able to connect with the RTC as normal.
Do you have any link/documentation on this? One of our install BC14 CU7 just started having this problem, 1 time last week and again today. All modifications are done by extensions, so there are no table changes in the old development system.
Going over the documentation for CU15, I cannot find anything referring to this, so I am hoping that you might have something?