Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Close
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
84248members
353348posts

[Imported] IEC60870-104 fails with error 80004005

EcoStruxure Geo SCADA Expert Forum

Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.

Solved
sbeadle
Janeway Janeway
Janeway
0 Likes
1
611

[Imported] IEC60870-104 fails with error 80004005

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: alexs, originally posted: 2019-05-31 04:42:16 Id:441
After updating ClearSCADA 2015 to ClearSCADA 2017 I faced with problem in IEC60870-104 driver. The driver spontaneously fails with error "80004005 - Unspecified error". Has anyone faced this problem?


Logging started at 30-MAY-2019 01:30:41.188 (UTC)
File : C:\\ProgramData\\Schneider Electric\\ClearSCADA\\Logs\\Drivers\\DriverIEC60870_001.log
System : Microsoft Windows Server 2012 R2 Standard Edition, 64-bit (6.3.9600)
CPU : 1 x Intel Unknown Family 6, Model 79, Stepping 1
Intel(R) Xeon(R) CPU E5-2620 v4 [at] 2.10GHz
ClearSCADA Core : Build 6.78.7021.1 (Release)
Local time zone : UTC+05:00 (no DST)
Computer : SVD-AD01-SCDA01
Driver : IEC60870
Started : 30-MAY-2019 01:30:41.188
Uptime : 0 00:00:00.000

Logging options:
APP : Application
ERR : Errors
OBJ : Database Objects
CHN : Channels
SET : Outstation Sets
OS : Outstations
PNT : Points
SCN : Scanners
REQ : Requests (Actions)
DAT : Point Updates (Data)
APL : IEC60870 Application Layer
Threads:
5444 : Main
-------------------------------------------------------------------------------
Registry settings:
HKEY_LOCAL_MACHINE\\Drivers\\ErrorMsgBox = False
HKEY_LOCAL_MACHINE\\Drivers\\HeartbeatEavesdrop = False
HKEY_LOCAL_MACHINE\\Drivers\\ServerPollInterval = 5000
HKEY_LOCAL_MACHINE\\Drivers\\AsyncPointRequests = True
HKEY_LOCAL_MACHINE\\Drivers\\SecondaryDataMaxPointUpdates = 250
HKEY_LOCAL_MACHINE\\Drivers\\MaxPendingAsyncPointRequests = 300
HKEY_LOCAL_MACHINE\\Drivers\\ValueMapScanningInterval = 1000
HKEY_LOCAL_MACHINE\\Drivers\\SelectBestChannel = False
HKEY_LOCAL_MACHINE\\Drivers\\BreakDuration = 100
HKEY_LOCAL_MACHINE\\Drivers\\PostHangupDelay = 0
HKEY_LOCAL_MACHINE\\Drivers\\TimeJumpLimit = 50
HKEY_LOCAL_MACHINE\\Drivers\\RequestTimeout = 600
HKEY_LOCAL_MACHINE\\Drivers\\RequestTimeoutExtn = 300
HKEY_LOCAL_MACHINE\\Drivers\\ScannerCommandTimeout = 30
HKEY_LOCAL_MACHINE\\Drivers\\ScannerRequestTimeout = 180
HKEY_LOCAL_MACHINE\\Drivers\\EavesdropPSTNTimeout = 30
HKEY_LOCAL_MACHINE\\Drivers\\RxFailureLimit = 10
HKEY_LOCAL_MACHINE\\Drivers\\TxFailureLimit = 10
HKEY_LOCAL_MACHINE\\Drivers\\RetryAssignInterval = 30
HKEY_LOCAL_MACHINE\\Drivers\\RxTimeoutLimit = 20
HKEY_LOCAL_MACHINE\\Drivers\\TxTimeoutLimit = 20
HKEY_LOCAL_MACHINE\\Drivers\\GracefulSocketCloseTimeout = 1000
HKEY_LOCAL_MACHINE\\Drivers\\AllowInboundConFromAllOS = False
HKEY_LOCAL_MACHINE\\Drivers\\DirectOnDemandRetryPeriod = 120
HKEY_LOCAL_MACHINE\\Drivers\\ComtrolFreeportDelay = 250
HKEY_LOCAL_MACHINE\\Drivers\\MaxBatchWriteSize = 1000
HKEY_LOCAL_MACHINE\\Drivers\\ListenPortRangeStart = 0
HKEY_LOCAL_MACHINE\\Drivers\\ListenPortRangeEnd = 0
HKEY_LOCAL_MACHINE\\DriverIEC60870\\LogEnableTelnet = False
30-MAY-2019 01:30:41.204 [Data Cache] Started new thread (ID=9152)
HKEY_LOCAL_MACHINE\\DriverIEC60870\\24BitTimeStampMaximumForwardOffset = 1
30-MAY-2019 01:30:41.204 [Main] Database classes (37)...
Name |Type
------------------------+----------------
CProfile |Resource
CProfileFloat |Resource
CProfileULong |Resource
CProfileLong |Resource
CAdvBITValueMap |Resource
CAdvBYTEValueMap |Resource
CAdvWORDValueMap |Resource
CAdvDINTValueMap |Resource
CAdvUDINTValueMap |Resource
CAdvREALValueMap |Resource
CAdvDOUBLEValueMap |Resource
CAdvStringValueMap |Resource
CDynacardStore |Resource
CAdvOutstation |Modem
CIEC60870ChannelDirect |Channel
CIEC60870ChannelPSTN |Channel
CIEC60870LinkDirect |Outstation
CIEC60870LinkShared |Outstation
CIEC60870OSLinkLayer |Broadcast Outstation
CIEC60870OSDirect |Outstation
CIEC60870ASDU |Outstation
CIEC60870OSPSTN |Outstation
CIEC60870OSShared |Outstation
CIEC60870LinkSlDirect |Outstation
CIEC60870SlOSLink |Broadcast Outstation
CIEC60870SlOSDirect |Slave Outstation
CIEC60870SlASDU |Outstation
CIEC60870AnalogIn |Point
CIEC60870AnalogOut |Point
CIEC60870DigitalIn |Point
CIEC60870DigitalOut |Point
CIEC60870SetDirect |Set
CIEC60870SetSwitched |Set
CIEC60870SetPSTN |Set
CIEC60870SetShared |Set
CIEC60870SlChanDirect |Slave Channel
CIEC60870SlSetDirect |Slave Set
------------------------+----------------
30-MAY-2019 01:30:41.204 [Scan Value Map] Started new thread (ID=9088)
30-MAY-2019 01:30:41.204 [Main] Error at line 408, file Class.cpp
80004005 - Unspecified error
Advise driver failed
30-MAY-2019 01:30:41.204 [Data Cache] Thread terminated (ID=9152)
30-MAY-2019 01:30:41.204 [Scan Value Map] Thread terminated (ID=9088)
30-MAY-2019 01:30:41.204 [Main] Driver stopped after 0 00:00:00.016
-------------------------------------------------------------------------------


