Hi to all,
I'm facing a problem in a simple and small model that I'm developing in Cognos Planning 10.1.
Because the client is using SQL 2012 and I was getting errors regarding the SQL DMO usual issues, I've installed SQL 2008 Express in the server and recreated the model with this environment.
When publishing the cube (around 40 elist itens with 2 small dimensions in the cube), I get a cancel information when I have only one item left (this test was done after placing information in one item of the elist).
The error I got is :
2013-01-18T19:13:16.871+00:00
Machine details: COGNOS\COGNOSPLANNING
User details: COGNOSPLANNING\bi4all
Process ID / Thread ID: 5896 / 5272
Source: ACE2_10.ModelBlock
ErrorGuid: {7F7DE6D8-45DD-4FE7-884C-352774F0FFA2}
StackPosition: 3
PreviousUserDomain: COGNOSPLANNING
PreviousUserName: bi4all
PreviousComputerDomain: COGNOS
PreviousComputerName: COGNOSPLANNING
Error Number: -2147352567
Line Number: 400
Description: Unable to execute Job Item
Execution failed after 3 attempt(s).
Exceptions were generated in the property access or method call. If GetLatestExceptionInformation is called next it will return further information of interest. :
Message 0 of 6: Exception Code: unpack_cannot_open_later_version
Text: Cannot open ModelBlock : it is a later version. Object level=5.0000 class level=4.0000
Orignator Class:
Originator Guid: {00000000-0000-0000-0000-000000000000}
Originator Name:
Date/Time: 2013-01-18 19:13:16
Message 1 of 6: Exception Code: unpack_cannot_open_later_version
Text: Cannot open ModelBlock : it is a later version. Object level=5.0000 class level=4.0000
Orignator Class:
Originator Guid: {00000000-0000-0000-0000-000000000000}
Originator Name:
Date/Time: 2013-01-18 19:13:16
Message 2 of 6: Exception Code: unpack_cannot_open_later_version
Text: Cannot open ModelBlock : it is a later version. Object level=5.0000 class level=4.0000
Orignator Class:
Originator Guid: {00000000-0000-0000-0000-000000000000}
Originator Name:
Date/Time: 2013-01-18 19:13:16
Message 3 of 6: Exception Code: unpack_cannot_open_later_version
Text: Cannot open ModelBlock : it is a later version. Object level=5.0000 class level=4.0000
Orignator Class:
Originator Guid: {00000000-0000-0000-0000-000000000000}
Originator Name:
Date/Time: 2013-01-18 19:13:16
Message 4 of 6: Exception Code: unpack_cannot_open_later_version
Text: Cannot open ModelBlock : it is a later version. Object level=5.0000 class level=4.0000
Orignator Class:
Originator Guid: {00000000-0000-0000-0000-000000000000}
Originator Name:
Date/Time: 2013-01-18 19:13:16
2013-01-18T19:13:22.050+00:00
Machine details: COGNOS\COGNOSPLANNING
User details: COGNOSPLANNING\bi4all
Process ID / Thread ID: 5896 / 4576
Source: JobExecutor_10.Executor.RunJobEndIfAppropriate
ErrorGuid: {AEC6D7C5-B6DC-4A5B-9440-4A91DF296525}
StackPosition: 2
PreviousUserDomain: COGNOSPLANNING
PreviousUserName: bi4all
PreviousComputerDomain: COGNOS
PreviousComputerName: COGNOSPLANNING
Error Number: -2147220566
Line Number: 280
Description: Unable to get Job Item
The Job management step failed. An attempt has been made to mark the 'REPORTING_PUBLISH' Job as CANCELLED. Please rectify the problem and re-create a similar Job.
Job Task {1537EEFE-7438-48A4-9D6A-028491429266} is not attempting JobEnd because there are 1 FAILED job items
Does anyone have any idea on this subject?
Thanks in advance, Best regards,
Jorge
Hey there,
You are running into a known defect with the product. Essentially, the node(s) that it's failing on is of a newer version than the rest of the elist items / environment. This can happen if you use the 10.1.1 contributor client to access a 10.1.0 elist item. It will upgrade that node to the newer 10.1.1 code and make it non-functional in the 10.1.0 environment.
To fix the problem:
Since the elist item has been upgraded, you will need to restore the application from backup, or re-create the application in the CAC.
Moving forward:
From what I can recall, there is a 10.1.0 hotsite that you can get in touch with IBM to obtain that should prevent this issue from occurring again.
We decided to install cognos planning 10.1.1 and we were able to resolve the issue.
Thanks for the feedback.
Excellent. Yes, that would be another solution to the problem. :)
Glad you worked it out.