Set Server = CreateObject('ASIServer.clsServer') Instead, a couple steps later when the reference to the server component must be created: ErrSubject = 'Calling ClsServer ' There's no error code returned from the Coinitialize call, as I shouldbe seeing the 'CoinitializeSecurity Failed' message in this case. MS suggested replacing the RPC_C_AUTHN_LEVEL_NONE with RPC_C_AUTHN_LEVEL_CALL, but that's not sufficient. This worked just fine prior to the latest update to Windows which introduced issues documented by MS. MsgBox 'CoInitializeSecurity failed with error code: 0x' _ RPC_C_AUTHN_LEVEL_NONE, RPC_C_IMP_LEVEL_ANONYMOUS, _ LngHr = CoInitializeSecurity(ByVal API_NULL, -1, _ In order to get this working with the client, VB6 has to make an explicit call to CoInitialize: Dim lngHr As Long There are also entries in global dcom which grant Anonymous Login local and remote access so that callbacks between the client exe and activex server will function correctly. The global DCOM permissions on the machines are set to 'Connect' and 'Identify', the authentication on the server components is set to 'None', and the identity associated with the activex servers in DCOM has full admin rights on the machine in question.
There is a workstation component and two activex server components. I have an application which uses Activex servers (written in VB6 - no flames please).
