197
Faults
28.2.7 Portal Transfer Fault messages
Portal Transfer Fault messages
Error code Message Possible cause/remedy
101 The server address could
not be resolved.
The access type was not congured. An
alternative DNS server is required. The wrong
server was entered. The network connection
was disconnected and could not be reestab-
lished.
102 Cannot open socket. Possible causes: Unknown. If this error contin-
ues to occur, contact our technical support.
103 Cannot connect to the
socket.
Possible causes: The connection is blocked by
a rewall or a router. The wrong server was
entered. The server is ofine.
104 and 106 Connection error This can occasionally happen with GPRS con-
nections. Try it again. The network cable has
a loose connection. There are problems with
your Internet connection.
220 Authentication failure
(portal)
The portal registration was done incorrectly.
The portal was not congured for HTTP
transfers. The wrong server was entered.
222 Connection to the server,
but not response to re-
quest
Check the portal server entered.
This can occasionally happen with GPRS con-
nections. Try it again.
Other General errors There is detailed description of this error.
If this error continues to occur, contact our
technical support.
.
28.2.8 Fault messages Feed-in Management
These fault messages are displayed on the LCD display.
The percentage symbol blinks and the corresponding error code is displayed.
Fault messages
Feed-in Management
Error code Possible cause/remedy
1 Undened status for the PM+ interface or an invalid channel setting
for the active and reactive power management.
=> Check the wiring and conguration.
2 Communication error with the I/O Box
=> Check the wiring and the power supply for the I/O Box.
=> Check the interface selected under Conguration | Special Func-
tions | Feed-in Management | Prole.