PECTAgent Crashing in WinPE with DS 7.1

[Migration User]

I've been experimenting with DS 7.1 and have hit a bit of a problem.

My client will PXE boot into a PXE Automation configuration that I created in the console (WinPE x86).
When the WinPE finishes starting up I can see the expected messages stating the agent is starting and then a message "Startup.bat was successfuly called!"
At this point the client does not seem to be visible in the console at all.  I've checked and the task server is not showing the client as having a live connection.

In the WinPE session:

1. The PECTAgent.exe process is not running
2. I can ping the SMP server
3. The PECTAgent.ini seems to have the right settings
4. The Agent.log file lists the following:

Log File Created. Version 7.01.598
AgentGlobals.h:103 RegisterLibrary: x:\program files\altiris\altiris agent\Client Task Agent.dll has been registered sucessfully
AgentGlobals.h:103 RegisterLibrary: x:\program files\altiris\altiris agent\AeXNetComms.dll has been registered sucessfully
AgentGlobals.h:103 RegisterLibrary: x:\program files\altiris\altiris agent\AeXBasicInventory.dll has been registered sucessfully
AgentGlobals.h:103 RegisterLibrary: x:\program files\altiris\altiris agent\AeXNSEvent.dll has been registered sucessfully
PECTAgent.cpp:150 calling SetClientConfig
ClientConfig.cpp:501 NS Port No in ini file=80
ClientConfig.cpp:513 NS Server name in ini file=[MYSMPSERVERNAME]
ClientConfig.cpp:533 Resource guid not found in PECTAgent.ini, calling InitializeMachineGuid to get guid from NS
ClientConfig.cpp:188 CClientConfig::InitializeMachineGuid called
ClientConfig.cpp:198 Checking For Dell client..
ClientConfig.cpp:152 Calling SMBIOS..
PECTAgent Error: Unhandled runtime exception, GetLastError returned 0


Has anyone seen this before?  I can see the SMBIOS call may well be causing the PECTAgent to crash but I've been unable to get any more information.  The usual altiris agent verbose logging regsitry settings don't yield any more information in the logs.  Re-running the PECTAgent.exe just causes the same messages in the log.

I am running this in a Microsoft Hyper-V virtual guest environment and I can accept that this may be a contributing factor- especially if an unusual SMBIOS call is being made.  Has anyone successfully run the PECTAgent.exe in a Hyper-V environment?

[Migration User]

I had this problem but it was because of two things:

1. I had a second website running on the NS server for Workflow. IIS logs showed the PECTAgent was connecting to this second website instead of the NS default website.
2. I had Require SSL enabled but the PECTAgent was using port 80. I haven't found a work around to reset the WinPE settings so the PECTAgent will use SSL on port 443. Right now I just turned off Require SSL for all in IIS on the default website.

I suggest checking your IIS logs for errors on the NS server. Also see if you can tracert to the FQDN from the WinPE environment. PING doesn't exist in WinPE but TRACERT does.

[Migration User]

Thanks for the feedback - much appreciated.
I've checked the IIS logs but they show no traffic or errors from the ip address that my WinPE client is on.  I've also verified that I can tracert to the DS with both the fqdn and server name.

Is there anyone out there who is successfully running the PECTAgent.exe in WinPE on a MS Hyper-V, Virtual PC or Virtual Server guest?

[Migration User]

It turns out this is nothing to do with Hyper-V.  This KB appeared the other day and the fix resolves the issue.

https://kb.altiris.com/article.asp?article=53355&p=1

Just for anyone who is wondering, I'm using all CMS 7.1 SP2 MR1 components quite successfully in a Hyper-V environment.  You'll need the legacy network adapter to PXE boot clients.  Hyper-V makes an excellent test environment due to its excellent hardware compatibility.

[Migration User]

Had the same issue, except when I was imaging a PC with deployanywhere, it was just straight failing right after.  the clientdeploylog pointed me to a the DeployAnywhere.txt file in the task server (non-existant log file lol) which stumped me.

