OS Layer Finalize fails with error “It looks like the packaging Machine has never been powered on”.

While finalizing an OS layer edit in the App Layering appliance, you receive an error, “It looks like the packaging Machine has never been powered on.”

Can see the below error in ELM logs:

2019-11-01 09:53:36,890 ERROR [27] CpTaskResultMessag: Got Error type GlobalizedError. FailureReason: It looks like the Packaging Machine has never been powered on. Please power it on, install your applications, and double-click the Shutdown for Finalize icon.. Details: No extra details found.

Related:

  • No Related Posts

User may be unable to reconnect to Existing sessions.

User may be unable to reconnect to Existing sessions. You may also see machine failure with reason none, in Citrix Director

You may see following errors in traces:

TdUdtListenerCreate: Retry number XX to listen: Listener <Hex number> on port 2598″,””

“setListener failed”,””

CUDTUnited::listen failed. Error:-28″,””

CUDT::listen Error:-28″,””

TdUdtListenerCreate: UDT::listen error 0xffffffe4″,””

Related:

  • No Related Posts

XenApp 7.15 : Cannot update Machine Catalogue “PBM error occurred during PreProcessReconfigureSpec: pbm.fault.PBMFault”

After updating a machine catalog that was created using Machine Creation Services (MCS), virtual machines hosted on vSAN 6 or later might fail to start. The following error message appears in the VMware console:

“A general system error occurred: PBM error occurred during PreProcessReconfigureSpec: pbm.fault.PBMFault; Error when trying to run pre-provision validation; Invalid entity.”

Related:

  • No Related Posts

IDM profile indexing “Error: Indexing was unsuccessful. Check the log files for details”

I need a solution

Hello,

after upgrade to DLP 15.1 MP1 + hotfixes 15.1.0102 and 15.1.0105 I’m getting error while doing IDM profile indexing “Error: Indexing was unsuccessful. Check the log files for details.” During document indexing, enforcer shows error event: “Code: 3000 Summary: Protect Error 1001: Unexpected indexing error occurred. Detail: Protect Error 1001: Unexpected indexing error occurred. Document profile wasn’t created.”

I did some tests in lab enviroment and found out, that problem with IDM indexing starts after applying the Hotfix_15.1.0102.

In the Tomcat log I see below errors:

Thread: 73 SEVERE [com.vontu.profiles.manager.document.DocumentRepository] Unknown error during document indexing Cause: java.lang.NoClassDefFoundError: com/vontu/messaging/chain/message/NativeFileInfo java.lang.NoClassDefFoundError: com/vontu/messaging/chain/message/NativeFileInfo at com.vontu.directorycrawler.DiscoverNativeFile.getFileInfo(DiscoverNativeFile.java:71) at com.vontu.directorycrawler.VontuFile.retrieveFileTimes(VontuFile.java:1783) at com.vontu.directorycrawler.VontuFile.lastModified(VontuFile.java:842) at com.vontu.profiles.manager.document.DocumentRepository.createRepository(DocumentRepository.java:114) at com.vontu.profiles.manager.document.DocumentRepository.<init>(DocumentRepository.java:66) at com.vontu.profiles.manager.document.DocumentRepositoryFactory.createDocumentRepository(DocumentRepositoryFactory.java:37) at com.vontu.profiles.manager.document.DocumentSourceIndexCreator.doIndex(DocumentSourceIndexCreator.java:374) at com.vontu.profiles.manager.document.DocumentSourceIndexCreator.indexInfoSourceOnManager(DocumentSourceIndexCreator.java:309) at com.vontu.profiles.manager.InfoSourceIndexCreator.indexListOfDataSources(InfoSourceIndexCreator.java:254) at com.vontu.profiles.manager.document.DocumentSourceIndexJob.index(DocumentSourceIndexJob.java:31) at com.vontu.profiles.manager.InfoSourceIndexJob.execute(InfoSourceIndexJob.java:75) at org.quartz.core.JobRunShell.run(JobRunShell.java:213) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557) 15 Jan 2019 13:00:00,943- Thread: 73 SEVERE [com.vontu.profiles.manager.document.DocumentSourceIndexCreator] Error during document indexing Cause: com.vontu.profiles.common.ProfilesException: com/vontu/messaging/chain/message/NativeFileInfo com.vontu.profiles.common.ProfilesException: com/vontu/messaging/chain/message/NativeFileInfo at com.vontu.profiles.manager.document.DocumentRepository.createRepository(DocumentRepository.java:177) at com.vontu.profiles.manager.document.DocumentRepository.<init>(DocumentRepository.java:66) at com.vontu.profiles.manager.document.DocumentRepositoryFactory.createDocumentRepository(DocumentRepositoryFactory.java:37) at com.vontu.profiles.manager.document.DocumentSourceIndexCreator.doIndex(DocumentSourceIndexCreator.java:374) at com.vontu.profiles.manager.document.DocumentSourceIndexCreator.indexInfoSourceOnManager(DocumentSourceIndexCreator.java:309) at com.vontu.profiles.manager.InfoSourceIndexCreator.indexListOfDataSources(InfoSourceIndexCreator.java:254) at com.vontu.profiles.manager.document.DocumentSourceIndexJob.index(DocumentSourceIndexJob.java:31) at com.vontu.profiles.manager.InfoSourceIndexJob.execute(InfoSourceIndexJob.java:75) at org.quartz.core.JobRunShell.run(JobRunShell.java:213) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)

0

Related:

  • No Related Posts