Quote:
Originally Posted by Getch
That sounds like a similar problem someone had. Basically, the web server you are on has a limit on the CPU one process can eat up. Running the development report hits that CPU limit, and the server kills it. It gets to about 5200, and it gets killed. The date of the develoment report is updated last, so that is why it is not updated.
I should be releasing a quick update to my utilities soon, and I will split the development report update into two actions, which should hopefully not hit the CPU limit on these web servers. Can't tell you win as for the next week or two I am swamped with holiday "fun".
|
Well, that makes total sense. I'll look forward to the update. Thanks again!