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
- 304 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Debugging FaxServer Object
alsol
Member Posts: 243
Hi there,
I am trying to implement a fax solution using the FaxServer object (msdn.microsoft.com/en-us/library/windows/desktop/ms689109%28v=vs.85%29.aspx). It works when I map my local virtual fax to the RDP connection but it does not work with a real fax in the environment of the customer. There is alway an error message saying "ConnectedSubmit failed: Operation failed".
In theory the object should return an error code that would help us identify the issue. But it does not do that in RTC. What is the best way to debug this in RTC? We cannot run it using the classic client because we access RTC via WAN and the database is hosted in a datacenter. So we somehow need to debug the object in RTC.
Any ideas?
I am trying to implement a fax solution using the FaxServer object (msdn.microsoft.com/en-us/library/windows/desktop/ms689109%28v=vs.85%29.aspx). It works when I map my local virtual fax to the RDP connection but it does not work with a real fax in the environment of the customer. There is alway an error message saying "ConnectedSubmit failed: Operation failed".
In theory the object should return an error code that would help us identify the issue. But it does not do that in RTC. What is the best way to debug this in RTC? We cannot run it using the classic client because we access RTC via WAN and the database is hosted in a datacenter. So we somehow need to debug the object in RTC.
Any ideas?
0