We are having problems using Windows Server 2012 R2 with BR - errors mainly related to file input/output, network errors, record locking and file locking.
I've tried both Client/Server and non-Client/Server versions of BR. I've also tried BR versions 4.2, 4.3, and 4.31 - none of them are working well with Windows Server 2012 R2.
Has anyone else used Windows Server 2012 R2 with BR?
Windows Server 2012 R2 problems
Moderators: Susan Smith, admin, Gabriel
Re: Windows Server 2012 R2 problems
Try to search the forum for "SMB2", there are a few threads on it.
Also, our #1 answer to Microsoft Windows issues is:
http://www.petri.com/how-to-disable-smb ... r-2008.htm
SMB2 even fully patched still is a cause of data corruption (Sometimes).
Also, our #1 answer to Microsoft Windows issues is:
http://www.petri.com/how-to-disable-smb ... r-2008.htm
SMB2 even fully patched still is a cause of data corruption (Sometimes).
Re: Windows Server 2012 R2 problems
Thank you, Luis, I will try this solution...
On another note, I am using PDFLIB.dll to print to PDF, and it works fine for regular BR, but NOT in Client-Server.
Here is my open statement:
open #255: 'name=PDF:/Adobe PDF,PrintFile='&save_name$&',recl=1000',display,output
In non-client server, I get a file as a result, but in client-server the program acts like everything is working, but the file disappears after I close #255:
On another note, I am using PDFLIB.dll to print to PDF, and it works fine for regular BR, but NOT in Client-Server.
Here is my open statement:
open #255: 'name=PDF:/Adobe PDF,PrintFile='&save_name$&',recl=1000',display,output
In non-client server, I get a file as a result, but in client-server the program acts like everything is working, but the file disappears after I close #255:
Re: Windows Server 2012 R2 problems
In Client Server, you need to worry about where you put the 'PrintFile'.
Printfile=test.pdf will be created in your application, probably on the server.
Printfile=@::Test.pdf will be created in your Client Folder
This code worked for me in client server. The file was Created on the 'C: Drive in the Same Folder as BRclient.exe
Printfile=test.pdf will be created in your application, probably on the server.
Printfile=@::Test.pdf will be created in your Client Folder
This code worked for me in client server. The file was Created on the 'C: Drive in the Same Folder as BRclient.exe
Code: Select all
00010 OPEN #255: "name=PDF:/READER,PrintFile=@::Test.pdf,recl=1000",DISPLAY,OUTPUT
00020 PRINT #255: "TEST"
00030 CLOSE #255:
Re: Windows Server 2012 R2 problems
When I use "@::" everything works fine, but when I do not, the file doesn't get saved to the server for some reason...
On another hand, back to the previous issue:
We disabled SMB 2, which seems to have solved the problem with users getting kicked out, but cost us performance-wise... Luis, is this something you experienced as well?
On another hand, back to the previous issue:
We disabled SMB 2, which seems to have solved the problem with users getting kicked out, but cost us performance-wise... Luis, is this something you experienced as well?
Re: Windows Server 2012 R2 problems
Yes, SMB2 is faster because it does things like assume Opportunistic Locking on multiple machines simultaneously.
That's fine, except data gets damaged.
That's fine, except data gets damaged.
Re: Windows Server 2012 R2 problems
I take that back. We turned off SMB 2 and are still getting reports of people getting kicked out...
Is anyone else using Client/Server BR 4.31 with a Windows server and Windows clients?
If so, what is your Windows server OS version and Windows client OS versions?
Is anyone else using Client/Server BR 4.31 with a Windows server and Windows clients?
If so, what is your Windows server OS version and Windows client OS versions?