Log viewer looks really bad
Starting at 10 til 1 today my log files are bleeding worse than a Tarantino film.
This is what is in the error log
Log File Name: D:\Program Files\Altiris\Notification Server\Logs\a8.log
Priority: 1
Date: 6/1/2009 12:47:04 PM
Tick Count: -2037639203
Host Name:
Process: aexsvc.exe (6780)
Thread ID: 2304
Module: AltirisNativeHelper.dll
Source: Altiris.NS.ClientMessaging.FileDispatcher.ProcessFileCallback
Description: Unable to process the file "D:\Program Files\Altiris\Notification Server\NSCap\EvtQFast\Process\nse5106.tmp" Moving to "D:\Program Files\Altiris\Notification Server\NSCap\EvtQFast\Bad\ItemNotFoundException\nse5107.tmp". Reason: Unable to load the target item for the client message. (Guid: "6ff00b06-1613-4f83-aaa3-8b28f761c265")
The next error is which is odd because deployment solution is not installed on this server.
<?xml version='1.0' ?>
<XmlData>
<WbemEventObject class='CE_NfySvrRemoteEvent'>
<MessageID></MessageID>
<Resource guid='{80B4D936-7065-4D42-87E6-BAC783D32148}' typeGuid='493435F7-3B17-4C4C-B07F-C23E7AB7781F'><Attribute name='Domain' value=''/><Attribute name='Name' value=''/><Attribute name='Altkey1' value=''/><Attribute name='Altkey2' value='00-1C-C4-85-97-C6'/></Resource>
<ScenarioGUID>{6FF00B06-1613-4f83-AAA3-8B28F761C265}</ScenarioGUID>
<RemoteEvent>
<inventoryClass guid='{8710F30B-9FD7-4f1a-A91C-5EF923394685}'
manufacturer='Altiris'
platform='Win32'
name='AeX PCTBuild'
version='1.0'
description=''
dataTableName='AeXEvt_AeX_PCTBuild'
historyTableName=''
source=''
confirmSchema=''
batchSize='1'
ignoreMissingResources=''>
<schema>
<columns>
<column name='WrkstaSrc' isNullable='false' shortName='c0' id='1' sqlType='nvarchar (128)' />r
<column name='StartDate' isNullable='false' shortName='c1' id='2' sqlType='datetime' />r
<column name='Duration' isNullable='false' shortName='c2' id='3' sqlType='float' />r
<column name='FileCount' isNullable='false' shortName='c3' id='4' sqlType='int' />r
<column name='FileSize' isNullable='false' shortName='c4' id='5' sqlType='int' />r
<column name='Size' isNullable='false' shortName='c5' id='6' sqlType='int' />r
<column name='Package' isNullable='false' shortName='c6' id='7' sqlType='nvarchar (256)' />r
<column name='ExitCode' isNullable='false' shortName='c7' id='8' sqlType='int' />r
<column name='ExitString' isNullable='false' shortName='c8' id='9' sqlType='nvarchar (512)' />r
<column name='Template' isNullable='false' shortName='c9' id='10' sqlType='nvarchar (256)' />r
<column name='OSSrc' isNullable='false' shortName='c10' id='11' sqlType='nvarchar (64)' />r
</columns>
</schema>
<data>
<resource partialUpdate='true' >
<row
c0='' c1='2009-06-01 12:43:57' c2='169' c3='1989' c4='244303' c5='170083' c6='\\SERVERNAME\PCT\Personalities\DOMAIN\USERNAME.exe' c7='0' c8='No Errors' c9='\\SERVERNAME\express\PCT\Template\admin.pbt' c10='WinXP'/>
</resource>
</data>
</inventoryClass>
</RemoteEvent>
<TimeGenerated>20090601124701.842000+240</TimeGenerated>
<MessageBody></MessageBody>
<MessageLabel></MessageLabel>
<TransportFlag></TransportFlag>
<TransactionCookie></TransactionCookie>
</WbemEventObject></XmlData>
I read KB 38588 https://kb.altiris.com/article.asp?article=38588&p=1 and ran the SQL queries but it doesn't return anything.
Comments
Did you delete any task or remove a solution
that had active tasks? These errors are generally caused by improperly removing items, before 'notifying' the clients that they are gone. Tasks and policies should always be disabled for at least one full client configuration cycle before deleting. Check out the bad items referenced in the log errors (they will be in the event queue bad folders). You can see what was removed.
Lots of ways to fix this, but let's find out what is missing first.
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
Thanks for the reply
The weird thing about this is we do not have deployment solution installed on our NS and the error logs seem to indicate that its PC Transplant that is missing. Another thing that is weird is that we are using web DS as well as 32Bit DS and there are PCTranspland jobs configured, but they are not triggered by the NS.
I'm fairly new to the company (2 months) so I will ask the resident Altiris Admin if there is something setup that I don't know about when he is back . The timing of these errors is weird as well as they started at 12:50PM on the 1st day of the month and all erros were exactly as above execpt from different computers. Today the error log is fine.
PCTransplant
used to be a solution and it was eventually 'legacied', while still remaining an important tool in the 32bit DS world. So I'm thinking, but it's just a guess, that you have some clients still with a PCT Agent on them and based on some random schedule are still sending events. If it was pure DS errors, you wouldn't see these in the NS logs.
Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.
Resident Altiris Admin
We are currently running version 6.8.1032 in which AKB32959 states that version 6.8.1043 corrects this issue. I have been informed that this only happens on the secondary DS server, where as all other sites here have PCT installed as a stand-alone app on PXE servers.
Thanks lukychrm
That is the fix we will go with. Guess we will have to submit a CNR for that one :)
I thought there was another
I thought there was another KB that used to be posted for a resolution to this issue. From my understanding is that the DS agent wil keep trying to post events to the NS agent stating that a PCT was completed. We're using DS 6.9 and still seeing this issue and I cannot find a workaround for this problem.
Would you like to reply?
Login or Register to post your comment.