Accepted Solutions
sbeadle
Janeway Janeway
Janeway
0 Likes
0
610

Re: [Imported] IEC60870-104 fails with error 80004005

>>Responses imported from previous forum


Reply From User: JesseChamberlain, posted: 2019-06-03 03:31:58
Any reason you've upgraded to CS2017 instead of CS2017R3? I'd suggest upgrading to the latest Update of CS2017 if not the latest Update of CS2017R3 as a first step.

I'd also recommend restarting the server, and re-saving the value maps and slave devices.

Essentially the advise link between the driver and DBServer has failed, apparently when starting to scan a value map. Please get in touch with local CS Support and give them driver, DB and DBSnapshot logs as a starting point. We will probably need to enable additional logging classes.


Reply From User: andrewscott, posted: 2019-06-03 09:07:35
This error is not related to value maps.

To find out why the advise has failed would need the matching DB log showing the **AdviseDriver()** request. The **DBDRQ** logging option needs to be enabled. However, I would suspect that the issue is related to the IEC 60870 driver being invalid (e.g. not licensed), check the "General \\ Modules" page in the server status tool.

See Answer In Context

1 Reply 1
sbeadle
Janeway Janeway
Janeway
0 Likes
0
611

Re: [Imported] IEC60870-104 fails with error 80004005

>>Responses imported from previous forum


Reply From User: JesseChamberlain, posted: 2019-06-03 03:31:58
Any reason you've upgraded to CS2017 instead of CS2017R3? I'd suggest upgrading to the latest Update of CS2017 if not the latest Update of CS2017R3 as a first step.

I'd also recommend restarting the server, and re-saving the value maps and slave devices.

Essentially the advise link between the driver and DBServer has failed, apparently when starting to scan a value map. Please get in touch with local CS Support and give them driver, DB and DBSnapshot logs as a starting point. We will probably need to enable additional logging classes.


Reply From User: andrewscott, posted: 2019-06-03 09:07:35
This error is not related to value maps.

To find out why the advise has failed would need the matching DB log showing the **AdviseDriver()** request. The **DBDRQ** logging option needs to be enabled. However, I would suspect that the issue is related to the IEC 60870 driver being invalid (e.g. not licensed), check the "General \\ Modules" page in the server status tool.