Strange system crashing (AREV Specific)
At 14 OCT 2004 05:18:42AM Craig X Tildesley wrote:
We have a source record which is just short of 64k. It's about 64503 bytes which should really be ok. However, when attempting to install the update with this our system crashes with a windows window giving us a termination code. This happens in one of our testing environments but not our development environment which works fine. Attempting to do a listmedia on the upgrade also causes the arev session to hang, but only from the network drive that the test system is on. I've dumped the file and the records length is 65531 with the long program name. A clue certainly but it seems rather odd that it dies on one system and not the other.
The only remaining answer, as far as I can see, must be in the setup of the NT service which is running on both servers. Can someone help?
At 14 OCT 2004 02:41PM Don Miller wrote:
I've seen AREV crash with records just over 64000 bytes. Remember to include the length of the key plus the overhead bytes in calculating the size of a record.
Don
At 15 OCT 2004 10:27AM Hippo wrote:
Sorry, I don't know the answer.
Does the different handle length cause the difference? …
do you try mimic the test environment path in development path?
I mean if test path is f:\dir1\dir2\dir3\bla,
the development dir should be c:\dir1\dir2\dir3\bla (for this experiment).
In all cases, avoid being on the 64k edge.