Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

Task does not run

Created: 30 Jan 2013 | 11 comments

In the last couple days I have run into the following problem.  I create a new Software Delivery Package for an MSI file.  Then I created a Delivery Task and scheduled the task to run now and override maintenace window.  I can see the agent show the task is running, the MSIEXEC process never starts in Windows Task Manager. 

After 30 minutes the task shows fails with a return code 0.

Has anyone see this before?

 

Comments 11 CommentsJump to latest comment

andykn101's picture

Post your command line.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

72smith's picture

msiexec.exe /i "hyland onbase client.msi"

image3.PNG
andykn101's picture

You need:

msiexec.exe /i "hyland onbase client.msi" /qn

for it to run quietly with no interaction (if it's on Windows 7 it won't run in a session a user can interact with any way.

I always add logging:

msiexec.exe /i "hyland onbase client.msi" /qn /l*v "%temp%\hyland.log"

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

andykn101's picture

And check the Windows Installer Service isn't disabled.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

72smith's picture

Andy

The Windows Installer server is set to manual.  I can run the MSI manual or with a batch file and it works fine.  It just does not run as a Delivery Task.

andykn101's picture

Check the Altiris log.

Have you got the Software Management Solution Agent installed?

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

mclemson's picture

Rather than run it /qn, run it /qb to see if any feedback is provided.  If you are running it as the Application Identity, ensure that your manual test from command line uses the same credential for testing purposes.  I assume that account is a local administrator on the targeted box.

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

72smith's picture

I am not running the task /qn or /qb.  I want it to show the prompts. 

msiexec.exe /i "hyland onbase client.msi"

I am running the task with the same credentials as when I run it manually.

 

andykn101's picture

What is the client OS?

When you run it manually you are logged in with the credentials you run it as.

When Altiris runs it with those credentials that account isn't the logged in account, so the logged in account doesn't necessarily see what's running in the context of the credentials you are using.

If you are using XP it might work using the Logged on User option in Altiris to run the Task. But you are much better off doing a proper siloent unattended install.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

72smith's picture

Windows XP is the client OS

I have tried to use several differnet credentials, with no success.

Ultimately I will run the install quiet, but for now I am just trying to get it to run.

Here is what gets logged by the client.

<event date='Feb 01 08:20:19' severity='4' hostName='WPZL1SMITHR' source='SWDTSPAgent' module='smfagent.dll' process='AeXNSAgent.exe' pid='1820' thread='5944' tickCount='949921078' >
  <![CDATA[<DeliverSoftwareTask><DeliverSoftware guid="{729ecb78-edaf-4650-920b-b19733fc8efe}" PackageGuid="{c8de7cb5-70c9-4f0e-ac1a-cb1dc62b2317}" SoftwareGuid="{00000000-0000-0000-0000-000000000000}" PackageName="" PackageContainsFile="True" InternalVersion="1359564505" ProgramGuid="{f8e074c8-a765-4b36-ab3d-3553febac19b}" ProgramName="" CommandLine="msiexec.exe /i &quot;Hyland OnBase Client.msi&quot;" ExecutionFlag="True" SuccessCodes="0, 1641, 3010" FailureCodes="" WorkingDir="" ProgramCanRun="None" IsInteractive="True" StartingWindow="Normal" TerminateAfter="360" CleanupAfter="10080" ExecutionContext="SystemAccount" User="" Password="" Domain="" /><Advanced DefaultAgentSettings="True" RunFromServer="False" RunFromServerAboveRate="-1" RunLocally="True" RunLocallyAboveRate="0" AlternateLocation="" /></DeliverSoftwareTask>]]>
</event>
<event date='Feb 01 08:20:19' severity='4' hostName='WPZL1SMITHR' source='Client Task Agent' module='client task agent.dll' process='AeXNSAgent.exe' pid='1820' thread='2644' tickCount='949921078' >
  <![CDATA[CTaskStatusEngine::OnTaskFinished(): Got status for 160442b5-3bca-4608-8c59-b8d83369fc03]]>
</event>
<event date='Feb 01 08:20:19' severity='4' hostName='WPZL1SMITHR' source='Client Task Agent' module='client task agent.dll' process='AeXNSAgent.exe' pid='1820' thread='2644' tickCount='949921093' >
  <![CDATA[CClientTaskStatusCollector::Task: Hyland OnBase 12 has finished]]>

 

Keep in mine I can run task that were created a month ago fine, only the new tasks do not run.

 

mclemson's picture

Complete the command line and run using /qb (unattended) or /qn (silent).  For example:

msiexec.exe /i "hyland onbase client.msi" /qb

Run the task as the Logged on user or specify the application identity -- whatever is an administrator on the box.  (Hopefully the application identity is part of local administrators on the targeted boxes.)  If you configure Altiris to run with account xyz (which has no privileges), and then manually test with account abc (which has administrator privileges), you're of course going to get a different result.

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com