After a lot of searching, I found This Thread where someone had a similar issue, turns out to be an out of date custom component.
After a lot of searching, I found This Thread where someone had a similar issue, turns out to be an out of date custom component.