"Child is not Folder && not VMPG && not SPPG" error while running SRM configuration export tool

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:
SRM import/export tool throw an error " Child is not Folder && not VMPG && not SPPG"
Impex.log shows below errors.

2019-04-10 17:19:00,214 [srm-reactive-thread-6] WARN  com.vmware.srm.client.reactive.impl.PromiseImpl - Function 'com.vmware.srm.client.impex.exporters.folders.ProtectionGroupFoldersExporter$$Lambda$139/1949817751@1b0bbad9' failed.
java.lang.IllegalStateException: Child is not Folder && not VMPG && not SPPG.
    at com.vmware.srm.client.impex.exporters.folders.ProtectionGroupFoldersExporter.lambda$getChildren$220(ProtectionGroupFoldersExporter.java:111)
    at java.util.stream.ReferencePipeline$3$1.accept(Unknown Source)
    at java.util.Spliterators$ArraySpliterator.forEachRemaining(Unknown Source)
    at java.util.stream.AbstractPipeline.copyInto(Unknown Source)
    at java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
    at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(Unknown Source)
    at java.util.stream.AbstractPipeline.evaluate(Unknown Source)
    at java.util.stream.ReferencePipeline.collect(Unknown Source)
    at com.vmware.srm.client.impex.exporters.folders.ProtectionGroupFoldersExporter.getChildren(ProtectionGroupFoldersExporter.java:115)
    at com.vmware.srm.client.impex.exporters.folders.ProtectionGroupFoldersExporter.lambda$getConfigurables$219(ProtectionGroupFoldersExporter.java:68)
    at com.vmware.srm.client.reactive.impl.PromiseImpl$ApplyCompletion.complete(PromiseImpl.java:244)
    at com.vmware.srm.client.reactive.impl.PromiseImpl$Result.complete(PromiseImpl.java:39)
    at com.vmware.srm.client.reactive.impl.PromiseImpl$Completion.lambda$null$1(PromiseImpl.java:71)
    at com.vmware.srm.client.utilities.ThreadContext.lambda$wrap$7(ThreadContext.java:38)
    at com.vmware.srm.client.utilities.ThreadContext.execute(ThreadContext.java:183)
    at com.vmware.srm.client.utilities.ThreadContext.execute(ThreadContext.java:193)
    at com.vmware.srm.client.utilities.ThreadContext.execute(ThreadContext.java:176)
    at com.vmware.srm.client.utilities.ThreadContext.setupContext(ThreadContext.java:59)
    at com.vmware.srm.client.utilities.ThreadContext.setupContext(ThreadContext.java:87)
    at com.vmware.srm.client.reactive.impl.PromiseImpl$Completion.lambda$setResult$2(PromiseImpl.java:71)
    at com.vmware.srm.client.reactive.impl.AsyncDispatcherImpl$Worker.run(AsyncDispatcherImpl.java:34)
    at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
    at java.util.concurrent.FutureTask.run(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

Environment

VMware vCenter Site Recovery Manager 8.x

Cause

• The issue is caused as PG name has special characters like @ ! and spaces between the name

Resolution

Note: Stop the SRM service on both sites (Production and recovery) and take a back of the SRM DB

• Stop the SRM service from services.msc console 
• Backup SRM DB - https://docs.vmware.com/en/Site-Recovery-Manager/8.1/com.vmware.srm.install_config.doc/GUID-E1FC67CD-48E3-4B25-AA1D-8A2408F5B517.html
• Re-name PG and remove special characters and spaces if present.