Forum Discussion

DanielCapilla's avatar
DanielCapilla
Level 4
4 years ago

Display problem "Storage" - no entries / rows to small

Hi, does anyone have a solution for this display problem? BE 21.1 Best regards, Daniel
  • DanielCapilla's avatar
    DanielCapilla
    4 years ago

    Update. I could solve it on my own.

    The corresponding registry values, that define the view seemed to be cotrupt.

    Solution:
    Computer\HKEY_CURRENT_USER\Software\Veritas\Backup Exec For Windows\Backup Exec\21.0\User Interface\GridColumns\storageTreeView

    delete storageTreeView or rename it. 


    When restarting Backup Exec. It is fixed, because the key is recreated with default values.

DanielCapilla's avatar
DanielCapilla
Level 4

Only under the storage tab.
I restarted the server several times and also changed the language from german to english, but no change.

Clicking inside the "invisible" spaces works, so you may navigate to the tape-drive, b2d and so on ... but
the text and graphics are missing, like in the screenshot documented.

DanielCapilla's avatar
DanielCapilla
Level 4
4 years ago

Update. I could solve it on my own.

The corresponding registry values, that define the view seemed to be cotrupt.

Solution:
Computer\HKEY_CURRENT_USER\Software\Veritas\Backup Exec For Windows\Backup Exec\21.0\User Interface\GridColumns\storageTreeView

delete storageTreeView or rename it. 


When restarting Backup Exec. It is fixed, because the key is recreated with default values.

  • RogRubin's avatar
    RogRubin
    Moderator
    4 years ago

    Great that you managed to fix this issue and hopefully your solution might help someone else in a similar situation.
    Your response and sharing your solution is much appreciated.

    FYI - I did some test and tried to corrupt the key by changing entries in the values, deleted the values completetly and even renamed the main key you mentioend above.
    All I had to do is to close / open the BE GUI (I did not neet to restart the services) and the key was back and everything was working, meaning I could not reproduce the issue.
    Anyway, thanks again for sharing the solution.