Question Re: RepoScan in Source and Destination? Commit Status=Commit attempted and failed in Technology Q&A

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

victortorreblanca — Tue, 27 Jun 2023 07:36:51 GMT

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?

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

ayman_salem — Tue, 27 Jun 2023 08:17:27 GMT

What error did you get in the log file?

The most common reason is that there is an Object with the same name in the Recycle Bin. Therefore, empty the recycle bin before importing.

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

victortorreblanca — Tue, 27 Jun 2023 08:23:13 GMT

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

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

Joe_Peters1 — Tue, 27 Jun 2023 11:41:04 GMT

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.

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

JohnClark — Tue, 27 Jun 2023 13:12:31 GMT

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.

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

victortorreblanca — Tue, 27 Jun 2023 13:14:31 GMT

Hello,

indeed what we want to transport...does not exist on Production yet.

I'm on my way to obtain the logs

Thanks!

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

victortorreblanca — Wed, 28 Jun 2023 12:28:22 GMT

In the glf file I see this:

|EA5C60361A144EB4B824BAA7F9D547700|2023 06 28 10:43:57.453|+0100|Error| |==|E| |aps_vhgpvbopsbo01.APS.PromotionManagementVictor| 2122| 84|service builder-5| |0|0|0|0|-|-|-|-|-|-||||||||||com.businessobjects.lcm.utilities.LCMLogger||[SingletonWithFailoverServiceManager, AU7oR.6xB11IowSY3_XY.9o, #initAndSetBeanId] Service with bean ID 89 is hosted by server with friendly name: vhgpvbopsbo01.AdaptiveProcessingServer5 |

EA5C60361A144EB4B824BAA7F9D547701|2023 06 28 10:43:58.633|+0100|Error| |==|E| |aps_vhgpvbopsbo01.APS.PromotionManagementVictor| 2122| 80|service builder-1| |0|0|0|0|-|-|-|-|-|-||||||||||com.businessobjects.lcm.utilities.LCMLogger||[SingletonWithFailoverServiceManager, AZopnyVDx8tDj8vbuiHNTjs, #initAndSetBeanId] Service with bean ID 87 is hosted by server with friendly name: vhgpvbopsbo01.AdaptiveProcessingServer5 |

EA5C60361A144EB4B824BAA7F9D547702|2023 06 28 10:46:37.015|+0100|Error| |>>|E| |aps_vhgpvbopsbo01.APS.PromotionManagementVictor| 2122| 67|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||java.lang.ArrayIndexOutOfBoundsException: while trying to load from index 0 of an object array with length 0, loaded from field com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.POANameHasher.poaID_ of an object loaded from local variable 'this' |

EA5C60361A144EB4B824BAA7F9D547703|2023 06 28 10:46:37.016|+0100|Error| |>>|E| |aps_vhgpvbopsbo01.APS.PromotionManagementVictor| 2122| 67|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.POANameHasher.<init>(POANameHasher.java:48)

|EA5C60361A144EB4B824BAA7F9D547704|2023 06 28 10:46:37.016|+0100|Error| |>>|E| |aps_vhgpvbopsbo01.APS.PromotionManagementVictor| 2122| 67|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.POALocator.locate(POALocator.java:66)

|EA5C60361A144EB4B824BAA7F9D547705|2023 06 28 10:46:37.016|+0100|Error| |>>|E| |aps_vhgpvbopsbo01.APS.PromotionManagementVictor| 2122| 67|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.POAManager_impl._OB_locatePOA(POAManager_impl.java:709)

|EA5C60361A144EB4B824BAA7F9D547706|2023 06 28 10:46:37.016|+0100|Error| |>>|E| |aps_vhgpvbopsbo01.APS.PromotionManagementVictor| 2122| 67|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OBPortableServer.POAOAInterface_impl.createUpcall(POAOAInterface_impl.java:120)

|EA5C60361A144EB4B824BAA7F9D547707|2023 06 28 10:46:37.016|+0100|Error| |>>|E| |aps_vhgpvbopsbo01.APS.PromotionManagementVictor| 2122| 67|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPServerWorker.executeRequest(GIOPServerWorker.java:569)

|EA5C60361A144EB4B824BAA7F9D547708|2023 06 28 10:46:37.017|+0100|Error| |>>|E| |aps_vhgpvbopsbo01.APS.PromotionManagementVictor| 2122| 67|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPServerWorker.execute(GIOPServerWorker.java:439) |

EA5C60361A144EB4B824BAA7F9D547709|2023 06 28 10:46:37.017|+0100|Error| |>>|E| |aps_vhgpvbopsbo01.APS.PromotionManagementVictor| 2122| 67|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPServerWorkerThreaded.receiverRun(GIOPServerWorkerThreaded.java:456) |

EA5C60361A144EB4B824BAA7F9D54770a|2023 06 28 10:46:37.017|+0100|Error| |>>|E| |aps_vhgpvbopsbo01.APS.PromotionManagementVictor| 2122| 67|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPServerWorkerThreaded$ReceiverThread.run(GIOPServerWorkerThreaded.java:129) |

EA5C60361A144EB4B824BAA7F9D54770b|2023 06 28 10:46:37.017|+0100|Error| |>>|E| |aps_vhgpvbopsbo01.APS.PromotionManagementVictor| 2122| 67|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||Exception in thread "ORBacus:Server:ReceiverThread" com.crystaldecisions.thirdparty.com.ooc.OB.AssertionFailed: ORBacus encountered an internal error

|EA5C60361A144EB4B824BAA7F9D54770c|2023 06 28 10:46:37.017|+0100|Error| |>>|E| |aps_vhgpvbopsbo01.APS.PromotionManagementVictor| 2122| 67|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OB.Assert.assertTrue(Assert.java:42) |

EA5C60361A144EB4B824BAA7F9D54770d|2023 06 28 10:46:37.018|+0100|Error| |>>|E| |aps_vhgpvbopsbo01.APS.PromotionManagementVictor| 2122| 67|ORBacus:Server:ReceiverThread| ||||||||||||||||||||||at com.crystaldecisions.thirdparty.com.ooc.OB.GIOPServerWorkerThreaded$ReceiverThread.run(GIOPServerWorkerThreaded.java:134)

In the trc file I see this:

[Thr 46918734292736] Wed Jun 28 11:43:55 2023

[Thr 46918734292736] ***LOG Q0I=> NiPConnect2: 127.0.0.1:6404: connect (111: Connection refused) [nixxi.cpp 3283]

[Thr 46918734292736] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 1/sock 554 (SI_ECONN_REFUSE/111; I4; ST; 127.0.0.1:6404) [nixxi.cpp 3283]

[Thr 46918734292736] *** ERROR => NI raw handle failed to be initilized at IDEL to CONNECTED, connection to agent destination failed to be established in agent 1 [ncsmtdatasen 137]

[Thr 46918738495232] Wed Jun 28 11:44:51 2023

[Thr 46918738495232] *** ERROR => NI raw handle failed to be initilized at IDEL to CONNECTED, connection to agent destination failed to be established in agent 1 [ncsmtdatasen 137]

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

ayman_salem — Wed, 28 Jun 2023 14:01:40 GMT

What I meant by log file is the result of the Promotion job (Details)

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

victortorreblanca — Wed, 28 Jun 2023 14:04:26 GMT

Hi Ayman, this is how it looks like

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

ayman_salem — Wed, 28 Jun 2023 14:17:28 GMT

So it appears to be a user rights issue as the promotion user does not have sufficient rights to add/replace the objects.

If you want contact me via LinkedIn, maybe I can help you.

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

victortorreblanca — Wed, 28 Jun 2023 14:23:31 GMT

Hi Ayman,

I added you in LinkedIn
I'm not sure about the rights, I tried with the AdminUser and also didnt work 😞

Regards

Victor Torreblanca

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

ayman_salem — Wed, 28 Jun 2023 14:29:47 GMT

see LinkedIn

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

victortorreblanca — Fri, 30 Jun 2023 08:37:21 GMT

I still believe it's a problem of communication between the BO Platform the CMS to commit the changes...

[Thr 46918734292736] ***LOG Q0I=> NiPConnect2: 127.0.0.1:6404: connect (111: Connection refused) [nixxi.cpp 3283]

[Thr 46918734292736] *** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 1/sock 554 (SI_ECONN_REFUSE/111; I4; ST; 127.0.0.1:6404) [nixxi.cpp 3283]

[Thr 46918734292736] *** ERROR => NI raw handle failed to be initilized at IDEL to CONNECTED, connection to agent destination failed to be established in agent 1 [ncsmtdatasen 137]

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

ayman_salem — Fri, 30 Jun 2023 09:02:52 GMT

Then stop the BI system and check whether port 6404 is free and not being used by another program.

Then restart the BI system.

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

victortorreblanca — Fri, 30 Jun 2023 16:46:20 GMT

Dear friends

I found the problem and the solution.

It is described in https://me.sap.com/cases/002075129400005354592023

On Production environment, I went to CMC > Servers > Rite click on Nodes > User Security

I added the user we use to import files in BO Production and gave him view rights

Now it works fine 🙂