I'm getting two recurring errors in the Lite version. I'm using the Server.Execute on track.asp feeding to SQL Server 2000
1. Script timeout on track.asp
2. clslog.asp Line 312 Header error. the http headers are already written to the client browser. any http header modification must be made before writing page content
#2 is no big deal, but #1 is sending my processor to 100% for the duration of my timeout (which I lowered from the default 90 seconds to 20 to cope with this). While my processor is pinged, it serves web pages about as fast as dead snail.
I like Meta A LOT, but I can't deal with this script timeout which seems to occur about a dozen times a day or more.
Any idea what's getting stuck and how to fix it?
www.SFReader.com
2 Errors, 1 BAD
Pretty weak that you can't reply to my error post. Makes it easy to decide on whether or not to get the pro upgrade.....
www.SFReader.com
2 Errors, 1 BAD
I generally respond to all posts if someone doesn't beat me to it. I didn't see your original post which is why I never responded. I'm disregarding the "weak" comment.
There are two solutions to the HTTP header problem: place the tracking code above the opening tag or enable buffering in IIS or on each ASP page. See this page for more info:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q229657
Regarding the script timeout error, do you know what the script timeout setting is on your server? (How many seconds?) How much traffic does your web site get? Is it in a shared hosting environment? Is the SQL Server on the same machine? This may be a web server performance issue, database issue or a lot of other things. Solving this problem requires more detail about your exact web hosting setup.
~Chad