Have any of you had issues with BR not wanting to load due to drive statement issues? I had a similar problem in 2016 (it's the previous thread in this forum section). This might be related to that (or even the same problem that is continuing). We tried most of the suggestions then, but never really solved the issue. And odd thing is that we can get the problem to stop by turning off Windows Defender! When Windows Defender is on, we get a 4152 error processing the drive statement. Then another msgbox appears, saying "Problem converting the BR path L:\BR\WBSERVER.DAT to an OS path. This could be a drive statement problem". The drive statement is L:,L;,L;,\BR
Note that this happens almost every time on ONE workstation and very sporadically on others. So MOST of the time, BR loads just fine with this drive statement. And when the error occurs, I CAN access the BR folders on the network via My Computer or File Explorer. It's just that BR is choking.
As per the suggestions last year, I tried using the UNC name in the drive statement, but it didn't make any difference. And the odd thing is that it USUALLY works. It works reliably on almost all of the 15 workstations. But one workstation will fail almost every time unless we turn off Windows Defender. We were using Cylance Anti-virus, but it seemed to have even MORE problems with BR so we took it off temporarily. On this one problematic workstation, the user just keeps a window open at all times so she can turn off Windows Defender when she goes into BR, and turn it back on when she needs to access the web. Silly, but it works. Of course, if she needs to access the internet WHILE she is in BR, she walks to another workstation because we have asked her not to access the internet when there is no anti-virus running on her workstation. Some of the other workstations exhibit the same thing, but only every once in a while.
We are running BR 4.2o on a Windows Server 2008 network. All workstations are running up to date Win7.
I don't know where to go next with this. The poor network/hardware guy is pulling his hair out. We may considering going to Client Server, but the boss is unhappy with that solution (for the time being) and wants me to find out what's going on.