1 reply to this topic

[SanDiegoDeveloper]

We are having a problem that is particular to the new Windows Server 2003.

The code below adds a COM application in our setup and, after it completes on any platform (other than Server 2003), you can look in component services to find the new component and the property “Enforce access checks for this application” will be unchecked. Our script is then able to use these components.

The problem is, the same code will create the COM Application on a Server 2003 target and the property “Enforce access checks for this application” will be checked. Unless we set a breakpoint in the installer and uncheck that manually using Windows 2003 Component Services before the script attempts to use the component, the use of the component will fail and so also does our install operation.

Have there been any reports or suggested workarounds to this? Anywhere specific I should be looking?

Thanks,
Don Rasmussen
EOS International
Carlsbad, Ca.

function BOOL CreateCOMApplication( AppName, UserID, Password, CreatedBy, Description )
OBJECT oCOM, oApps, oApp;
BOOL bSuccess;
begin
try
set oCOM = CreateObject("COMAdmin.COMAdminCatalog");
set oApps = oCOM.GetCollection("Applications");

set oApp = oApps.Add;

oApp.Value("Name") = AppName;
oApp.Value("CreatedBy") = CreatedBy;
oApp.Value("Description") = Description;
oApp.Value("AccessChecksLevel") = 0;
oApp.Value("RunForever") = TRUE;

if ( UserID != "" ) then
oApp.Value("Identity") = UserID;
oApp.Value("Password") = Password;
endif;

oApps.SaveChanges;

bSuccess = TRUE;
catch
bSuccess = FALSE;
endcatch;

set oCOM = NOTHING;
set oApps = NOTHING;
set oApp = NOTHING;

return bSuccess;

end;

[SanDiegoDeveloper]

Looks like Server 2003 comes with many security options that default to "true". For this COM+ Object, the solution seems to be:

oApp.Value("ApplicationAccessChecksEnabled") = FALSE;