Why Do My SystemLink Enterprise States Show Empty With Errors?

Updated Jan 23, 2026

Reported In

Software

  • SystemLink Enterprise

Issue Details

I can create new system software states in SystemLink Enterprise, but when I click on the state to edit it afterwards, it always appears empty and pops up the error that the state does not exist.

Solution

It is likely that you have an invalid encryption string configured in the systemstate.secrets.encryptionKey field of the Helm chart you used most recently to deploy your SystemLink Enterprise.  All encryption keys in SystemLink Enterprise must be plain strings that are exactly 32 bytes long and contain only alphanumeric characters (A-Z, a-z. 0-9).  Here are 2 different methods to generate a valid (and random) encryption key:

 

  • Powershell
    -join ((48..57) + (65..90) + (97..122) | Get-Random -Count 32 | % {[char]$_})
  • Open SSL
    openssl rand -base64 24






The result will look like this:  G6h8K2mN9pQ1rT4uX7yZ2aB5dE8gH1jm

                                    


                        

                    

                

 
                
                

                

                

                    

                        

                            
                            

                                

                                    

                                    


                                    

                                        
Other Support Options

                                        
Ask the NI Community

                                        
Collaborate with other users in our discussion forums

                                        
                                        

                                        

                                        
Request Support from an Engineer

                                        
A valid service agreement or active software subscription may be required, and support options vary by country.