{"id":32331,"date":"2023-03-14T15:07:10","date_gmt":"2023-03-14T15:07:10","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/sageaccpacerp\/?p=32331"},"modified":"2024-05-14T09:43:12","modified_gmt":"2024-05-14T09:43:12","slug":"possible-cause-for-issue-error-code-2147221164-class-not-registered","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sageaccpacerp\/2023\/03\/14\/possible-cause-for-issue-error-code-2147221164-class-not-registered\/","title":{"rendered":"Possible cause for issue: “Error code -2147221164 class not registered”"},"content":{"rendered":"\n

In Sage 300 ERP, user might come across some complicated error messages while opening screens (UI). In this blog we will discuss about one of the common errors while opening the customized screen or a third-party module screen.<\/p>\n\n\n\n

Many times, when standard Sage 300 screen is customized by the third party by adding some additional functionality in it. User might come across some issue while opening the customized screen. Refer below screenshot, where standard sage 300 OE entry screen is customized in some custom module where additional functionality is added into it. When user tries to open this customized OE order entry screen user get an error \u201cError code: -2147221164 Class not registered\u201d.<\/strong><\/p>\n\n\n\n

\"Image<\/a><\/center>\n\n\n\n

However, the error description is quite simple to understand, that the control\/ screen or rather OCX is not registered properly. And it needs to be register properly. But, sometimes screen might already have been got register properly, Or it can be registered with REGACC command.<\/p>\n\n\n\n

But sometimes this command or registering individual OCX manually will also not work as the possible cause for the error might be some DLL to which it is referring to is not getting registered properly.<\/p>\n\n\n\n

So below solution might help to resolve the scenario:<\/p>\n\n\n\n