Transfer 2000 Eng

marketing.manager®

update.transfer2000

update software AG

marketing.manager update.transfer2000

May 2003

This document contains information protected by Austrian and US copyright laws, international treaty provisions and all other applicable national laws.

Copyright © by update software AG, 2003

All rights reserved

The user is entitled to load information, to enter and store said information in local databases and to forward it in electronic format.

Many of the names used by manufacturers and traders to refer to their products are registered trademarks. Where names of this type appear in this document and update is aware that these are trademarks, this is indicated by the use of the appropriate symbol (, ).

marketing.manager® is a trademark of update, all other computer and software names listed in this publication are brand names and/or registered trademarks of their respective manufacturers.

This document is for information purposes only and is subject to change without prior notification. UPDATE MAKES NO EXPRESS GUARANTEES OR ANY GUARANTEES IMPLYING LEGAL INTENT WITHIN THIS DOCUMENT. The content of this document is not intended to represent any recommendation on the part of update. Companies, names and / or data shown in screenshots are fictitious, unless otherwise stated.

Subject to alterations and corrections.

update software AGOperngasse 17-21

A-1040 Vienna/AustriaTel.: +43/1/878 55 - 0

Fax: +43/1/878 55 - 200www.update.com

[email protected]

http://www.update.com/

Contents

update.transfer 1

Overview....................................................................................................................................1Main features of update.transfer2000........................................................................................1Security issues............................................................................................................................2

IP Package Encryption.................................................................................................2Limited Server Access.................................................................................................2update.transfer protocol...............................................................................................3Transfer control............................................................................................................3Access monitoring.......................................................................................................3

About the manual.......................................................................................................................3

Client version 4

Overview....................................................................................................................................4Installation and setup..................................................................................................................4User interface.............................................................................................................................9

Menu bar......................................................................................................................9Settings.....................................................................................................................................11

Marketing.Manager Settings tab................................................................................11Preconfigure Phonenumbers tab................................................................................12Misc Features tab.......................................................................................................13

New SSLW connection............................................................................................................14New LAN connection..............................................................................................................17New FTP connection................................................................................................................19

Server version 21

Overview..................................................................................................................................21Installation and setup................................................................................................................21User interface...........................................................................................................................25

Menu bar....................................................................................................................25Icon bar......................................................................................................................26

Server Properties......................................................................................................................28Upgrade functionality...............................................................................................................30

Adding upgrades........................................................................................................30Upgrade manager.......................................................................................................31Upgrade properties.....................................................................................................32

Adding users.............................................................................................................................33

marketing.manager update.transfer2000 Contents · i

Troubleshooting 34

Overview..................................................................................................................................34update.transfer2000 – Server logging codes:.............................................................34update.transfer2000 – Client error codes:..................................................................35Appendix WSA_ERROR_Codes:.............................................................................37

Index 49

ii · Contents marketing.manager update.transfer2000

update.transfer

OverviewIn general, the update.transfer2000 client/server solution serves as a tool to transfer delta files for the communication from the central station to and from notebooks. It permits automated file transfer via port-to-port, FTP or LAN connection.

Since data transfer via FTP or LAN is standard procedure, there is no unusual functionality to take into account. The technological framework rules out both data compression and special security protocols.

The port-to-port solution, however, allows for 32 bit compression and protocol entries on the server side.

The data transfer process is fully automated and the communication module of marketing.manager (mmco.exe) is called with the appropriate parameters, if desired.

update.transfer gives you shorter connection times during communication processes, allows you to use compression when you transfer files via modem, comes with a scripting language which gives the administrator greater flexibility and is a true WIN32 application which handles multi-threading, improves memory management and offers complete control for dial-up processes.

Main features of update.transfer2000· Easy to set up.

· Only one authentication is visible to the user, i.e. the user logs on using his remote ID, all other authentication processes are not visible.

· Short connection time because no additional network authentication is necessary (between 10 and 15 seconds per connection).

· All data are transferred using 32 bit compression.

· Reporting structure based on the server provides communication information throughout the entire network.

· DNS name resolution is used.

· marketing.manager upgrades as well as other software upgrades are handled.

marketing.manager update.transfer2000 Main features of update.transfer2000 · 1

· Comprehensive tracking of distributed software using scripts, i.e. who has it, when was it used, how long did it take, etc.

· Registry file and mm.ini file can be edited using scripts, if required.

· Built-in scripting language for upgrades allows for greater functionality. update.transfer's online help which is accessed from the Upgrade Properties dialogue box contains detailed information, see Upgrade Properties on page 32.

· Scripts can be distributed on user level.

· Auto-sensing function on network connection. If no LAN connection can be detected, a dial-up connection is established automatically.

· Extensive list of error codes for troubleshooting, see Troubleshooting on page 34.

· Built-in compression on all modem connections.

· Clients can be pre-configured on the central station and sent to the client notebooks.

· The modem connection is active only during actual upload and download time.

· Win32 multi-threaded user interface. The user is therefore able to abort the communication process at any time.

· Multi-threaded Win32 NT service with local heap management.

Security issuesupdate.transfer is a very safe way to transfer delta files due to the following reasons:

IP Package EncryptionEach transferred IP package is encrypted individually and can only be decoded together with all other transferred packets. This makes it difficult for listening attackers to retrieve individual packages from the network and to read any coherent data.

Limited Server AccessEach user account has only limited access rights to server drives. In general, only the respective station directory, where only binary encrypted marketing.manager data are available, can be accessed. These binary files in turn only make sense if a marketing.manager system with exactly identical communication protocol is used to analyse the data. The appropriate database content is also necessary to successfully carry out the decoding process.

