There might be a lot of reasons, but a some brains storm ideas might be: a) New type of data (well formed or not) is feed to the script, and it cant handle this type of format. b) New functionality has been added and these function can't handle either valid or invalid data formats c) Old functions has been changed and trigger an error when certain kind of data is feed to them. d) time out problems e) solar activities f) hacking activities has compromised parts of the system g) data has, become inconsistent in the db by some reason I would suggest that you insert debug code in your scripts that validates data and in addition prints out a trace of function calls, to be able to get an answer on the following question: Does the error always emerge when this particular part of code is executed, or does it happen only in certain cases? If it happens in only certain cases try to isolate the set of data that causes the error to emerge, and then back track to the particular code segment that causes the script to fault. If it always happens review your (entire) code carefully once again, that is including the full call stack. Kind regards, //Anders On Mon, 2003-09-22 at 13:05, Francesco wrote: > My platform: W2000 Server SP4 with latest MS vulnerability patches applied. > Apache 1.3.22, PHP 4.2.2. > > Since a couple of weeks I have this very nasty problem: Intermittently PHP > is not parsing a valid script. It spits out an error regarding some syntax > error in the code, but the code is in fact perfectly ok. In fact if I reload > the page the script executes normally. > > This happens (unfortunately) quite often now, albeit randomly. I would say > that in 10-15% of script executions it happens. > > Anyone has a clue of what might be wrong? > > Thanks in advance > > Francesco -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
