Command line activation not working in Win7

Make sure you are using Avamar 5.0 SP2 and above.

Is the Win7 in same network or located remotely , if so make sure you have the necessary ports (28000, 29000 27000)open to activate and communicate with the Avamar server.

Check and make sure the Win7 client is resolvable to Avamar server both forward and reverse.

If the above doesnt fix the issue, look for log information to check the issue C:\Program Files\avs\var\avagent.log.

Rudresh

Thank you for the reply. Here's some more info from my attempts if you are interested in helping some more.

nslookup is working from the Avamar utility node both by name and by address. Firewall is off on the current workstation I'm using that's failing. Using version 6.1.0-402 server and client. Our Data Security tem reports the network is wide open between this workstation and this avamar grid. the Admin console software on this workstation is working great.

the logs seem to disagree. Here's the excerpts:

this is the ending of the reply from the command on the workstation:

avagent Error <5493>: Unable to create CID file "C:\Program Files\avs\var\cid.bin"
avagent Info <6610>: ****** Current MCS name 'nkpp1infaa01' ******

avagent Info <7502>: Registration of client /Workstations/info_kl-gtj2qj1.cbsh.com with MCS nkpp1infaa01:28001 successful.
avagent Error <5101>: Unable to open file "C:\Program Files\avs\var\avagent.cfg"avagent Info <5405>: avagent returning with exitcode 0

This is the excerpt from the avagent.log on the workstation:

2013-01-30 18:11:05 avagent Error <6210>: Unable to register 'info_kl-gtj2qj1' with MCS at :28001

2013-01-30 18:11:05 avagent Error <7500>: Registration error: NULL message received

2013-01-30 18:11:05 avagent Error <6053>: Error trying to update MCS with new ip address

2013-01-30 18:11:05 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2013-01-30 18:11:05 avagent Info <5363>: Skipping registration, no MCS name

2013-01-30 18:11:05 avagent Info <5434>: MCS unknown, entering listen mode.

2013-01-30 18:11:05 avagent Info <5321>: Unable to connect to Management Console (), sleep 38 minutes, 14 seconds before retry

This looks like a permissions issue. Does the account being used to run the registration have read / write permissions to the Avamar installation path?

The MCS address is recorded into the cid.bin file and as you can see from the messages in the logs, avagent is unable to create this file.

This actually worked after a large delay and 2 reboots. The init attempt we tried on Friday afternoon left 2 more failure attempts in the log after rebooting friday evening, then on Saturday morning after another reboot, it just worked without us touching it. Now we're looking for the reason for the delay. There are entries in the avagent log about waiting peiods, so we're wanting to know more about the expected process for it to wait and try over and over, maybe untul it succeeds?

Any ideas on how this works?

I would need to see the avagent.log and cid.bin files from the affected client.

Thank you for the continued interest. We have case 52806454 open, and the avagent.log and cid.bin are attached. If you're interested, I think we've about stumped everyone so far.