Slow printing with Event ID error 512
This is affecting multiple users in our environment. We are running BarTender 2019 R10 and last night I had updated my Windows Server 2019 to include several updates, 2021-10 Cumulative Update Preview for .NET Framework 3.5, 4.7.2 and 4.8 for Windows Server for x64 (KB5006847), 2021-10 Cumulative Update Preview for Windows Server 2019 (1809) for x64-based Systems (KB5006744), and 2021-10 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5006672). Now today my users are encountering very slow printing. After checking the Windows Event Viewer, I'm seeing
Log Name: Application, Source: Seagull TCP Library V3, Event ID: 512, Level: Warning.
bartend.exe: TCPSocketWithReUse::Connect: SocketException occurred. ID: 0x00000000224EA770, Host:server02.corp.company.net, Port: 5130 Error: 0x0000274C A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
I've seen these errors before but printing hasn't been this slow. At first I created a firewall rule to allow all domain TCP connections to port 5130 on server02 (not my actual server name) and that did not fix the issue. I then turned off the firewall completely and even that did not fix the issue. All services are running on server02.
Are the Windows updates at fault? Is there something else going on? What should be listening on port 5130?
Not 100% sure, but from Seagull driver version 2017.1 the drivers started using port 5130 (instead of 6130) for the language monitor for internal comms with the Seagull drivers plus for status monitoring and network settings sharing features.
It could be if you are using older Seagull drivers that it maybe worth updating these to the recent ones as the Windows update may have caused an issue with them.0
Adding the following. My license is for the automation version of BarTender. My new ERP system integrates with it. So I just finished installing the ERP client on the same machine as the license server so there should be no communication issues since everything is local. I'm still getting the same event ID 512 errors above and my printouts are deathly slow. Oh, and this was after I had removed KB5006744 and KB5006672.
This is slow. Extremely slow. I'm figuring that timeouts need to happen before anything gets printed. If I wait long enough (10+ minutes), I get the print prompts and/or the print occurs. So while things are working, something has changed that is causing the delays and I haven't figured it out yet.0
I did get mixed up with the server that BarTender was connecting to. The server in question was actually my network printer server, not the server BarTender was installed on. So it turns out that either KB5006744 or KB5006366 on my printer server was causing the issue. BarTender could not talk to the actual printer server -- I was printing through a UNC location like \\server02\my label printer.
After uninstalling both Windows Server updates, I am working normally now and have not received the event ID 512 errors since removing the two updates from the print server.0
Since two days I see bad Performance with Integration Service. We print from an application server to printers which are specified in interface scriptfile with UNC \\Printserver\Printername.
On the application server I see lots of warnings like this
BarTend.exe: TCPSocketWithReUse::Connect: SocketException occurred. ID: 0x000000001E667BB0, Host:DEPS101, Port: 5130 Error: 0x0000274D No connection could be made because the target machine actively refused it.
Which functionality uses Port 5130?
Monitoring is disabled?
Should the TCP connection between Application Server and Printserver over port 5130 enabled?0
As above Seagull Language Monitor uses port 5130 to allow bi-directional communication with the printers. Have you checked for recent updates on the server, such as the ones mentioned above, as they seemed to be blocking this port from being used?0
Hi Pete, thanks a lot for support. I discovered that when I enable bidirectional communication the performance is good.0
Same problem. After installing the newest driver (2022) the problem is fixed.0
Please sign in to leave a comment.