Hi, I'm using DCOM. The server doesn't provide launch access right to clients (it runs on Windows 2003 SP1). Server object is implemented as windows service (singleton). If service is running, clients can activate server DCOM object and work with it. But if service is stopped, I see errors on server every time some client tries to activate server object: The machine wide limit settings do not grant Remote Launch permission for the COM Server application with CLSID {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} to the user Domain\user SID (S-1-5-XX-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX-XXXX). This security permission can be modified using the Component Services administrative tool. But I don't want to provide launch access right to clients. Is there a way to suppress such error messages on server? I can suppress client error messages using CLSCTX_NO_FAILURE_LOG flag of CoCreateInstanceEx. But how to suppress them on server? regards, Michael A.
Hi Michael, > The machine wide limit settings do not grant Remote Launch permission > for the COM Server application with CLSID > {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} to the user Domain\user SID > (S-1-5-XX-XXXXXXXXXX-XXXXXXXXXX-XXXXXXXXXX-XXXX). This security > permission can be modified using the Component Services administrative > tool. > > But I don't want to provide launch access right to clients. Is there a > way to suppress such error messages on server? I can suppress client > error messages using CLSCTX_NO_FAILURE_LOG flag of CoCreateInstanceEx. > But how to suppress them on server? Are you asking how to suppress the failure logs without modifying client code? I've been wondering about this as well, but I came to the conclusion that it's not doable, because the server is not involved in the activation. If the client has no access to the server DCOM application, the server code is never involved -- the COM runtime makes the decision and logs the message. So I think your best bet is to try and change your client if you can. - Kim
