Personality Transplant in DS 7.1 failing.

[Migration User]

 

Working on our migration plan from XP to Win7.  In that, I'm doing some testing with the personality Transplant task now available in the 7.1 console.  When trying to capture the XP personality, it always returns back "Failure - return code -1".  I set the client logs to verbose and I might have more detail on the failure, but no clue why its failing in DS via the 7.1 console and not in the original DS 6.x console.  Below is the brake down of the failure (I believe anyway).  Also the full log is attached.

 

Capture Personality-Jon has started

 

CClientTaskInstanceWin32::CreateTaskHandler(): bstrClassId=DeploymentSolutionAgent_Task

 

ClientTaskInstance::Execute(): CAtrsException exception, error = "Unable to find class ID", OS error = 2147746291, at line 56

re-throw at CAtrsComPtr::CoCreateInstance

re-throw at CAtrsComPtr::CoCreateInstance(BSTR)

re-throw at CClientTaskInstanceWin32::CreateTaskHandler

re-throw at CClientTaskInstanceBase::CreateTaskHandler

re-throw at CClientTaskInstanceBase::OnExecut

 

CTaskStatusEngine::OnTaskFinished(): Got status for 7ae3edae-42e6-49cd-a9b8-15a168b238d8

 

Task: Capture Personality-Jon has finished

 

CTaskStatusEngineBase::PostStatusFile(): Attempting to post C:\Program Files\Altiris\Altiris Agent\TaskManagement\status\7ae3edae-42e6-49cd-a9b8-15a168b238d8.type.empty.xml, type empty

 

CTaskExecutionEngineBase::OnProcessPending(instance)(): CAtrsException exception, error = "Failed to execute task", OS error = 2147746291, at line 298

re-throw at CTaskExecutionEngineBase::OnExecuteTask

 

CTaskServerNetCommsConnection::Post(): Post to url "http://DEVSMC02/Altiris/ClientTaskServer/PostStatus.aspx?resourceGuid=c86ee971-d52d-48de-897e-50f965031eda"

 

CClientTaskInstance::FinalRelease(): Waiting for thread stop

 

CTaskServerNetCommsConnection::Post(): Post body "<status><event resourceGuid="c86ee971-d52d-48de-897e-50f965031eda" type="empty"><statusEvt type="empty" tig="7ae3edae-42e6-49cd-a9b8-15a168b238d8" pig="7ae3edae-42e6-49cd-a9b8-15a168b238d8" jng="00000000-0000-0000-0000-000000000000" tvg="81541a9e-f4a0-4212-956b-b8f908590efe"><output><param name="@Exception" type="System.String"><string>Error 0x800401f3 creating instance handler.  CAtrsException exception, error = &quot;Failed to execute task&quot;, OS error = 2147746291, at line 298

re-throw at CTaskExecutionEngineBase::OnExecuteTask</string></param><param name="@ExceptionType" type="System.String"><string>Altiris.ClientTask.CreateHandlerException</string></param><param name="@ReturnValue" type="System.Int32"><int>-1</int></param><param name="@Success" type="System.Boolean"><boolean>false</boolean></param></output></statusEvt></event></status>"

Attachment(s)

agent.log_.txt   128 KB 1 version

[arjain]

i hope that you have installed Deployment Plugin after Altiris Agent installation on client machine.

Can you run task on Win 7 machine so that we are sure that there is no problem on server side.

is the problem is with xp machine only?

are you using x64 bit version on Xp?

[Migration User]

The DS is in the 7.1 Beta console now.  It more or less uses Task Server.  So the target PCT box is a WinXP 32bit VM.

[arjain]

The task server is same as your NS/SMP or you have a seprate task server machine. If you have a seprate task servaer machine, then you must Package server and Deployment Site server component installed on it.

[Migration User]

Since the majority of the tasks that show "failed" there are DS tasks, there is the chance that the DS Task Handlers (from the site server components) are not installed on that task server.

However, the bottom/first task on the list also failed.  Are you sure you can run ANY tasks at all that don't fail?  If you're in the beta, maybe you're seeing something else.  Try just a basic run script task that echo's something to a command prompt and pauses, or a VBScript that does a message box - both in the current user context, and see if they work.  If not, then your problem isn't just the PCT task, it's the task delivery/execution overall.

You should also take a close look at the agent log right-after the execution of one of these tasks to see what it says.  Often, it will tell you what it ran into, or didn't find, or something like that, which can point you in the right direction for where the issue is.

[Migration User]

Sheesh sometimes I'm stupid!