This happens when a spare part has a picture set but the physical image file is missing, most likely due to it having not been replicated properly.
This is fairly normal, but the fact that it throws an error is a bug. Fixed in 2.655.5919 (Mar 16 2016) and higher.
TM Master Common Errors
Object reference not set to an instance of an object - SetSparePartImage
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article