Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Unable to initialize Remote Agent on Netware error

Updated: 21 May 2010 | 5 comments
Lars-Gunnar Nihlman's picture
0 0 Votes
Login to vote

Hi !
I'm running ver. 9.1 4691 on a Win2k server and use it to backup a Netware 6.5.5 server running Groupwise 6.5.6.
The problem is that when Groupwise is backed up I get his error message:
Unable to initialize Remote Agent

However the data is backed up.

This problem occured after migrating the server to new hardware, it's now running on a DELL PE1950 box with a dualcore CPU.
When doing the migration I also installed support pack 5 for NetWare.

I did not have this problem on the old hardware where I was using Netware 6.5 with support pack 3.

What could be the problem here ?

Comments

padmaja rajopadhye's picture
03
Jan
2007
0 Votes 0
Login to vote

Hi,

Check whether the Open File Option is selected for backup.
If so, try deselecting the option and run the backup again.


Regards
Padmaja

Lars-Gunnar Nihlman's picture
03
Jan
2007
0 Votes 0
Login to vote

Open File Option is not selected for the backup job.

I've been using GWTSA.NLM for backup of Groupwise but I've just found out that there is a new way to backup Groupwise.

I've tried this:
LOAD TSAFS /EnableGW=yes

LOAD SYS:\SYSTEM\TSAFSGW /HOME-VOL1:\GRUMSDOM /HOME-VOL1:\GRUMSPO

However this will not fix my problem, I still get the message "Unable to initialize Remote Agent" when both the Groupwise domain and postoffice is backed up.

Any other ideas ?

Lars-Gunnar Nihlman's picture
04
Jan
2007
0 Votes 0
Login to vote

Problem solved !

When I switched from using GWTSA to TSAFS I took the new NLM's from tsa5up19.exe.But there is a problem with SMDR.NLM so I used SMDR.NLM from tsa5up18.exe instead.
With this version of SMDR everything works fine.

There is a document on Novell's web site that describes this, Document ID 3000544.

Chris Riley's picture
04
Jan
2007
0 Votes 0
Login to vote

FYI:

There's also a Veritas/Symantec document that describes this problem:

http://support.veritas.com/docs/281829

Please mark thread as solved if you consider this to have answered your question(s)
 

Rucha Abhyankar's picture
08
Jan
2007
0 Votes 0
Login to vote

Issue is resolved so post is marked as answered.