"Object Reference Not Set to Instance of Object" on full build

Follow

Kevin Hobson

October 16, 2018 15:40

I have a cube that won't build anymore but I can't determine where the problem is. The only error I get is "Object Reference Not Set to Instance of Object". This happens on a full build (the knowledge base article with this error seems to be limited to a schema build)

0

• 

  Liliia Romanchuk November 02, 2018 15:09

  Hi,

  This is a very generic error so that there might be different causes of the issue. Please submit a request to the support team for further investigation.

  Regards,

  Lily

  -1

  Comment actions Permalink
• 

  Katie Garrison July 03, 2019 19:05

  In case you run into this message and a full build did not resolve the issue, please reference this section of the Build Errors Troubleshooting article. I've added a section about how to resolve this issue if a full build does not help.

  _______________________________________________________________

  Error message: "Object reference not set to an instance of an object"

  

  Build Stage: Initializing Build (or prior to Initialization)

  Note: This error can result from a few different issues, most commonly for custom columns and custom tables. It is also helpful to think about what changed in the model before you encountered this error.

  Troubleshooting: 

  Verify naming and references of each of the custom SQL expression tables and columns. 
  Also try a full build of the cube.

  Steps:

  1. Start out with trying a full build of the Elasticube.
  2. If you see this error at the beginning of a build, open each custom SQL table and parse/preview the expression. Verify table and column names match what is in the model.
  3. Try a full build.
  4. If you still see issues, open each custom column and parse/preview the expression. Verify table and column names match what is in the model.
  5. Try another full build.

  0

  Comment actions Permalink

Please sign in to leave a comment.