update.transfer protocolThe communication protocol specifically designed for update.transfer exists as readable source code only on update internal development PCs, is copyrighted und not accessible to people outside of update.

2 · Security issues marketing.manager update.transfer2000

Transfer controlIf even the slightest suspicion exists regarding an attack by hackers, the server sends the attacker on TCP/IP level the command to initiate the network connection. This command results in the disconnection of the modem connection or in the request of a new IP address.

Access monitoringPermanent access monitoring, which results in entries in the server's event log, allows the respective administrator to automate certain security mechanisms.

About the manualClient version The chapter entitled Client version contains a description of the setup and

installation process, an explanation of the key elements of the user interface as well as descriptions of key user activities such as how to add new FTP, LAN or port-to-port connections.

Server version The chapter entitled Server version contains a description of the setup and installation process, an explanation of the key elements of the user interface, how to set the server properties, the upgrade functionality and how to add users.

Troubleshooting The chapter entitled Troubleshooting contains a list and descriptions of server logging and client error codes.

marketing.manager update.transfer2000 About the manual · 3

Client version

OverviewThis section describes the installation and setup as well as the user interface elements of update.transfer client and how to add a new communication connection.

Installation and setupThe client version of update.transfer can be installed on Windows NT Workstation 4.0 (SP 3 or higher), Windows 98, Windows 2000 or Windows XP.

1. Place the marketing.manager installation CD in your computer's CD-ROM drive.

2. Open the Start menu and select Run.The Run dialogue box is displayed.

3. Start the update.transfer2000 client setup program by typing "d:\update.transfer\Client\setup" (where "d:" is the drive containing the marketing.manager CD) and press Enter.The Welcome screen is displayed as below.

4 · Installation and setup marketing.manager update.transfer2000

4. After reading the text, click Next.The License Agreement screen is displayed.

5. Accept this agreement by clicking Yes.If you choose No, the setup program is closed.The Choose Destination Location screen is displayed.

6. Specify the update.transfer2000 program folder. The default is as follows:C:\MM\transfer2000ClientIf you wish to change this, use the Browse button.

marketing.manager update.transfer2000 Installation and setup · 5

7. Click Next to continue.The Supervisor-Password screen is displayed.


8. To prevent the program settings from being changed by users, an application supervisor password can be entered. Mark the Yes radio button if you wish to do so. Enter the respective password in the Password and confirm Password fields which appear upon marking the Yes radio button.Communication should be run once or twice daily. Remind the user to start the communication process by marking the Yes radio button.If the permitted number of days is exceeded by the user, a dialogue box appears prompting the user to start the communication process.

9. Click Next to continue.The Preconfigure Phonenumbers screen appears.

10. Mark the Roaming user supported check box if you want to allow roaming users. The area underneath this check box appears greyed out if this check box is not marked.Enter the name of the location in the Aliasname field and the phone number including the code for an outside line (e.g. "0") in the Phonenumber field.Mark the Default check box if this is the default location.


11. Click Next to continue.The InstallShield Wizard Complete screen appears.

12. Click Finish to exit the setup wizard. update.transfer2000 client can now be started with the Start Programs menu option.


User interfaceThe update.transfer client user interface contains four areas to allow for easy configuration and navigation.

Menu bar

File menu

Save log as…Select this menu command to save the log.

ExitSelect this menu command to close update.transfer client.

Connections menu

New SSLW connectionSelect this menu command to add a new port-to-port connection.

New Lan connectionSelect this menu command to add a new Lan connection.

New FTP connectionSelect this menu command to add a new FTP connection.

marketing.manager update.transfer2000 User interface · 9

Remove ConnectionSelect this menu command to delete a selected connection.

ConnectSelect this menu command to connect.

Icon bar

ConnectSelect this icon to connect to the currently selected connection.

DisconnectSelect this icon to disconnect the connection you are currently connected to.

DeleteSelect this icon to delete a selected connection.

SSLWSelect this icon to add a new SSLW connection, see New SSLW connection on page 14.

LANSelect this icon to add a new LAN connection, see New LAN connection on page 17.

FTPSelect this icon to add a new FTP connection, see New FTP connection on page 19.

Configuration area

AppBatch-Cfg

· Click the "+" sign to display the settings of update.transfer client: Commandline, Path, Display Notification Message, Working Directory, etc. A "0" indicates that the relevant check box has not been selected, a "1" indicates that the relevant check box has been selected.

· Right-click to open the Settings dialogue box.See Settings on page 11.

Connections

· Click the "+" sign to display the connections already set up.

o Click the "+" sign of an existing connection to display the settings.

o Right-click an existing connection to open the connection properties dialogue box for the respective connection.

· Right-click to open a popup menu which contains menu options to add new SSLW, LAN or FTP connections or to delete an existing connection.

10 · User interface marketing.manager update.transfer2000

Display area

The display area contains information, e.g. about the transfer status.

Settings· Right-click AppBatch-Cfg.

The Settings dialogue box is opened.

Marketing.Manager Settings tab

App-PathEnter the path and name of the local communication module here. Alternatively, use the Browse button to search for the location of mmco.exe.

Working DirectoryEnter the working directory of the local communication module here. Alternatively, use the Browse button to search for the folder of the working directory.

marketing.manager update.transfer2000 Settings · 11

