Daktronics

When clicking Publish to display, receive error 'Venus 1500 has encountered a problem and needs to close.' and software crashes out.

Potential Symptoms

  • When clicking Publish to display in Venus 1500 v4, receive the following error:
    • Venus 1500 has encountered a problem and needs to close. We are sorry for the inconvenience.
    • DD2491235 1.jpg
  • When viewing the Venus 1500.log file located at C:\Program Data\Daktronics\Venus 1500 V4 or C:\Documents and Settings\All Users\Application Data\Daktronics\Venus 1500 V4, you see the following error:
    • The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://standards.daktronics.com/schemas/CommonPlayerAddIn_1_0:playerSchedule. The InnerException message was 'There was an error deserializing the object of type Daktronics.CommonPlayer.ServiceContract.Data.PlayerSchedule. The 'maximum bytes per Read operation' quota (4096) has been exceeded while reading XML data. Long element start tags (consisting of the element name, attribute names and attribute values) may trigger this quota. This quota may be increased by changing the MaxBytesPerRead property on the XmlDictionaryReaderQuotas object used when creating the XML reader.'.  Please see InnerException for more details.
    • DD2491235 2.jpg

Environment

  • Product Family: Software
  • Product: Galaxy, GalaxyPro
  • Component:
  • Control System: Venus 1500 v4.17

Cause

  • The schedule file needing to be published to the display became larger then what the Nucleus Server and Display knows to handle.

Resolution

  • None at this time.

For Temporary Operation

Step 1: Add maxBytesPerRead="2000000000" to the Nucleus Server.exe.config file.

  1. Go to Windows Start Menu, click Computer or My Computer.
  2. Navigate to the following location:
    • Windows 32 Bit - C:\Program Files\Daktronics\Nucleus Server
    • Windows 64 Bit - C:\Program Files (x86)\Daktronics\Nucleus Server
  3. Locate and right-click on Nucleus Server.exe.config, choose Open With.
  4. Select Notepad or click Browse and locate Notepad.
  5. Type [Control] + [F], to bring up the Find window.
  6. Type in the following: <netNamedPipeBinding>
  7. Click Find Next.
  8. You will see the below coding:
    • <netNamedPipeBinding>
              <binding name="netNamedPipe" receiveTimeout="14:00:00" sendTimeout="00:05:00" maxBufferSize="2000000000" maxReceivedMessageSize="2000000000">
                <readerQuotas maxStringContentLength="2000000000" maxArrayLength="2000000000">
                </readerQuotas>
                <security mode="None">
                </security>
              </binding>
              <binding name="netNamedPipeStream" receiveTimeout="14:00:00" sendTimeout="00:05:00" transferMode="Streamed" maxBufferSize="2000000" maxReceivedMessageSize="2000000000">
                <readerQuotas maxStringContentLength="2000000000" maxArrayLength="2000000000">
                </readerQuotas>
                <security mode="None">
                </security>
              </binding>
            </netNamedPipeBinding>
  9. After the two maxArrayLength="2000000000" highlight in the area above, type in the following: maxBytesPerRead="2000000000" *Note, 2 with 9 zeroes
  10. The code should now read like below:
    • <netNamedPipeBinding>
      <binding name="netNamedPipe" receiveTimeout="14:00:00" sendTimeout="00:05:00" maxBufferSize="2000000000" maxReceivedMessageSize="2000000000">
      <readerQuotas maxStringContentLength="2000000000" maxArrayLength="2000000000" maxBytesPerRead="2000000000">
      </readerQuotas>
      <security mode="None">
      </security>
      </binding>
      <binding name="netNamedPipeStream" receiveTimeout="14:00:00" sendTimeout="00:05:00" transferMode="Streamed" maxBufferSize="2000000" maxReceivedMessageSize="2000000000">
      <readerQuotas maxStringContentLength="2000000000" maxArrayLength="2000000000" maxBytesPerRead="2000000000">
      </readerQuotas>
      <security mode="None">
      </security>
      </binding>
      </netNamedPipeBinding>
  11. Click File -> Save.

Step 2: Restart the Daktronics Nucleus Server.

Step 3: Try and re-publish the playlist to the display.

 

KB ID: DD2491235

DISCLAIMER: Use of this content may void the equipment warranty, please read the disclaimer prior to performing any service of the equipment.

DAKTRONICS DOES NOT PROMISE THAT THE CONTENT PROVIDED HEREIN IS ERROR-FREE OR THAT ANY DEFECTS WILL BE CORRECTED, OR THAT YOUR USE OF THE CONTENT WILL PROVIDE SPECIFIC RESULTS. THE CONTENT IS DELIVERED ON AN "AS-IS" AND "AS-AVAILABLE" BASIS. ALL INFORMATION PROVIDED IN THIS ARTICLE IS SUBJECT TO CHANGE WITHOUT NOTICE. DAKTRONICS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANY WARRANTIES OF ACCURACY, NON-INFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. DAKTRONICS DISCLAIMS ANY AND ALL LIABILITY FOR THE ACTS, OMISSIONS AND CONDUCT OF YOU OR ANY THIRD PARTIES IN CONNECTION WITH OR RELATED TO YOUR USE OF THE CONTENT. ADJUSTMENT, REPAIR, OR SERVICE OF THE EQUIPMENT BY ANYONE OTHER THAN DAKTRONICS OR ITS AUTHORIZED REPAIR AGENTS MAY VOID THE EQUIPMENT WARRANTY. YOU ASSUME TOTAL RESPONSIBILITY FOR YOUR USE OF THE CONTENT AND ANY LINKED CONTENT. YOUR SOLE REMEDY AGAINST DAKTRONICS FOR DISSATISFACTION WITH THE CONTENT IS TO STOP USING THE CONTENT. THIS LIMITATION OF RELIEF IS A PART OF THE BARGAIN BETWEEN THE PARTIES.

The above disclaimer applies to any property damage, equipment failure, liability, infringement, or personal injury claim arising out of or in any way related to your use or application of the content, whether such claim is for breach of contract, tort, negligence or any other cause of action.