Today I ran into a problem where very first MSISetProperty API call from our custom dll failed. Some search on Google led me to the following solution.
MSISetProperty internally make calls to some COM component. To execute any COM call on a machine, INTERACTIVE and SYSTEM accounts should be added to the default access list for all COM components. So the COM objects which do not use any specific custom security setting, uses these default security settings.
This default security setting was not enabled on the problem machine and that’s why the MSISetProperty call was failing. The problem is solved after putting in access permission for these accounts
No comments:
Post a Comment