White Exclamation Mark in Red Button

[trainguy77]

When I'm loading a session, a white exclamation mark in a red button appears in the panel for the session I'm loading.
I can't get any info on it.
Does anyone know what this means?

 

[pware]

Does anyone know what this means?

The same icon but with a tan or tan-orange background means Faulty - usually "missing dependencies". I have never seen one with a red background. Could it mean a "more serious" fault?

What does Content Manager say about the session?

 

[trainguy77]

It could mean more serious fault. See my other post on Database Rebuild Problem.

 

[RetroRails12]

that Red Exclamation Mark Means FAULTY DEPENDENCIES and there is usually a Error Warning with it.. Clicking on it should bring you to the Download Station aka Content manager from there it will show the Dependencies for the route if any of them are marked Red or have the words Faulty with them then you have to find out what is wrong and Fix them. Easy Task to do.. I deal with this on a daily basis while building my mega route..

 

[trainguy77]

Thanks. Very helpful. For some reason when I clicked on it before nothing happened. But now it does. I see a lot information and possibilities. I'll work my way through.

 

[KotangaGirl]

I've seen this symbol most often in TRS19 when some 'update' in one of the myriad versions of TRS22 has broken something and somehow the fault has leaked down into TRS19. In my own situation I have found the red/white symbol impossible to get rid of, but fortunately it doesn't seem to be causing any great harm. Yet.

 

[schaffer]

Click on the icon should open content manager filtered on all of the assets in the route/session. You should be able to find the faulty object(s) in there

 

[JCitron]

I've seen this symbol most often in TRS19 when some 'update' in one of the myriad versions of TRS22 has broken something and somehow the fault has leaked down into TRS19. In my own situation I have found the red/white symbol impossible to get rid of, but fortunately it doesn't seem to be causing any great harm. Yet.

These can occur if it's a sub-dependency within the route or session such as an engine now showing a faulty dependency. The only way to find it is to use View dependencies recursively.

 

[trainguy77]

Thanks J Citron. I'm investigating following your insights.