• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 683
  • Last Modified:

Backupexec Netware SMS errors

I am receiving the following errors when I do a backup of my Groupwise mail server.  My current enviroment is Netware 6.5 sp6, Groupwise 7.0.1, and Backupexec 11d running on a Windows 2003 standard server with sp2 utilizing the Backupexec Netware remote agent 9.2.

1) Novell SMS errors were encountered. Begin Novell SMS errors:
TSAFSGW.NLM(TSAFS.NLM 6.52.2 334) An internal TSA error has occurred. See error log for details.
End Novell SMS errors

I am receiving the above error for my GWDOM and GWPO.

2) Backup- MAIL.NetWare File System/MAIL/GMAIL: Novell SMS errors were encountered.
Begin Novell SMS errors:
Tue Apr  3 23:04:34 2007
  Warning: Unable to set GroupWise timestamp for user database USER0DI.DB.
  Error code: 0x8201.
Tue Apr  3 23:04:50 2007
  Warning: Unable to set GroupWise timestamp for user database USER0FZ.DB.
  Error code: 0x8201.

I am receiving the above error for every user db.

Any help is appreciated.
1 Solution
Is there message traffic being processed while the backup is running?  That would cause database inconsistencies.  I know getting consistent backups is a common topic of discussion in the GW message forums.  You might consider a GW specific backup solution, such as http://www.gwava.com/products/reload_overview.php

GilardiCoAuthor Commented:
Yeah, there is always message traffic on that server.  I have considered Reload however the company has made a significant investment in Backupexec so it is what I have to work with.
Some idead:

Are you running your GW modules in protected memory space?
If so, you'll need to run GWENN4 in space 0.

Are you starting GW from SYS:SYSTEM (default)?
 Make sure that the GWENN4.NLM in SYS:SYSTEM of your mail server is the same version that you are calling to start GroupWise.

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

GilardiCoAuthor Commented:
Thanks Mo,
I did see a TID on exactly that and I verified that GWENN5.NLM (GW 7 version of GWENN4) is running in space 0.  With all of my searches that one TID is all I have found so I am at a lose at this point.  There is actually four instances of GWENN5 one of which is in space 0S.


That could be your problem right there. It *looks* like you're using TSAFSGW.NLM from GroupWise v6.5, but you're running GroupWise v7.0.1. Unless that version number is the one for GroupWise v7.
GilardiCoAuthor Commented:
Yes this is the version that GW 7.0.1 uses.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now