This week I’ve been working on a case from a customer who was migrating his web application to Windows 2003, and while on the old servers (Windows 2000) and on his development machine everything was working fine (as usual š), after deployment on the production server he got a nasty “ActiveX component can’t create object” errorĀ message, and was not able to fix it. The troubleshooting started from the usual and maybe most obvious possible causes (component registration, permissions etc…), but we soon realized the problem was not that obvious as we expected. The application was made by a custom ActiveX VB6 object which internally referenced other custom dlls and msrdo20.dll; this was then embedded into a .aspx page to show some use interface in IE to the end user. The customer sent me his application to try to reproduce the problem on my machine, and at the first run I got exactly the same error message he reported! Ah Ah! I got you! šĀ On my machine IĀ got rid of it registering all the involvedĀ components, something we already tried on the phone, butĀ worth another check.Ā I came back to the customer and set up an EasyAssist session to carefully check his…
Automate Everything