Error No.

Area

Description

123

Server

Softalk Share Server is unable to start. This is because another program is listening on the port that Softalk Share Server uses. Run netstat –a from a command prompt and look to see which other program is listening on port 8100 (the default port for Softalk Share Server). Stop this program and try running Softalk Share Server again. Alternatively, change the port that Softalk Share Server uses.

125

Server Setup

Setup failed to determine if there is an existing Softalk Share Server store with data. This is caused by setup not being able to open the existing message store, or, if the store is opened OK, not being able to determine if there is any data in the message store. This error can be safely ignored. However, you must only choose to transfer data from your existing PST to the newly installed Softalk Share Server message store if you know that there is no data already in your existing Softalk Share Server message store.

126

Server Setup

.NET 2.0 could not be installed because another instance of dotnetfx.exe may be running. Another instance of dotnetfx.exe running possibly because a previous version of setup failed to complete the .NET setup. Initially, the best solution is to wait for the previous instance of .NET 2.0 framework setup to complete. If this does not work, as a last resort, open task manager and go to the Processes tab. Select any instances of msiexec.exe and press End Process. Then try running Setup again.

127

Server Setup

.NET 2.0 could not be installed because the Windows Installer is not properly installed. .NET 2.0 needs Windows Installer 3.0 or later installed on the computer before it can itself be successfully installed. Download the Windows Installer 3.0 from Microsoft's site at http://www.microsoft.com/downloads/details.aspx?FamilyID=889482fc-5f56-4a38-b838-de776fd4138c&DisplayLang=en.

128

Server Setup

.NET 2.0 could not be installed and returned an error code. The error code returned is one of those listed below:

3010 Reboot is required.

A computer reboot is required following the installation of the .NET Framework

4096 Improper usage/invalid parameters.

Either the syntax used to specify parameters to Dotnetfx.exe is incorrect, or the parameters are invalid.

4097 On Windows 2000, Windows XP or Windows Server 2003, need Administrator rights to (un)install.

You do not have the permissions required to install or uninstall this application. Please contact your administrator.

4098 Installation of Windows Installer components failed.

The Windows Installer installation failed. As a result, the installation of Dotnetfx.exe cannot proceed.

4099 Windows Installer is not installed properly on computer.

Due to the improper installation of Windows Installer, the installation of Dotnetfx.exe cannot proceed.

4100 CreateMutex failed.

A fatal error occurred and the installation of Dotnetfx.exe cannot proceed.

4101 Another instance of setup is already running.

If another instance of setup is running, it will be allowed to continue and the current installation cannot proceed.

4102 Cannot open MSI Database

4103 Cannot read from MSI Database

4111 Cannot get Temporary directory.

4113 Beta NDP components detected.

A beta version of the .NET Framework was detected on the computer. You must uninstall any beta versions before attempting to install Dotnetfx.exe.

4115 The length of the %temp% path is too long

4116 The length of the source path is too long

4118 Failed to create or write to the log file

4119 The Darwin service is hung and requires a reboot in order to continue

4120 An internal error occurred while trying to initialize the Darwin Service

4121 One or more prerequisites for this product is missing

4122 The product does not support installing on the detected operating system type

8191 Setup Failure—unknown reason.

A fatal error occurred. The installation of Dotnetfx.exe cannot proceed.

8192 Reboot is required

129

Server Setup

The Windows installer could not be installed and returned an error code. An undetermined error occurred when trying to install the Windows Installer. You should download and install this yourself from Microsoft's web site and then try re-running Setup. You can download from http://www.microsoft.com/downloads/details.aspx?familyid=889482fc-5f56-4a38-b838-de776fd4138c&displaylang=en

130

Server Setup

Microsoft Data Access Components (MDAC) could not be installed and returned an error code. An undetermined error occurred when trying to install MDAC. You should download and install this yourself from Microsoft's web site and then try re-running Setup. You can download from http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&DisplayLang=en.

131

Server Setup

SQL Express could not be installed and returned an error code. An undetermined error occurred when trying to install SQL Express. You should download and install this yourself from Microsoft's web site and then try re-running Setup. You can download from http://msdn.microsoft.com/vstudio/express/sql/download.

