Problem upgrading from 3.0 to 3.4.8

[jesrig]

We recently moved our drupal 6 site to a new hosting server and we needed to do a CiviCRM update, as version 3.0 is not compatible with PHP 5.3 (on the new server). The issue was that users could not be created.
I tried upgrading from 3.0 to 3.4.8 with these docs https://wiki.civicrm.org/confluence/display/CRMDOC40/Upgrade+Drupal+Sites+to+3.4
and the upgrade did not work correctly. Below are the issues I encountered:

I had an error where it said it did not find a column locale_custom_strings in table civicrm_domain. In an attempt to get rid of the error, I added the column and the error went away.

I was able to run the update now, but now I got the next error when trying to create a user:
require_once(CRM/Contact/Page/View/DashBoard.php): failed to open stream: No such file or directory in/[site_path]/sites/all/modules/civicrm/CRM/Core/Invoke.php on line 201.

This file did not exist on the version 3.4 module, so I found it in the 3.0 module and copied it over. This error now went away.

However, while I was able to create a user, whenever I save I get an error of:
Database table not found
and the php log says:
PHP Fatal error:  Uncaught <table border="1" cellspacing="0">\n<tr><td colspan="3" bgcolor="#ff9999"> <b>PEAR_Exception</b>: DB Error: no such table in <b>unknown</b> on line <b>unknown</b></td></tr>\n<tr><td colspan="3" bgcolor="#ff9999">- <b>DB_Error</b>: DB Error: no such table in <b>unknown</b> on line <b>unknown</b></td></tr>\n<tr><td colspan="3" bgcolor="#aaaaaa" align="center"><b>Exception trace</b></td></tr>\n<tr><td align="center" bgcolor="#cccccc" width="20"><b>#</b></td><td align="center" bgcolor="#cccccc"><b>Function</b></td><td align="center" bgcolor="#cccccc"><b>Location</b></td></tr>\n<tr><td align="center">0</td><td>CRM_Core_Error::exceptionHandler(Object(DB_Error))</td><td>unknown:unknown</td></tr>\n<tr><td align="center">1</td><td>call_user_func(Array, Object(DB_Error))</td><td>/{site_path}/htdocs/sites/all/modules/civicrm/packages/PEAR.php:931</td></tr>\n<tr><td align="center">2</td><td>PEAR_Error->PEAR_Error('DB Error: no suc&hellip;', -18, 16, Array, 'DELETE FROM civi&hellip;')</td><td>/var/www/ in /{site_path}/htdocs/sites/all/modules/civicrm/CRM/Core/Error.php on line 532, referer: http://{site_path}/admin/user/user/create


The reason why we aren't upgrading to hte latest version of 4.4 is because its not supported for Drupal 6 (and we don't want to make the upgrade to Drupal 7 right now.) Does anyone have any ideas where I might have gone wrong?

[Hershel]

CiviCRM is community supported for Drupal 6, including version 4.4.4, so there is no reason not to upgrade to that.

Regarding what you did wrong, it's not recommended to manually change the database schema. If you have a schema error, try the http://wiki.civicrm.org/confluence/display/CRMDOC/Ensuring+Schema+Integrity+on+Upgrades procedure.