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
- 300 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Data director 3.0 with nav
nizar_mneimneh
Member Posts: 3
Hello,
I am having a problem with the new data director 3.0 which ive been working on with the job monitor, whenever a job freezes or results in an error all the following jobs freeze and the whole replication process is compromised! I was told that a job causing a problem would do that with this version of DD! This never happened when we were working with nav 2009 is there any way to work around it? I cancelled the job causing the problems but i cant just sit there all day watching the monitor for jobs failing.
The jobs are stuck with status processing until the job is cancelled
I am having a problem with the new data director 3.0 which ive been working on with the job monitor, whenever a job freezes or results in an error all the following jobs freeze and the whole replication process is compromised! I was told that a job causing a problem would do that with this version of DD! This never happened when we were working with nav 2009 is there any way to work around it? I cancelled the job causing the problems but i cant just sit there all day watching the monitor for jobs failing.
The jobs are stuck with status processing until the job is cancelled
0