I've done only one project. In the end, I was co-ordinating the project. We had around 50 active users at the peak. We had fair share of above types of error. Fortunately, the project was controlled by some terrific guys (giants) in the Netherlands. Invariably, they'd help us to solve almost everything. The reason for this long description, I just reply by the gut-feel and some experience which I had on the project.
1. When the user has remained inactive for a longer duration, chances are that other users have updated, modified and deleted elements in the database. Now when the user becomes active and does some action which accesses random data (e.g. running clash, add all within vol etc.) there are floaters around due to unsaved data. This causes the error.
2. The best pointers in these cases, lie with the users. Tell your users, to save screenshots every time they get such errors. In the beginning it seems futile but helps in playing the investigator. Tell them to list it along with MDB, action and module.
3. The databases, need to be compact in size (I don't remember the size limit told by one of those guys!) but you need to carry out db maintenance periodically if you are reaching the peak of project.
Always read those logs. I almost got killed (figuratively of course :)) by not heeding towards the logs that appear. It was clash manager. But I guess, the game remains much the same. All the best!
I've done only one project. In the end, I was co-ordinating the project. We had around 50 active users at the peak. We had fair share of above types of error. Fortunately, the project was controlled by some terrific guys (giants) in the Netherlands. Invariably, they'd help us to solve almost everything. The reason for this long description, I just reply by the gut-feel and some experience which I had on the project.
1. When the user has remained inactive for a longer duration, chances are that other users have updated, modified and deleted elements in the database. Now when the user becomes active and does some action which accesses random data (e.g. running clash, add all within vol etc.) there are floaters around due to unsaved data. This causes the error.
2. The best pointers in these cases, lie with the users. Tell your users, to save screenshots every time they get such errors. In the beginning it seems futile but helps in playing the investigator. Tell them to list it along with MDB, action and module.
3. The databases, need to be compact in size (I don't remember the size limit told by one of those guys!) but you need to carry out db maintenance periodically if you are reaching the peak of project.
Always read those logs. I almost got killed (figuratively of course :)) by not heeding towards the logs that appear. It was clash manager. But I guess, the game remains much the same. All the best!
