Error: “Control is not properly installed” while opening customized screen in Sage 300 ERP

We have many situations where we customize the Sage 300 ERP screens and get the error while opening the customized screen “Control is not properly installed”. Sometimes this error occurs only for certain systems and the screen works fine on other systems. The reason behind this error is that the Sage 300 is unable to locate the CLSID specified for the control in the registry and the roto.dat file of the selected module.

New Stuff: Confirm On Print Preferences in Sage 300

We will take the example of the O/E Order Entry screen which is customized and is throwing an error “Control is not properly installed” while opening the screen from Sage 300 ERP Desktop.

We can investigate to check whether the cause of the error is due to the mismatched CLSID following below steps:

1. Open the registry (Run “regedit” command) and search for the control causing the error i.e. in our case “AccpacOE1100UICtrl”. Navigate to the CLSID of the control, the class id is available under Data column ({CAF35233-78CD-4852-BEDF-D01B323F953A}).

2.  Execute the “rotoedit.exe” available only if the Sage 300 SDK is installed. This executable is present under path “\Pluswdev\BIN\”.

3. Open the “roto.dat” file for the module i.e. OE module. Scroll to locate the control ID “OE1100” and click on Edit. The last part under the Module contains the CLSID present in the registry ({caf35233-78cd-4852-bedf-d01b323f953b}).

4. Compare the same with the CLSID of the registry and make sure that roto.dat contains the same ID as that in the registry and save the changes.

5. Reopen Sage 300 Company and the O/E Order Entry screen where you will be now able to open the screen and the error no more exists.

Alternatively, you can also check with the other solution as the cause of the issue may differ from system to system. Follow “Control is not properly installed” error in Sage 300 ERP.

So, this can be helpful when the developer cannot track the cause and all the permissions are granted correctly but the registry for some systems changed.

Also Read:

1. “Error code: 713, Class not registered” on opening customized screen in Sage 300 ERP
2. Error Occurred while Opening View
3. Error: Sage 300 ERP UI Container has stopped working message occurs when printing reports
4. Troubleshoot: Error while configuring the Sage 300 Web Screens
5. Database Error 49153 in Sage 300 ERP

About Us

Greytrix is one stop solution provider for Sage ERP and Sage CRM needs. We provide complete end-to-end assistance for your technical consultations, product customizations, data migration, system integrations, third party add-on development and implementation expertise.

Greytrix have some unique solutions of Sage 300 integration with Sage CRM, Salesforce.com and Magento eCommerce along with Sage 300 Migration from Sage 50 US, Sage 50 CA, Sage PRO, QuickBooks, Sage Business Vision and Sage Business Works. We also offer best-in-class Sage 300 customization and development services to Sage business partners, end users, and Sage PSG worldwide.

For more details on Sage 300 Services, please contact us at accpac@greytrix.com. We will be glad to assist you.