Hey y'all,

My apologies if I'm wasting anyones bandwidth...

I've recently (within the last week) patched/upgraded our SugarCRM installation from 5.0 -> 5.1 via the Upgrade Wizard, and the upgrade appeared to work as expected. However, I've been flagged that Accounts no longer have their Contacts linked to them, and I verified this to be the case. I don't know what else is going to rear it's ugly head, but Spidey Sense says that something went amiss during the upgrade...

Here's the details (per the POST request for help how-to):

ENVIRONMENT:
-----------------------
Operating System : Fedora 7
Sugar Version & Edition : Community 5.1
Category : (Accounts, Contacts - so far)
PHP Version : 5.2.6
Database : MySQL 5.0.45
Web Server : Apache 2.2

Steps To Reproduce:
------------------------------
The steps to reproduce are simply going to the Accounts page and it renders with no Contacts, History, etc that were previously linked to the Account. The individual modules all appear to function without issue within their respective page, however...

Error Message(s)
------------------------
Notice in http error log is as follows (after running Diagnostics):

[Wed Oct 08 11:37:40 2008] [error] [client 172.16.13.1] PHP Notice: Undefined index: dbType in /path-to-applications/SugarOS/modules/Administration/DiagnosticRun.php on line 656, referer: http://www.domain-name.org/appdir/in...ion=Diagnostic
[Wed Oct 08 11:37:40 2008] [error] [client 172.16.13.1] PHP Notice: Undefined index: len in /path-to-applications/SugarOS/modules/Administration/DiagnosticRun.php on line 657, referer: http://www.domain-name.org/appdir/in...ion=Diagnostic
[Wed Oct 08 11:37:40 2008] [error] [client 172.16.13.1] PHP Notice: Undefined index: comment in /path-to-applications/SugarOS/modules/Administration/DiagnosticRun.php on line 658, referer: http://www.domain-name.org/appdir/in...ion=Diagnostic

It appears there's an indexing issue w/ MySQL. The database server is physically located on another server in the domain - but this I'd doubt is the issue. It's been running like this for a coupla years without issues. I went to install the latest patch for 5.1.0a to correct things and that's what appears up in the apache system logs. I think things got Squirrely on the 5.0.0f to 5.1.0 upgrade process, but again everything appeared to be functioning normally post-upgrade...

We're at a stand-still here and dead in the water, can anyone be of assistance or point me in the direction where I could ferret out the information to correct this issue(s)? Any and all input is greatly appreciated. I'm at a loss...

Thanx so much in advance to everyone for their time and help regarding this matter...