Commandline SwitchesEnter the desired parameters for the communication module, e.g. -u…, -k…, etc. Detailed information on command line parameters can be found in the Supervisor manual part 2.

Preconfigure Phonenumbers tab

Roaming user supportedMark this check box if roaming dial-up is supported.

DefaultMark this check box if this is the default user.

AliasnameEnter the alias of the dial-up connection here.

PhonenumberEnter the phone number of the dial-up connection here.

Existing dial-up connections are displayed in the pane below with the alias and the phone number.

Modify, Add, DeleteUse the respective button to modify, add or delete a dial-up connection.

12 · Settings marketing.manager update.transfer2000

Misc Features tab

Display Notification Message boxesMark this check box if notification message boxes should be displayed so that the user is prompted to confirm each communication step, e.g. when the connection is established.

Remember user to replicateMark this check box to remind the user to start the communication process. If this check box is selected and a number of days is entered in the Timespan field a message box is displayed.

TimespanEnter a number of days here to display an animation to remind the user to start the communication process.This field appears greyed out and cannot be edited if the Remember user to replicate check box is not marked.

LZW Compression

LAN ConnectionsMark this check box to enable LZW compression during LAN connections.

Modem ConnectionsMark this check box to enable LZW compression during modem connections.

marketing.manager update.transfer2000 Settings · 13

New SSLW connectionSSLW or port-to-port connection is the connection type which is used in most cases. Also, it is the only connection type which supports integrated script language. It allows the transfer of data at the lowest network level (TCP/IP).

During data transfer by modem, data from the client and from the server are compressed. If the connection is lost, data transfer resumes at the point where the interruption occurred. The nature of the security structure of the port server means that it is not necessary to log on to the network during dial-up connection (NT domain). The user needs only request an IP address via the DHCP server. This not only saves time during dial-up but is also less expensive since logging on to a Windows NT domain or a mail server can take a very long time in practice and connection often fails due to poor quality connection infrastructure.

1. Right-click Connections in the display area.A popup menu is displayed.

2. Select the Add New SSLW Connection menu command.

14 · New SSLW connection marketing.manager update.transfer2000

The SSLW – Connection – Properties dialogue box is displayed.

3. Enter the respective information in the following fields:

ConnectionNameEnter the name of the connection in this field. Blanks are not allowed.

Dialup - ConnectionAs the communication process can be carried out via dial-up connection, you can select the respective dial-up connection from this drop-down list box.

DialupUserIDThe user name of the dial-up user is taken automatically from the dial-up connection but can be edited.

marketing.manager update.transfer2000 New SSLW connection · 15

Dialup-PasswordThe user password of the dial-up user is taken automatically from the dial-up connection but can be edited.

SSLW - Server (IP or DNS)Enter the port server name of update.transfer2000 server or the appropriate IP address.

SSLW - PortThe default port number is 80 but can be edited. If the network is protected by a firewall, either the port must be opened or the firewall package filter must be adapted to update.transfer2000.

SSLW -UserIDIn order to access the update.transfer2000 server a user name is required and must be entered here.

SSLW - PasswordIn order to access the update.transfer2000 server a user password is required and must be entered here.

Local-PathEnter the path for the local marketing.manager including the workstation number of the station you want to communicate with, e.g. C:\Program Files\marketing.manager\1000 if 1000 is the number of the station you want to communicate with. Alternatively, use the Browse button to search for the location of the workstation.

Connection-TypeSelect the connection type here. The following options are available: Network, Modem and Automatic.

Show final messagebox after successful replicationMark this check box to display a message box after a successful communication process.

Keep modem connection alive after replicationMark this check box to maintain the modem connection after a successful communication process.

Volatile RAS PasswordMark this check box if it should not be possible or allowed to store the RAS password but the user should only be asked once to enter a password.

Suppress RAS DialogMark this check box if the Microsoft default dialogue box should not be used.

Hold connection during application callMark this check box if the modem connection should not be disconnected whilst the communication process is running.

16 · New SSLW connection marketing.manager update.transfer2000

Create DesktopShortcutAfter you have filled in the configuration fields above, click this button to create a shortcut on the user's desktop. This shortcut contains the following parameters: "-a" for "automatic" and "-s" for "switch".In the future, all the user needs to do to start the communication process is double click the desktop shortcut. Normally, it is not necessary to open update.transfer client after the user and the connection have been configured.

New LAN connectionThe connection via local area network does not support integrated script language.


2. Select the Add New LAN Connection menu command.

The LAN – Connection – Properties dialogue box is displayed.



marketing.manager update.transfer2000 New LAN connection · 17





Remote-PathEnter the remote path for marketing.manager including the workstation number of the client's station in standard FTP notation (RFC) or use the Browse button.




Create DesktopShortcutAfter configuration, click this button to create a shortcut on the user's desktop. This shortcut contains the following parameters: "-a" for "automatic" and "-s" for "switch".

In the future, all the user needs to do to start the communication process is double click the desktop shortcut. Normally, it is not necessary to open update.transfer client after the user and the connection have been configured.

18 · New LAN connection marketing.manager update.transfer2000

New FTP connectionThe connection via FTP does not support integrated script language.


2. Select the Add New FTP Connection menu command.

The FTP – Connection – Properties dialogue box is displayed.






marketing.manager update.transfer2000 New FTP connection · 19


Remote-PathEnter the remote path for marketing.manager including workstation number in standard FTP notation (RFC) or use the Browse button.




Create DesktopShortcutAfter configuration, click this button to create a shortcut on the user's desktop. This shortcut contains the following parameters: "-a" for "automatic" and "-s" for "switch".

