Dear friends,
I have a bad situation at hand and it’s as follows:
I help support a Vfp6 app in a hospital and the .dbfs/cdx/fpts are stored on a 64bit Windows Server 2008. They do not use DBC. It’s a mix of OSes; winxp and win7 mostly.
From 2012 October things have been fairly ok. (There has been one problem though. Sometimes vfp fails to save some records posted at client computers without an error)
In March 2014 the app all over sudden started having SEVERE CDX CORRUPTION. The experience is now a nightmare to all.
Recreating the index tags stops the problem for some few hours then cdxes get corrupted again.
Fatal Error exception C000000FD
(The error is at insert level, particulary when a key field is changed)
I googled some info and got a list of things to check for.
1.) Bad characters in fields {I removed especially from key fields but the problem persist}
2.) Disable Oplocks {IT manager refused siting –ve implications on some applications}
3.) One bad NIC could result in bad behaviour – {not able to test this]
4.) Bad network environment – {not sure what to look for}
5.) Disable SMB2 – {not sure of any -ve implications on the network}
The system is actually unusable for now.
Kindly advise on what to do.
Benson
I have a bad situation at hand and it’s as follows:
I help support a Vfp6 app in a hospital and the .dbfs/cdx/fpts are stored on a 64bit Windows Server 2008. They do not use DBC. It’s a mix of OSes; winxp and win7 mostly.
From 2012 October things have been fairly ok. (There has been one problem though. Sometimes vfp fails to save some records posted at client computers without an error)
In March 2014 the app all over sudden started having SEVERE CDX CORRUPTION. The experience is now a nightmare to all.
Recreating the index tags stops the problem for some few hours then cdxes get corrupted again.
Fatal Error exception C000000FD
(The error is at insert level, particulary when a key field is changed)
I googled some info and got a list of things to check for.
1.) Bad characters in fields {I removed especially from key fields but the problem persist}
2.) Disable Oplocks {IT manager refused siting –ve implications on some applications}
3.) One bad NIC could result in bad behaviour – {not able to test this]
4.) Bad network environment – {not sure what to look for}
5.) Disable SMB2 – {not sure of any -ve implications on the network}
The system is actually unusable for now.
Kindly advise on what to do.
Benson