>>Looks like I already had a 'SET REPROCESS TO 1000' in there. I added the suggested 'SET REPROCESS TO 1000 SYSTEM' but it also had no effect on the error count.
>>
>>On reflection I don't see why either of the above would have an effect anyway because:
>>(a) in my case I'm not attempting to lock anything and
>>(b) the default for SET REPROCESS is an indefinite wait which would be *less* likely to generate an error.
>>
>>Anyway I also tried 'SET REPROCESS TO 1' and 'SET REPROCESS TO 0' - neither affected the outcome.
>>
>>I looked at the IIS logs - sometimes when the 500 return code occurred the sc-win32-status was 64 ("Specified network name is no longer available", I think) but this code also appears sometimes when the sc-status was 200 so I don't suppose it's relevant....
>
>Yes, I also remember having seen something about this a while ago when we started to troubleshoot this situation. I also didn't understand the relation of that and the current situation. I also cannot understand why this could have resolved the issue for the person who mentioned that note on the bug tracker. Maybe that was a different issue.
AFAICS, if you are updating and need a record lock then the 'REPROCESS' setting is relevant but setting it to 200 would force an error if no lock was achieved - as against waiting indefinitely (which is the default). Seems like a question of choosing the lesser of two evils - leave it at 0 and you could clog up the server; set it to 200 and the update might fail.....
Regards,
Viv
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only