Unable to upload content via Local File Networking (LFN) in BrightAuthor

Last Updated: June 7, 2016

There is currently a known bug that affects the upload/transfer of content to the BrightSign player while publishing a presentation via Local File networking. This issue seems to affect some users that have enabled Authentication by entering a password for the Local Web Server (via the User name and Password options in Tools > Setup BrightSign Unit > Unit Configuration).

If you have enabled Authentication for the Local Web Server when setting up the player, follow the below steps to resolve this issue.

1) Clear the player registry using the steps described in this FAQ.

2) Close BrightAuthor.

3)Find and delete the BrightSignUnits.xml file for the version of BrightAuthor you're currently using. The path should be similar to the following:

4) Open BrightAuthor.

5) Go to Tools > Setup BrightSign Unit to create a new setup card without a password for the Diagnostic Web Server or Local Web Server.

6) Insert the new setup card into the player.

7) Connect the power cable (or Ethernet cable if using PoE).

8) In BrightAuthor go to the Publish tab, Select New Unit, click the "+" icon to add the new unit IP address, and click OK.

Note: If you don't know the IP address of your player, see this FAQ for help.


Have more questions? Submit a request


  • 0

    I was experiencing similar issues with a communication error to the BrigthSign unit when publishing content over the Local Network.

    Following the steps to clear the player's registry, upon reboot the messages do not appear. The unit simply displays the logo and version #.

    I am also having trouble locating the BrightSignUnits.xml file.


  • 0

    @BSmith - You need to create and apply the unit setup files again after clearing the player registry, as the clear deletes those files and settings.

    The BrightSignUnits.xml file is in %appdata%..\Local\BrightSign\BrightAuthor_ver.sion.num.ber_

    For example, if you have BrightAuthor installed, it would be in %appdata%..\Local\BrightSign\BrightAuthor\

  • 0
    Patrick Straffen

    Thank you for this solution! Is there a way to set a username and password after the unit has been set up? Resetting the unit as described above fixed my communication error, but it would be most helpful to still be able to use credentials to access the unit.

  • 0

    Hi Patrick,

    Is there a way to set a username and password after the unit has been set up?

    Yes, but that would probably cause the file upload to fail again. If you access the DWS page (FW 6.0.25+) at the bottom of the info page there is a link for "set password".

    However it might be useful (for debugging purposes) to get a TCP dump captured whilst the file upload does fail when the DWS password is enabled. In order to start the Network capture process before the upload failure happens, please go to the Diagnostics tab > Network Packet Capture > Network Capture > click Start.

    Please note that the default capture time is set to 5 minutes (300 seconds) so depending on when the upload fails you may need to adjust the capture time. When the failure upload message does appear in BA, click stop in the DWS (to stop the network capture process). Download the capture.pcap file and uploaded it to a FTP or via www.wetransfer.com and provide the download link so we can review the capture file.





  • 0
    Dustin Prather

    When will the ability to set authenticated users be restored.  I do not want to leave the device on the network without restricted administrative access.  I can send files that are >500MB, but anything larger than that is failing and the log file states. 

    Exception is: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.

    at System.Net.ScatterGatherBuffers.AllocateMemoryChunk(Int32 newSize)

    at System.Net.ScatterGatherBuffers.Write(Byte[] buffer, Int32 offset, Int32 count)

    at System.Net.ConnectStream.InternalWrite(Boolean async, Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callback, Object state)

    at System.Net.ConnectStream.Write(Byte[] buffer, Int32 offset, Int32 size)

    at BrightAuthor.HTTPPost.HttpUploadFile(String url, String filePath, String fileName, NameValueCollection nvc, String userName, String password, LWSPublisher lwsPublisher)

    at BrightAuthor.LWSPublisher.UploadFileToBrightSign(String filePath, String fileName, String sha1, LocalBrightSign lbs)

  • 1

    Are there any plans to address this issue?  I keep encountering this issue, and not being able to use authentication is just not acceptable (not to mention, resetting the firmware remotely is just not an option).

    Edited by lightbulb
  • 0
    MidwichAU Support

    If you update the BrightAuthor version you are using to the latest, is this likely to also fix this issue? Or do we still need to follow the above instructions to fix this issue?



  • 0
    Mike Orlovsky

    Did this issue ever get fixed?

  • 0
    Patrik Palos

    This issue is still present 8 years later. I'm using latest BA:c and latest production OS. How has this issue not been addressed yet?

    Edited by Patrik Palos
Please sign in to leave a comment.
Can't find what you're looking for? Try to
Powered by Zendesk