Saw this KB and thought id take a look at my WAIK folder and who woulda guessed it was at that ~580 mark.

Running though the solution right now to see if it fixes the issue.  

[Migration User]

didn't fix it, trying a full DS7.1 repair and restart.

[Migration User]

spoke too soon kinda, looks like a Repair and a restart took care of it, PECTAgent just completed successfully! and the job continues on...

[Migration User]

Christovan, did you upgrade from DS7.0 to 7.1?  My guess is thats when the WAIK folder occurs.

I also had too reboot too - I guess I should have mentioned that

[Migration User]

I had 7.1 for a while, this was going from 7.1 to 7.1 MR1

However, it seems like it is happening again, may need to open a support ticket on this one.

[Migration User]

Update again:

my WAIK folder is the correct 340MB in size, but I am still getting PECT errors as per this KB.

It is strange though, as if i image a group of 7 PCs, 3 will work and the rest error out

Do it again, and then 1 works rest error out.

do it again, and 5 work but 2 don't

Does anybody else have any more info on this issue currently?

EDIT ::

Here is the log on the WinPE image:

[2010/07/01 20:18:12.31 1868:1872 2] Log File Created. Version 7.01.598

[2010/07/01 20:18:12.140 1868:1872 2] AgentGlobals.h:103 RegisterLibrary: x:\program files\altiris\altiris agent\Client Task Agent.dll has been registered sucessfully

[2010/07/01 20:18:12.453 1868:1872 2] AgentGlobals.h:103 RegisterLibrary: x:\program files\altiris\altiris agent\AeXNetComms.dll has been registered sucessfully

[2010/07/01 20:18:12.468 1868:1872 2] AgentGlobals.h:103 RegisterLibrary: x:\program files\altiris\altiris agent\AeXBasicInventory.dll has been registered sucessfully

[2010/07/01 20:18:12.484 1868:1872 2] AgentGlobals.h:103 RegisterLibrary: x:\program files\altiris\altiris agent\AeXNSEvent.dll has been registered sucessfully

[2010/07/01 20:18:12.531 1868:1872 2] PECTAgent.cpp:150 calling SetClientConfig

[2010/07/01 20:18:12.531 1868:1872 2] ClientConfig.cpp:501 NS Port No in ini file=80

[2010/07/01 20:18:12.531 1868:1872 2] ClientConfig.cpp:513 NS Server name in ini file=AMHDEVNS7.ictgroup.com

[2010/07/01 20:18:12.531 1868:1872 2] ClientConfig.cpp:533 Resource guid not found in PECTAgent.ini, calling InitializeMachineGuid to get guid from NS

[2010/07/01 20:18:12.531 1868:1872 2] ClientConfig.cpp:188 CClientConfig::InitializeMachineGuid called

[2010/07/01 20:18:12.531 1868:1872 2] ClientConfig.cpp:198 Checking For Dell client..

[2010/07/01 20:18:12.531 1868:1872 2] ClientConfig.cpp:152 Calling SMBIOS..

[2010/07/01 20:18:25.656 1868:1872 2] common\system\smbios.cpp:163 In CSmbios::GetStrings() table=1,offset=0 strValue=Hewlett-Packard

[2010/07/01 20:18:25.656 1868:1872 2] common\system\smbios.cpp:163 In CSmbios::GetStrings() table=1,offset=1 strValue=HP d530 CMT(DS555S)

[2010/07/01 20:18:25.656 1868:1872 2] ClientConfig.cpp:170 Got information from SMBIOS..

[2010/07/01 20:18:25.656 1868:1872 2] ClientConfig.cpp:172 ManufacturerName = Hewlett-Packard

[2010/07/01 20:18:25.656 1868:1872 2] ClientConfig.cpp:173 ProductName = HP d530 CMT(DS555S)

