[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 1.4.1 cannot access LSMB

On 23 September 2014 15:46, Chris Travers <..hidden..> wrote:
> As a temporary fix try this in psql:
> UPDATE BATCH SET locked_by = NULL;
> I am looking further in to why this might happen.

<dbname>=# UPDATE BATCH SET locked_by = NULL;

Ok I can use the data. I will do the same again and report back

The only thing that I ignored initially was a that I had to run 1.4.1.
setup.pl twice. Here is what I did:

1. copy DB 1.3.40 to DB-newname
2. logged on to DB-newname with 1.3.40, basic checks ok.
3. log off and the open setup.pl with the DB-newname with 1.4.1
4. convert DB
5. log on to LSMB with 1.4.1 then error: using a 1.4.0 DB where
expecting a 1.4.1
6. again run 1.4.1 setup.pl
7. log on using 1.4.1 all ok and the I took the actions as described
in first mail

So potentially the conversion is not what it should be.


Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
Ledger-smb-users mailing list