0

Developing an ActiveX DLL in VB6 for ASP on my development XP - in the VB environment everything works well - no problem to late bound instantiate the DLL by CreateObject (I don't work with GUID).

Under ASP I always get the 438 error - although it's on the same machine, under my super-user with all privileges (I gave the IUSR_machine the highest privileges).

I have already burned three days and did not find a solution. I hesitate to upgrade IIS because I do all my development on this machine and never had a problem like this (e.g. "never change a running horse")

Maybe someone can give me a link how to locate the resource that IIS thinks is missing. In DependencyWalker I have IESHIMS.dll and WER.dll missing but according to tyranid this can be ignored. I know that Sysinternal's REGMON can do this job - but how to filter ?

Thank you for any hint - if there is no other possibility I'll upgrade IIS.

Alfabravo
  • 7,354
  • 6
  • 45
  • 79
Meiki1964
  • 35
  • 2
  • 8
  • Are you sure it's the CreateObject that is giving you this error? This is not an error one would expect from CreateObject. Regmon and Procmon (both from sysinternals) can help debug object creation errors. A good staring point is to search for the CLSID of your object. You will find it in your registry under HKEY_LOCAL_MACHINE\\Clsid. – GTG Nov 03 '11 at 19:45
  • Good question - but I have already checked that : it does not execute the first instruction of the Class Initialization - seems like the Class Init pulls some other classes and one of them is OK in the VB environment but not in ASP. Regarding Regmon - what filter do you suggest - the CLSID ? – Meiki1964 Nov 04 '11 at 01:34
  • When using Regmon I usually start with no filters, just search for the CLSID. I sometimes add filters to exclude noise from some services (e.g. virus control). One thing you should look at is the Class_Initialize event in the object you are creating. – GTG Nov 04 '11 at 08:48
  • @GTG - what is your opinion about upgrading IIS on the development machine ? On the production machine I run IIS V6.0, but for project internal reasons I cannot switch to production until everything over here runs smooth. On the other hand I have a lot of projects on the development machine with IIS V5.1 which make no problems at all. – Meiki1964 Nov 04 '11 at 11:10
  • I guess that since you are using ASP, this will always be late-bound (using CreateObject() is irrelevant in this situation, although I take it that this is Server.CreateObject() ?). Since you are having problems with Class_Initialize, perhaps you could give us the code, with annotations? – Mark Bertenshaw Nov 04 '11 at 11:28
  • Uff - lot of work to strip down to the essential. Seems to me that with half the effort I can give a try on the production server. Or upgrade to IIS V6 - I'll keep you guys updated. – Meiki1964 Nov 04 '11 at 13:33
  • @Mark : interim report : same error on the production machine – Meiki1964 Nov 05 '11 at 19:52
  • *** Problem solved *** For reason I cannot reproduce a procedure declaration was missing in the class module - Thank you for your comments and patience - seems time for me to retire (;-) – Meiki1964 Nov 06 '11 at 09:10
  • 1
    @Meiki1964, FYI, if you've solved your own problem, you should post your solution as an answer and mark that answer as accepted by clicking the checkmark. – Cheran Shunmugavel Nov 06 '11 at 19:29

0 Answers0