I’ve a couple of users having an issue with my C6 app and was wondering if anyone had any pointers. The app is freezing on 2 client sites, but if they leave it 3-5 mins it comes back to life. 1 client site is running on W10 desktops where the data is stored on a Windows 2019 server, and the other site is running via terminal services into a Windows 2019 server.
They are getting no error messages, and everytime I run diagnostic checks on the data everything is fine.
I’m wondering if this has something to do with SMB1/2 and/or OpLocks…
“A few weeks ago, I upgraded from Windows 7 Ultimate to Windows 10 Pro. The
most frustrating problem has been that mapped drives on my server frequently
disconnect. One of my database programs relies on a mapped drive and keeps
Wondering if anyone has suggestions… Posted in Clarion9 newsgroup, as
My software is written in Clarion 9.1, uses Topspeed database files, and
is a multi-dll application.
We have a client who has been successfully running our software for
years. They recently upgraded their PC’s from Windows 7 to Windows 10.
The workstations are running Windows 10 Pro version 2004. During their
testing phase, before the official OS upgrade, if they returned to
Windows 7, all was once again fine.
Since the OS upgrade, they have random lock-ups within our application.
All PC’s on the network have the problem. The lockups happen when the
PC sits idle, and frequently when simply closing a window in the
program. Often, there are no record updates happening, but sometimes
they are entering records.
They have removed anti-virus software and Windows Defender.
Sometimes, the lockup is just a spinning circle. Other times, the
program says it can’t find a file, but it has no filename (which it
normally would). It’s as if they’ve lost their network connection,
though they have tried doing some continuous pings, which confirm the PC
is still connected to server.
Thanks Carl, I’ll take a read, from an initial quick scan of the text it sounds exactly like my users are experiencing, and yet at one site the IT guys placed a utility on a workstation to test the ping to the server and it never failed a ping test, well one client anyway, as the other client is using Terminal Services…
Thanks Sean. After running ProcMon (thanks Jeff! :)) the system isn’t actually crashing, it’s waiting, because a file it’s requesting (and this changes per freeze) cannot be locked due to a Network Error, so I’ve forwarded on Carl’s suggestions to the client’s IT department. The ProcMon logs also show an awful lot of NAME NOT FOUND errors when referencing C:\Windows\CSC\v2.0.6\namespace…, which when I’ve googled is something to do with local cache for offline files…
As for the AV, I did think that ages ago, but that hasn’t changed in recenty times and it also has an exception to ignore .TPS files.