SageForum for UK versions of Sage 50- Help and support.

Hi guys,

I help some friends of mine with their IT. They have historically used Sage in a client/server environment without issues.

Mainly Win 7 clients, 2 x Win 10 and a Win 7 pro machine acting as a server in a workgroup.

Recently, they began to have issues with Sage hanging and eventually crashing many times a day.

Have been backwards and forwards with Sage, we moved the data from the server to another PC and this cleared the crashing issue up, however, Sage did run slowly.

Fast forward, a new server has been purchased, basically a very powerful PC (i7, 16GB ram etc.) Sage support are happy that is everything is installed correctly on the new server. Sage is now stable, however, it is now taking up to a minute to load the login prompt from the splash screen on the client machines. On the server install itself, the login prompt appears immediately.

Any ideas what might be causing this? The only thing that has changed is a new server, which is now running Win 10 as opposed to Win 7, with a new server name.

All client machines have been connected to new location, company file edited and are using unc path. As stated, the server has a different name to the old one. Will this make any difference?

The network is fine, it does EVERYTHING at a very good speed. It is also used as a file and print server.

Sage have been on remotely again today and are scratching their heads. They have removed A/V, turned off firewalls etc. but still no change.

Thanks for reading!

Windows 10 indexing service had caused issues renaming files on shares. I would try excluding the sage data path from indexing.

Also worth checking the smb2 settings if they had a mixed environment in the past smb2 could be turned off on the win7 machines.

Antivirus has been uninstalled on both workstations and server but have the exclusions been set up in windows defender?

Hi Bruce,

Thanks for replying.

Windows Defender is turned off on all machines.

With regards to SMB, I read this, "Networking Issues - SMB2 and SMB1 mixed environments cause really bad performance. You need to switch off SMB2 on all new PC's until such time as you have no XP or earlier PC's you can then enable SMB2 on all equipment. There is a great free tool to simplifiy SMB2 settings SMB2toggletoo" and assumed it only applied to XP and earlier machines.

Would you be kind enough to clarify please?

Thanks.

SMB is Server Message Block, it is a Microsoft protocol for sharing files mainly used in windows but emulated by other systems.

The new version SMB2 that came with W7 was partly incompatible with SMB1 (Old Microsoft systems and by implication non Msoft systems) so it caused things to not work as we would like and got a lot of people to buy upgrades.

To fix this without upgrading you can make W7 ignore SMB2 and always use SMB1 and the problem goes away, until years later you change the server and it uses SMB2 (or 3!) at which point it goes slow, you can force the server to SMB1 and it will work again, or you can change the Workstations to use SMB2/3 and it will work again but faster and better.