IIS and Object Loading 1

[oisin]

Hi,

I am using an ActiveX DLL in my ASP script (a wrapper over another ActiveX DLL whcih uses Winsock to talk to a database on a remote port). I instantiate it, use it and then destroy using the 'set obj = nothing' command. The problem I have is that after an uncertain amount of hits (usually around 140), it refuses to connect to the database (or rather the parent ActiveX DLL refuses.) I wrote a test program in VB to use the wrapper DLL and it will keep on connecting until the cows come home. This leads me to believe it has something to do with the way IIS handles objects. My head is wrecked with this one so if anybody has any suggestions, no matter how wild or madcap, I would appreciate them a lot,

Thanks

Oisín

 

[DomPedro]

I've found that the IIS Exception Monitor is pretty useful when trying to find out what's going wrong with a web application that uses external DLLs. Try :

http://msdn.microsoft.com/library/default.asp?URL=/library/en-us/dniis/html/ixcptmon.asp

Might help you.

 

[oisin]

Cheers DomPedro, I am using it now, hopefully it will help me solve the problem

 

[DomPedro]

Try to make sure that you are using debug versions of any of the problem DLLs and there's an option somewhere to download the symbols files for IIS, which makes reading the logs it producing much easier.
Good luck.

 

[shax]

Does anyone know where I can download the symbols for Exception Monitor as most of MS' links dont work anymore due to their unthoughtfull web redesign. (are they on any MSDN cds?)

Can I use version 7 on an NT box, cant download 6 from this link:

http://msdn.microsoft.com/library/default.asp?URL=/library/en-us/dniis/html/ixcptmon.asp

Thanks.

 

[DomPedro]

Exception Monitor should give you the option to download the symbols (one 61Mb file), but I'm not sure where it gets it from.

 

[DomPedro]

Version 7.1 doesn't appear to give you the option anymore, whereas version 6 did. Typical.

 

[DomPedro]

One last update on this (i've got work to do), MSDN's Using Microsoft debuggers provides this info :

To install symbol files for Windows 2000

Make sure you have at least 500 MB of available space on the disk drive of the host machine.
Insert the Customer Support Diagnostics CD.
Click on Install Symbols.
Select either Install Retail Symbols (free build) or Install Debug Symbols (checked build). The symbols must match the version of the operating system being debugged.
Enter the path where the symbols are to be stored, or accept the default path. The default path is %windir%\symbols.

To install symbol files for Windows NT 4.0

Make sure you have at least 450 MB of available space on the disk drive of the host machine.
From the command prompt, go to the \support\debug folder on the Windows NT 4.0 product CD-ROM.
Run the ExpndSym command. ExpndSym requires two command line parameters, Source_drive and Target_folder. Source_drive is the CD-ROM drive. Target_folder is where you want the symbol files installed.
A typical example of the use of the tool might look like the following:

expandsym d: c:\winnt
In this example, the symbols will be placed in c:\winnt\symbols (not in c:\winnt itself).