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
- 269 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 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
Socketevents Application error
Johnny_Reggae
Member Posts: 63
One user with one of our clients runs frequently into this error :
SocketEvents: fin.exe - Application Error.
The instruction at '0x004feba3' referenced memory at '0x02251e50'. The memory could not be "read".
I have no clue what could be the solution....
Any ideas ?
SocketEvents: fin.exe - Application Error.
The instruction at '0x004feba3' referenced memory at '0x02251e50'. The memory could not be "read".
I have no clue what could be the solution....
Any ideas ?
0
Comments
In that case : first thing to try : re-install Navision.
Or also : The error lets me think that some machine-code in the memory tries to read some memory location. That memory-location is defect or non-existent. This would mean the memory is defect and should be replaced. But in this case also other applications should have the error (at least if other applications happen to use that memory location) If it is always the same memory location it is probably this the problem. And in this case one of the memory-chips must be replaced. Which one? You have to try it out.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
One thing is also odd : when the error occurs, it's with a preview of a certain report (always the same). Once the error has occurred, it's not possible for this user in his session to print the report again, unless he logs off and logs in again.
It's also not possible to reproduce the error, it sometimes occurs and sometimes doesn't.
-Every user has his zup-files? If yes, it is possible the error is in the zup-file. (not likely)
-Other users use the same report?
- If Yes, has the user a default printer for that report ? If yes, maybe it is the printerdriver. If No, maybe the printerdriver of his default Windows-printer has a bug in it (preview uses the default windows-printer driver)
- If No, maybe something strange happens in the report that generates the error.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!