Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 264 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
3.70A Server Service Stops Unexpectedly
brad77
Member Posts: 3
We recently upgraded the database server from 3.60 to 3.70A. During the night, the server service stopped twice. There were no errors messages in the Application Log, and the System Log contained the following message:
The Navision Database Server <name> service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 0 milliseconds: No action.
There were no changes to the hardware. During the upgrade, we split the DB into more files (12 files on 6 physical volumes on our RAID) to increase the number of instances of "slave.exe" in an effort to speed things up a bit. Our database was then restored into the 3.70A DB.
Is anyone aware of any stability issues with this build of the server service? Other posts make mention of hardware problems, but I'm not so sure seeing as we didn't make any changes to the config.
Thanks in advance to anyone who has input.
Brad
The Navision Database Server <name> service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 0 milliseconds: No action.
There were no changes to the hardware. During the upgrade, we split the DB into more files (12 files on 6 physical volumes on our RAID) to increase the number of instances of "slave.exe" in an effort to speed things up a bit. Our database was then restored into the 3.70A DB.
Is anyone aware of any stability issues with this build of the server service? Other posts make mention of hardware problems, but I'm not so sure seeing as we didn't make any changes to the config.
Thanks in advance to anyone who has input.
Brad
0