Author Topic: Published Cube Package not seen as dimensional data - ANS-ERR-0003  (Read 982 times)

Offline cheriesheriff

  • Full Member
  • ***
  • Join Date: Nov 2011
  • Posts: 7
  • Forum Citizenship: +1/-0
We upgraded from Cognos 8.4 to 10.1 over this past weekend. 

When I publish my cubes from Transformer, the cube packages cannot be selected by Analysis Studio (the underline that shows it is applicable is not there).  If there are no changes to the model, I can link to the package from an existing report.  If there are changes to the model, I receive an ANS-ERR-0003 trying to load the package in Analysis Studio this way. 

I have system admin permissions.  I have selected to operate in any namespace.  My data source test succeeds.  My model has no errors on a model check. 

I have even taken a model we have in production and produced a new cube from it as a different name and cannot access it through Analysis Studio.

Does anyone have any ideas where else I should look to resolve this issue?

Offline bdbits

  • Statesman
  • ******
  • Join Date: Feb 2010
  • Posts: 514
  • Forum Citizenship: +38/-0
A few ideas:
* Check the server logs for any related error messages. You may find more information there.
* When you build a cube, it produces a log file. Check that to see if there were any warnings or errors when the cube was built.
* If you have in-cube security, make sure you have appropriate permissions there.

Usually, when I have seen that error, it was due to lacking access to any of the cube data, most often from security filters. Depending on how your authentication is set up and how you migrated this could be part of the problem. Or not. It is hard to tell without knowing more about your setup.

Offline cheriesheriff

  • Full Member
  • ***
  • Join Date: Nov 2011
  • Posts: 7
  • Forum Citizenship: +1/-0
I am thinking this may have something to do with my x64 vs x86 environments.  In production, I can publish the cubes and access them just fine.  Only in my development environment am I seeing this issue. 

I currently have sysadmin permissions in both places for troubleshooting this out, there is no cube security built.  There are no errors on the build of the cube either. 

I am looking at the patch levels in both environments as well to try to determine how to fix our development environment. 

Thank you for your response. 

 



         
Twittear