Solution exception:No data is available for encoding 0

nastasiasnk · August 19, 2025, 7:19am

Hi there!

Recently I have encountered the following error that appears in all ladybug, honeybee and dragonfly components:
1. Solution exception:No data is available for encoding 0. For information on defining a custom encoding, see the documentation for the Encoding.RegisterProvider method.

Error logs
Runtime error (NotSupportedException): No data is available for encoding 0. For information on defining a custom encoding, see the documentation for the Encoding.RegisterProvider method.

Traceback:
line 950, in open, "C:\Program Files\Rhino 8\Plug-ins\IronPython\Lib\logging_init.py"
line 920, in init, “C:\Program Files\Rhino 8\Plug-ins\IronPython\Lib\logging_init_.py”
line 64, in init, “C:\Program Files\Rhino 8\Plug-ins\IronPython\Lib\logging\handlers.py”
line 171, in init, “C:\Program Files\Rhino 8\Plug-ins\IronPython\Lib\logging\handlers.py”
line 9, in , “C:\Program Files\ladybug_tools\python\Lib\site-packages\honeybee_init_.py”
line 65, in get_logger, “C:\Program Files\ladybug_tools\python\Lib\site-packages\honeybee\logutil.py”
line 46, in script

LB tools version - 1.9.0
Rhino version - 8.22

The error appeared after I have imported codecs library using old python component in Rhino 8, but I am not sure if that can be a direct reason.

The other strange thing is that there is badge “old” on all components, despite that this is the latest version.

The error disappears only when starting Rhino as administrator. But it’s my work computer so I can’t do that myself.

What has been done:

Pollination reinstallation
Full Rhino reinstallation
We tried to install LB tools to user folder too
We tried to add different python path to env variables
All this didn’t help and we run out of ideas : (

Other plugins or scripting components in Grasshopper are not affected. I am wondering if you can suggest any other solutions. I rely on ladybug a lot in my work, and it’s the first time even reinstallation didn’t help.

Best,
Nastia

chris · March 30, 2026, 7:13pm

Hi @nastasiasnk ,

I am very sorry that this fell through the cracks months ago. It would seem that you are not alone as another user also experienced this issue on the Pollination forum.

I tried to recreate the issue on my machine by importing the codecs module but I have not had any success:

The traceback is useful and I can see that this is the line of our code that triggers the failure:

github.com

ladybug-tools/honeybee-core/blob/master/honeybee/logutil.py#L65


      
              filename: Logger filename.Setting filename to None will remove the file handler
                  (Default: honeybee.log).
              file_log_level: Log level for file handler as a string (Default: DEBUG).
              console_log_level: Log level for stream handler as a string (Default: WARNING).
          """
          logger = logging.getLogger(name)
          
          # create a file handler to log debug and higher level logs
          if filename:
              log_file = os.path.join(_get_log_folder(), filename)
              file_handler = TimedRotatingFileHandler(log_file, when='midnight')
              file_format = logging.Formatter('%(asctime)s - %(name)s - %(levelname)s - %(message)s')
              file_handler.setFormatter(file_format)
              file_handler.setLevel(_get_log_level(file_log_level))
              logger.addHandler(file_handler)
          
          # create a console handler that only prints out errors and warnings
          stream_handler = logging.StreamHandler()
          stream_format = logging.Formatter('%(name)s - %(levelname)s - %(message)s')
          stream_handler.setFormatter(stream_format)
          stream_handler.setLevel(_get_log_level(console_log_level))

… but the failure itself is deep within the IronPython that ships with Rhino and it’s technically an issue that is more on McNeel’s side of things.

However, we might just be able to put the line of code on the Ladybug Tools side into a try/except with no negative consequence and this would solve the issue. Before I try to do this, do you have a sample file with how you are importing the codecs module that might help me recreate the issue?

chris · March 30, 2026, 7:21pm

I also have another question for you - is there a chance that you have a non-ASCII character in your username? I can see how this possibly could trigger an encoding error here.