In the future, all the user needs to do to start the communication process is double click the desktop shortcut. Normally, it is not necessary to open update.transfer client after the user and the connection have been configured.

20 · New FTP connection marketing.manager update.transfer2000

Server version

OverviewThis section describes the installation and setup, the user interface elements of update.transfer server, how to set the server properties, the upgrade functionality and how to add users.

Installation and setupThe server version of update.transfer can be installed on Windows NT Server 4.0 (SP 3 or higher), Windows 98, Windows 2000 or Windows XP.

1. Place the marketing.manager installation CD in your computer's CD-ROM drive.

2. Open the Start menu and select Run.The Run dialogue box is displayed.

3. Start the update.transfer2000 setup program by typing "d:\update.transfer\Server\setup" (where "d:" is the drive containing the marketing.manager CD) and press Enter.The Welcome screen is displayed.


4. After reading the text, click Next.The License Agreement screen is displayed.

5. Accept this agreement by clicking Yes.If you choose No, the setup program is closed.The Choose Destination Location screen is displayed.

6. Specify the update.transfer2000 program folder. The default isC:\MM\transfer2000Server.If you wish to change this, use the Browse button.


7. Click Next to continue.The Start Copying Files screen is displayed.

8. The current settings are displayed. Use the Back button if you wish to review any settings.

9. Click Next to continue.The installation process is started and the status is displayed.

10. The InstallShield Wizard Complete screen appears.


11. Click Finish to exit the setup wizard.

12. Do the following to complete the installation of update.transfer2000 server:

a. Open the Start menu and select Run.The Run dialogue box is displayed.

b. Type the path of your update.transfer2000 server installation, e.g. "C:\MM\transfer2000Server\MMT_srv.exe", and add the following parameter: -u

c. Press Enter.

d. Open the Start menu and select Run again.The Run dialogue box is displayed.

e. Type the path of your update.transfer2000 server installation, e.g. "C:\MM\transfer2000Server\MMT_srv.exe", and add the following parameter: -i

update.transfer2000 server is now fully installed and can be started from Windows Explorer.


User interfaceThe update.transfer server user interface contains four areas to allow for easy configuration and navigation.

Menu bar

Server menu

Server PropertiesSelect this menu command to enter or modify the server properties, see Server Properties on page 28.

Stop Server-ServiceSelect this menu command to stop the server service.

Start Server-ServiceSelect this menu command to start the server service.

QuitSelect this menu command to close update.transfer client.


Import/Export menu

The update.transfer2000 server is able to handle hundreds of users. To facilitate or automate the transfer of user data it is possible to import from and export data to a Microsoft Excel® spreadsheet using an OLE interface.

Import Userdata from ExcelsheetSelect this menu command to import user data from a Microsoft Excel® spreadsheet.

Export Userdata to ExcelsheetSelect this menu command to export user data to a Microsoft Excel® spreadsheet.

Backup menu

It is possible to back up all server data for security reasons. A .reg4 file is used to back up the data. This file can be used in any location.

Backup Configuration-DataSelect this menu command to back up the configuration data.

Icon barNew UserSelect this icon to add a new user.

Delete UserSelect this icon to delete a selected user.

New UpgradeSelect this icon to add a new upgrade.

Delete UpgradeSelect this icon to delete an upgrade.

Upgrade ManagerSelect this icon to open the Manage Upgrades dialogue box, see Upgrade manager on page 31.

26 · User interface marketing.manager update.transfer2000

Configuration area

upgrades

· Click the "+" sign to display existing upgrades.

· Right-click to open a popup menu which contains menu options to add a new upgrade or to display the upgrade manager, see Upgrade manager on page 31.

user

· Click the "+" sign to display the users already set up.

o Click the "+" sign to display the user settings in a list.

o Right-click an existing user to open the Modify User dialogue box to edit the user's UserID, password or the local path.

· Right-click to open a popup menu which contains the new user-account menu options to add a new user account, see Adding users on page 33.

Display area

The display area contains information about the connected users. This area is empty if no users are connected.


Server Properties1. Select the Server Server Properties menu command.

2. The Server Properties dialogue box is displayed.

3. Enter the respective information in the following fields to add or modify the settings of the server:Server IP-AddressEnter the IP address of the server here. The IP address allows the user interface to establish a connection to the NT service via "Named Pipes".

PortEnter the port number. The port number can be selected and must be approved by the network administrator to avoid conflicts with the firewall or other running services, e.g. IIS.

Server-Root-PathEnter the update.transfer2000 server root path to which all users have access and for which subdirectories are created, e.g. C:\Program Files\marketing.manager\.

Upgrades-Root-PathUpgrades (scripts and files) also require a root path in order for a clear structure to be established.

28 · Server Properties marketing.manager update.transfer2000

Server-MachinennameEnter the server machine name here.

inactivity time-span till disconnection … secondsFor each user logged on to the server, an individual process is started. If communication is interrupted, the user is disconnected after the time specified here.

Eventlogging OutputoptionsThe system administrator is able to log all stages of the data transfer. Either the NT event log or an ASCII file can be used. The ASCII file is located in the "log" subfolder of your update.transfer server installation.

Eventlogging OptionsYou can specify here which events are logged. The following options are available: log failed logons, log successful logons, log failed file operations, log successful file operations.

Automatic BackupIf this check box is marked, after the server user interface is closed, the user is prompted whether the server data should be saved in an external file.

marketing.manager update.transfer2000 Server Properties · 29

