x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 2 replies
  • Subscribers 42 subscribers
  • Views 3535 views
  • Users 0 members are here
Browse Forums
Announcements
68
topics
93
replies
Customization and Integration
262
topics
822
replies
Financials, Projects, and Administration
382
topics
843
replies
General Discussion
327
topics
836
replies
Installation and Technical Issues
335
topics
1k
replies
Manufacturing, Distribution, and Applications
341
topics
696
replies
Reporting and Analytics
123
topics
480
replies
Erik Wehr

User has issue - OLE Dispatch Error: m_scError:266744(0x000411f8)

Posted By

We have a user here who just upgraded to a Windows 10 laptop. She'd been getting random errors since then, which we thought were fixed by reinstalling and allowing Sage500 through Microsoft's builtin screening tools (and setting the SQL settings in ODBC correctly), but today she received this - OLE Dispatch Error: m_scError:266744(0x000411f8). Couldn't find anything on those error codes, and it's definitely not a Network issue as it seems to think it is. She was just trying to re-enter a Purchasing Order to print to PDF because it didn't do anything the first time she entered it. Doesn't happen every time. I found something on another page that referenced these forums, but the thread it's linked to doesn't seem to exist anymore. Anybody have any ideas? TIA.

  • 0
    These OLE Dispatch errors are typically the reult of a momentary loss of connection from teh workstation to the SQL server. Have you confirmed the re is no issue with the ethernet cables, workstation NIC (including verifying it does not haev any Pwer Save feature enabled), server NIC, ports on the router/switch, etc.?
  • 0 in reply to D.Hart
    Looks like we got it fixed. We had checked all of that. Seemed to happen after the user got a new laptop running Windows 10 with a new installation. She moved to a different location with a new network port, and it was still happening. Nothing else was disconnecting though. We completely uninstalled Sage, reinstalled, checked AV, firewall, allowed through SmartScreen, resetup her SQL settings in ODBC, made sure it was set to use Windows authentication, set the power settings to High (thought I'd already done that, no powersave on NIC), and checked a few other things. Something seems to have fixed it. Weird. Thanks for your suggestions though.

*Community Hub is the new name for Sage City