Greetings,

         I have run into a strange issue I am hoping someone out there can assist with or might have some tips to further troubleshoot the issue.  We have made customizations to various existing tasks and created new tasks for Sage 500 2017.  

         The modifications have been installed to various machines and operating systems with no issues.   However, recently we have now run into an issue on Windows 10 machines where any of the customized tasks will not launch and the tracker is recording an error 430 "class does not support automation" in the task's class method InitializeObject when it makes the call to DefaultInitializeObject (CAppInterface.dll).

         Standard Sage 500 tasks continue to work so it appears to be some sort of permissions issue.  Going along that line line of thinking and using one of the tasks developed with the SDK, a test system was set up and the following done:

• Logged in as Admin
• Turned off all virus checkers and Windows Defender
• Installed Sage 500 client using proper compatibility and administrative privileges.
• Copied the SDK developed tasks to the appropriate folder
• Using a command prompt with administrative privileges manually registered the ActiveX EXE using regserver command
• Restarted Sage 500 with Administrative privileges

         After doing all this, I was still receiving the error 430 when trying to start the task from the desktop.  A review of the CLIDs for CAppInterface shows the correct GUID expected by the task.  I also verified that registry entries were made for the SDK task I was testing with.

        Another thing we tried was to ensure the task was compiled on a 64 bit machine and that the references were pointing to the proper Sage folder.  Still no Joy.

        I even went so far as to spin up a Windows 10 VPC in Azure and test there to see if I could duplicate the issue, but I was unable to.  At this point, I am scratching my head trying to think of what the issues might be with these Windows 10 machines when it comes to allowing access to CAppInterface when starting a task.

        Any ideas or tips would be greatly appreciated.

Thanks