SQL-Ledger Homepage

SQL-Ledger User Forum

Forum index page

Log in | Register

Back to the board
Thread view  Mix view  Order
timhalford(R)

02.02.2015, 17:55
 

dataset locked and previously reconciled items not hidden (General)

I replaced my computer and installed version 2.8.33, which I was previously using. It was running well but when I tried to reconcile accounts, the previously reconciled items (checked) all showed up.

Rather than try to fix the old version, I upgraded to 3.06. Now I have two problems:

The dataset is locked when I try to access it using admin.pl.

The original problem reconciling accounts still exists.

I would appreciate any suggestions.

Dieter Simader(R)

02.02.2015, 23:44

@ timhalford

dataset locked and previously reconciled items not hidden

I replaced my computer and installed version 2.8.33, which I was previously
using. It was running well but when I tried to reconcile accounts, the
previously reconciled items (checked) all showed up.

Enter a period, if nothing is entered every transaction shows up.


Rather than try to fix the old version, I upgraded to 3.06. Now I have two
problems:

The dataset is locked when I try to access it using admin.pl.

The original problem reconciling accounts still exists.

I would appreciate any suggestions.

Datasets remain locked if the upgrade failed. You can unlock the dataset but first find out what went wrong. You probably have log files for postgresql.

timhalford(R)

03.02.2015, 02:23

@ Dieter Simader

dataset locked and previously reconciled items not hidden

I re-did the reconciliation up to a point where an entry was missing (about a year into the history). Now, it's working as advertised and the missing entry is back. Perhaps it was just un-checked and I missed it. I'll call that solved, for now.

The sql log shows a few errors from around the time I changed the version.

CST ERROR: relation "acsrole" does not exist at character 61
CST STATEMENT: SELECT e.acs, a.acs
FROM employee e
LEFT JOIN acsrole a ON (e.acsrole_id = a.id)
WHERE login = 'tim'
CST ERROR: relation "employee" does not exist at character 33
CST STATEMENT: SELECT e.acs, a.acs
FROM employee e
LEFT JOIN acsrole a ON (e.acsrole_id = a.id)
WHERE login = 'tim'
CST ERROR: relation "employee" does not exist at character 32
CST STATEMENT: SELECT id
FROM employee
WHERE login = 'tim'

I can put the 2.8.33 folder back and get into the admin section, but the dataset no longer works with that version.

By the way, thanks for the help.

# end

I replaced my computer and installed version 2.8.33, which I was
previously
using. It was running well but when I tried to reconcile accounts, the
previously reconciled items (checked) all showed up.

Enter a period, if nothing is entered every transaction shows up.


Rather than try to fix the old version, I upgraded to 3.06. Now I have
two
problems:

The dataset is locked when I try to access it using admin.pl.

The original problem reconciling accounts still exists.

I would appreciate any suggestions.

Datasets remain locked if the upgrade failed. You can unlock the dataset
but first find out what went wrong. You probably have log files for
postgresql.

Dieter Simader(R)

03.02.2015, 11:18

@ timhalford

dataset locked and previously reconciled items not hidden

I re-did the reconciliation up to a point where an entry was missing (about
a year into the history). Now, it's working as advertised and the missing
entry is back. Perhaps it was just un-checked and I missed it. I'll call
that solved, for now.

The sql log shows a few errors from around the time I changed the version.

CST ERROR: relation "acsrole" does not exist at character 61
CST STATEMENT: SELECT e.acs, a.acs
FROM employee e
LEFT JOIN acsrole a ON (e.acsrole_id = a.id)
WHERE login = 'tim'
CST ERROR: relation "employee" does not exist at character 33
CST STATEMENT: SELECT e.acs, a.acs
FROM employee e
LEFT JOIN acsrole a ON (e.acsrole_id = a.id)
WHERE login = 'tim'
CST ERROR: relation "employee" does not exist at character 32
CST STATEMENT: SELECT id
FROM employee
WHERE login = 'tim'

I can put the 2.8.33 folder back and get into the admin section, but the
dataset no longer works with that version.

By the way, thanks for the help.

# end

I replaced my computer and installed version 2.8.33, which I was
previously
using. It was running well but when I tried to reconcile accounts, the
previously reconciled items (checked) all showed up.

Enter a period, if nothing is entered every transaction shows up.


Rather than try to fix the old version, I upgraded to 3.06. Now I have
two
problems:

The dataset is locked when I try to access it using admin.pl.

The original problem reconciling accounts still exists.

I would appreciate any suggestions.

Datasets remain locked if the upgrade failed. You can unlock the dataset
but first find out what went wrong. You probably have log files for
postgresql.

what do you get when you run

select * from defaults where fldname = 'version';

timhalford(R)

03.02.2015, 12:38

@ Dieter Simader

dataset locked and previously reconciled items not hidden

I re-did the reconciliation up to a point where an entry was missing
(about
a year into the history). Now, it's working as advertised and the
missing
entry is back. Perhaps it was just un-checked and I missed it. I'll call
that solved, for now.

The sql log shows a few errors from around the time I changed the
version.

CST ERROR: relation "acsrole" does not exist at character 61
CST STATEMENT: SELECT e.acs, a.acs
FROM employee e
LEFT JOIN acsrole a ON (e.acsrole_id = a.id)
WHERE login = 'tim'
CST ERROR: relation "employee" does not exist at character 33
CST STATEMENT: SELECT e.acs, a.acs
FROM employee e
LEFT JOIN acsrole a ON (e.acsrole_id = a.id)
WHERE login = 'tim'
CST ERROR: relation "employee" does not exist at character 32
CST STATEMENT: SELECT id
FROM employee
WHERE login = 'tim'