Upgrade functionalityThe upgrade functionality allows the system administrator to send script files to update.transfer2000 clients. These scripts are used to transfer data, run programs and read and write registry information. The script commands are clearly described in the help file available on the server.

Adding upgrades1. Right-click upgrades in the configuration area.

Alternatively, you can use the New Upgrade icon in the icon bar.

2. Select Add New Upgrade from the popup menu.The Add New Upgrade dialogue box is displayed.


Upgrade NameEnter any name for the upgrade.

Upgrade DirectoryEnter the path for the upgrade directory where the update.spt script file and all additional files are saved or use the Browse button. Alternatively, you can add new directories by entering the directory path including the desired directory and clicking the Create Directory button.The entry in the Upgrade Name field is entered automatically as upgrade directory but can be edited.

30 · Upgrade functionality marketing.manager update.transfer2000

DescriptionEnter any text here.

Upgrade managerThe upgrade manager allows connections to be displayed and modified. Modifications are made by clicking on the respective user, upgrade or connection.

1. Right-click upgrades in the configuration area.

2. Select Show Upgrade Manager from the popup menu.The Manage Upgrades dialogue box is displayed.

3. The following panes/buttons are available:

UsersAll available users are listed here. Select one or more users in this pane and an upgrade in the Upgrades pane to add or remove them in the Users with Upgrades pane by clicking one of the following buttons: Add->, <-Remove, RemoveAll, AddAll.

UpgradesAll available upgrades are listed here. Select an upgrade in this pane and one or more users in the Users pane to add or remove them in the Users with Upgrades pane by clicking one of the following buttons: Add->, <-Remove, RemoveAll, AddAll.

Users with Upgrade: <Upgrade Name>All users attached to upgrades are displayed here. The name of the currently selected upgrade is displayed in the pane window.

marketing.manager update.transfer2000 Upgrade functionality · 31

Delete UpgradesSelect an upgrade in the Upgrades pane and click this button to delete an upgrade. Alternatively, you can select the respective upgrade in the configuration and click the Delete Upgrade button in the icon bar.

Upgrade properties1. Right-click an existing upgrade in the list below upgrades in the configuration

area.

2. The Upgrade Properties dialogue box is displayed.

3. Use the following fields or buttons to enter or modify the respective information:

Upgrade NameName of the upgrade. This field cannot be edited.

DescriptionDescription of the upgrade.

Upgrade Directory LocationPath of the upgrade directory where the update.spt script file and all additional files are stored. This field cannot be edited.

32 · Upgrade functionality marketing.manager update.transfer2000

View/Edit ScriptClick this button to open the script in Notepad where you can edit it.

ScriptHelpClick this button to open the script help file.

Attached UsersAll users attached to this upgrade are displayed in this pane.

Remove->Click this button to delete selected users in the Attached Users pane.

Adding users1. Right-click user or an existing user (in the list below upgrades) in the

configuration area.

2. The Modify User dialogue box is displayed.

4. Use the following fields or buttons to enter or modify the respective information:

UserIDName of the user.

PasswordPassword of the user.

local pathEnter the path of the marketing.manager user directory on update.transfer2000 server or use the browse button.

marketing.manager update.transfer2000 Adding users · 33

SSLW-Client VersionVersion number of the client. This information is only available for SSLW connections.

Troubleshooting

OverviewThis section gives you an overview of the error codes logged in the NT event log of servers as well as of clients.

update.transfer2000 – Server logging codes:The codes logged by the update.transfer2000 Service in the NT event log have the general format: <description> #<FACILITY><CODE>

The following table lists the possible values, descriptive text has been omitted.

The importance of a log entry is valued from 1 to 5, where 1 has the least impact on the functionality and 5 means that there are severe configuration or network problems.

Logging Code Description Importance

#Err: F88 This log entry originates from a failed attempt to get the file’s attributes during the start of a server to client transfer.

2

#Err: F89 Read error of the requested file during server to client transfer. Indicates problems with exclusive file locks.

2

#Err: F90 The file offset announced by the client for resuming an interruptedupload is is invalid. The upload will start over at Offset zero.

1

#Win32: <ErrorCode> This indicated problems at WIN32 File I/O- API level. The ErrorCode value is the WIN32 Error Code corresponding to the preceding function call that failed. Possible cases that cause these kind of log entries are wrong directory permissions or a shortage of available file handles.

3

34 · Overview marketing.manager update.transfer2000


#Offset: <OFFSET> A Socket related error occurred in the Receivefunction, this can be caused by a timeout or a reset of the virtual-circuit connection to the server, for example when a dialup-link is interrupted. Check the network environment. In most cases the WSA_ERROR_CODE does not have a meaningful value .

4

update.transfer2000 – Client error codes:The codes which appear on the update.transfer2000 client are used for diagnostics in case of transfer errors. They have the following general format:

<description>#f<FN_ID>; #w<SOCK_ERR>; #fn1:<SOURCE_FILE> #fn2:<DEST_FILE>

Where Description

FN_ID The ID of the internal function that failed

SOCK_ERR A Windows socket error code of a Winsock function call that failed.

SOURCE_FILE The file name of the source file that was being transmitted when the error occurred. During download this is the file stored on the server.

DEST_FILE The file name of the destination file that was being transmitted when the error occurred. During download this is the local file on the client.

The following table lists the possible values and descriptive text.

The importance of a log entry is on a scale from 1 to 5, where 1 has the least impact on functionality and 5 means that there are severe configuration or network problems.