[2010/07/01 20:18:25.656 1868:1872 2] ClientConfig.cpp:182 CheckForDellManufacturer():: It is NOT a Dell PowerEdge server.

[2010/07/01 20:18:25.765 1868:1872 2] ClientConfig.cpp:87 BaseBoardSerialNumber=USU347084G

[2010/07/01 20:18:25.781 1868:1872 2] ClientConfig.cpp:91 BiosSerialNumber=USU347084G

[2010/07/01 20:18:25.796 1868:1872 2] ClientConfig.cpp:95 ComputerUUID=5F91941C-1B5A-11D8-BBD8-9D9F63CB000D

[2010/07/01 20:18:25.796 1868:1872 2] ClientConfig.cpp:98 Got m_bIsDellClient = 0

 

[2010/07/01 20:18:25.812 1868:1872 2] ClientConfig.cpp:107 Creating hash..

[2010/07/01 20:18:25.812 1868:1872 2] ClientConfig.cpp:115 Board ComputerFingerprintHash=oGBsZRj8pLZfNCLm3A4WYQ==

[2010/07/01 20:18:25.812 1868:1872 2] ClientConfig.cpp:217 InitializeMachineGuid()::m_bIsDellClient = 0

[2010/07/01 20:18:25.812 1868:1872 2] ClientConfig.cpp:239 InitializeMachineGuid:: calling DS webservice to get ResourseGuid...

[2010/07/01 20:18:25.812 1868:1872 2] ClientConfig.cpp:261 CClientConfig::PrepareGetResourceGuidXML() called.

[2010/07/01 20:18:25.812 1868:1872 2] ClientConfig.cpp:294 CClientConfig::GetResourceGuidFromWebService() called.

[2010/07/01 20:18:25.812 1868:1872 2] ClientConfig.cpp:304 Request Url = http://AMHDEVNS7.mydomain.com:80/Altiris/Deployment/Services/GetResourceGuid.aspx

[2010/07/01 20:18:25.812 1868:1872 2] ClientConfig.cpp:308 CClientConfig::GetResourceGuidFromWebService, Request XML = <request>

<resourcekeys>

<key name="uniqueid" value="oGBsZRj8pLZfNCLm3A4WYQ=="/>

</resourcekeys>

</request>

 

[2010/07/01 20:18:25.906 1868:1872 2] ClientConfig.cpp:320 Calling webservice to get ResourceGuid...

[2010/07/01 20:18:50.171 1868:1872 2] PECTAgent Error: Unhandled runtime exception, GetLastError returned 0

[Migration User]

You're getting past the SMBIOS point that I was at.  Looks like a different error to mine.

Have you tried creating a new WinPE automation (not recreating existing) and trying with that?

Given that its not constantly reproducable on the same machines I'd look for a cause outside WinPE like network or firewall or server load related issues.

[Migration User]

those last two lines makes me think it is related to something with IIS on the NS server.

it tries to get a resourceGUID from the webservice (I am assuming the same webservice as a few lines above when it has my amhdevns7.mydomain http link)

maybe a restart will fix any IIS issues.

[Migration User]

Christovan
This was the PECTAgent error I was seeing. Exactly there at that line. I would get the error intermittently...sometimes it would stay, and a restart of my main NS's server and IIS services would clear it up. I ended up finding that KB, finding the WAIK folder being too big and following the instructions. Just on my main NS, which doesn't even PXE. I haven't run into it since, but I can't say for sure that the problem is gone. For what that's worth...

I have talked to you before on other forums christovan, you have helped me out. Would you be interested in calling each other to discuss issues/plans with Altiris 7? We are fairly well into testing and looking at production procedures currently. It's hard to find many people actually using this product.

[Migration User]

I knew the name looked familiar!

I'll shoot you a PM on the other boards in the near future... if i forget shoot me one! (company is going through a HUGE, rushed, domain migration meaning lots of headaches, 60hr weeks and no free time for altiris :( )