FrontAccounting forum — Cannot log in

Re: Cannot log in

null@example.com (itronics) — Thu, 03 Apr 2008 09:45:36 +0000

If you would not use InnoDB you can end with unconsistent database after any error while including document. I think You should make some experiments with InnoDB settings to make it right , if you wish to use FA safely. May be your real path for db files is not the same as the default one in standard settings.
I still do not understand the source of problem as the mentioned error message is related to config_db.php settings, not MySQL.

Janusz

Re: Cannot log in

null@example.com (crimmelcp) — Sat, 29 Mar 2008 14:35:06 +0000

Got it working.

I am using EasyPHP

Seems if you enable innodb, that EasyPHP conflicts with the SQL starting.

If I keep innodb commented out it seems to work fine

Thanks
Charlie Crimmel
crimmelcp@suddenlink.net
West Virginia, USA

Re: Cannot log in

null@example.com (crimmelcp) — Sat, 29 Mar 2008 10:29:43 +0000

Still No luck

I checked php.ini and session auto start is set to 0
checked sql
the follwing is commented out
# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /usr/local/var/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /usr/local/var/
#innodb_log_arch_dir = /usr/local/var/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50

when I uncomment I get error message, failure to connect to database.

Is there someting wrong with my SQL?

Thanks
Charlie Crimmel
crimmelcp@suddenlink.net
West Virginia, USA

Re: Cannot log in

null@example.com (joe) — Sat, 29 Mar 2008 06:02:34 +0000

The default user/password in file is: admin/password

/Joe

Re: Cannot log in

null@example.com (crimmelcp) — Sat, 29 Mar 2008 00:52:27 +0000

OK Reinstalled using automatic install
Got rid of the error
still cannot log in
table prefix has increased to 2
Used PHPAdmin and added users
Tried using admin/admin
demouser/cooldemo
crimmelcp/crimmel

get error message
Incorrect Password

The user and password combination is not valid for the system.

If you are not an authorized user, please contact your system administrator to obtain an account to enable you to use the system.
Any Ideas now

Thanks
Charlie Crimmel
crimmelcp@suddenlink.net
West Virginia, USA

Re: Cannot log in

null@example.com (crimmelcp) — Fri, 28 Mar 2008 23:08:46 +0000

I did that but company is still blank and get error message invalid password.

still Get error
Document.forms.0.company_login_name.options 0 is null or not an object

Any other Ideas

Thanks
Charlie Crimmel
crimmelcp@suddenlink.net
West Virginia, USA

Re: Cannot log in

null@example.com (joe) — Fri, 28 Mar 2008 21:32:36 +0000

Check the file, config_db.php, and change it to

$def_coy = 0;

$tb_pref_counter = 1;

$db_connections = array (
    0 => array ('name' => 'Training',
        'host' => 'localhost',
        'dbuser' => 'user',
        'dbpassword' => 'password',
        'dbname' => 'dbname',
        'tbpref' => '0_')
    );

change the values for dbuser, dbpassword and dbname to fit your database creation.

/Joe

Cannot log in

null@example.com (crimmelcp) — Fri, 28 Mar 2008 20:35:00 +0000

Have just installed front accounting on to localhost
could not install by the auto so manual installed
uploaded the sql file via phpmyadmin.
set the db conect file to my details
now when i go to login for the first time. i just get the user name password don't match.
added new user with same results
The company dropdown in blank.
Get error
Document.forms.0.company_login_name.options 0 is null or not an object

Thanks
Charlie Crimmel
crimmelcp@suddenlink.net
West Virginia, USA