Did VB 6/.NET interop recently get broken by a Windows update? Did VB 6/.NET interop recently get broken by a Windows update? windows windows

Did VB 6/.NET interop recently get broken by a Windows update?


Are you running the COM+ components as proxies against other servers? If so, I've had problems before when installing e.g. SP2 for Windows 2003 server, in that the COM+ settings (Component Services, root node) have had the "remote activation" security setting permission missing after the update. Don't know if this is your problem, though.