Error: 1

This is a common error message that occurs when a user is deleted and the
mailbox retention time is set to a value other than 0.

The Job Notification reports:

(Server: “Servername”) (Job: “Backup 00006″) Backup 00006 — The job
failed with the following error: The directory is invalid.

The error in the job log reports:

Completed status: Failed

Final error: 0xe000fe09 – The directory is invalid.

Final error category: Resource Errors

For additional information regarding this error refer to
link V-79-57344-65033

Backup- \\SERVER\Microsoft Exchange Mailboxes V-79-57344-65033
- Directory not found. Cannot backup directory ?User Name [uname] and its subdirectories.

Link to Veritas Support Doc:

mhttp://seer.entsupport.symantec.com/docs/241981.htm

You can set the deleted mailbox retention time to 0 to fix the
problem, but this will disable the ability to recover a deleted
mailbox. Open the Server Management screen on the server and
expand the Advanced Management section. Drill down through the
Exchange instance, Servers, Servername, First Storage Group,
Mailbox Store. Right click on the Mailbox Store and select
Properties. Go to the Limits tab, and change the option Keep
Deleted Mailboxes for (Days) to the appropriate amount of
days that the mailbox should stay on the server to 0.

The other option is to train the person that is responsible
for deleting users to purge the mailbox after deleting the
user. Open the Server Management screen on the server and
expand the Advanced Management section. Drill down through
the Exchange instance, Servers, Servername, First Storage
Group, Mailbox Store, Mailboxes. Right click the Mailboxes
folder in the left pane and click the Run Cleanup Agent.
Recently deleted user’s mailboxes will be in the list with
a small red “x” on them. Right click the recently deleted
user.s mailbox and select Purge. Please note that selecting
yes will permanently delete the mailbox and the email therein
will not be retrievable except from previous backups.

Error: 2

I have only run into this error once, and I am still not
sure what caused the problem. My guess is that a program
that included an SQL SP3a backend was installed on the
server that had SP4 already installed on it.

The job log reported:

V-79-57344-33938 – Backup or restore operation terminated
abnormally. An error occurred on a query to database.

0xe0008492 – Database Query Failure. See the job log for details.

Link to Veritas Support Doc:
http://seer.entsupport.symantec.com/docs/276443.htm

The solution was as follows:

1. In the SQL 7.0 installation path (by default \Mssql7\Binn)
   rename the DLL’s Sqlresld.dll and Sqlvdi.dll to
   Sqlresld7.old and Sqlvdi7.old
2. Copy from the SQL 2000 installation path (by default
   \Program Files\Microsoft SQL Server\80\COM) the DLL’s
   Sqlresld.dll and Sqlvdi.dll into the SQL 7.0 installation
   path (by default \Mssql7\Binn)
3. According to the Microsoft article, it is also recommended
   to place the Sqlunirl.dll and Sqlsvc.dll (into \Mssql7\Binn)
   due to the DLL’s dependencies.

Before I overwrote the files as the support document suggested,
I checked the file dates and sizes. The files to be overwritten
were older. I also stopped all SQL services before overwriting
the files, though the article did not specify to do so.

Error: 3

This was a seemingly random error that occurred out of the blue
after several weeks of successful backups.

The job log reported:

Completed status: Failed

Final error: 0xe00084f8 – The network connection to the Backup
Exec Remote Agent has been lost. Check for network errors.

Final error category: Resource Errors

Backup- SERVER\SHAREPOINT AOFO: Initialization failure on:
“\\SERVER\Microsoft Information Store\First Storage Group”.
Advanced Open File Option used: No.
The network connection failed during the snapshot. Check
the network, and then run the job again.

V-79-57344-65072 – The Exchange Store service is not
responding. Backup set canceled.
AOFO: Initialization failure on: “Shadow?Copy?Components”.
Advanced Open File Option used: No.
The network connection failed during the snapshot. Check the
network, and then run the job again.

V-79-57344-65072 – The connection to target system has
been lost. Backup set canceled.

This was resolved by changing the Resource Order of the
Exchange items. The Veritas solution was to try to backup
the Exchange Public Folders and Mailboxes in separate
jobs, but I found an alternate solution that resolved
the problem. It was as simple as setting the Public
Folder Store to be backed up before the Mailbox Store.
Thanks to the original poster in the Veritas Newsgroups.
I was not able to find the Newsgroup thread again to give
proper credit to the gentleman who came up with the solution.

A default installation of Windows 2003 Server, including Small
Business Server, will have the Network Load Balancing Service
enabled. This will cause the Service Control Manager to display
an Application popup before login: “At least one service or
driver failed during system startup. Use Event Viewer to examine
the event log for details”. In the Event Viewer a Service Control
Manager Event ID: 7000 will be displayed with the following details:

Description:

The Network Load Balancing service failed to start due to the following error:

The service cannot be started, either because it is disabled or
because it has no enabled devices associated with it.

A supposed fix for this is to view the properties of the network
connections on the server and remove the check for the Network
Load Balancing Service in the list of Services. I have yet to
see this fix work.

The fix that I have found and use on my productions servers
requires a quick registry change. Please note that changing
the Windows registry can have disastrous results if you make
the wrong changes. If you are not sure about the changes you
are making, contact qualified professionals like New Age
Digital to assist you!

1. Start Registry Editor. Click Start, Run, type
   “regedit” in the Open box, and click OK.
