GPMSWiki/AdministratorDocumentation/ProblemsAdministratingGPMS: Difference between revisions
Jump to navigation
Jump to search
imported>LutzKrause No edit summary |
m (11 revisions) |
||
| (4 intermediate revisions by one other user not shown) | |||
| Line 4: | Line 4: | ||
In this page you can find reasons for problems that frequently occur while managing the GPMS. | In this page you can find reasons for problems that frequently occur while managing the GPMS. | ||
* If you encounter an error message like ''DBD::mysql::db do failed: Table 'table_name' doesn't exist at /vol/gpms-intern/projectmanagement/share/perl/'' while adding a Member or a new DataSource::DB to a Project, the current Tables of the Database do not match the Rights/Privileges that where defined for the Project_Class of | * If you encounter an error message like ''DBD::mysql::db do failed: Table 'table_name' doesn't exist at /vol/gpms-intern/projectmanagement/share/perl/'' while adding a Member or a new DataSource::DB to a Project, the current Tables of the Database do not match the Rights/Privileges that where defined for the Project_Class of that Project. The reason might be that someone has deleted a table for which privileges where defined or privileges where defined for a table that never existed. To solve the problem update the Roles and Rights for that Project_Class to adapt the defined privilege to your current database scheme and make sure that all required tables exists in the database. | ||
Author: [http://www.cebitec.uni-bielefeld.de/~lkrause Lutz Krause] | Author: [http://www.cebitec.uni-bielefeld.de/~lkrause Lutz Krause] | ||
Latest revision as of 07:16, 26 October 2011
Problems while administrating the GPMS
In this page you can find reasons for problems that frequently occur while managing the GPMS.
- If you encounter an error message like DBD::mysql::db do failed: Table 'table_name' doesn't exist at /vol/gpms-intern/projectmanagement/share/perl/ while adding a Member or a new DataSource::DB to a Project, the current Tables of the Database do not match the Rights/Privileges that where defined for the Project_Class of that Project. The reason might be that someone has deleted a table for which privileges where defined or privileges where defined for a table that never existed. To solve the problem update the Roles and Rights for that Project_Class to adapt the defined privilege to your current database scheme and make sure that all required tables exists in the database.
Author: Lutz Krause