Re: Damaged database

2016-11-11 Thread stardata.info
This is the log error in the windows event. + System - Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Level 2 Task 100 Keywords 0x80 - TimeCreated [ SystemTime] 2016-11-10T13:38:56.0Z EventRecordID 11229 Channel

RE: Damaged database

2016-11-10 Thread stardata.info
Hi Tim, Where i find the Event Viewer? Thanks /Ferdinando/ Il 11/11/2016 01:09, 4d_tech-requ...@lists.4d.com ha scritto: Message: 11 Date: Thu, 10 Nov 2016 23:24:52 +0100 From: Timothy Penner<tpen...@4d.com> To: 4D iNug Technical<4d_tech@lists.4d.com> Subject: RE: Damaged databas

RE: Damaged database

2016-11-10 Thread Timothy Penner
> * Problem on the database : Last database flush did not complete. (1;139) This is usually only seen when the application crashed during a flush. Maybe your code that logged the successful quit had already executed when 4D crashed. You should check the Event Viewer to see if there are any

Re: Damaged database

2016-11-10 Thread stardata.info
Hi All, I have these two error in the log: * Problem on the database : Last database flush did not complete. (1;139) * Problem on index definition [index #6] : Checksum is invalid (16;66) Someone have suggestions? Thanks /Ferdinando/

RE: Damaged database

2016-11-10 Thread stardata.info
Tim, Below the my answers. Il 10/11/2016 21:00, 4d_tech-requ...@lists.4d.com ha scritto: Message: 10 Date: Thu, 10 Nov 2016 20:22:22 +0100 From: Timothy Penner<tpen...@4d.com> To: 4D iNug Technical<4d_tech@lists.4d.com> Subject: RE: Damaged databas

RE: Damaged database

2016-11-10 Thread stardata.info
scritto: Message: 3 Date: Thu, 10 Nov 2016 15:26:57 + From: "Dennis, Neil"<neil.den...@umb.com> To:"4d_tech@lists.4d.com" <4d_tech@lists.4d.com> Subject: RE: Damaged database Message-ID: <838740227206e84f82973ff5d9ea59b74a761...@wsys6041a.umb.corp.umb.com

RE: Damaged database

2016-11-10 Thread Timothy Penner
Some comments/suggestions: > In one my customer that use one application developed in 4D V13.2 You are using a very old release of an unsupported product (v13 is no longer supported nor updated); I would suggest that you, at the very least, update to the final release of v13.6 so that you can

RE: Damaged database

2016-11-10 Thread stardata.info
ot; <4d_tech@lists.4d.com> Subject: RE: Damaged database Message-ID: <838740227206e84f82973ff5d9ea59b74a761...@wsys6041a.umb.corp.umb.com> Content-Type: text/plain; charset="utf-8" >I open in MCS, repair and restart, someone know if i must do other things for

RE: Damaged database

2016-11-10 Thread Dennis, Neil
> The Windows is 7 and the application is in single mode. Check this against the certification chart from 4Ds website for the version of 4D you are using. They are found at the bottom of each tab in the download section http://www.4d.com/downloads/products.html Neil -- Privacy

RE: Damaged database

2016-11-10 Thread Dennis, Neil
> When i do a recover operation, i see that there are a message: "some > anomalies" , so i must to do the operation one second time. The message is telling you what it found (and corrected). Running it a second time tells you that it found nothing since it was corrected the first time. Neil

Re: Damaged database

2016-11-10 Thread stardata.info
Hi, When i do a recover operation, i see that there are a message: "some anomalies" , so i must to do the operation one second time. Thanks Ferdinando Il 10/11/2016 16:11, stardata.info ha scritto: Hi All, In one my customer that use one application developed in 4D V13.2 from two months,

Damaged database

2016-11-10 Thread stardata.info
Hi All, In one my customer that use one application developed in 4D V13.2 from two months, i have two or tre time a message for damage database. " The database is damaged, it will opened in maintenance mode " I open in MCS, repair and restart, someone know if i must do other things for solve

RE: Damaged database

2016-11-10 Thread Dennis, Neil
> I open in MCS, repair and restart, someone know if i must do other things for > solve this periodical issue? Examine the network, and computer memory and drive, and routers, look for any errors or failures. Make sure the OS is compatible with the version of 4D both on server and client Neil