Weird DB Error for Web Mailil

[cVarz]

This is the error I get after logging into to web mail:

A fatal error has occurred:

DB Error: insufficient permissions

[line 108 of C:\Inetpub\vhosts\webmail\horde\lib\Prefs\sql.php]

Details have been logged for the administrator.


These are lines 103-108 of the SQL.php file:

/* Connect to the SQL server using the supplied parameters. */
include_once 'DB.php';
$this->db = &DB::connect($this->params, true);
if (DB::isError($this->db)) {
Horde::fatal($this->db, __FILE__, __LINE__);
}

My questions is the "include" statement for the file DB.php. Should that be in the same directory as the SQL.php file? If so, I am missing the file some how. If not, can someone please elaborate on what they think may be wrong.

Thanks in advance.

 

[futec]

We have the same problem after a failed upgrade from 6.5 to 7.0

We restored to 6.5 and this is the last problem we have...

I also don't understand why the horde database is almost empty...

This is my sql dump for the horde DB:

CREATE TABLE `horde_categories` (
  `category_id` int(11) NOT NULL default '0',
  `group_uid` varchar(255) NOT NULL default '',
  `user_uid` varchar(255) NOT NULL default '',
  `category_name` varchar(255) NOT NULL default '',
  `category_parents` varchar(255) NOT NULL default '',
  `category_data` text,
  `category_serialized` smallint(6) NOT NULL default '0',
  `category_updated` timestamp(14) NOT NULL,
  PRIMARY KEY  (`category_id`),
  KEY `category_category_name_idx` (`category_name`),
  KEY `category_group_idx` (`group_uid`),
  KEY `category_user_idx` (`user_uid`),
  KEY `category_serialized_idx` (`category_serialized`)
) TYPE=MyISAM;

CREATE TABLE `horde_prefs` (
  `pref_uid` varchar(255) NOT NULL default '',
  `pref_scope` varchar(16) NOT NULL default '',
  `pref_name` varchar(32) NOT NULL default '',
  `pref_value` longtext,
  PRIMARY KEY  (`pref_uid`,`pref_scope`,`pref_name`)
) TYPE=MyISAM;

CREATE TABLE `horde_users` (
  `user_uid` varchar(255) NOT NULL default '',
  `user_pass` varchar(32) NOT NULL default '',
  PRIMARY KEY  (`user_uid`)
) TYPE=MyISAM;
CREATE TABLE `turba_objects` (
  `object_id` varchar(32) NOT NULL default '',
  `owner_id` varchar(255) NOT NULL default '',
  `object_type` varchar(255) NOT NULL default 'Object',
  `object_members` blob,
  `object_name` varchar(255) default NULL,
  `object_alias` varchar(32) default NULL,
  `object_email` varchar(255) default NULL,
  `object_homeaddress` varchar(255) default NULL,
  `object_workaddress` varchar(255) default NULL,
  `object_homephone` varchar(25) default NULL,
  `object_workphone` varchar(25) default NULL,
  `object_cellphone` varchar(25) default NULL,
  `object_fax` varchar(25) default NULL,
  `object_title` varchar(255) default NULL,
  `object_company` varchar(255) default NULL,
  `object_notes` text,
  PRIMARY KEY  (`object_id`),
  KEY `turba_owner_idx` (`owner_id`)
) TYPE=MyISAM;

As you can see it is completely empty .

I assume no-one even Plesk hasn't an answer for this problem, to comfort you your not the only one having this problem, is has been posted many times here and I never see any replies

 

[cVarz]

Two responses back from them. None of which offered a reason why they released a product that was not fully tested.

1) Upgrade to Server 2003. ( Thanks, let me spend $800.00 so your program works )

2) Wait until an official release of 7.0 comes out for Server 2000. ( another great anwser ).

I am glad they got their money for the program though, it will be the last $$ from me or anyone I come in contact with.

 

[futec]

Well I dont think a upgrade will work, we do run on Windows 2003 Server.

Another great option the upgrade to 7.0.

We tried the upgrade from 6.5 to 7.0 that was great fun

Plesk doesn't upgrade like all other software in the world, let me explain the steps Plesk does.

1: Create backup of 6.5 (100% complete)
2: Remove Plesk 6.5 (weird, but ok, 100%)
3: Instrall Plesk 7.0 (100%)
4: restore backup:

While restoring at 71% it says: A record not found for domain.com. And then you have 2 buttons
1: Quit
2: Abort

Well isn't that great! Now you can manually remove 7.0 and reinstall 6.5 and cross your fingers that it will restore on 6.5 again.

So your server is all messed up 6.5 to 7.0 and back to 6.5 and after restoring webmail doesn't work at all anymore...

To bad this beautiful produkt has some leaks in it