Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange Licensing Issues 11.5 2

Status
Not open for further replies.

LMarie

MIS
Oct 1, 2007
10
US
Have valid licenses for both ARCserve Backup r11.5 for Windows Agent for Microsoft Exchange and the Premium Add-on. When I install them on an Exchange 2003 server, (Windows Server 2003) the install goes fine, but it does not ask me to input the licensing keys. Also, when I run the backup job for the Exchange Database, it fails at dbaexchis the error E8604"Product Grace Period Expired".

I have unistalled, rebooted, reinstalled, then recreated the backup job, and it still continues to fail. Comparing the registry keys on a different Exchange server that backups just fine I noticed that it has the following key HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\License . This key is missing from the Exchange server that fails out.

Is this just a matter of Exporting the Registry Key from one server to the other? Anyone experience this issue, and tried this to resolve it
 
go to Manager, Help About, click the License button to enter the license information for the agent.
 
go to C:\program files\CA\Shared Components\CA_LIC.
Run CALICNSE.EXE and fill in the registration keys (5 strings of 5 characters) below and click add. If this ends up succesfully restart all ARCserve related services and run a testbackup. This should resolve your issue.

regards
 
Thank you both. The AS server already had the license key. As for the agent on the Exchange server, Cyklops I did as you suggested, yet I am still getting the same error when the job runs.

One thing I did notice is that when I added the license keys using CALICNSE.EXE, where it usually will show the actual key listed with the agent, it displayed all 9's. I find this very odd, also the registry key I referred to in my first post is still the same. Hmmmmmm?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top