RepoScan in Source and Destination? Commit Status=Commit attempted and failed

[#1]

Dear all,

we have migrated our Test and Production BO systems to 4.3.

I exported a Report from Test into a .lcmbiar file, with the idea of using Promotion Management to move it to Production.

But when I try to transport it, I get the error "Commit Status=Commit attempted and failed., Promotion Status=Failure : Object has failed to promote. Please see the log for more details."

Then we tried to run RepoScan in Production, but we still get same error again.

Does RepoScan have to be run in BO Test environment as well?

[JohnClark]

The Repository Diagnostic Tool (RepoScan) won't necessarily fix you problem, there are only certain things that it does. As joe.peters2 says, you have to be careful when you run it as well.

Only the LCM Logs will tell you what is actually happening. Even then, the log entries may not very helpful unfortunately.

If you report already exists in Production, make sure that the CUID for the report is the same that it is in Test. They must match in order to have a successful migration. I've seen this were users delete and replace a report in Test and then it won't migrate. You usually get a different error message for this case though.