Promotion Management Job Failure in 4.1

[abdussamad_peera]

A user is given all the required access to promote objects from dev to q and all works well except when the user has a crystal report to promote

the PM throws the following error.  As an administrator it works fine.   Any idea why?

Resolution Status=Not Applicable, Dependency Status=Not Applicable, Commit Status=Commit attempted and failed., Promotion Status=Failure : com.businessobjects.sdk.biar.BIARException$SDKException: CE SDK Exception occurred : 'The authentication credentials do not permit the operation. (FWB 00061) ' (FWM 04002)

Thanks

Abdul

[Former Member]

I am not sure if you have resolve the issue but if you are still looking for a solution try below.

Make sure the users or delegate administrator group have "Download files associated the object" right is granted.

Access level-->under add and remove--> Content-->Crystal reports

You can also try directly granting this right on the folder or crystal report you are trying to migrate and see if it resolves the issue.

[Former Member]

Hi,

Please confirm whether you have given proper rights to promote objects using SAP KBA

1712888 - BI 4.0 - Delegated Administration rights for Promotion
Management

Also check below KBA and add specific rights for Crystal Reports.

1880076 - File Repository Server error: The authentication
credentials do not permit the operation. ...

Regards,

Hrishikesh

[abdussamad_peera]

I applied rights as in 1880076 KBA but now I get a different error;

Resolution Status=Copied, Dependency Status=All the required dependencies are included., Commit Status=Commit attempted and failed., Promotion Status=Failure : The property of an object is not unique

I have created a brand new promotion job with a different crystal report than the original one (which generates the same error).

Abdul

[Former Member]

Does the object exists in destination system? If it exists, check the CUID of of the report in both systems. If it does not match, you need to delete the report from destination and promote.

[abdussamad_peera]

Ironically the objects are getting promoted to destination but the Job Status is failure!

I checked the CUID in both are same.  However the ID is different (which i believe is ok).

I have tried deleting the crystal from destination but then PM throws some error about

ID not being unique!  Somehow it still remembered the old promoted object ID.  

So I selected another report which didn't exist in destination and it gets

promoted except the Job status is failure (no specific reason).

Should the ID along with CUID be the same?  Even when I am promoting a brand new

crystal that doesn't exist in destination it fails.

[Former Member]

HI,

The idea of migrating object is to keep the CUID same in both the environment.

ID is not a problem for us.

Also, if you are migrating a object which is already there in destination, both should have same CUID else you would face problem like you are in.

Regards,

Jatin

[Former Member]

Is the crystal is based on universe or BVM? Some times BVM might be a culprit.

[abdussamad_peera]

Crystal is based on a universe on a relational DB.

[Former Member]

Check the connection and Universe CUIDs of both the systems. Make sure they are identical in source and destination system.