Getting odd 'build_broadcast_args' error

When I tried my GMiner app today, I am getting an odd error that hasn't occurred before. Anyone know what the issue is?
My setup 'string':

Getting the same message, all my older rigs are down

Swampcritter wrote: When I tried my GMiner app today, I am getting an odd error that hasn't occurred before. Anyone know what the issue is?

Code:

+----------------------------------------------------------------+
|                          GMiner v2.60                          |
+----------------------------------------------------------------+
Algorithm:          Ethash
DevFee:             0.65%
Stratum server:
  host:             prohashing.com:3358
  user:             [Sanitized]
  password:         l=4,i=e3_180,a=ethash-lowmemory,n=[Sanitized]
Power calculator:   on
Color output:       on
Watchdog:           on
API:                off
Log to file:        off
Selected devices:   GPU0
Intensity:          100
Temperature limits: 90/120
------------------------------------------------------------------
00:26:11 Nvidia Driver: 471.11
00:26:11 Connected to prohashing.com:3358 [50.220.121.209]
00:26:11 Authorized on Stratum Server
00:26:11 Connection Error: 'NoneType' object has no attribute 'build_broadcast_args'
00:26:17 Connected to prohashing.com:3358 [50.220.121.209]
00:26:17 Authorized on Stratum Server
00:26:17 Connection Error: 'NoneType' object has no attribute 'build_broadcast_args'
00:26:22 Connected to prohashing.com:3358 [50.220.121.209]
00:26:22 Authorized on Stratum Server
00:26:22 Connection Error: 'NoneType' object has no attribute 'build_broadcast_args'
00:26:22 All user mining pools are unavailable
00:26:22 Miner terminated, watchdog will restart process after 10 seconds
00:26:44 Miner terminated, watchdog will restart process after 10 seconds

My setup 'string':

Code:

C:\GMiner>miner.exe --algo ethash --server prohashing.com:3358 --user [Sanitized] --pass l=4,i=e3_180,a=ethash-lowmemory,n=[Sanitized]

Thanks for submitting a ticket about this issue. Since we don't have any indication that this issue is widespread, let's continue our discussion there, where I can collect more information about your account.

This issue has been resolved by restarting the mining servers.

We aren't sure what caused the issue, and will perform further investigation if it happens a second time. Thanks for the report!

This error has come back once again. Just started seeing it today.

22:02:42 Nvidia Driver: 472.12
22:02:42 Connected to prohashing.com:3358 [50.220.121.209]
22:02:42 Authorized on Stratum Server
22:02:42 Connection Error: 'NoneType' object has no attribute 'build_broadcast_args'

2:09:37 Nvidia Driver: 457.09
12:09:37 Connected to prohashing.com:3358 [50.220.121.209]
12:09:38 Authorized on Stratum Server
12:09:38 Connection Error: 'NoneType' object has no attribute 'build_broadcast_args'
12:09:43 Connected to prohashing.com:3358 [50.220.121.209]
12:09:43 Authorized on Stratum Server
12:09:43 Connection Error: 'NoneType' object has no attribute 'build_broadcast_args'

seanief wrote: 2:09:37 Nvidia Driver: 457.09
12:09:37 Connected to prohashing.com:3358 [50.220.121.209]
12:09:38 Authorized on Stratum Server
12:09:38 Connection Error: 'NoneType' object has no attribute 'build_broadcast_args'
12:09:43 Connected to prohashing.com:3358 [50.220.121.209]
12:09:43 Authorized on Stratum Server
12:09:43 Connection Error: 'NoneType' object has no attribute 'build_broadcast_args'

Swampcritter wrote: This error has come back once again. Just started seeing it today.

22:02:42 Nvidia Driver: 472.12
22:02:42 Connected to prohashing.com:3358 [50.220.121.209]
22:02:42 Authorized on Stratum Server
22:02:42 Connection Error: 'NoneType' object has no attribute 'build_broadcast_args'

If you haven't already, please make sure to submit a support ticket so we can address the issue.

Sarah Manter wrote: If you haven't already, please make sure to submit a support ticket so we can address the issue.

Sent one in yesterday.

This issue has finally been identified and resolved, but the changes have not yet been released. Chris will schedule a time for the release later today.

The fix has been released as of 6 PM EDT today.
Let us know if you're experiencing any further issues!