Deployment Solution

All,

This started when we needed to remove duplicate computer listings from our DS console. It began on DS version 6.8 and still exists after upgrading to 6.9 SP1 MP1. Not sure what the problem is here, but we've been having this issue for the past few months now. Get an hourglass for about 30-60 seconds before the attempt times out and the item(s) to be deleted remain in the console. I can go into the SQL database and use a simple DELETE query to remove the machines one by one, but not everyone has access to do this. I was wondering if there was something simple to check before we got our DBAs involved.

The DBManager.log shows some interesting errors in it. Also when the problem first began, I was receiving "Error deleting jobs through Altiris Database Management Service. Last error was 'Unknown error''.

The DS has been uninstalled and reinstalled, but still has this issue

Also note that the console will lockup when I trigger the "Remove inactive computers after XX days" and "Delete history entries older than XX days" options. Something appears to be misaligned in the database. We haven't changed anything with the service account used to administer the database. "Help me Obi-Wan, you're our only hope!"

Sounds like your database is corrupt. When you reinstalled DS did you use the same database or did you create a new one?

lajuane, are you still having the problem? Let us know if you've solved it or if you've created a support case. Thanks!

I am experiencing the same issue. Will be calling in tomorrow.

Yes we used the same database; backup the express file and restored.  I take it we should've started fresh and maybe imported OR just started fresh and maybe imported from AD?

Also noticed something else weird--there are 2 express services on our system: Altiris Deployment Server and Altiris express Server; why is that?  We've also migrated SQL instances from when we first setup, on the same machine.  We've upgraded a few versions from when it was first implemented and have installed fresh when we ran into issues.  Now it's at it's worst; some computers/jobs will delete with ease, depending on their age in the DS, while others that have been there for some time are the hardest to remove.

Is it FUBAR'd yet?

Any luck with the call?

 It was on a server with about 2000 clients connecting. The console refreshing was also slow, and the altiris operators kept being frustrated by the computers pane (or job pane -can't quite recall)  they were browsing continuously skipping focus to the parent folder. When I was trying to delete old computers, I found I could not.

Problem went away after I migrated lots of the clients to another Deployment Server, splitting up the DS infrastructure. This wasn't a pain for me, as I had intended to do that anyway for management/political reasons.

Perhaps related issue is that at that time we had some machines in the database which had duplicate BIOS UUIDs, which was a primary lookup key. I deleted these by hand in the database and retired the equipment because it was causing havoc. To find those duplicates, you can use a SQL query like,

select count(*) as uuidcount, UUID from Computer
group by uuid
order by uuidcount DESC

Not sure if this is related, but I'm guessing duplicated UUIDs aren't good anyways.... ;-)

Kind Regards,
Ian./

Ours ended up being some process locking up that particular database. Recreated a new database with a different name and now all's working.

the db makeup is similar to that of 'ianatkin's.  We reimage machines constantly and our lookup keys are set to S/N and MAC address.  History and inactive computers were not being removed on specific intervals; just a mess. 

We are in the midst of a server refresh.  We'll take the time to setup the new DB from scratch and let the machines populate themselves since they all have the Aclient installed.  New setup will be maintained properly with less hands in the cookie jar