ExecuteReader: CommandText Property Has Not Been Initialized

Comments

3 comments

  • Avatar
    FIadmin Non-Production (Edited )

    We are having the same issue. The builds run fine when executed from ECM but the build always fails with the message above when running the builds from the Sisense web application. Is there any update for this?

    We are running Sisense 7.2.0.12014.

    Thanks,

    Mark

    0
    Comment actions Permalink
  • Avatar
    Katherine Mackenzie

    Hello!

    I think I finally figured it out. With all of my SQL connections I had checked the Encrypt and Trust Connection options and once I reconnected the tables, I did not check the the Encrypt and Trust, and now it works great. I'm not sure why encrypting would cause that issue. I hope that helps. 

    0
    Comment actions Permalink
  • Avatar
    Michelle Mangion

    Hi ,

    I am experiencing an error 'ExecuteReader: CommandText property has not been initialized' with a particular new Table when I try to import it from a SQL SERVER database. I have tried importing it from several cube to check, but I always get the failure result.

    I have also built a new ElasticubeCatalog and refreshed the ECM Service. Anyone has experienced this and how was it resolved please?

     

    thanks.

     

     

     

    0
    Comment actions Permalink

Please sign in to leave a comment.