Found N Tickets Search page HTML display error

Hello All,

I have a instance of RT 3.6.7 which some how has a really weird error
when I click on the default RT-At-A-Glance sections titled:

10 newest unowned tickets
or
10 highest priority tickets I own

Basically you click on the title “10 highest priority tickets I own"
and you get taken to the basic search page. Which displays every above
bar with “New Search · Edit Search · Advanced · Show Results · Bulk
Update” on it shows properly but the section between that bar and the
"don’t refresh this page” as well as other “footer” information shows
up like this:

a href id id a TITLE
/rt/Ticket/Display.html?id=58844 58844
/rt/Ticket/Display.html?id=58843 58843
/rt/Ticket/Display.html?id=58842 58842
/rt/Ticket/Display.html?id=58733 58733
/rt/Ticket/Display.html?id=58132 58132
/rt/Ticket/Display.html?id=56542 56542
/rt/Ticket/Display.html?id=56386 56386
/rt/Ticket/Display.html?id=54459 54459
/rt/Ticket/Display.html?id=44447 44447
/rt/Ticket/Display.html?id=30663 30663
/rt/Ticket/Display.html?id=30327 30327
/rt/Ticket/Display.html?id=26297 26297
/rt/Ticket/Display.html?id=19985 19985
/rt/Ticket/Display.html?id=14734 14734
/rt/Ticket/Display.html?id=14277 14277
/rt/Ticket/Display.html?id=12996 12996
/rt/Ticket/Display.html?id=12660 12660
/rt/Ticket/Display.html?id=12659 12659
/rt/Ticket/Display.html?id=12513 12513
/rt/Ticket/Display.html?id=10937 10937
/rt/Ticket/Display.html?id=10936 10936
Page 1 of 1

This RT 3.6.7 instance is using RT2-To-RT3 migrated data and the
following settings are set for:

RT::DefaultSearchResultFormat ‘id/TITLE:#’,
Subject/TITLE:Subject’,
Status, QueueName, OwnerName, Priority, ‘NEWLINE’, ‘’,
Requestors’, ‘CreatedRelative’,
ToldRelative’,
LastUpdatedRelative’,
TimeLeft

RT::WebBaseURL http://rt.server.com:80
RT::WebImagesURL /rt/NoAuth/images/
RT::WebPath /rt
RT::WebURL http://rt.server.com:80/rt/

What is most maddening is that in a different server using a different
database but using the same data, settings and even rt files this does
not happen.

Has anyone seen this error before? A search of the Mailing list shows
similiar errors but not a fix that I found applicable.

Thanks,

Brian