If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Transformer 8.4.2 TR0646 Error

Started by nj, 26 Jan 2010 08:10:48 AM

Previous topic - Next topic

nj

Hello

I've found a few solutions to this problem but none seem applicable to our particular issue.

In the Transformer 8.4.2286 gui, models (pyj and mdl) will randomly not build or validate due to the following errors:

PowerPlay Transformer DA Server  Tue Jan 26 02:51:21 2010
Tue 26 Jan 2010 02:51:24   2   00000000   (TR0646) Column or filter 'House Number' is based on reference '[Report].[All Houses.0].[HouseNo]' which cannot be found in package or report 'Non PP House Names'.
Tue 26 Jan 2010 02:51:25   3   00000000   (TR0649) One or more columns or filters cannot be found in datasource 'Non PP House Names Query'. [->OK]


This is also the case using a batch file with cogtr.exe to build.

By checking columns and using the data source viewer manually, a successful build can be obtained. Also we run these overnight using a scheduler that keeps attempting to build the cube if it fails like this. After 4 attempts, the cube usually succeeds with no user intervention.

I have so far tried the following:

  • Amending the data source reports to make them simpler (e.g. no filters etc.)
  • Amending the package the data source reports use to have only one namespace
  • Adding the COGROOT system variable to Environment Variable on the OS where transformer runs
  • Updating Transformer to the latest release
  • Adding a default signon
  • Changing the signon

I'm now about out of ideas. Note that these models are not upgrades from 8.3. There is no issues with accessing iqds or local csv data sources etc. The signon seems fine, since the cube does build some of the time.

Any ideas or comments would be greatly, greatly appreciated.

Siogie

NJ - I'm having a similar issue running the same version of Transformer.  Did you find a solution?

My cube builds successfully in the DEV environmment both in the GUI and using batch job.  For system testing I copied the .MDL to the test server. 

Every time I open in Transformer on TEST server and run Check Model I get TR0649 / TR0646 errors.  I don't make any changes and run Check Model again and error has disappeared.  The batch process to build the cube fails with TR0646/TR0649 as each run is equivalent to re-opening of Transformer. 

I'm very new at this and inclined to think it may be a path or preference setting that's different between my DEV and TEST box, but I could be way off base. 

We are using SSO and like you I do not believe the issue is with it as the cube build works after the second check model.  I've also set the COG_ROOT system variable referenced in other posts without success.

I'm running out of ideas and appreciate your help.

bdbits

I know this post is getting old and these are just some general ideas, but it sounded desperate. :)

I am assuming your data source is an FM package and you are on Windows. Please back up your models (FM and Transformer) first. Then see if any of the following help:

* Republish the Framework Manager model. If it has any issues, fix and repeat until you get an error-free publish, and if building on another server export/import the package to the target server. Try a build.

* If you have an exported model file (*.mdl), import it and try to use that. If successful save that as your model (*.pyj). Note: Generally, you should actively work with pyj and not mdl files. It is also a good practice to periodically export to a *.mdl file as *.pyj files are known to sometimes get corrupt.

* Export the model *.pyj to a *.mdl file and then import the mdl back in, and try a build.

* Open your mdl and do Tools > Clean House... then try a build.

* Make sure Tools > Check Model comes up clean.

* Permissions can also be important to a successful build. Not only Cognos permissions, but filesystem permissions to several folders on the build box. If possible, have yourself included in the "Local Administrators" group to mitigate potential permissions issues.