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
- 263 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
RTC Client Crashes directly after start on some machines
LudwigBeck_Muenchen
Member Posts: 5
Hi all,
i´m experiencing the following behaviour on some machines:
When starting the RTC, the application starts and directly after viewing the sidebar immediately crashes.
The behaviour must be machine-depending, as the same users can connect to NAV with the RTC on different machines.
In the case of such a crash, the Eventlog shows:
1) 1001
Fehlerbucket 128911675617, Typ 5
Ereignisname: CLR20r3
Antwort: Not available
CAB-Datei-ID: 0
Problemsignatur:
P1: Microsoft.Dynamics.Nav.Client
P2: 8.0.42603.0
P3: 55e020ec
P4: Microsoft.Dynamics.Nav.Types
P5: 8.0.42603.0
P6: 55e020fb
P7: 600
P8: 85
P9: System.NullReferenceException
P10:
2) 1000 Application Error
Fehlerbucket 128911675617, Typ 5
Ereignisname: CLR20r3
Antwort: Not available
CAB-Datei-ID: 0
Problemsignatur:
P1: Microsoft.Dynamics.Nav.Client
P2: 8.0.42603.0
P3: 55e020ec
P4: Microsoft.Dynamics.Nav.Types
P5: 8.0.42603.0
P6: 55e020fb
P7: 600
P8: 85
P9: System.NullReferenceException
P10:
3) 1024 .Net Runtime
Application: Microsoft.Dynamics.Nav.Client.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at Microsoft.Dynamics.Nav.Types.EventLogEntryWriterProxy.WriteEntry()
at Microsoft.Dynamics.Nav.Types.EventLogWriter.ProcessEventQueue()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()
Did anybody experience this as well and found a solution on this ?
Kind regards,
Markus
i´m experiencing the following behaviour on some machines:
When starting the RTC, the application starts and directly after viewing the sidebar immediately crashes.
The behaviour must be machine-depending, as the same users can connect to NAV with the RTC on different machines.
In the case of such a crash, the Eventlog shows:
1) 1001
Fehlerbucket 128911675617, Typ 5
Ereignisname: CLR20r3
Antwort: Not available
CAB-Datei-ID: 0
Problemsignatur:
P1: Microsoft.Dynamics.Nav.Client
P2: 8.0.42603.0
P3: 55e020ec
P4: Microsoft.Dynamics.Nav.Types
P5: 8.0.42603.0
P6: 55e020fb
P7: 600
P8: 85
P9: System.NullReferenceException
P10:
2) 1000 Application Error
Fehlerbucket 128911675617, Typ 5
Ereignisname: CLR20r3
Antwort: Not available
CAB-Datei-ID: 0
Problemsignatur:
P1: Microsoft.Dynamics.Nav.Client
P2: 8.0.42603.0
P3: 55e020ec
P4: Microsoft.Dynamics.Nav.Types
P5: 8.0.42603.0
P6: 55e020fb
P7: 600
P8: 85
P9: System.NullReferenceException
P10:
3) 1024 .Net Runtime
Application: Microsoft.Dynamics.Nav.Client.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at Microsoft.Dynamics.Nav.Types.EventLogEntryWriterProxy.WriteEntry()
at Microsoft.Dynamics.Nav.Types.EventLogWriter.ProcessEventQueue()
at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()
Did anybody experience this as well and found a solution on this ?
Kind regards,
Markus
0
Best Answer
-
OptionsLudwigBeck_Muenchen
Member Posts: 5
Found a solution: running the NetFXRepair-Tool by Microsoft brought the Application back to a working state ... whatever the initial problem was exactly ...0
Answers
right click - propertys - details
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!