Frequently Asked Questions
Mifos FAQs provide a quick way to get answers to the most common problems and questions posed by our users. FAQs are sorted by topics and the content is searchable so you may quickly find the answers you need.
Configuration (3)
Savings Products (1)
Pertineo valetudo plaga amet sudo erat natu abluo turpis. Scisco vicis pertineo nimis. Aliquam uxor hendrerit rusticus abbas nutus interdico eligo. Ut plaga dolore quidne pneum nobis defui gemino nutus. Metuo mos ymo conventio euismod vero inhibeo similis metuo.
We shall soon see.
How do i add more details?
This is the answer
Database (4)
To restore your Mifos database using the MySQL Query Browser and MySQL Administrator user interface:
- If Mifos is running, log out.
- In MySQL Query Browser, drop the Mifos database by right-clicking mifos and selecting Drop Schema.
- In MySQL Administrator, click Restore in the left pane.
- Click Open Backup File and select the backup you created.
- Keep the default settings and click Start Restore. Start Mifos and verify that the restored data is there.
To restore your Mifos database from the command line:
mysql –u root –p db_name < source_sql_file.sql
To backup your Mifos database using the MySQL Administrator user interface:
- In MySQL Administrator, click Backup in the left pane.
- Click New Project.
- Enter a name in the Project Name text box. For example, mifos_012009
- In the Schemata list, highlight the Mifos schema.
- Click the > arrow to put the data into the Backup Content area.
- Click Execute Backup Now.
- In the Save As dialog box, select where you want to save the backup.
To backup your Mifos database from the command line:
mysqldump —add-drop-table –u root –p db_name > target_sql_file.sql
For incremental backups, you can turn on the binary log, then do something like this monthly:
mysqldump -u root --single-transaction --create-options --flush-logs --flush-privileges --master-data=2--delete-master-logs --databases mifos mysql | gzip > /backups/full-`date -u +%Y-%m-%dT%H:%M:%SZ`.sql.gz
and something like this, every other day:
mysqladmin -u root flush-logs
This error message appears when:
- you are using the wrong database
- your database has been corrupted
- the database version is too old and Mifos can't figure out how to upgrade it
Make sure the correct databases are specified in your LocalPropertiesFile.
If your database has become corrupt, follow the installation documentation to manually re-create your database.
If your database version is too old, you may be able to download an older version of Mifos, upgrade using that, then use the more recent version of Mifos to upgrade again.
See DatabaseVersionPersistence.java in the Mifos source code for more information about what causes this error.
This error message appears when one or more of the following occurs:
- MySQL is not running.
- MySQL is listening on a different port than Mifos is expecting (by default, 3306).
- You are using an incorrect username or password for MySQL. Mifos assumes that your MySQL username is root and your password is mysql.
To check whether MySQL is running and listening on a certain port, enter telnet <hostname> <port> at a command prompt. For example:
telnet localhost 3306
If MySQL is running on the machine you specify and listening on the port number you entered, you will get a response that includes the server’s MySQL version number. For example:
5.0.67-community-nt- For information on how to start MySQL, see the topic Start/Stop Service in the MySQL Administrator online help.
- For information on how to customize your database connection – for example, by using a non-default user name and password or a port other than 3306 – see Customizing your Database Connection.
Reporting (2)
Pertineo valetudo plaga amet sudo erat natu abluo turpis. Scisco vicis pertineo nimis. Aliquam uxor hendrerit rusticus abbas nutus interdico eligo. Ut plaga dolore quidne pneum nobis defui gemino nutus. Metuo mos ymo conventio euismod vero inhibeo similis metuo.
When attempting to run the Branch Cash Confirmation report while upgrading from Mifos 1.3 to Mifos 1.5, report does not successfully run. Get a value of -2.
To resolve this issue, follow Amit's workaround of downgrading BIRT and re-installing the report.
Upgrades (4)
- Remove Mifos as described above. If you created custom reports, make a copy of the report folder under Tomcat/webapps/mifos before you delete the webapps/mifos folder.
- Download the new Mifos installation package and extract the Mifos .war file.
- Follow the instructions in the Mifos INSTALL file to install and run the newer version of Mifos.
If you're running an earlier version of Mifos that you don't want to keep, use the following procedure to install a completely new version:
- Remove Mifos as described above.
- Drop the mifos schema in MySQL Query Browser.
- Download the new Mifos installation package and extract the Mifos .war file.
- Follow the instructions in the Mifos INSTALL file to install and run the newer version of Mifos.
- Log out of Mifos.
- Stop the Tomcat instance that’s running Mifos by either executing the shutdown script in your Tomcat bin directory or, if you’re running Tomcat as a Windows service, by stopping it.
- Delete the following:
- The mifos folder under Tomcat/webapps. Any custom reports you created are in Tomcat/webapps/mifos/report.
- The mifos folder under Tomcat/work/Catalina/localhost.
- The mifos.war file in your Tomcat webapps folder.
Attempting to upgrade MySQL database from version 220 to version 223 while upgrading from Mifos 1.4 to Mifos 1.5, and I get the following errors.
The correct versions for MySQL databases can be found here. You should follow the instructions for upgrading database here. Follow the instructions for upgrading Mifos WAR file here.

