#13472 - 07/08/08 10:56 AM
Corrupt Data - Damaged Index - Revisited
|
Adagio Maestro
Registered: 02/22/08
Posts: 1247
Loc: Ontario, Canada
|
We are having continual problems with damaged data. We have 20 Lanpaks, 9 XP Pro workstations on SBS 2003 server, all hardware meets or exceeds the Softrak minimum requirements. We have a gigabit lan. We're running DC 8.1A(071220), IC 8.1A(070825), Ledger 9.0A(080402), OE 8.1B (080326), AP 8.1A(070919), AR 8.1A(070920), SA 8.1A (080107), GV 8.1A (071008), POA 8.0 07-May-2008, Paymate Acclaim 5.50 July 2008. Just about every week, sometimes a few times a week, we are all working away when suddenly the data becomes corrupt (can't scroll through items or customers, items or customers repeated in the scroll window, etc). We then get everyone off of Adagio and run a DataCare integrity check where multiple errors are found. We rebuild the errors (what other choice do we have?) and the rebuilding process strips a bunch of our shipping addresses. I can't say specifically what might be causing these problems. We are not doing anything unusual. Occassionally we might have deleted a customer or an item. POA was often in use on the day of the errors. However, I can't really pin point if it's any one thing since we use all the software in many ways every day and there's nothing different we are doing on the particular days when the data becomes corrupt.
Is anyone else experiencing data corruption? Has anyone ever successfully fixed this problem?
Please advise.
-----------------------------------------
Summary
File Integrity ... 110 error(s) found .......................................... FAILED Application Integrity ... 34 error(s) found .................................... FAILED
Finshed at: 2008.07.08 10:34
Data Repair Phase
Rebuilding Items (1) ... Done
Correcting Phase 2 Errors *** Customer must be manually corrected for document I 179897 *** Customer must be manually corrected for document I 179903 *** Item line must be manually corrected for document I 179904 *** Item line must be manually corrected for document I 179905 *** Item line must be manually corrected for document I 179907 *** Customer must be manually corrected for document I 179915 *** Customer must be manually corrected for document I 179917 *** Item line must be manually corrected for document O 155488 *** Customer must be manually corrected for document O 175510 *** Customer must be manually corrected for document O 177182 *** Customer must be manually corrected for document O 178986 *** Customer must be manually corrected for document O 179674 *** Customer must be manually corrected for document O 179773 *** Item line must be manually corrected for document O 179773 *** Customer must be manually corrected for document O 179775 *** Customer must be manually corrected for document O 180026 *** Customer must be manually corrected for document O 180117 *** Customer must be manually corrected for document O 180176 *** Customer must be manually corrected for document O 180186 *** Customer must be manually corrected for document O 180262 *** Item CO CNF302Z OnSales Order was adjusted at loc WA *** Item CO CMP6 ShipNotCosted was adjusted at loc KI *** Shipping address EL9742 for customer has been removed. *** Shipping address FE8843 for customer has been removed. *** Shipping address FE8843 for customer AJAX has been removed. *** Shipping address FE8843 for customer BARRIE has been removed. *** Shipping address FE8843 for customer CHATHM has been removed. *** Shipping address FE8843 for customer COBORG has been removed. *** Shipping address FE8843 for customer LONDON has been removed. *** Shipping address FE8843 for customer PETERB has been removed. *** Shipping address FE8843 for customer WOODBR has been removed. *** Shipping address FL3737 for customer 1 has been removed. *** Shipping address FM7006 for customer has been removed. *** Shipping address GO0093 for customer has been removed.
Rebuilding Customers ... Done Rebuilding Customers Extension ... Done
Finished rebuilding integrity errors. Please repeat Data Integrity Check.
_________________________
Susan Tennier TDL Canada Trenton, Ontario
|
Top
|
|
|
|
#13476 - 07/08/08 12:00 PM
Re: Corrupt Data - Damaged Index - Revisited
[Re: Softrak Support]
|
Adagio Maestro
Registered: 02/22/08
Posts: 1247
Loc: Ontario, Canada
|
I just installed the service pack so I am completely up-to-date now (I must have missed it before). I also realized a WAY easier way to get all the shipping addresses back. I opened up the data in OE from last nights back up and exported the shipping addresses. Then imported them into the repaired current data today. Saved a ton of time.
I would still like to know if there is a solution to this problem. Thanks.
_________________________
Susan Tennier TDL Canada Trenton, Ontario
|
Top
|
|
|
|
#13479 - 07/08/08 02:19 PM
Re: Corrupt Data - Damaged Index - Revisited
[Re: Softrak Support]
|
Adagio Maestro
Registered: 02/22/08
Posts: 1247
Loc: Ontario, Canada
|
Yes the problem recurred already. This time the errors were only in Inventory and OE. However, we also lost a cash batch in AR somewhere along the line today that is now being reenterred manually. We have no idea if anything else has been lost. There were 50 or more invoices enterred today, plus a few new inventory items, new POs, receiving, etc.
I will try next time to check the integrity in AR and IC before checking OE. We need to get this resolved somehow. Please help.
--------------------------------
Summary
File Integrity ... 6 error(s) found ............................................ FAILED Application Integrity ... 12 error(s) found .................................... FAILED
Finshed at: 2008.07.08 14:24
Data Repair Phase
Rebuilding Items (2) Additional ... Done Rebuilding Item (3) Extension ... Done Rebuilding Items (1) ... Done
Correcting Phase 2 Errors *** Item line must be manually corrected for document I 179928 *** Item line must be manually corrected for document O 155504 *** Item line must be manually corrected for document O 178207 *** Item line must be manually corrected for document O 178610 *** Item line must be manually corrected for document O 179324 *** Item line must be manually corrected for document O 179324 *** Item line must be manually corrected for document O 179763 *** Item line must be manually corrected for document O 179763 *** Item line must be manually corrected for document O 179763 *** Item line must be manually corrected for document O 179763 *** Item line must be manually corrected for document O 180351 *** Item line must be manually corrected for document O 180352
Finished rebuilding integrity errors. Please repeat Data Integrity Check.
_________________________
Susan Tennier TDL Canada Trenton, Ontario
|
Top
|
|
|
|
#13481 - 07/08/08 02:52 PM
Re: Corrupt Data - Damaged Index - Revisited
[Re: doswalt]
|
Adagio Maestro
Registered: 02/22/08
Posts: 1247
Loc: Ontario, Canada
|
Noone deleted any items today. Some new items were added however. No one added, changed or deleted any shipping addressess today. Once customer was deleted last night which I followed up with a data integrity check.
Just to confirm, this is not an error in Adagio because of a deleted item or customer referenced in an old invoice. This is full blown data corruption / damaged index.
_________________________
Susan Tennier TDL Canada Trenton, Ontario
|
Top
|
|
|
|
#13482 - 07/08/08 04:06 PM
Re: Corrupt Data - Damaged Index - Revisited
[Re: SusanTennier]
|
Adagio Master
Registered: 03/16/99
Posts: 10504
Loc: Canada
|
Hi Susan,
There's a hardware issue somewhere in your network. Unfortunately, these can be difficult to track down. The easiest way is to write batch file that does nothing but copy information up and down your network (from a workstation to the server and back). You need to have a "whole bunch" of little files, a one or two really large files in the directory you copy around and around. Have the batch file end by calling itself and let it run all night.
The next morning, use the DOS file compare utility (FC) to compare the contents of all the files you've been copying to the original. If there are ANY differences, then you've isolated the problem to the workstation/server you were testing.
Are any of your workstations "hanging" while in Adagio (or any other application)?
_________________________
Andrew Bates
|
Top
|
|
|
|
#13486 - 07/08/08 11:34 PM
Re: Corrupt Data - Damaged Index - Revisited
[Re: Retired_Guy]
|
Adagio Maestro
Registered: 02/22/08
Posts: 1247
Loc: Ontario, Canada
|
Hi Andrew,
I created 2 folders with 700 files each and made a slight difference in one file. In DOS I entered: FC c:\test1\*.* c:\test2\*.*
It finds the difference in the one file that I modified, however, the buffer in the DOS window holds only the last 100 or so records. So 600 hundred file results scroll past and are therefore no longer available. Is there a way to check all these files and get a summary at the end? I really only need to see the results of any discrepencies.
_________________________
Susan Tennier TDL Canada Trenton, Ontario
|
Top
|
|
|
|
#13491 - 07/09/08 12:32 PM
Re: Corrupt Data - Damaged Index - Revisited
[Re: SusanTennier]
|
Adagio Master
Registered: 03/16/99
Posts: 10504
Loc: Canada
|
Hi Susan, OK - here's the command you need to use to compare the two sets of files. First, make sure that your current directory is the original file set. The carefully type:
for %a in (*.*) do fc /b %a c:\test1\%a >>c:\x.txt
You'll see the computer do a binary file compare for each file in the directory. When it finishes type: to see the results of the comparisons. They should all look something like:
Comparing files glfrstim.xls and \TEST1\GLFRSTIM.XLS
FC: no differences encountered
Comparing files GLFSET'1.sam and \TEST1\GLFSET'1.SAM
FC: no differences encountered
Comparing files GLFSET'2.sam and \TEST1\GLFSET'2.SAM
FC: no differences encountered
Comparing files GLFSET'R.sam and \TEST1\GLFSET'R.SAM
FC: no differences encountered
unless there is a difference in which case you might see something like:
Comparing files GLGLOB.SAM and \TEST1\GLGLOB.SAM
00000002: 09 03
Comparing files GLGROUP.sam and \TEST1\GLGROUP.SAM
FC: no differences encountered
which highlights a difference between two bytes in the file. Since all you've done is copy data files around the network, there should be any differences between the copied files and the reference set. OK?
_________________________
Andrew Bates
|
Top
|
|
|
|
|
0 registered (),
45
Guests and
0
Spiders online. |
Key:
Admin,
Global Mod,
Mod
|
|
1865 Members
5 Forums
14467 Topics
70660 Posts
Max Online: 432 @ 01/20/25 10:17 PM
|
|
|
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
30
|
|
|
|
|
|