Loading...

ledger-smb-users@lists.sourceforge.net

[Prev] Thread [Next]  |  [Prev] Date [Next]

Re: [Ledger-smb-users] Everything's gone after upgrade Chris Travers Sat Feb 18 02:00:36 2012

This would have been caused by tablefunc.sql not loading. Which version of
LedgerSMB was this?

Best Wishes,
Chris Travers

On Fri, Feb 17, 2012 at 3:34 PM, Linda Ursin <[EMAIL PROTECTED]> wrote:

> Since I got the 1.3 working, I'd prefer just to populate the database in
> stead of going through it all again.
>
> I've attached the files.
>
> Linda
>
>
>
> ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~
>
> Linda Ursin
> Heksebua
>
> Adresse:                      Tlf:     (+47) 402 40 767
> Solvang                        www:     http://heksebua.com
> 7288 Soknedal              E-post:  [EMAIL PROTECTED]
>
> Org: NO 995 578 107
>
>
> On Sat, Feb 18, 2012 at 12:15 AM, Chris Travers <[EMAIL PROTECTED]>wrote:
>
>>
>>
>> On Fri, Feb 17, 2012 at 1:14 PM, Linda Ursin <[EMAIL PROTECTED]> wrote:
>>
>>> Hi
>>>
>>> After a lot of help and work, I got the upgrade to 1.3.11 right. But
>>> there's one problem: Everything's gone!
>>> I'm missing everything: parts, assemblies, orders, customers, vendors,
>>> accounts.
>>>
>>> How did this happen and how can I fix it. I have a huge number of parts,
>>> and I don't feel like adding them all again. It would also be nice to be
>>> able to compare the result to earlier years. But it the numbers and
>>> accounts aren't there, I can't.
>>>
>>> The first thing to do is look in the /tmp/ledgersmb directory and grab
>> all files with a name like dblog, dblog_stderr, and dblog_stdout.
>>
>> What probably happened was the actual upgrade transaction failed  The
>> error is probably in the dblog file.  In the mean time you can run the
>> 1.3-1.2.sql to get back to 1.2 if you need to while evaluating the error
>> (you will probably need to do this anyway before correcting the error).
>>  Remember, this is not a destructive upgrade so the fact that the data
>> appears gone means it just didn't populate the 1.3 database.
>>
>> This might occur if there was something that was valid in the 1.2
>> database but not in the 1.3 database, and if it was not in the
>> pre-upgrade-checks that I have included.  If you can attach these dblog
>> files that would be helpful.
>>
>> Best Wishes,
>> Chris Travers
>>
>>
>> ------------------------------------------------------------------------------
>> Virtualization & Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing
>> also focuses on allowing computing to be delivered as a service.
>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>> _______________________________________________
>> Ledger-smb-users mailing list
>> [EMAIL PROTECTED]
>> https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
>>
>>
>
>
> ------------------------------------------------------------------------------
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Ledger-smb-users mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
>
>
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Ledger-smb-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users