Tom
|
| Posted: 09/18/2002, 6:23 AM |
|
I've read thru several threads that seem to be related to this but I need a clue from someone. My CC developed ASP2 works fine on my XP server but any CCS generated ASP3 just hang and never respond in the browser (I don't even get an error message or a timeout).
These projects use the custom connection string Provider=Microsoft.Jet.OLEDB.4.0; ... to a ms access database.
I searched the help and community and looked to see if this error was a Windows NT permissions problem was applicable http://support.codecharge.com/files/CodeChargeFAQ.html#_Toc517263838 but I'm not sure I fully understand if it is the problem and how to fix.
When the page is brought up in the browser, I see a ldb file created in the directory (this directory houses both the database and the asp code) when the page is called up. And the anonymous internet user IUSR_machine name has read and execute permissions. I'm confused in that my asp2 works fine but asp3 does not. Is there something that I need for my MS webserver to load to run asp3 code?
I've also tried to follow the message thread 'I cant stand it any more...database problem!' http://www.gotocode.com/disc_viewt.asp?mid=8874& on websharing but I'm not sure how those folk solved their problem.
Anyone have a clue or can I give you more info.
Desparately need help.
|
|
|
 |
Tom
|
| Posted: 09/18/2002, 9:20 AM |
|
I got my problem solved by Code Charge support and wanted to post the solution here.
CC support got back to me in less than 20 minutes (attaboy!)
My Xp machine has norton antivirus on it (I had just reimaged my pc). CC referred me to http://www.aspfaq.com/show.asp?id=2180. On that site was this info:
Why does FileSystemObject hang all of a sudden?
5,407 requests - last updated Tuesday, July 2, 2002
--------------------------------------------------------------------------------
Likely, you (re-)installed or re-configured Norton Anti-Virus, and as a result, a call within ASP to OpenTextFile hangs and/or other methods stop responding. This program has an option called 'script blocking' which, among other things, prevents FileSystemObject from working on the local file system. With the default setting, Norton raises a 'prompt'... and sits there waiting and waiting for a response from ASP (which it can obviously never get). To stop this from happening, go to Norton's Options screen, click on 'Script Blocking' and uncheck 'Enable Script Blocking'...
Keep in mind you shouldn't be running client applications like this on a commercial web server... hopefully this issue is only affecting your workstation!
There is more information available from Microsoft and Symantec on this issue:
Microsft KB #Q295375
Symantec KB #2001031311101006
|
|
|
|
|