#f1w<WSA_ERROR_CODE>

A socket-related error occurred in the receive function, this can be caused by a timeout or a reset of the virtual circuit connection with the server, for example when a dial-up link is interrupted. You should check the network environment. In most cases the WSA_ERROR_CODE does not have a meaningful value.

4

marketing.manager update.transfer2000 Overview · 35


#f2w<WSA_ERROR_CODE>

A socket-related error occurred in the send function. This can be caused by exactly the same reasons described above (#f1w<WSA_ERROR_CODE>).

The WSA_ERROR_CODE value can be helpful here. A list of WSA_ERROR_CODES can be found in the Appendix.

4

#f4w< WSA_ERROR_CODE>

An event could not be assigned to the communicaton socket. This can be caused by a shortage of network resources.

You should check that there are no applications running concurrently on the particular machine.

2


The socket could not be switched into blocking state.

Check WSA_ERROR_CODE.

Possible reasons are incompatibilities with the Winsock .dll files.

5


Error in the same function because of an unsuccessful call to ioctlsocket. Also caused by incompatibilities with Winsock DLLs.

4


File error during download operation.

WSA_ERROR_CODE is not used.

2

#f8 w< WSA_ERROR_CODE>

This error occurs when the local destination file cannot be opened for writing. Check in the indirectory whether the file has Read only attribute or if the correct permissions have been set in the "in" directory.


4


Occurs during upload when the local file in the "out" directory could not be opened for reading. This could happen when the file is discarded by another application during upload transfer.


3


Occurs during upload when the File I/O API call GetFileSize could not determine the size of the local file being uploaded.


3




This error is the result of a communication-failure of the underlying network.

The WSA_ERROR_CODE value is important here.

This is found in the socket dispatch routine.

2


See #f11 2


The server sent an MSG_ERROR message to indicate a communication problem. This message has a universal use, and therefore has no special meaning for the client itself.

It is recommended that you check the server’s log file for related entries.

You should make a note of the WSA_ERROR_CODE value.

2


A attempt to resume an upload has failed. Check if the existing stub of the file intended to be uploaded has been modified since the last attempt.

The WSA_ERROR_CODE value is not important here.

3

#f15< WSA_ERROR_CODE>

A file to be uploaded could not be opened locally. Check for problems relating to the "out" directory.

The WSA_ERROR_CODE value is not important here.

4

Appendix WSA_ERROR_Codes:The following is a list of possible error codes returned by the WSAGetLastError call, along with their extended explanations. Errors are listed in alphabetical order according to error macro. Some error codes defined in WINSOCK2.H are not returned by any function - these have not been listed here.

WSAEACCES

(10013)

Permission denied.

An illegal attempt was made to access a socket forbidden by access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST).


WSAEADDRINUSE

(10048)

Address already in use.

Can be used once only. Multiple use of a socket address (protocol/IP address/port) is not normally permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, a socket that has not been closed properly, or one that is still being closed. For server applications that need to bind multiple sockets to the same port number, use setsockopt (SO_REUSEADDR). Client applications do not usually need to call bind at all - connect will choose an unused port automatically. When bind is called with a wildcard address (involving ADDR_ANY), a WSAEADDRINUSE error could be delayed until the specific address is "committed." This could happen with a call to another function later, including connect, listen, WSAConnect or WSAJoinLeaf.

WSAEADDRNOTAVAIL

(10049)

Cannot assign requested address.

The requested address is not valid. Normally results from an attempt to bind to an address that is not valid for the local machine. This can also result from connect, sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote machine (e.g. address or port 0).

WSAEAFNOSUPPORT

(10047)

Address family not supported by protocol family.

Address used is incompatible with the requested protocol. All sockets are created with an associated "address family" (i.e. AF_INET for Internet Protocols) and a generic protocol type (i.e. SOCK_STREAM). This error is displayed if an incorrect protocol is explicitly requested in the socket call or if an address from the wrong family is used for a socket, e.g. in sendto.

WSAEALREADY

(10037)

Operation already in progress.

An operation was attempted on a non-blocking socket that is already carrying out an operation - i.e. calling connect a second time on a non-blocking socket that is already connecting, or cancelling an asynchronous request (WSAAsyncGetXbyY) that has already been cancelled or completed.


WSAECONNABORTED

(10053)

Software caused connection abort.

An established connection was aborted by the software on your host machine, possibly due to a data transmission timeout or protocol error.

WSAECONNREFUSED

(10061)

Connection refused.

No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host, i.e. a host with no server application running.

WSAECONNRESET

(10054)

Connection reset by peer.

An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host used a "hard close" (see setsockopt for more information on the SO_LINGER option on the remote socket.) This error may also result if a connection was interrupted due to "keep-alive" activity detecting a failure while one or more operations are in progress. Operations in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.

WSAEDESTADDRREQ

(10039)

Destination address required.

A required address was omitted from an operation on a socket. For example, this error will be returned if sendto is called with the remote address of ADDR_ANY.

WSAEFAULT

(10014)

Bad address.

The system detected an invalid pointer address while attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value, or if the buffer is too short. For instance, if an argument which is a struct sockaddr is shorter than sizeof(struct sockaddr).


WSAEHOSTDOWN

(10064)

Host is down.

A socket operation failed because the destination host was down. Networking activity on the local host has not been initiated. These conditions are more likely to be indicated by the error WSAETIMEDOUT.

WSAEHOSTUNREACH

(10065)

No route to host.

