This post is more than 5 years old

2 Posts

2012

December 2nd, 2009 00:00

avscc.exe crasching

I have problems installing avamar on one of our Windows 2003 R2 SP2 servers.

It seams that the service is running.

net start "backup Agent"
The requested service has already been started.

and the process avagent.exe shows up in the processlist.

But the is no Avamar icon in the system tray and when I try to start the client, nothing happens other than the following event shows up in the eventlog.

Faulting application avscc.exe, version 4.1.105.95, faulting module avscc.exe, version 4.1.105.95, fault address 0x0026a669.

I have tried with version 4.1.100-1470 and 4.1.105-95 but both fails.

Any solutions?

December 2nd, 2009 00:00

Is this relevant?

solution esg106015

Symptoms

avscc will not start after upgrading to Avamar client to 4.1.x.
The avscc icon is not available on the taskbar.
Windows Application Event Viewer reports application fault on avscc.exe.

Faulting application avscc.exe, version 4.1.100.1470, faulting module avscc.exe, version 4.1.100.1470, fault address 0x00268829.

Cause

APC Powerchute v7.0.x is installed on the client and causes various products to experience issues of this nature.  Avamar 4.1.x is affected by this behaviour although earlier versions of Avamar are not.

Resolution


Bug 13965 is currently under investigation although there is no resolution as yet there are several workarounds available.

1) Downgrade the client to v4.0.3.24, which did not have this compatibility issue with the APC Powerchute. Given that there are some additional enhancements/bug fixes in the v4.1.xxx series of clients, this is probably the least desirable solution.

2) Uninstall APC Powerchute, and then install the v4.1.xxx Avamar client and use the AVSCC to activate the client. Once the client is activated, there is very little practical need for having the AVSCC.

The avagent and avtar are the only processes that need to run to perform scheduled backups, on-demand backups from the MC GUI, and restore from the MC GUI.

After the client is activated with the grid, the customer can re-enable APC Powerchute. This is the easiest and most-often recommended solution.

3) Leave APC Powerchute enabled, and install the v4.1.xxx Avamar client. The customer will then need to activate the client with the Avamar grid using the avagent command.

2 Posts

December 2nd, 2009 01:00

APC Powerchute was the problem!!!

Thanx, problem solved!

Top