pepr
asked on
Can Win2003 restrict the rights to call a COM method? (C++ and simple component created by Visual FoxPro 6)
This is a link to the 500 point question https://www.experts-exchange.com/questions/22046531/Can-Win2003-restrict-the-rights-to-call-a-COM-method-C-and-simple-component-created-by-Visual-FoxPro-6.html
Sorry, if it is not the right channel. However, I need someone who knows Windows, C++, COM and possibly FoxPro...
Summary: We have observed a situation, when the application can create instance of the component but it fail when a method of the component is called. It happens when the application is executed on one specific Windows 2003 R2 Small Business Server. However, it runs on another Win2003 SBS without problems. Are there any rights that could restrict calling methods of components?
[detailed description, code snipets and URL to full sources are shown in the linked question]
It seems that Windows 2003 can restrict calling the component somehow. However, I am completely stupid in this area. We run such component and the application several years on say hundreds computes (servers and desktops) and nobody reported the problem. It could be the case that the problem is well known and they have better administrators to set the rights. Could you help, please?
Claim your points also here to clean the topic after being solved.
Sorry, if it is not the right channel. However, I need someone who knows Windows, C++, COM and possibly FoxPro...
Summary: We have observed a situation, when the application can create instance of the component but it fail when a method of the component is called. It happens when the application is executed on one specific Windows 2003 R2 Small Business Server. However, it runs on another Win2003 SBS without problems. Are there any rights that could restrict calling methods of components?
[detailed description, code snipets and URL to full sources are shown in the linked question]
It seems that Windows 2003 can restrict calling the component somehow. However, I am completely stupid in this area. We run such component and the application several years on say hundreds computes (servers and desktops) and nobody reported the problem. It could be the case that the problem is well known and they have better administrators to set the rights. Could you help, please?
Claim your points also here to clean the topic after being solved.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.