A socket operation attempted to contact an unreachable host. See WSAENETUNREACH

WSAEINPROGRESS

(10036)

Operation now in progress.

A blocking operation is currently running. Windows sockets only allow one outstanding blocking operation per task or thread and if any other function call is made (whether or not it references that or any other socket), the function fails with the WSAEINPROGRESS error.

WSAEINTR

(10004)

Interrupted function call.

A blocking operation was interrupted by a call to WSACancelBlockingCall.

WSAEINVAL

(10022)

Invalid argument.

An invalid argument was supplied (for example specifying an invalid level to the setsockopt function). In some instances, this also refers to the current state of the socket, for instance, calling accept on a socket that is not listening.

WSAEISCONN

(10056)

Socket is already connected.

A connect request was made on an already connected socket. Some implementations also display this error if sendto is called on a connected SOCK_DGRAM socket (for SOCK_STREAM sockets, the to parameter in sendto is ignored), although other implementations treat this as a legal occurrence.


WSAEMFILE

(10024)

Too many open files.

Too many open sockets. Each implementation has a maximum number of socket handles available, either globally, per process or per thread.

WSAEMSGSIZE

(10040)

Message too long.

A message sent on a datagram socket was longer than the internal message buffer or another network limit, or the buffer used to receive a datagram was smaller than the datagram itself.

WSAENETDOWN

(10050)

Network is down.

A socket operation encountered a dead network. This could indicate a serious network system failure (i.e. the protocol stack that the WinSock .dll file runs over), network interface failure, or local network failure.

WSAENETRESET

(10052)

Network dropped connection on reset.

The connection has been interrupted due to "keep alive" activity detecting a failure while the operation was in progress. This can also be displayed by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed.

WSAENETUNREACH

(10051)

Network is unreachable.

A socket operation attempted to contact an unreachable network. This usually means that the local software knows no route to reach the remote host.

WSAENOBUFS

(10055)

No buffer space available.

An operation on a socket could not be performed because the system lacked sufficient buffer space or because the waiting line was full.

WSAENOPROTOOPT

(10042)

Bad protocol option.


An unknown, invalid or unsupported option or level was specified in a getsockopt or setsockopt call.

WSAENOTCONN

(10057)

Socket is not connected.

A request to send or receive data was denied because the socket is not connected and no address was supplied when sending on a datagram socket using sendto. Any other type of operation might also display this error - for example, setsockopt setting SO_KEEPALIVE if the connection has been reset.

WSAENOTSOCK

(10038)

Socket operation on non-socket.

An operation was attempted on something that is not a socket. Either the socket handle parameter did not reference a valid socket, or for select, a member of an fd_set was not valid.

WSAEOPNOTSUPP

(10045)

Operation not supported.

The object referenced does not support the attempted operation. This occurs when a socket descriptor reaches a socket that cannot support this operation, for example trying to accept a connection on a datagram socket.

WSAEPFNOSUPPORT

(10046)

Protocol family not supported.

The protocol family has not been configured into the system or no implementation exists. Has a slightly different meaning to WSAEAFNOSUPPORT, but is interchangeable in most cases, and all Windows Sockets functions that return either of these specify WSAEAFNOSUPPORT.

WSAEPROCLIM

(10067)

Too many processes.

A Windows Sockets implementation may have a limit to the number of applications that may use it simultaneously. WSAStartup may fail with this error if the limit has been reached.

WSAEPROTONOSUPPORT

(10043)

Protocol not supported.


The requested protocol has not been configured into the system, or no implementation exists. For example, a socket call requests a SOCK_DGRAM socket, but specifies a stream protocol.

WSAEPROTOTYPE

(10041)

Protocol wrong type for socket.

A protocol specified in the socket function call does not support the semantics of the socket type requested. For example, the ARPA Internet UDP protocol cannot be specified with a socket type of SOCK_STREAM.

WSAESHUTDOWN

(10058)

Cannot send after socket shutdown.

A request to send or receive data was not allowed because the socket had already been shut down. By calling shutdown a partial socket close is requested, which is a signal that sending, receiving or both have discontinued.

WSAESOCKTNOSUPPORT

(10044)

Socket type not supported.

The support for the specified socket type does not exist in this address family. For example, the optional type SOCK_RAW might be selected in a socket call, but the implementation does not support SOCK_RAW sockets.

WSAETIMEDOUT

(10060)

Connection timed out.

A connection attempt failed because the connected party did not respond after a period of time, or established connection failed because connected host failed to respond.

WSATYPE_NOT_FOUND

(10109)

Class type not found.

The specified class was not found.

WSAEWOULDBLOCK

(10035)

Resource temporarily unavailable.

This error is returned from operations on non-blocking sockets that cannot be completed immediately, for example recv when no data is waiting to be read from the socket. It is a non-fatal error, and the operation should be retried later. It is normal for


WSAEWOULDBLOCK to be reported as the result from calling connect on a non-blocking SOCK_STREAM socket, since some time must elapse for the connection to be established.

WSAHOST_NOT_FOUND

(11001)

Host not found.

No such host is known. The name is not an official hostname or alias, or it cannot be found in the database(s) being queried. This error may also be returned for protocol and service queries, and means the specified name could not be found in the relevant database.

WSA_INVALID_HANDLE

(OS dependent)

Specified event object handle is invalid.

An application attempts to use an event object, but the specified handle is not valid.

WSA_INVALID_PARAMETER

(OS dependent)

One or more parameters are invalid.

An application used a Windows Sockets function which directly maps to a Win32 function. The Win32 function is indicating a problem with one or more parameters.

