AClient and Microsoft Office

JenH · 08-21-2008, 02:00 PM

We are seeing issues where AClient is causing Office applications like Excel and Word take up to 30 seconds to load. When AClient service is stopped, Word and Excel open open instantly, which is the expected behavior.

Upon looking at these systems with this behavior, both show to have errors in the Aclient log. One machine showed this:

Quote:

[08/18/08 14:35:18.406] CInteractiveUserService::SendDataToHiddenApp(): Thread 0 returned error 10061.

Another showed this:

Quote:

[08/17/08 13:31:07.296] connect() failed. Error: Connection timed out. No response from server. (Last Windows error 0)
[08/17/08 19:26:07.343] connect() failed. Error: A device attached to the system is not functioning. (Last Windows error 0)

In both cases, we ended up removing and re-installing AClient and the issue was resolved, however, we would like to know if others have seen this behavior.

We are using DS 6.8SP2 (6.8.378)

Thanks,

Jen

Nick · 08-21-2008, 02:59 PM

That's new to me Jen but I did see there is an Altiris KBA on it HERE. Nothing helpful in it though.

andykn · 08-22-2008, 04:43 AM

New one on me, too.

lowteq42 · 01-30-2009, 06:41 PM

Hello.

We've recently started noticing this problem as well. One thing we have noticed it only occurs on desktop computers which have Broadcom NICs. Specifically the HP/Compaq Dc530, D7100 and D7600. Has anybody else noticed something similar. We tried updating to new versions of the NICs driver without success.

Does anybody know anything more about the mechanism which causes this problem to occur?

Craig.

titan90 · 01-31-2009, 08:51 PM

I have seen this behavior and contributed to a now archived thread on the Altiris forums about the issue and opened a case about the issue with Altiris support in 2007.

There are detailed instructions in the Altiris forum thread on how to replicate what we were seeing.
Do an advanced search in the Altiris forum for the thread started by GXman called "Workstation slowdowns - Normal after stopping aclient".

Basically tools that were being run to scan our network were causing the aclient to start multiple instances - draining system resources and affecting MS apps.

Altiris support's answer was to use the dagent.exe which was actually not officially released at that time. It was not a decent solution for us and the place were I was working at that time ended up getting rid of all Altiris products anyway.

I have not tried to duplicate the error with 6.9 and the newer dagent.exe. I see you are running 6.8 and I was too at that time.

I hope they have solved the issue as Altiris support was well aware of it a few years ago.

Good luck.