2. Drill down to the
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WLBS
   registry key.
3. Right click the WLBS registry key and click Export.
   Save the file with a descriptive filename to a secure
   location. This will backup the registry key and allow
   you to restore the key if you make a mistake or decide
   to use Network Load Balancing in the future.
4. In the right window pane, right click registry
   entry named Group, and then click Modify.
5. Clear the Value data. Simply delete the PNP_TDI
   and leave the field blank. Click on OK, and close
   the Registry Editor.
6. On reboot the Error message will no longer be displayed.

If you wish to enable Network Load Balancing, browse to the
backup of the registry key and double click it. Windows will
ask you to confirm importing the data into the registry.
Approve the import and reboot. Note that any registry key
restore will overwrite existing registry values. Any changes
made to the other values under the WLBS key will be
overwritten as well.

(Portions of this document are parphrased from or directly copied
from Microsoft KB article 555022 by Bernard Cheah, MVP.)

Passive Mode FTP connections are normally required by clients connecting through a
NAT firewall or router. The client connects on port 21 and issues a PASV command,
the server responds with a port in the 1024-65535 range for the data connection.
After a data connection command is issued by the client, the server connects to
the client using the port immediately above the client-side port of the control
connection. The Windows 2003 SP1 Firewall will prevent PASV FTP from working
properly unless exceptions for the ports are created. A metabase property key
named PassivePortRange can be configured to specify the port range the server
will respond with. This can be used to limit the security risk for the FTP
server. The property key only exists in IIS 6.0. Support for IIS 5.0 on
Windows 2000 can be added, but the system administrator will need to install
Service Pack 4 and add the PassivePortRange key in the system registry. Two
ports must be opened for each concurrent FTP connection.

On Windows 2003 Server with IIS6

• To Enable Direct Metabase Edit
  1. Open the IIS Microsoft Management Console (MMC).
  2. Right-click on the Local Computer node.
  3. Select Properties.
  4. Make sure the Enable Direct Metabase Edit checkbox is checked.
• Configure PassivePortRange via ADSUTIL script
  1. Click Start, click Run, type cmd, and then click OK.
  2. Type cd Inetpub\AdminScripts and then press ENTER.
  3. Type the following command where the range is specified in
     “..”. cscript.exe adsutil.vbs set /MSFTPSVC/PassivePortRange
     “5001-5201″ 
  4. Restart the FTP Publishing Service.

You’ll see the following output, when you configure via ADSUTIL script:

Microsoft (R) Windows Script Host Version 5.6

Copyright (C) Microsoft Corporation 1996-2001. All rights reserved.

PassivePortRange : (STRING) “5001-5201″

• Add each port to the Windows Firewall
  1. Click Start, click Control Panel, open Windows Firewall,
     and select the Exceptions tab.
  2. Click the Add Port button.
  3. Enter a Name for the Exception and the first number in the
     port range.
  4. Click TCP if not already selected and click OK.
  5. Repeat for each port in the range – for large ranges see
     the end of the document.
  6. Enable the Windows Firewall on the General Tab.

On Windows 2000 Server with IIS5

Configure PassivePortRange via Registry Editor

1. Start Registry Editor (Regedt32.exe).
2. Locate the following registry key:
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msftpsvc\Parameters\ 
3. Add a value named “PassivePortRange” (without the quotation marks) of type REG_SZ.
4. Close Registry Editor.
5. Restart the FTP Publishing Service.Note: The range that FTP will validate is from 5001 to 65535.

To add a range of ports to Windows Firewall from the Command Line

1. Click Start, click Run, type cmd, and then click OK.
2. Type in the following where the range is specified
   in ( ) and the name of the firewall entry is in ” “.      

   FOR /L %I IN (5001,1,5201) DO netsh firewall add portopening
   TCP %I “Passive FTP”%I 

3. Each port in the range will be added with an “OK” confirmation.

Retail Management System(RMS) is a Microsoft product for managing your
retail store. RMS is a versatile Point of Sale(POS) product with
manageability and security built in. There are three parts
of the system that work together to make this product easy to
use and manage. The administration, manager and the POS make RMS
an easy product to run your retail needs.

The administration program is where the database is setup and maintained.
There are two types of databases that can be used with RMS. If your
store’s data storage needs are small(under 2 gigabytes), then you can run
the MSDE provided with the RMS product. Storage needs greater than 2 gigs
will have to be setup using Microsoft SQL Server, which can handle very
large databases.

The Manager is where the day to day activities are carried out. It can
run reports, set up cashier and manager accounts as well as employees,
and set up and manage many other aspects of your store’s operation.
employees. Employee security rights are setup to restrict what portions
of RMS can be viewed and used by your employees. Manager is very powerful
tool to view, report and control your retail. Multiple stores can be
tied together with the addition of the headquarters package which allows
all stores to share account information as well as the ability to transfer
product from one location to another.

The Point of Sale(POS) is where all transaction are processed. This is
a simple to use GUI that is very customizable to suit your stores needs.
This is where your cashiers conduct all transactions such as sales, back
orders, work orders, layaways and much more.

Whether you are a small or large retail store, you will find
Microsoft Retail Management System
powerful enough to handle your needs. Ease of use and manageability
will make you and your employees more productive. If you would like a 90
day trial version of Microsofts Retail Management System then
contact us at New Age Digital, Inc. for details.