First check whether you have access with Windows Explorer on the
computer concerned and whether your network is working properly. If
the target computer cannot be reached via the Windows Explorer,
continue with 'Possible cause 2' described below.
This error message can have different causes. In the following
we explain three solutions for clearing the problem based on three
Possible cause 1: Unintentional start of the OS Runtime on
OS Runtime was activated once unintentionally on the ES (not
simulating OS RT). Consequently the databases (e.g.
OS(1)ALG.ldf or OS(1)ALG.mdf) were created on the ES.
With the subsequent download these database files from the ES will
attempt to overwrite the files that are on the server. However, the
files on the server are "occupied" by the SQL server. This then can
lead to the download being aborted with an error message.
- Delete these files from your project directory on the ES (path:
- Databases other than OS(1)ALG.mdf might also be occupied by the
SQL server after terminating, WinCC Explorer. Therefore it is
better to user the SQL tool on the server to check the database
connections and if necessary, detach them. This is the preferable
Possible cause 2: If being used, HOSTS or LMHOSTS
On all computers, look in the path
C:\WINNT\system32\drivers\etc and check whether both the
lmhosts and hosts files have the correct parameters.
When Windows is installed, these two files are created
"hosts" and "lmhosts.sam". The "hosts" file contains all the
entries for the "localhost". You must enter all the computer
names and associated IP addresses, even the local addresses,
in this file. The
"lmhosts.sam" file is a sample file. Copy this into a file
and insert all computer
names with the associated IP addresses, even the local
addresses, into this file.
Add to the Hosts and Lmhosts files the IP address
and the computer name of each computer (including the local
computer) linked to the WinCC network.
Enter the IP address and computer name separated by a TAB
(or blank) (Fig. 1). In the WINS address properties of the
TCP/IP protocol, activate the LMHOSTS query so that the Hosts list
can be loaded by the local PC. You should not import LMHOSTS. You
must remove superfluous network protocols.
Fig. 1: Hosts file (e.g. 192.168.1.75 OSServer1)
Many plant networks are located in domains and use a DNS server
for name resolution. In this case you don't have to process the
Hosts or Lmhosts file, because name resolution is done via DNS
starting with Microsoft Windows 2000. Then you must make the
entries in the DNS name resolution in the DNS server.
Entering the computers in the Host file is
problematic when using a DNS and DHCP server, because if there are
changes to the IP addresses, you have to change the Hosts files
manually on each of the computer, whereas the DNS server updates
the entries automatically. If you forget to do this, problems might
arise in communications, because the Hosts file (loaded into the
cache) is always queried first for name resolution.
Possible cause 3: Write-protected file
Check your ES project for files that might be write-protected.
The write-protection helps to load the file onto the server for the
first time without any problems. However, when the data is reloaded
onto the server, this file cannot be overwritten and the download
is aborted with an error message.
Remove the write-protection from your files in your ES project and
on the OS server.
Unpacked project data from the CD is always write-protected.
More possible sources of error:
- Incorrect file or release authorizations
- Incorrect configuration of the server path in the ES
- Network problems on the OSM/Hub
After compilation of one of the above-mentioned
changes reboot your ES computer. If possible, it is also
recommended to reboot the server too.
Download, Load, Transfer