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?

[victortorreblanca]

Hi Ayman,

unfortunately I dont have access to the logs 😞 But Im going to request them

Yes, I had come accross that issue in the past and I tried that solution the first, but no...it's not the case

The recycle bin is empty.

We requested to run ScanRepo on Prod. env. and it's been done. But I have the feeling that also has to be run on Test env. and I will have to regenerate the lcmbiar files.

But this is just my theory.

The question would be: "After an upgrade, if you need to run ScanRepo, does it have to be done in all the environments?"

Thanks, best regards

Victor Torreblanca

[Joe_Peters1]

You really need the LCM logs -- the error is generic and the actual problem could be any number of things.

Running reposcan occasionally isn't a bad idea. If you run it without the -repair option, it'll just output the list of problems it found but doesn't actually change anything.

Be careful with reposcan. It has caused problems for me in the past. I typically just run it without -repair, get the list of problems, and address them manually.

One problem it causes is that it'll change the owner ID of completed scheduled instances if the original owner ID is no longer valid. The problem is that the timestamp of those instances gets updated to the current time. So you have all instances of a report with the same timestamp.