[Jeanie]

We lost our connection with the server earlier today and it corrupted our items.dbf file. The error says to open DBUWIN and perform a copy/zap/append to correct the problem, but I am unable to get that to open. When I click on the application, I get an error stating that access is denied and it shows the path to the momuser.dbf file. I'm logged into the server as administrator, so I should have full read/write access to any files in the momwin folder. I don't know what to do. Customers are calling us and sales people are on my case. We chose not to renew our $2,300 per year contract with Dydacomp because we weren't really using it.

Can anyone help???!

***************

Never mind, got it taken care of via a really helpful member.

[dseibold]

Jeanie, on Jun 13 2008, 12:25 PM, said:

We lost our connection with the server earlier today and it corrupted our items.dbf file. The error says to open DBUWIN and perform a copy/zap/append to correct the problem, but I am unable to get that to open. When I click on the application, I get an error stating that access is denied and it shows the path to the momuser.dbf file. I'm logged into the server as administrator, so I should have full read/write access to any files in the momwin folder. I don't know what to do. Customers are calling us and sales people are on my case. We chose not to renew our $2,300 per year contract with Dydacomp because we weren't really using it.

Can anyone help???!

Is everyone out of MOM? I believe you need exclusive access to MOM and dbuwin.exe to do this action.

[Videoflicks2004]

Which version of MOM are you using?

I'm guessing you don't have a backup?

regardless .. backup now -- whatever you have - -

open mom re-index (if it lets ya) ...

dseibold, on Jun 13 2008, 04:24 PM, said:

Is everyone out of MOM? I believe you need exclusive access to MOM and dbuwin.exe to do this action.

[Jeanie]

Videoflicks2004, on Jun 15 2008, 06:05 PM, said:

Which version of MOM are you using?

I'm guessing you don't have a backup?

regardless .. backup now -- whatever you have - -

open mom re-index (if it lets ya) ...

Thanks. Someone helped me resolve the situation on Friday so I'm all taken care of.

[planetdj]

Jeanie, on Jun 16 2008, 07:22 AM, said:

Thanks. Someone helped me resolve the situation on Friday so I'm all taken care of.

Glad to be able to help, Jeanie

[ypf1258]

Jeanie, on Jun 16 2008, 08:22 AM, said:

Thanks. Someone helped me resolve the situation on Friday so I'm all taken care of.

What was the solution

[CDI Fulfillment]

The instruction given in the error message tells you what to do (copy, zap, append), but really isn't very helpful if you don't know what that means.

• Make a backup copy of the corrupt database file
  
• Open DBUWin for the company with the corrupt database
  
• Open and browse the corrupt databse
  
• Click on Table -> Copy To...
  
• Click OK, then choose the location to save the file (I suggest something like the desktop, not in the MOMWIN folder)
  
• Click on Table -> Zap (you should get a message that warns you that this will permanently delete everything from the table. If you haven't made your backup yet, this is the point of no return)
  
• Once the ZAP is complete, browse the table again; it should be completely empty
  
• Click on Table -> Append From...
  
• Select the file that you saved on your desktop
  
• Restoration is complete. Close out of DBUWin and you should now be able to go into MOM
  
• Note: I have seen where multiple databases will get corrupted and you have to do this multiple times. MOM only tells you about one at a time, so you may have to go through this whole process, try to log in, then find out that an additional database is corrupt and have to go through the whole process again.

Always remember, DBUWin is a very powerful tool and anything that you do within the program CAN NOT be undone. Make a backup. If your still not comfortable working with DBUWin, hire someone that knows what they're doing.

[planetdj]

ypf1258, on Jun 26 2008, 10:38 AM, said:

What was the solution

CDI is correct, and very detailed, as usual.

The only thing I'll add is I also rename the .CDX files for the corrupt database and let MOM rebuild it upon startup.

Also, before I ever start the whole Copy/Zap/Append procedure, I try the following (which works over 50% of the time and is MUCH quicker):
1. Make a backup copy of the corrupt database file
2. Open DBUWin for the company with the corrupt database
3. Open and browse the corrupt databse
4. Add a new record to the database
5. Then mark that record for deletion
6. Pack the database.
7. Rename the .CDX for the corrupt database
8. Close out of DBUWin and you should now be able to go into MOM and let it rebuild the new index file.

Oddly, this issue "corrupt database" issue happened to me about 2 weeks ago, and I've also had 3 MOM customers contact me within the past 10 days asking how to resolve the same issue. Interesting.