.

Am 27. September 2017 16:19:27 OESZ schrieb Maah Moussa <[email protected]>:
>On Wednesday, September 27, 2017 at 12:17:20 PM UTC, Sergi Almacellas
>Abellana wrote:
>> El 27/09/17 a les 12:11, Maah Moussa ha escrit:
>> > Yes. Thanks. It got connected as postgres after running
>trytond-admin correctly. The DB is working. Except the invoicing It
>gets this message:
>> > The value of the field "Account" on "Invoice" is not valid
>according to its domain.
>> > I used the migration through opensuse upgrade.sql

This is the standard upgrade script provided by GNU Health  (just for the 
records)

>> > All seems working except the invoicing.
>> The invoice domain enforces two things:
>> 
>> 1. The account used is from the same company as the invoice account.
>> 2. If it's an out invoice it should be of kind receivable. Otherwise
>it 
>> should be of kind payable.
>> 
>> One (or both) of this conditions is not valid. You should check the 
>> values used.
>> 
>> -- 
>> Sergi Almacellas Abellana
>> www.koolpi.com
>> Twitter: @pokoli_srk
>
>The restored DB used to have invoiced customers. Now I can't invoice
>customers even after putting the customer payment term.
>I'm sorry. I don't quite grasp your points. The accounts are configured
>and used to be working. 
>Also I noticed issues through back up 
>2017-09-27 12:19:03 [INFO] START Database Backup
>2017-09-27 12:19:06 [INFO] Compressing Database Backup
>2017-09-27 12:19:09 [INFO] Creating compressed tarball with DB and GNU
>Health Attachment directory
>tar: Removing leading `/' from member names
>/var/lib/tryton/
>/var/lib/tryton/trytond.pid
>./gnuhealth-control: line 183: message: command not found

Indeed, instead of 'message' it should read 'cli_msg'.
I trust Luis will correct this once he is back from Africa. For the openSUSE 
Version I did a correction to Factory tree already

>tar: Removing leading `/' from member names
>/home/gnuhealth/Downloads/backup_gnuhealth30_2017-09-27_121903.gz
>tar:
>/home/gnuhealth/Downloads/gnuhealth_gnuhealth30_fs_backup_2017-09-27_121903.tar.gz:
>Cannot stat: No such file or directory
>tar: Exiting with failure status due to previous errors
>2017-09-27 12:19:09 [ERROR] Bailing out !
>2017-09-27 12:19:09 [ERROR] Removing backup lock file
>
>Is there a method to make sure the DB is restored and migrated
>correctly?

Don't mix things up: restoration and migration are two different things.
First make sure you took a proper backup - use pg_dump for this (actually 
gnuhealth_control uses this in the background as well), and pg_restore to 
restore - it should tell you the errors that appear. Same for the upgrade 
script.

Viele Grüße
Axel 
-- 
Diese Nachricht wurde von meinem Android-Tablet mit K-9 Mail gesendet

-- 
You received this message because you are subscribed to the Google Groups 
"tryton" group.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tryton/E5D94D09-2363-45BD-996F-8DF8A15DFFB1%40gmx.de.

Reply via email to