Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K 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
- 317 Dynamics CRM
- 110 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 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
Navision Application Server stops after SQL Log Backup
raceface
Member Posts: 3
Hello everybody
We have following problem with Navision 3.7 and NAS. NAS stops executing jobs after we perform a transaction-log-backup in SQL Server. The service is running, but no jobs. Has somebody the same problems or some tips for me?
We are now running the transaction-log-backups only once per day, after the NAS-Service is shutting down. And we restart the service after the backup is finished.
We would like to backup the transaction-log every hour (also to keep it small). The backup usually takes only 4-5 seconds.
thank you all...
kind regards
Roger Breu
We have following problem with Navision 3.7 and NAS. NAS stops executing jobs after we perform a transaction-log-backup in SQL Server. The service is running, but no jobs. Has somebody the same problems or some tips for me?
We are now running the transaction-log-backups only once per day, after the NAS-Service is shutting down. And we restart the service after the backup is finished.
We would like to backup the transaction-log every hour (also to keep it small). The backup usually takes only 4-5 seconds.
thank you all...
kind regards
Roger Breu
0
Comments
Do you see any nas-entries in the windows application log?
What is your nas doing? If there are any timers involved, try to put some messages on the ::TimerError-Trigger to find out whether this trigger is fired.
Hope this helps
Thomas
thanks for your reply... we will test it and i will repost the results...
roger