Ошибка dbfntx 1012 обнаружено разрушение данных

#1

Отправлено 13 Июнь 2016 — 18:31

#2

Phil

Отправлено 14 Июнь 2016 — 05:25

б) Появление при работе с программой сообщения об ошибке 
вида:
ERROR DBFNTX/1012 : Corruption Detected (имя файла)
Внимание ! 
1) При выполнении функции не должны выполняться ни-
какие операции с файлами БД с других рабочих мест. Все файлы 
данных, открытые в момент индексации, не будут проиндекси-
рованы (соответствующее сообщение вида:
Файл БД - <название файла>
блокирован другим пользователем. Ждите : <число>
Для отказа от выполнения операции нажмите клавишу ESC
 будет выведено на экран и выполнении функции будет 
приостановлено).

#3

hmm3rulez

Отправлено 14 Июнь 2016 — 11:33

#4

pampeil

Отправлено 22 Июнь 2016 — 15:22

• Remove From My Forums

• Question

• I am getting a «DBFNTX/1012 Corruption detected» error which mysteriously recently appeared without any changes to the system or network. We have run this db program (written in Clipper ’87) for many years, including  XP under Win7 for the past year
  plus. This error was happening across a network, so as a troubleshooting step, I copied the entire folder from our server onto the C: of the Virtual Server/XP Mode computer (the computer where the error first appeared—the error also appears running it from
  the server’s computer), and still, am getting this error. I can use an indexing program I wrote as an adjunct to the db program which creates an .ntx file without issue. And, in fact, using the program it initially works until you attempt page up or down to
  the next screen within the program or apply any changes. I have not seen anything applicable searching the internet for a solution (there are a few articles on changing the opportunistic locking in the registry, which didn’t seem to apply to Win7—SMB2).

• Remove From My Forums

• Question

• I am getting a «DBFNTX/1012 Corruption detected» error which mysteriously recently appeared without any changes to the system or network. We have run this db program (written in Clipper ’87) for many years, including  XP under Win7 for the past year
  plus. This error was happening across a network, so as a troubleshooting step, I copied the entire folder from our server onto the C: of the Virtual Server/XP Mode computer (the computer where the error first appeared—the error also appears running it from
  the server’s computer), and still, am getting this error. I can use an indexing program I wrote as an adjunct to the db program which creates an .ntx file without issue. And, in fact, using the program it initially works until you attempt page up or down to
  the next screen within the program or apply any changes. I have not seen anything applicable searching the internet for a solution (there are a few articles on changing the opportunistic locking in the registry, which didn’t seem to apply to Win7—SMB2).

Правила форума

Счетчик сообщений в этом форуме выключен.