132

Server Setup

Setup failed to add a user to the database. During the installation of Softalk Share Server, the setup program tries to add the first user to the database. However in this case it failed.

133

Server Setup

Setup failed to configure the JET data source. During the installation of Softalk Share Server, the setup program tries to configure a data source called SoftalkBusinessServer to point to a JET database .mdb, which resides in the data folder that you selected during setup. Unfortunately this process failed. The cause could be a corrupt JET driver. Try re-installing MDAC (Microsoft Data Access Components). You can download from http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&DisplayLang=en. Note that if you are running Windows XP SP2 or later, you will not be able to re-install MDAC since it comes built into the operating system.

134

Server Setup

Setup failed to configure the SQL Server data source. During the installation of Softalk Share Server, the setup program tries to configure a data source called SoftalkBusinessServer to point to a SQL Server database. Unfortunately this process failed. The cause could be a corrupt SQL Server ODBC driver.

135

Server Setup

Setup failed to remove the JET data source. During the installation of Softalk Share Server, the setup program attempts to remove a data source called SoftalkBusinessServer. However, in this case the process failed.

136

Server Setup

Failed to create the SoftalkBusinessServer database in SQL Server. Setup detected that there was no existing database called SoftalkBusinessServer in the SQL Server database, however on execution of the CREATEDATABASE command, SQL Server returned a failure. Try looking for the file SoftalkBusinessServer.mdf in the folder C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data and rename or delete the file SoftalkBusinessServer.mdf and SoftalkBusinessServer_log.mdf . Then re-run setup.

137

Client

Failed to connect to the Softalk Share Server server. The server may not be running, you may have entered the wrong server and authentication details or there may be a problem with your network. Check your server and authentication details in the Mail applet in the control panel. Check with your system administrator that the Softalk Share Server server program/service is running. Check your network connections to see that you can access the server computer.

140

Server Setup

Windows Installer requires a reboot part way through the installation of .NET and SQL Server Express. Setup failed prior to the installation of SQL Server Express because the Windows Installer was not fully installed. Setup installed the Windows Installer (which is a prerequisite component for SQL Server Express) but the Windows Installer required a reboot of Windows before it was properly installed. This meant that Setup could not continue with the installation of SQL Server Express. Reboot the computer and run Setup again, selecting to install SQL Express.

141

Client Setup

Failed to open Softalk Share Server message store! Check that the server is running and that you have the correct login details. Client setup failed to open the Softalk Share Server message store in order to update its details. This may be because the server is not running or because the login details supplied to client setup are not correct. Make sure that the Softalk Share Server server is running on the server computer. Make sure that you have supplied client setup with the correct server name, whether SSL encryption is being used and the correct login credentials. If you are authenticating using the Active Directory, get your administrator to make sure that there is a Softalk Share Server user linked to your Windows user account.

142

Administrator

You cannot add users and/or groups from the Active Directory as this computer is not running as part of a Windows domain! This computer is not running as part of a Windows domain. In order to add users and groups from the Active Directory, connect this computer to a Windows domain.

143

Administrator

The selected user does not have a Windows logon account on the target computer! You have chosen a computer on which to install the client software. However, the selected user does not have a Windows logon account on that computer and the operation cannot complete. Retry the operation, selecting a computer that the user has previously logged on to or select a user that has a Windows logon account on the target computer.

144

Administrator

Your trial period is over! The product will either not function or will function in limited fashion until a keycode has been purchased.

145

Administrator

Too many users defined! You have more users defined that you have a license for. The product will either not function or will function in limited fasion until a keycode has been purchased.

146

Server

Local system account chosen. You have chosen to log into the Softalk Share Server Windows service as the local system account. If you are using Active Directory authentication then this may not work under the local system account. To resolve this potential probem, log onto the Windows service as a user that is able to authenticate Active Directory users.

150

Server

Failed to open database with supplied connection string! The data source specified or the database specified may not exist or you may not have access to it. Check that the data source exists, that the actual database specified in the data source exists and that you have permissions to access the database.