I can put the 2.8.33 folder back and get into the admin section, but the
dataset no longer works with that version.

By the way, thanks for the help.

# end

I replaced my computer and installed version 2.8.33, which I was
previously
using. It was running well but when I tried to reconcile accounts,
the
previously reconciled items (checked) all showed up.

Enter a period, if nothing is entered every transaction shows up.


Rather than try to fix the old version, I upgraded to 3.06. Now I
have
two
problems:

The dataset is locked when I try to access it using admin.pl.

The original problem reconciling accounts still exists.

I would appreciate any suggestions.

Datasets remain locked if the upgrade failed. You can unlock the
dataset
but first find out what went wrong. You probably have log files for
postgresql.

what do you get when you run

select * from defaults where fldname = 'version';

fldname | fldvalue
---------+----------
version | 3.0.0
(1 row)

In case it matters, I have two databases and they both show the same result.

Dieter Simader(R)

04.02.2015, 11:14

@ timhalford

dataset locked and previously reconciled items not hidden

what do you get when you run

select * from defaults where fldname = 'version';

fldname | fldvalue
---------+----------
version | 3.0.0
(1 row)

In case it matters, I have two databases and they both show the same
result.

version is correct.

check if you have the employee and acsrole relations

timhalford(R)

04.02.2015, 17:06

@ Dieter Simader

dataset locked and previously reconciled items not hidden

what do you get when you run

select * from defaults where fldname = 'version';

fldname | fldvalue
---------+----------
version | 3.0.0
(1 row)

In case it matters, I have two databases and they both show the same
result.

version is correct.

check if you have the employee and acsrole relations

\dt lists both relations.

Dieter Simader(R)

04.02.2015, 17:50

@ timhalford

dataset locked and previously reconciled items not hidden

what do you get when you run

select * from defaults where fldname = 'version';

fldname | fldvalue
---------+----------
version | 3.0.0
(1 row)

In case it matters, I have two databases and they both show the same
result.

version is correct.

check if you have the employee and acsrole relations

\dt lists both relations.

well then everything seems to be ok.

as for the missing 'admin' add the login as per upgrade instructions in the doc directory.

timhalford(R)

04.02.2015, 20:31

@ Dieter Simader

dataset locked and previously reconciled items not hidden

what do you get when you run

select * from defaults where fldname = 'version';

fldname | fldvalue
---------+----------
version | 3.0.0
(1 row)

In case it matters, I have two databases and they both show the same
result.

version is correct.

check if you have the employee and acsrole relations

\dt lists both relations.

well then everything seems to be ok.

as for the missing 'admin' add the login as per upgrade instructions in the
doc directory.

Nope.

I can log into login.pl and "unlock" the dataset in the "system/maintenance" area but it changes nothing. I can still use the database so I don't think the problem is there.

I can't enter the administration page.

admin.pl takes me to the administration login page.

The login page takes me to the page where I can choose the dataset.

When I choose the dataset the next page lets me set a "lock message" or "Delete" or "Lock Dataset".

When I check the html behind the page, the action is indeed "Lock Dataset".

If I set the lock message, I can bring up an "Unlock Dataset" button. That button does not unlock the dataset. The action for that button is also "Unlock Dataset".

Where is the lock, that keeps the administration page locked out, located?

timhalford(R)

04.02.2015, 20:36

@ timhalford

dataset locked and previously reconciled items not hidden

what do you get when you run

select * from defaults where fldname = 'version';

fldname | fldvalue
---------+----------
version | 3.0.0
(1 row)

In case it matters, I have two databases and they both show the
same
result.

version is correct.

check if you have the employee and acsrole relations

\dt lists both relations.

well then everything seems to be ok.

as for the missing 'admin' add the login as per upgrade instructions in
the
doc directory.

Nope.

I can log into login.pl and "unlock" the dataset in the
"system/maintenance" area but it changes nothing. I can still use the
database so I don't think the problem is there.

I can't enter the administration page.

admin.pl takes me to the administration login page.

The login page takes me to the page where I can choose the dataset.

When I choose the dataset the next page lets me set a "lock message" or
"Delete" or "Lock Dataset".

When I check the html behind the page, the action is indeed "Lock
Dataset".

If I set the lock message, I can bring up an "Unlock Dataset" button. That
button does not unlock the dataset. The action for that button is also
"Unlock Dataset".

Where is the lock, that keeps the administration page locked out, located?

Is the admin setup page gone now?

Dieter Simader(R)

04.02.2015, 20:51

@ timhalford

dataset locked and previously reconciled items not hidden


Is the admin setup page gone now?

admin.pl is only used for creating, deleting and un/locking datasets.

all the admin functions like creating logins is done in the program.

timhalford(R)

04.02.2015, 20:58

@ Dieter Simader

dataset locked and previously reconciled items not hidden


Is the admin setup page gone now?

admin.pl is only used for creating, deleting and un/locking datasets.

all the admin functions like creating logins is done in the program.

Thanks for your time. iou

Back to the board
Thread view  Mix view  Order
986 Postings in 325 Threads, 327 registered users, 112 users online (0 registered, 112 guests)
SQL-Ledger User Forum | Admin contact
RSS-Feed
powered by my little forum