Has anyone experienced this error, EAccessViolation, within automated web publishing? This has appeared in our log files after WebPublisher (6.3 - we've not got round to 6.4 yet) was unable to overwrite some previous timetables. It is fairly easily cured by restarting the server where WebPublisher is automatically running, but after around a month of automated web publishing the PF usage (Windows Server 2003 Standard R2) is not released and eventually runs out of space. Perhaps the two issues are related... though that's just a guess Any ideas? Chris |