Hi,
We are currently running a VFP9 SP2 app on a windows 2003 server, which has been virtualised. We want to move to either 2008 server or preferably 2012 server. The app has a DBC and DBFs and has been running happily for over 10 years. The problem we have when transferring the data over to a virtualised 2008 or 2012 server is that we get index corruption once or more a day. We then have to move the data back. We have tried a few different configurations but do not know why this is happening.
I just want to check what servers people are using for their networked VFP app and any problems (or not) they have had.
Please let me know what version of windows you are using and what version of VFP and if the server is virtualised or not.
TIA
Peter
This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email.
www.whisperingsmith.com
Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR. Tel:0161 831 3700 Fax:0161 831 3715
London Office:17-19 Foley Street, London W1W 6DW Tel:0207 299 7960
Peter,
We have run FoxBase+, FoxPro for DOS, VFP5, VFP9 RTM, and VFP9 SP2 apps on Windows Server 2003 and 2008 without problem in a non-virtualized environment. I copy database and index files to and from Windows XP, Vista, and 7 (though not often between servers) routinely without problem.
Could your problem be with the copy method rather than the environment? Are the tables and indexes being accessed or modified during the copy process?
Mike
_______________________________________________
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Peter Cushing Sent: Monday, March 21, 2016 10:47 AM To: profoxtech@leafe.com Subject: Which server for VFP9 app
Hi,
We are currently running a VFP9 SP2 app on a windows 2003 server, which has been virtualised. We want to move to either 2008 server or preferably 2012 server. The app has a DBC and DBFs and has been running happily for over 10 years. The problem we have when transferring the data over to a virtualised 2008 or 2012 server is that we get index corruption once or more a day. We then have to move the data back. We have tried a few different configurations but do not know why this is happening.
I just want to check what servers people are using for their networked VFP app and any problems (or not) they have had.
Please let me know what version of windows you are using and what version of VFP and if the server is virtualised or not.
TIA
Peter
This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email.
www.whisperingsmith.com
Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR. Tel:0161 831 3700 Fax:0161 831 3715
London Office:17-19 Foley Street, London W1W 6DW Tel:0207 299 7960
_______________________________________________
Take a stroll through the archives here and look for discussions pertaining to SMB.
--
rk
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Peter Cushing Sent: Monday, March 21, 2016 10:47 AM To: profoxtech@leafe.com Subject: Which server for VFP9 app
Hi,
We are currently running a VFP9 SP2 app on a windows 2003 server, which has been virtualised. We want to move to either 2008 server or preferably 2012 server. The app has a DBC and DBFs and has been running happily for over 10 years. The problem we have when transferring the data over to a virtualised 2008 or 2012 server is that we get index corruption once or more a day. We then have to move the data back. We have tried a few different configurations but do not know why this is happening.
I just want to check what servers people are using for their networked VFP app and any problems (or not) they have had.
Please let me know what version of windows you are using and what version of VFP and if the server is virtualised or not.
TIA
Peter
We run several VFP9/SP2 apps (and some old FPDOS) on virtual servers of Win2008R2 (a Hyper Server (32G ram) running 3 virtuals (8GB each), 1 for the office file/print server, 1 as a web server (accessing the Fox data), and 1 as a remote desktop server, all 3 were Win2008R2) with no problems for over 2 years now. Before that the apps ran on 2003 Servers and I only recall a single .DBF of about 5000 rows being corrupted between the years of 2008 and 2013. All the workstations (about 20) were XP Pro when on the 2003 server, then they were all upgraded to Win7 Pro about 3 years before the move to the 2008 servers.
Fred
On Mon, Mar 21, 2016 at 9:47 AM, Peter Cushing <pcushing@whisperingsmith.com
wrote:
Hi,
We are currently running a VFP9 SP2 app on a windows 2003 server, which has been virtualised. We want to move to either 2008 server or preferably 2012 server. The app has a DBC and DBFs and has been running happily for over 10 years. The problem we have when transferring the data over to a virtualised 2008 or 2012 server is that we get index corruption once or more a day. We then have to move the data back. We have tried a few different configurations but do not know why this is happening.
I just want to check what servers people are using for their networked VFP app and any problems (or not) they have had.
Please let me know what version of windows you are using and what version of VFP and if the server is virtualised or not.
TIA
Peter
This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email. www.whisperingsmith.com
Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR. Tel:0161 831 3700 Fax:0161 831 3715 London Office:17-19 Foley Street, London W1W 6DW Tel:0207 299 7960
[excessive quoting removed by server]
Peter Cushing wrote on 2016-03-21:
Hi,
We are currently running a VFP9 SP2 app on a windows 2003 server, which has been virtualised. We want to move to either 2008 server or preferably 2012 server. The app has a DBC and DBFs and has been running happily for over 10 years. The problem we have when transferring the data over to a virtualised 2008 or 2012 server is that we get index corruption once or more a day. We then have to move the data back. We have tried a few different configurations but do not know why this is happening.
I just want to check what servers people are using for their networked VFP app and any problems (or not) they have had.
Please let me know what version of windows you are using and what version of VFP and if the server is virtualised or not.
TIA
Peter
Peter,
We host our data on a Server 2012 with application being run from Server 2008 accessing the data. We get CDX corruption. Some clients more than others. We have a nightly routine to index troubled clients data sets.
Since you asked this. I'm starting some research to see which files get corrupt the most. There might be a pattern to our corruption, and a pattern to the code that touches the files.
Tracy Pearson PowerChurch Software
On 21/03/2016 18:45, Tracy Pearson wrote:
We host our data on a Server 2012 with application being run from Server 2008 accessing the data. We get CDX corruption. Some clients more than others. We have a nightly routine to index troubled clients data sets. Since you asked this. I'm starting some research to see which files get corrupt the most. There might be a pattern to our corruption, and a pattern to the code that touches the files.
Thanks for the responses.
From what I've been reading the problems with SMB were version 1 and early version 2, although there is a lot of conflicting advice out there, even on mircosoft sites. As far as I can see later versions should be ok on the opportunistic locking/caching front. Found a few people who recommended turning off server leasing:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/7336d31b-6c2...
A couple of suggestions from the site:
The solution here is to leave SMB2/3 enabled but disable leasing. Leasing is just an enhanced form of OpLocks.
Here is the registry entry that needs to be added to disable server leasing for SMB2.1. You will need to reboot after setting this entry.
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters Value: DisableLeasing Type: DWORD Data: 0x1
---------------------------------------------------------
We migrated from a Windows 2008 file server cluster with four nodes to a Windows 2012 R2 file cluster with two nodes. After the migration to the new file server cluster our customers running Windows 7 SP1 started reporting Access Database corruption and slow file access. However, if the SAME Access Database file was hosted on a Windows 2012 R2 file server NOT in a cluster there was no corruption. I will not bore you with all the tests we ran while trying to determine the cause but here is what we did to fix the issue. The solution was provided via an open case with Microsoft.
1. Create the following registry entries on all Windows 2012 R2 Servers in the new file server CLUSTER and reboot.
Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
Value: DisableLeasing
Type: DWORD
Data: 0x1
We have put this change on and will see how it goes.
Thanks,
Peter
This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email.
www.whisperingsmith.com
Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR. Tel:0161 831 3700 Fax:0161 831 3715
London Office:17-19 Foley Street, London W1W 6DW Tel:0207 299 7960
My advice with Server 2008R2 and later is to leave SMB, oplocks, leasing and caching alone unless you're forced to mess with them.
On 3/21/2016 12:47 PM, Peter Cushing wrote:
I just want to check what servers people are using for their networked VFP app and any problems (or not) they have had.
I don't recall what the issue was, but We were advised to not upgrade to Server 2012, and are still using 2008R2. No problems, however, it's a hardware box, not virtual.
On 3/21/16 9:47 AM, Peter Cushing wrote:
I just want to check what servers people are using for their networked VFP app and any problems (or not) they have had.
I've had no issues hosting fox data on Linux/Samba since moving to it in the NT4 days when we had regular index corruption. The workstations connecting have gradually been replaced with newer and newer machines, the latest running Windows 10 and the oldest running Win2k (yeah, really). Still no serving issues however the newer versions of Windows needed some (well documented) registry tweaks that, depending on your setup, you won't even need to worry about.
I really wish I could shoot it in the head though and move them to postgres. Hosting business-critical data on smb has been killing me a little every day for more than a decade.
Paul
On Mon, Mar 21, 2016 at 12:47 PM, Peter Cushing pcushing@whisperingsmith.com wrote:
The problem we have when transferring the data over to a virtualised 2008 or 2012 server is that we get index corruption once or more a day.
Well, that shouldn't happen. If the machine's up to date, it ought to work. Are you seeing any errors in the logs of the server, or in the logs of the clients running that application? What else is running on the VM that might be interferring -- a resource-intensive app like Exchange, or a greedy malware scanner?
On 22/03/2016 20:25, Ted Roche wrote:
Well, that shouldn't happen. If the machine's up to date, it ought to work. Are you seeing any errors in the logs of the server, or in the logs of the clients running that application? What else is running on the VM that might be interferring -- a resource-intensive app like Exchange, or a greedy malware scanner?
Checked error logs but nothing around the time the corruption occurred. There's not much else of note running on the server apart from DNS. CPU utilisation is normally 10% or less. Definitely no exchange.
The problem has been alright for a day now so we think it may have been to do with the RDP server. We have a main and backup RDP server and they were a bit behind on windows updates. The reason for this is that sometimes the updates break the RDP software, so we usually wait a couple of weeks after updates have been released to make sure there are no problems. We then apply the updates to one server, and make sure RDP still works, then apply to the other.
We also ran this reg fix on the RDP server:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters] "FileInfoCacheLifetime"=dword:00000000 "FileNotFoundCacheLifetime"=dword:00000000 "DirectoryCacheLifetime"=dword:00000000
If we have no more problems then it could be the windows updates or the reg setting or a combination of both but hopefully that has fixed it.
Peter
This communication is intended for the person or organisation to whom it is addressed. The contents are confidential and may be protected in law. Unauthorised use, copying or disclosure of any of it may be unlawful. If you have received this message in error, please notify us immediately by telephone or email.
www.whisperingsmith.com
Whispering Smith Ltd Head Office:61 Great Ducie Street, Manchester M3 1RR. Tel:0161 831 3700 Fax:0161 831 3715
London Office:17-19 Foley Street, London W1W 6DW Tel:0207 299 7960
On Wed, Mar 23, 2016 at 7:38 AM, Peter Cushing pcushing@whisperingsmith.com wrote:
We also ran this reg fix on the RDP server:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
I'm not really sure where the RDP server plays into this, but I'm glad to hear the problem seems abated.
Lanman. Ha!
-
Alan Bourke -
Fred Taylor -
Michael Glassman -
Paul McNett -
Peter Cushing -
Richard Kaye -
Ted Roche -
Tracy Pearson -
Vince Teachout