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
- 305 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
Codeunit 397 and NS Outlook Synchronization Handler problem
blusky75
Member Posts: 22
We have a 4.0 SP3 environment and have some processes to send mail via outlook. We're trying to get this working for a new workstation but we're getting the following error when codeunit 397 is called from one user's machine:
Could not create an instance of the OLE control or Automation server
identified by GUID={03BC4F50-2ABB-48B3-B2A6-3F08EB1D013E} 1.7:{F3B45F48-1F4A-40C9-8DE6-5CC377BF4F82}:'NS Outlook Synchronization Handler'.OSendMail.
After some researching, we went through the necessary steps - install the outlook toolbar via the SP3 installation (client install), ran regsvr32 olhandler.dll, but Navision still refuses to create an instance of that object at run-time.
When we log in as a superuser on the affected workstation and compile codeunit 397, we have no issues. When the superuser windows account calls that codeunit, everything appears to work. When we log in the affected user however, we get the above error. It's as if the automation object (olhandler.dll) is registered for some users, but not others (the affected user by the way is a member of the machine's local admin group so I don't believe it to be permissions-related).
Any idea why this object is behaving so erratically?
Could not create an instance of the OLE control or Automation server
identified by GUID={03BC4F50-2ABB-48B3-B2A6-3F08EB1D013E} 1.7:{F3B45F48-1F4A-40C9-8DE6-5CC377BF4F82}:'NS Outlook Synchronization Handler'.OSendMail.
After some researching, we went through the necessary steps - install the outlook toolbar via the SP3 installation (client install), ran regsvr32 olhandler.dll, but Navision still refuses to create an instance of that object at run-time.
When we log in as a superuser on the affected workstation and compile codeunit 397, we have no issues. When the superuser windows account calls that codeunit, everything appears to work. When we log in the affected user however, we get the above error. It's as if the automation object (olhandler.dll) is registered for some users, but not others (the affected user by the way is a member of the machine's local admin group so I don't believe it to be permissions-related).
Any idea why this object is behaving so erratically?
0