Recently a VB 6 application using .NET 1.1/2.0 components stopped working on my companies XP machines. The IT department was installing Windows patches at the time, so I'm wondering if anyone has heard of an update breaking VB 6/.NET interop?
Asked
Active
Viewed 342 times
8
-
5Not that I know of. If you post some more details about the problem, maybe we could help track down the cause? – MarkJ Sep 24 '10 at 18:27
-
There was a security patch for .Net 2.0 that affected how errors are being raised in both .net 1.1 and 2.0. There did not break my COM interop but I did more errors across COM. – Gary Kindel Jan 28 '11 at 21:17
-
That might have been it, as the old components were definitely written in .NET 1.1. – Jonathan Allen Jan 30 '11 at 19:45
-
1I don't know about this in particular, but Windows updates frequently break COM component registrations, causing software to need to be reinstalled. Usually, re-installing the broken program or identifying and manually re-registering the component using regsvr32 fixes the problem. – Steve Jorgensen Feb 14 '11 at 08:48
1 Answers
1
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.
Erik A. Brandstadmoen
- 10,430
- 2
- 37
- 55