Q:

File Replication Monitor server module does not communicate with Control center.

A:

Make sure if Net BIOS over TCP/IP is enabled and Client for Microsoft Networks was installed on a computer. Also network cable has to be plugged in.

Q:

Do I need to uninstall File Replication Monitor before upgrading to a new version?

A:

No.

Q:

I have problems with the new product version installed recently.

A:

You can get back to your last product version. Replace the files in the %File Replication Monitor home% folder with the files from the %File Replication Monitor home%\Backup folder.

Q:

Stream write error message while copying.

A:

Disk is full. Free disk space.

Q:

FTP transmit error 426

A:

Local file is in use by some program.

Q:

Create database error I/O 112

A:

Disk is full. Free disk space.

Q:

It is impossible to close Control center immediately after its start.

A:

A large log file was loaded. Please, wait.

Q:

Files are being copying very long.

A:

File Replication Monitor sends LAN notification messages (may be error message) to a computer not existing on LAN.

Q:

Path is not accessible message. (1)

A:

File Replication Monitor service has been installed under the Local System account. This account does not provide access to network resources. To change the service account select the Services item in Windows Control panel. Find the File Replication Monitor entry in the opened window and click on it. Enter the desired account name and password on the Log On page and press OK button.

Q:

Path is not accessible message. (2)

A:

You use a mapped remote disk as a destination location. This is valid if you start File Replication Monitor as executable application. But if you use it as a Windows service the mappings made before are not valid for the service. This is a common Windows problem rather then File Replication Monitor. There are two ways how to solve it: use UNC name in destination ("\computer_name\Shared Folders" instead of "G:\Shared Folders") or launch File Replication Monitor as the executable application.

Q:

Transfer speed value doesn't display in some log lines.

A:

For the short files the transfer time is too small to display.

Q:

May I run File Replication Monitor version 1 and version 2 on the same computer simultaneously?

A:

No. Version 1 and 2 can't work on the computer at the same time.

Q:

What is a maximum length of the file path?

A:

255 symbols.

Q:

My SMTP server does not accept the emails from  File Replication Monitor(usually error 501 5.5.4).

A:

Your SMTP server does not accept a "File Replication Monitor" name as a valid sender name/address. Replace it with the correct one (from your email client for example). Replacement is required in Program settings window -> Network page -> Email section.

Q:

My SMTP server still doesn't accept the emails after the changes from the answer above which have been made.

A:

Remove blank spaces in the sender name you have changed.

Q:

File Replication Monitor works on one computer and doesn't work on the other one.

A:

Check if the option Net BIOS over TCP/IP is ENABLED on this computer.

Q:

My File Replication Monitor is installed on Windows 95 (98/ME) computer. Can I replicate NTFS permissions from the remote computer?

A:

No. Windows 95/98/ME operating system does not allow to work with NTFS permissions.

Q:

File Replication Monitor skips files without extensions.

A:

Use file mask "*" instead of "*.*" in the Include/Exclude files field.

Q:

I need to change a location of the directory where File Replication Monitor keeps temporary files.

A:

Insert the following text to the file frm.cfg01 file and restart the server module:

[Custom]

TEMPDIR=New_directory_location

For example:

[Custom]

TEMPDIR=D:\Temp.

Q:

File Replication Monitor "DATA" directory occupies much space.

A:

Set a Windows NTFS Compression attribute for the folder DATA and all its subfolders. The compression ratio can reach 7-8 times.

So a lot of space can be saved.

Q:

When I install service the error 1057 (The account name is invalid or does not exist) occurs.

A:

Enter user name like "domainname\username" or ".\username" for a local computer. The example is shown the in the install service window of File Replication Monitor.

Q:

When the HTML email message is sent, there are no CRLF ( ) characters in the resulting email.

A:

Use a standard <BR> tag to include CRLF into the HTML emails.

Q:

On a computer with Windows XP, when I disconnect the network cable, the Control Center is unable to connect to the server module.

A:

This is an option of Windows XP called DHCP Media Sense. It automatically disables the TCP/IP stack whenever there is no network connection. Switching it off requires adding a key to the Windows registry.

Open the Registry Editor and locate the folder

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters

Add a new DWORD key named DisableDHCPMediaSense with a value of 1 and reboot your computer.

To re-enable Media Sense, change the value to 0 and reboot your computer.

Q:

How to move File Replication Monitor to another server.

A:

The best way of moving File Replication Monitor from one server to another is to move both the Home folder and the Application Data folder from the old server to the same letter disk drive on the new one. In this case you don't need to change any properties and paths.

Q:

I installed the service but when I start, I have an error msg that says: "Start service error 1069".

A:

To solve this problem, type the correct password in the File Replication Monitor service account.

To correct the password in Microsoft Windows 2000 Server and Microsoft Windows XP:

1. Click Start, point to Settings, and then click Control Panel.

2. Double-click Administrative Tools, and then double-click Services.

3. Double-click File Replication Monitor service item, and then click the Log On tab.

4. Type the correct password in the Password and Confirm password text box, and then click OK.

Also the error 1069 occurs if the service was started from an account that does not have the "Log on a service" right. To work around this problem, you should grant to this account the "Log on a service" right.