Forum Discussion

Ole_S_P's avatar
Ole_S_P
New Contributor III
25 days ago

Genesis cannot start: "Value cannot be null."

Hi

What to do when I get this error messages in Genesis:

 

Unable to open dashboard 'OpenPlace_(Designer)'.

Error processing DataSet 'GetWFSteps'. Error executing Workspace Assembly Service class 'Workspace.Gen.CubeViewCharts_x2x.MUAssemblyFactory'.Value cannot be null. (Parameter 'reader').

How to reset?

The problem happens when working with Block: Cube View Charts. It will not read my cube view and give the following comment: Value cannot be null. An error messages that is difficult to work with, as it does not say where the problem is. But this second, as I cannot get into the genesis instance.

2 Replies

  • JSlone's avatar
    JSlone
    Icon for OneStream Employee rankOneStream Employee

    Hello,

    I am not entirely sure why it's throwing an error on your chart, but to get back into your instance, try resetting your parameters (this can only be done from the WinApp):

     

     

     

     

    Once you're in the Designer, you can delete the block causing the error and start again.

    If that doesn't clear the error so you can get back to the Genesis Designer, then in this case you can resolve it from the Genesis Workspace.

    1. Go to the Application | Workspaces page, and locate your Genesis Workspace
    2. Expand the workspace and scroll down to the Maintenance Units labeled 'XLI_Page. You will see there is a Maintenance Unit for each block you have injected in your instance. 
    3. Locate the Cube View Charts Maintenance Unit throwing the error and delete the entire Maintenance Unit. 

      Then you can go back into the Designer and try again.

      Just to make sure, you've confirmed the Cube View renders as normal when running it by itself, correct?  What chart type are you using? Also, please ensure you're using the latest version of the block (if not connected to the Content Library via Azure).

     

  • keski's avatar
    keski
    New Contributor II

    we have the same issue. I'll update if we resolve it