-
Notifications
You must be signed in to change notification settings - Fork 749
Installation FAQ's
This error is usually encountered when the MifosX platform server you are trying to connect to is not available or you are trying to connect with Invalid Credentials
Troubleshoot the same as follows:
The default username/password are mifos/password
Try connecting to the Mifos platform with the default credentials and ensure that you get a JSON response Ex: https://localhost:8443/mifosng-provider/api/v1/clients?tenantIdentifier=default&pretty=true
Some of the most commonly found errors are
If you see an error log similar to
Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'jdbcTenantDetailsService' defined in file [C:\Tomcat7\apache-tomcat-7.0.53\webapps\mifosng-provider-jpa-pu\WEB-INF\classes\org\mifosplatform\infrastructure\security\service\JdbcTenantDetailsService.class]: Unsatisfied dependency expressed through constructor argument with index 0 of type [javax.sql.DataSource]: : No qualifying bean of type [javax.sql.DataSource] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {@org.springframework.beans.factory.annotation.Qualifier(value=tenantDataSourceJndi)}; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type [javax.sql.DataSource] found for dependency: expected at least 1 bean which qualifies as autowire candidate for this dependency. Dependency annotations: {@org.springframework.beans.factory.annotation.Qualifier(value=tenantDataSourceJndi)} at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:738) ~[spring-beans-3.2.5.RELEASE.jar:3.2.5.RELEASE]
Verify the following
If you see and error similar to
Exception sending context initialized event to listener instance of class org.sp ringframework.web.context.ContextLoaderListener org.springframework.beans.factory.BeanCreationException: Error creating bean wit h name 'tenantDatabaseUpgradeService': Invocation of init method failed; nested exception is org.springframework.jdbc.CannotGetJdbcConnectionException: Could no t get JDBC Connection; nested exception is org.apache.tomcat.dbcp.dbcp.SQLNested Exception: Cannot create PoolableConnectionFactory (Access denied for user 'root '@'localhost' (using password: YES))
Verify the following
- The table "tenants" in "mifosplatform-tenants" has a row for "mifostenant-default". If your database credentials are not "root" and "mysql", update the same accordingly in this row
- Verify that you have created a database called
mifostenant-default
If you see an error similar to
http-bio-8443-exec-9" java.lang.OutOfMemoryError: PermGen space
you would have to increase the permgen space for tomcat. There are a number fo ways of doing the same, the simplest being setting the size in an environment variable called JAVA_OPTS
Ex: JAVA_OPTS = -Xms1024M -Xmx1024M -XX:MaxPermSize=256m
Refer http://www.youtube.com/watch?v=tk7uyjAM37U Or https://www.youtube.com/watch?v=JgTJCiyOsIQ or You can refer the following link https://hackpad.com/Mifos-X-Reporting-Training-zlXGVQerbOv
Please Go through the following steps:
- Download the latest version from the below link(Note that below link is showing the latest version MifosX 1.24, at this point of time) http://sourceforge.net/projects/mifos/files/Mifos%20X/
It will be the zipped file and you need to unzip it in any required drive/folder.
-
Please Delete the "mifosng-provider.war" file present in the tomcat/webapps folder and copy the new "mifosng-provider.war" file from downloaded latest MifosX and paste it in tomcat/webapps folder.
-
Please delete the "community-app" and "api-docs" folders from \tomcat\webapps\ROOT folder and copy the same folders from downloaded latest MifosX and paste them in tomcat\webapps\ROOT folder.
-
Finally, delete the "mifosng-provider" folder present in the \tomcat\webapps folder and restart the tomcat Server.
That's it!! You'll be welcomed to the latest version of MifosX
(Assuming you already know how to generate keystore file or if you don't know, please refer the following link, http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html#Configuration) There are mainly two reasons for this error.(other reasons may exist)
- You have generated a .keystore file but you haven't set its right path in the server.xml file which is present in the \tomcat\conf. Most of the time, .keystore file is generated in your home directory or you can put it in some other directories too, but ensure that you have set the right path for .keystore file in server.xml file and also remember the password you've given while generating .keystore file.
2)You might have given wrong password in the server.xml file, (ie "keystorepass")
- [I am currently using Mifos X 1.24 and unable to login to the Platform App.A dialog box pops up that says authentication required when I try to connect or I get an Error message that says:A username and password are being requested by https://localhost:8443. The site says: "Mifos Platform API".When I input my credentials i.e.,[root,mysql] then a "HTTP Status 401 - Bad credentials" message is displayed.I've observed that the mysql server 5.6.20 I'm using also doesn't allow me to connect using telnet(port=3306).It responds with ....mysql_native_password connection to host lost.Similarly I'm unable to login to the Community App.I get a message saying "Please try again, your credentials are not valid"]
Solved: A friend pointed out to me that I was using incorrect credentials to log in vis a vis I should use mifos/password instead of the beguiling root/mysql.If you are new to Mifos it could be a bit tricky to figure it out as it is not mentioned in the install docs that come with the shipping for Mifos X 1.24.
While you are configuring mysql, you have run the following sql command, which has loaded some pre-sample data
mysql -uroot -pmysql mifostenant-default < database/migrations/sample_data/load_sample_data.sql
(Consider the following answer as the one of the possibility. There can be several reasons for invalid credentials, though you have entered correct username and password)
It looks like mifosng-provider.war file hasn't run. Please cross verify and make sure that the war file is in tomcat/webapps folder.