WSAINVALIDPROCTABLE

(OS dependent)

Invalid procedure table from service provider.

A service provider returned a bogus proc table to WS2_32.DLL. (Usually caused by one or more of the function pointers being NULL.)

WSAINVALIDPROVIDER

(OS dependent)

Invalid service provider version number.

A service provider returned a version number other than 2.0.

WSA_IO_INCOMPLETE

(OS dependent)

Overlapped I/O event object not in signalled state.

The application has tried to determine the status of an overlapped operation which is not yet completed. Applications that use WSAGetOverlappedResult (with the fWait flag set to false) in a polling mode to determine when an overlapped operation has completed will receive this error code until the operation is complete.


WSA_IO_PENDING

(OS dependent)

Overlapped operations will complete later.

The application has initiated an overlapped operation which cannot be completed immediately. A completion indication will be given at a later time when the operation has been completed.

WSA_NOT_ENOUGH_MEMORY

(OS dependent)

Insufficient memory available.

An application used a Windows Sockets function which directly maps to a Win32 function. The Win32 function is indicating a lack of required memory resources.

WSANOTINITIALISED

(10093)

Successful WSAStartup not yet performed.

Either the application has not called WSAStartup or WSAStartup failed. The application may be accessing a socket which the current active task does not own (i.e. is trying to share a socket between tasks), or WSACleanup has been called too many times.

WSANO_DATA

(11004)

Valid name, no data record of requested type.

The requested name is valid and was found in the database, but it does not have the correct associated data. An example of this is a hostname -> address translation attempt (using gethostbyname or WSAAsyncGetHostByName) which uses the DNS (Domain Name Server), and an MX record is returned but no A record - indicating the host itself exists, but cannot be reached directly.

WSANO_RECOVERY

(11003)

This is a non-recoverable error.

This indicates some sort of non-recoverable error during a database lookup. This may be because the database files (e.g. BSD-compatible HOSTS, SERVICES or PROTOCOLS files) could not be found, or a DNS request was returned by the server with a severe error.

WSAPROVIDERFAILEDINIT

(OS dependent)

Unable to initialise a service provider.

Either a service provider's .dll file could not be loaded (LoadLibrary failed) or the provider's WSPStartup/NSPStartup function failed.


WSASYSCALLFAILURE

(OS dependent)

System call failure.

Returned when a system call that should never fail, fails. For example, if a call to WaitForMultipleObjects fails or one of the registry functions fails trying to manipulate the protocol/namespace catalogs.

WSASYSNOTREADY

(10091)

Network subsystem is unavailable.

This error is returned by WSAStartup if the Windows Sockets implementation cannot function because the underlying system it uses to provide network services is currently unavailable. You should check the following:

· that the appropriate Windows Sockets .dll file is in the current path,

· that they are not trying to use more than one Windows Sockets implementation simultaneously. If there is more than one WINSOCK .dll file on your system, ensure the first one in the path is appropriate for the network subsystem currently loaded.

· the Windows Sockets implementation documentation to be sure all necessary components are currently installed and configured correctly.

WSATRY_AGAIN

(11002)

Non-authoritative host not found.

This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server. A retry some time later may be successful.

WSAVERNOTSUPPORTED

(10092)

WINSOCK.DLL version out of range.

The current Windows Sockets implementation does not support the Windows Sockets specification version requested by the application. Check that no old Windows Sockets .dll files are being accessed.

WSAEDISCON

(10094)

Graceful shutdown in progress.

Returned by WSARecv and WSARecvFrom to indicate that the remote party has initiated a graceful shutdown sequence.


WSA_OPERATION_ABORTED

(OS dependent)

Overlapped operation aborted.

An overlapped operation was cancelled due to the closure of the socket or the execution of the SIO_FLUSH command in WSAIoctl.


Index

A

Access monitoring 3Adding

SSLW connection 13Upgrades 27Users 31

C

ClientInstallation 4Setup 4

Client user interface 8Configuration area 9Display area 10Icon bar 9Menu bar 8

Client versionOverview 4Settings dialogue box 10

Configuration areaClient user interface 9Server user interface 24

D

Display areaClient user interface 10Server user interface 25

F

FTP connectionAdding 17

I

Icon barClient user interface 9Server user interface 24

Installation

Client 4Server 19

IP Package Encryption 2

L

LANAdding connection 16FTP connection 17

LAN connectionAdding 16

Limited Server Access 2

M

Menu barClient user interface 8Server user interface 23

N

NewFTP connection 17LAN connection 16Port-to-port connection 13SSLW connection 13Users 31

O

Overview 1

P

Port-to-port connection 13Properties

Server 25

S

Security 2Access monitoring 3IP Package Encryption 2Limited Server Access 2Transfer protocol 3update.transfer protocol 3

ServerInstallation 19Properties 25Setup 19

Server user interface 23Configuration area 24Display area 25Icon bar 24

marketing.manager update.transfer2000 Index · 49

Menu bar 23Server version

Overview 19Settings

Client 10Setup

Client 4Server 19

SSLW connectionAdding 13

T

Transfer protocol 3Troubleshooting 31

U

update.transferOverview 1

update.transfer protocol 3Upgrade functionality 27Upgrade manager 28Upgrade properties 30Upgrades

Adding 27User interface

Client 8Server 23

UsersAdding 31

50 · Index marketing.manager update.transfer2000

Transfer 2000 Eng

Documents

Transcript of Transfer 2000 Eng