Yet another damned fool question - Repair Database

[sologuitarist61]

I thought I had been at the Trainz lark long enough to know what 'Rebuild Database' is supposed to do, but I am getting some really strange things happening on my T:ANE install.

For example, last night I finished a session in which no downloads were made and only existing assets were used. Before closing T:ANE completely I did a 'Rebuild Database' with the result that I had 0 errors and 4 warnings. Today I have opened T:ANE and before I could get into the route it did a Rebuild Database with the result that I now had 40 errors and 1573 warnings - how can that be after last nights result, when nothing had changed?

Anyway I ran it three more times as I didn't believe the result. On the next run through the result had dropped to 4 errors and 1400+ warnings. I then ran it again and got the result 0 errors 1425 warnings. Encouraged that it was at least going the right direction, I ran it again and this time it was back to the original 40 errors and 1500+ warnings

I then closed it down and reopened it - again it did an automatic Rebuild Database but this time the result was 8 errors and 1573 warnings - different yet again..

Is this right? Seems very strange to me or have I missed the point?

 

[shaneturner12]

Might be worth checking that nothing's changed in the Settings box.

Shane

 

[sologuitarist61]

Might be worth checking that nothing's changed in the Settings box.

Shane

Thanks Shane, everything is as before.

As matter of interest I have just restarted it again and did a rebuild database with the result 0 errors and 2 warnings - it makes no sense at all.

 

[shaneturner12]

Without seeing a screenshot, it's difficult to tell.

Shane

 

[sologuitarist61]

Without seeing a screenshot, it's difficult to tell.

Shane

Not quite sure how to put a screenshot on here, but firstly what do you want to see

 

[JCitron]

Hi Richard,

If you have any faulty content, the repair process will report these as errors. You can see what faulty content you have installed by going to Manage Content, and change the filter to Faulty. Note: You may want to edit the filter by opening up the arrows and removing missing dependencies so you only see what is really faulty.

The reason, my hunch, you got two different quantities of faulty content is the database did validation after the repair. This was once that awful lengthy process that used to kick in on TS12, while now it's only a few minutes if that. Once the content was validated and indexed in the database, the program had the actual number of faulty items. In the old days, as if it was so long ago, we had to do part of this by hand by viewing errors and warnings with TS2010 and TS12. When we did this, it forced the database to update the status and removed the false errors. This process must be automatic now with T:ANE.

John

 

[sologuitarist61]

Hi Richard,

If you have any faulty content, the repair process will report these as errors. You can see what faulty content you have installed by going to Manage Content, and change the filter to Faulty. Note: You may want to edit the filter by opening up the arrows and removing missing dependencies so you only see what is really faulty.

The reason, my hunch, you got two different quantities of faulty content is the database did validation after the repair. This was once that awful lengthy process that used to kick in on TS12, while now it's only a few minutes if that. Once the content was validated and indexed in the database, the program had the actual number of faulty items. In the old days, as if it was so long ago, we had to do part of this by hand by viewing errors and warnings with TS2010 and TS12. When we did this, it forced the database to update the status and removed the false errors. This process must be automatic now with T:ANE.

John

Thanks John!