Subsequent installs fail after successful install/uninstall on Windows.

InstallShield must have corrupted one of the installs. To fix the problem, delete the<M-Business_Home> directory from the registry and delete the two InstallShield directories. The steps below assume that you do not have the Show hidden files and folders option enabled. If this option is enabled already, begin with step number 5 below:

Error message, "Setup failed to launch installation engine" when attempting to uninstall M-Business Server.

Run the installer again (this will overinstall M-Business Server) then you will be able to uninstall.

To avoid this problem, reboot your machine between uninstalling and installing M-Business Server.

Write Timeout message is received on device OR syncing large data set fails repeatedly

Sometimes this problem does not generate a Write Timeout message—the only symptom is that syncing repeatedly fails on a large data set. To be sure that timing out is the problem, check the M-Business Server sync error log (<M-Business_Home>/ logs/sync_error.log) for the following pattern of errors associated with the series of failed synchronizations—the important part is bolded:

[Mon Sep 22 19:01:23 2003] [warn] (1496) Sync ending with error message: code==1, message==Account locked. Try again later. user=fun

[Mon Sep 22 19:03:43 2003] [error] (2312) Error fetching schemaset(saletask): httpStatus==404, error==23/File Not Found.

[Mon Sep 22 19:03:45 2003] [warn] (2312) TIMED: fetching: never finished

If you see this sequence, the problem is most likely that the synchronization is timing out before the download of the large data set can be completed. Increase the DeviceReadTimeout SyncPref, and maybe the DeviceWriteTimeout SyncPref as well.

For more information on these settings, see User addable settings.

Error 1069: "The service did not start due to a logon failure"

You may have entered an incorrect domain account password during installation.

In the Services dialog, double-click on M-Business Sync Server service and modify the domain account information as necessary.

Also, make certain the account has administrator privileges. See Postinstallation tasks.

The shortcut to the M-Business Server Manager in the Start Menu does not work.

In order for this shortcut to function, you must have the Microsoft Management Console (MMC) installed when you install M-Business Server.

Unable to view the M-Business Server administration pages.

M-Business Server runs on port 80. If you want to install on a machine with another web server you will have to change the port number to something other than port 80. For more information, refer to Changing the Port Number in the section for your operating system.

A Domain Name Server (DNS) is not available on my network.

You will need to set the ServerName directive in the sync.conf.default file. See Customizing M-Business Server .

Admin Server service does not start with NT domain integration.

Try manually starting the Admin Server service in the Services control panel. If this fails and you get an Error 1069: The service did not start due to a logon failure, you probably entered an incorrect domain account password during the installation. If you double-click on M-Business Admin Server service in the Services control panel, you can reenter any part of the domain, account name, and password information.

Error occurs when syncing large binary applications.

If you try to synchronize a binary application, such as a .prc, that is higher than the default 256K maximum, you will receive a file size limit error.

To enable downloads of binaries that exceed the default channel properties maximum, change the WebToGoMaxTextSize directive in the sync.conf.default file to a size larger than the binary application to be downloaded.

M-Business Server drops connection when syncing large channels using WinInet and proxy server.

This could occur if the proxy server’s timeout value is reached before the entire channel’s contents are fetched. To avoid this issue, increase the proxy server’s timeout value.

Users see Version Mismatch dialog when attempting to synchronize to M-Business Server

.

A 6.0 or later M-Business Client will not work with M-Business Server versions earlier than 5.3. The laptop version of the 6.0 or later M-Business Client will not work with M-Business Server versions earlier than 5.5.

Users cannot synchronize to sites that require login cookies.

If your M-Business Server accesses the Web through a proxy server, your users may experience difficulties with sites requiring login cookies. To prevent this, we suggest turning off the proxy server’s caching ability.