Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
DLL's on Win 2003 Server with IIS 6
Message
 
To
05/08/2005 09:11:48
General information
Forum:
Visual FoxPro
Category:
Internet applications
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows Server 2003
Network:
Windows 2000 Server
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01038863
Message ID:
01038940
Views:
16
I had something similar when one of our customers moved from 2k to 2k3 iis6. one of my dll's was not connecting into our backend properly after the move. i added in some code in various places that connected to a logging table and added in a record when it had got so far. i was intending to use this to tell me where exactly it was going wrong, but this actually fixed the problem so i left it there! i didn't change a single lone of functional code bar adding in about six instances of
sele logtable
append blank
repl field1 with "starting"
since it fixed the problem i havn't revisited it but know that i should:)
Slán
~M

>I am having trouble with an ASP.NET application running on Win 2003 Server (SP1) with IIS6. The application runs fine with IIS5 on a W2000 Pro machine. Switching IIS6 to run in IIS5 isolation mode doesn’t help. The web app uses a dll which is built with VFP 8 to gather and store data from/to a VFP database. Each call to the dll creates an instance in VB, gets/stores data, and then closes the object. However, using IIS6, after about 25 calls to the dll on various pages, the object created doesn’t work correctly. Objects created inside the dll disappear shortly after they are created. The VFP code checks to make sure the object is there and then before it can use the object it is gone and an ‘object not found’ error occurs. I cannot find any setting for IIS that ‘fixes’ the problem or makes it worse or better in any way. Both machines are using version 1.1.4322 of the .net framework.
>Thanks for any help or suggestions.
Go raibh maith agat

~M
Previous
Reply
Map
View

Click here to load this message in the networking platform