Altiris Log Errors

pstage's picture

I'm receiving hundreds of the errors (very bottom) in my NS log. I have located Altiris KB28720 that addresses this error. The cause is apparently a NULL value in the Inv_AeX_AC_tcpip subnet column. Their resolution is to run a these scripts.



This to locate them.



SELECT vc.name, ip.*

FROM Inv_Aex_ac_tcpip ip

JOIN vcomputer vc on vc.guid = ip._resourceguid

WHERE ip.subnet IS NULL



This to update the subnet



UPDATE inv_aex_ac_tcpip

SET subnet = '255.0.0.0'

WHERE subnet is null



Sounds like a simple fix. However, I'm concerned why the subnet column is not being populated. As this should be populated from a basic inventory. That, and there are around 400 of my total 1200 nodes with this issue, leading me to believe something is a little off. I think this also may have caused the issues I had a couple days ago with my package servers.



Can anyone offer any suggestions on this before I just pop in subnets for these clients? Plus, they're on different subnets.





Log File Name: D:\Program Files\Altiris\Notification Server\Logs\a40.log

Priority: 1

Date: 1/30/2009 8:11:27 AM

Tick Count: 140506250

Host Name: NS

Process: w3wp.exe (7504)

Thread ID: 1584

Module: AltirisNativeHelper.dll

Source: Altiris.ClientTask.Web.GetClientTaskServers.Page_Load

Description: An exception occurred while attempting to get Client Task Server list ( Unhandled exception. Type=System.Data.SqlTypes.SqlNullValueException Msg=Data is Null. This method or property cannot be called on Null values. Src=System.Data

StackTrace=

at System.Data.SqlTypes.SqlString.get_Value()

at System.Data.SqlClient.SqlDataReader.GetString(Int32 i)

at Altiris.ClientTask.Web.GetClientTaskServers.LocateServersBasedOnSubnet(Guid resourceGuid)

at Altiris.ClientTask.Web.GetClientTaskServers.Page_Load(Object sender, EventArgs e) )

jharings's picture

Hi Paul,

One question would be are you in fact using Task Server?



Jim

Jim Harings
Technical Solutions Consultant
Xcend Group
http://xcendgroup.com

pstage's picture

Yes, I have all of the task agents rolled out to about 90% of my clients. I need to use this to roll out Credant within the next few weeks. So, no I'm not actively using it, but will be...provided it's still working.

pstage's picture

One side note, I do have the NS designated to be the task server. I have around 1200 nodes....should I designate a separate task server? If I change it, will it cause any issues with task agents already deployed?

pstage's picture

Also, I see I have 6.0.1404 of the task server installed. I'll update to 6.0.1505 first to see if that clears things up...doubt it, but might as well be on the latest version.

jharings's picture

quote:
Originally posted by: pstage

One side note, I do have the NS designated to be the task server. I have around 1200 nodes....should I designate a separate task server? If I change it, will it cause any issues with task agents already deployed?




The NS being a task server is fine, but it should not manage any more than 500 client task agents.

Jim Harings
Technical Solutions Consultant
Xcend Group
http://xcendgroup.com

pstage's picture

well...that sucks. Thanks!



It looks like .NET 1.1.4322 was not registered properly. I followed the instructions per Altiris KB27432 to register again. This appears to have resolved the original error. I also verified that Active Server Pages & ASP .NET v1.1.4322 were both allowed within IIS Manager\Web Service Extensions.



However, I'm now receiving this warning (better than error I suppose).





Log File Name: D:\Program Files\Altiris\Notification Server\Logs\a.log

Priority: 2

Date: 1/30/2009 3:32:50 PM

Tick Count: 166988812

Host Name: NTALTNS

Process: AeXNSAgent.exe (7440)

Thread ID: 6936

Module: Client Task Agent.dll

Source: Client Task Agent

Description: CAtrsException exception, error = "Unable to register", OS error = 2147549183, at line 478 re-throw at CTaskAgentBase::CheckRegister





I've found the KB articles for "at line 463", but those solutions don't work.

pstage's picture

OK, apparently when I upgraded the task server solution it removed my NS from being assigned to a collection. I just added it back. Appears to have solved the issue. I'll monitor for a bit. Thanks for your assistance! Really appreciated.