Sage Line 50 ACCOUNT.DTA lock not being released (Operating system locking issue).
We have a client with a small company that uses Sage Line 50.
The environment is a Windows 2008 R2 Server with Windows 7 clients using roaming profiles. The users are all on Windows 7 with all the Sage data files on a dedicated share on the Windows 2008 R2 Server.
We have the following issue:
Sage Line 50 relies on users being able to access a file called ACCOUNT.DTA
Intemittently users are being locked out of Sage.
Interogation of the Share and File Manager on the server reports that the ACCOUNT.DTA file is still open for write access, preventing further users accessing it, resulting in a system wide 'hang' of Sage.
The only way to relase this lock is via the Server Share and File Manager.
The strange thing is that the task that the user was doing in Sage HAS completed, but it looks like the lock is simply not being released back to the Operating system to allow the next user access to do their transaction.
We have had this problem for some time now and have been through all the usual hoops from Sage themselves, including running without anti-virus etc etc etc, with no real hope of a solution.
Sage support has now suggested moving the users to a peer to peer network (they obviously have no idea how disruptive this is going to be for a 'quick test').
I am keen to know if there is any history of Windows Server 'hiccuping' in this way and failing to release locks back to users and whether there is something I can try from an O/S point of view, having exhausted Sage support.
The environment is a Windows 2008 R2 Server with Windows 7 clients using roaming profiles. The users are all on Windows 7 with all the Sage data files on a dedicated share on the Windows 2008 R2 Server.
We have the following issue:
Sage Line 50 relies on users being able to access a file called ACCOUNT.DTA
Intemittently users are being locked out of Sage.
Interogation of the Share and File Manager on the server reports that the ACCOUNT.DTA file is still open for write access, preventing further users accessing it, resulting in a system wide 'hang' of Sage.
The only way to relase this lock is via the Server Share and File Manager.
The strange thing is that the task that the user was doing in Sage HAS completed, but it looks like the lock is simply not being released back to the Operating system to allow the next user access to do their transaction.
We have had this problem for some time now and have been through all the usual hoops from Sage themselves, including running without anti-virus etc etc etc, with no real hope of a solution.
Sage support has now suggested moving the users to a peer to peer network (they obviously have no idea how disruptive this is going to be for a 'quick test').
I am keen to know if there is any history of Windows Server 'hiccuping' in this way and failing to release locks back to users and whether there is something I can try from an O/S point of view, having exhausted Sage support.
ASKER
Hi,
Further investigation has shown the following: Sage is having locking issues with both 'READ' and 'READ/WRITE' locks. Either lock is not being release or taken out correctly and results in users 'locked out' and reciving error messages.
We have three users and each day we are getting 10-20 of these lockouts.
Now that we are monitoring it ourselves rather than letting Sage support 'handle' the issue we are noticing that various '.dta' files are being locked and not released.
Some files can be released by rebooting the machine (but not all). We are able to release all locks using the Share and File Manager and we are choosing this option as it is the cleanest and less disruptive to the users. Once the offending lock is terminated all error messages clear from other users and any queued ransactions continue OK.
Further investigation has shown the following: Sage is having locking issues with both 'READ' and 'READ/WRITE' locks. Either lock is not being release or taken out correctly and results in users 'locked out' and reciving error messages.
We have three users and each day we are getting 10-20 of these lockouts.
Now that we are monitoring it ourselves rather than letting Sage support 'handle' the issue we are noticing that various '.dta' files are being locked and not released.
Some files can be released by rebooting the machine (but not all). We are able to release all locks using the Share and File Manager and we are choosing this option as it is the cleanest and less disruptive to the users. Once the offending lock is terminated all error messages clear from other users and any queued ransactions continue OK.
Is SMB 2 disabled on one of the machines, had it been disabled in the past, for some other application in a mixed environment?
I would use SMB2ToggleToo to check and reset all PC's and Servers to have SMB2 enabled (or disabled).
http://www.symantec.com/connect/downloads/smb2-toggle-too-mikes-tool-set
If you are in a mixed environment with ANY SMB1 Servers/Workstations/Devic
I would use SMB2ToggleToo to check and reset all PC's and Servers to have SMB2 enabled (or disabled).
http://www.symantec.com/connect/downloads/smb2-toggle-too-mikes-tool-set
If you are in a mixed environment with ANY SMB1 Servers/Workstations/Devic
ASKER
I've been looking at the SMB2 issue previously.
Our server is a Windows 2008R2 and all the clients are windows 7, all with the latest patches and updates. SMB2 has not been disabled on any client or on the server.
I will, however, follow your advice and double check that no third party has seen fit to disable SMB2 and that all the clients and the server are running like for like on SMB2.
Regards.
Our server is a Windows 2008R2 and all the clients are windows 7, all with the latest patches and updates. SMB2 has not been disabled on any client or on the server.
I will, however, follow your advice and double check that no third party has seen fit to disable SMB2 and that all the clients and the server are running like for like on SMB2.
Regards.
ASKER
This problem is proving very frustrating. All Sage suggest is that we disband out environment and revert back to a pier to pier network. So are we really saying that Sage Line 50 does not work in a domain environment?
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
There are plenty of people using sage in a windows domain environment, it CAN work.
I would check that the network is working properly.
What level of packet loss under load are each of the workstations experiencing.
I would check that the network is working properly.
What level of packet loss under load are each of the workstations experiencing.
ASKER
There is no real solution.
I would monitor the issue and see if it is all users that are not releasing locks or just one.
It could be something daft such as a bad port on a switch dropping packets a duff network card driver etc etc.
Locked files has been an issue, but since V2012 much less of one.
Does logging the user off and back on again would release the lock?