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

Session Recording Agent Install Fails with “Error 1920, Service 'Citrix Session Recording Agent' (CitrixSmAudAgent) failed to start. Verify that you have sufficient privileges to start services.”

When attempting to install the session recording agent, the installation fails with the following message:

Installer Information

Error 1920. Service ‘Citrix Session Recording Agent’ (CitrixSmAudAgent) failed to start. Verify that you have sufficient privileges to start services.

System Event Log shows that Session Recording Agent service failed to start because SessionRecordingDriver service is not installed.

Related:

  • No Related Posts

'404 Not Found' when trying to browse a newly published Managed Path in SharePoint when accessed using Storage Zones Controller SharePoint Connector

After publishing a new Managed Path in SharePoint, you may find that attempts to access this resource by using Storage Zones Controller SharePoint Connector fail. Upon closer inspection, the Storage Zone Controller log files may contain error messages similar to the following:

ERROR GetParent:: Exception thrown Message(The remote server returned an error: (404) Not Found.) StackTrace( at System.Net.HttpWebRequest.GetResponse()

at Microsoft.SharePoint.Client.SPWebRequestExecutor.Execute()

at Microsoft.SharePoint.Client.ClientContext.GetFormDigestInfoPrivate()

at Microsoft.SharePoint.Client.ClientContext.EnsureFormDigest()

at Microsoft.SharePoint.Client.ClientContext.ExecuteQuery()

at SharePointConnector*Util.SharePointUtility.GetParent(ClientObject spItem))

Related:

  • No Related Posts

DeployAnywhere confused by a driver whose “Provider” contains a forward-slash

I need a solution

We were automatically provisioning a system using Symantec ITMS Deployment Solution. The DriverManager64.exe (part of DeployAnywhere) task failed on the client system with the following error:

SMPPackage.cpp@772: Error in downloading file from HTTP.source :http://itms/Altiris/PackageShare/pkggroup_guid/DriversDB/BayHubTech/o2flash.exe and dest :C:DS_SOISymantecDeploymentDriversDBBayHubTecho2flash.exe. The COM error = HTTP error occurred
[… many similar lines …]

On the ITMS server, I explored C:Program FilesAltirisDeploymentDriversDB and found that the BayHubTech subdirectory was a unique case:

DriversDBAdaptec.cda1000.4.20.38
DriversDBAdaptec.cda1000.4.20.38drivers.manifest.txt
DriversDBAdaptec.cda1000.4.20.38CDA1000.inf
[… other files …]

*versus*

DriversDBBayHubTech
DriversDBBayHubTechO2Micro.O2FJ2RDR.2.2.2.1076
DriversDBBayHubTechO2Micro.O2FJ2RDR.2.2.2.1076drivers.manifest.txt
DriversDBBayHubTechO2Micro.O2FJ2RDR.2.2.2.1076o2fj2x64.inf
[… other files …]

Notice how the BayHubTech subdirectory contains a further directory structure (“O2Micro”). None of the other drivers in this folder contained additional “layers” of directories — only BayHubTech. I determined that this driver is Dell’s O2 Micro OZ777xxx/OZ621XX memory card reader Driver, and upon further inspection I saw that the INF file contains (after variable substitution) the following line:

Provider = “BayHubTech/O2Micro”

I suspect that the forward-slash in this directive is being incorrectly interpreted in two different ways: it causes the ITMS DeployAnywhere DriversDB to create an extra layer of subdirectories, and it causes the DeployAnywhere client to stop parsing the name after “BayHubTech.” Furthermore, it is impossible to delete the impacted driver from the ITMS Driver Management interface; instead, the following lines appear on the server-side logs:

Altiris.Deployment.Web.DeployAnyWhereDriverDB: ArgumentsList:/del=”BayHubTech/O2Micro.O2FJ2RDR.2.2.2.1060″ /ddb=”D:AltirisDeploymentDriversDB”
Altiris.Deployment.Web.DeployAnyWhereDriverDB: Delete Drivername passed:BayHubTech/O2Micro.O2FJ2RDR.2.2.2.1060
Altiris.Deployment.Web.DeployAnyWhereDriverDB: Delete Driver Database return code is :11
Altiris.Deployment.Web.DeployAnyWhereDriverDB: Incorrect parameter(s) provided.

Can this behavior be fixed? I have needed to resort to recreating drivers.manifest.txt (as suggested in this forum discussion) in order to clear the bad driver.

0

Related:

  • No Related Posts

Installation Rollback due to GPOPolicyReview. Access is DENIED.

I need a solution

Hello guys

I’m trying to setup newly downloaded Symantec_Endpoint_Protection_14.2.0_RU1_Part1_Trialware_EN

But it does rollback during installation process. Here is an error from SEPM_INST.log

INFO  Exception CreateProcessW. Error code: 5: Access is denied.
CustomAction GPOPolicyReview returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

According to the post I found here https://support.symantec.com/us/en/article.tech233569.html the issue can have a couple different causes:

  1. TMP and TEMP variables do not have the same path.
  2. Restrictive permissions are prohibiting the installation.

But I checked all those causes and they are OK, TMP and TEMP have same path and the user is new and placed only in Administrators group.

Full log file is attached

Please help me

0

Related:

  • No Related Posts

Content install failed on the client Product: SEPC STIC

I need a solution

We are getting the following error on a number of servers in our environment and are not sure what causes this error and how to resolve.

Content install failed on the client

Product: SEPC STIC
Version: 14.0 RU1
Language: SymAllLanguages
Moniker: {075551EC-66BD-4487-9E2E-40645AF6F8B0}
Sequence: 190513038
Publish Date: Monday, May 13, 2019
Revision: 038

Any further information would be helpful.  Thanks!

0

Related:

  • No Related Posts

unable to access remote web console

I need a solution

Hi all,

i’m currently facing issue while accessing my SEPM remotly through web console. I tried to change the browsers but each time it comes up with “The connection timed out” error.

when i tried to get web console access on my physical SEPM server through I.E its working smoothly.

as server machine  has limited resources so i increased its RAM. but still its not working.

Please suggest if i need any configurational changes.?

0

Related:

  • No Related Posts

Event Details – Failed to get commands from the server. error code 3, Application category

I need a solution

I’m currently doing some testing on the SEP Cloud Testpad domain

I’ve successfully setup Endpoint and the policies however when trying to push commands from the cloud console to the device I never get an update.

Looking in the Event page I can see that the device keeps reporting the following error:

Failed to get commands from the server. error code 3, Application category

Any ideas on how I can troubleshoot this?

0

Related:

  • No Related Posts