Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

WinCCOLEDBProvider throws exception E_FAIL(0x80004005)

Created by: anton.narbut at: 5/11/2017 2:32 PM (5 Replies)

Rating (1)

Thanks 2

6 Entries

5/11/2017 2:32 PM	Rate (0)
anton.narbut Experienced Member Joined: 1/18/2017 Last visit: 11/14/2024 Posts: 54 Rating: (1)	Hello all! I am trying to access alarm logging archives via WinCCOLEDBProvider (same as appCoPack) from C#.NET application. Client machine has WinCC 7.0 installed, so there's no need for Connectivity Pack. Machines I'm trying to access are as following 1. WinCC 7.0 - success 2. WinCC 7.2 - success 3. WinCC 7.0 - fail, throws exception 4. WinCC 7.0 SP3 Upd 6 - fail, throws exception 5. WinCC 7.0 SP3 Upd 6 - fail, throws exception The exception message is: 'WinCCOLEDBProvider.1' failed with no error message available, result code: E_FAIL(0x80004005). When accessing alarm logging, there's no need to specify any credentials (username and password), WinCCOLEDBProvider handles the connection itself. If it's not access rights problem, then what is it?

Suggestion To thank Quote Answer

6/15/2017 9:42 AM	Rate (0)
anton.narbut Experienced Member Joined: 1/18/2017 Last visit: 11/14/2024 Posts: 54 Rating: (1)	I think I may have found a solution. Request from from client machine (e.g. .NET code) needs to be executed with user credentials that actually exist on server/workstation with WINCC archive database and have administrator privleges. In this case both alarm logs and history data can be accessed remotely via WINCCOLEDBProvider without any issues.

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users moh_gobran2010

9/12/2017 11:16 AM	Rate (0)
123bb Posts: 4 Rating: (0)	anton.narbut I think I may have found a solution. Request from from client machine (e.g. .NET code) needs to be executed with user credentials that actually exist on server/workstation with WINCC archive database and have administrator privleges. In this case both alarm logs and history data can be accessed remotely via WINCCOLEDBProvider without any issues. Hi ，Can you share how you solved it, I was troubled by this problem for more than a week
123bb Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

9/28/2017 4:40 PM	Rate (1)
The Body Gold Member Joined: 5/13/2008 Last visit: 12/18/2019 Posts: 836 Rating: (71)	Hi 123bb, note that connecting to alarms needs to be modofoed since WinCC V7.3: up to WinCC V7.2: CommandString = "ALARMVIEW:Select * From AlgViewEXEnu WHERE MsgNr = 1" since WinCC V7.3: CommandString = "ALARMVIEWEX:Select * From AlgViewEXEnu WHERE MsgNr = 1" Find also a good example there: Exporting Archive Data with the Aid of the SIMATIC WinCC/Connectivity Pack (OLE DB Provider)
	mfG / Best regards Roland
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users anton.narbut

11/23/2017 10:21 AM	Rate (0)
anton.narbut Experienced Member Joined: 1/18/2017 Last visit: 11/14/2024 Posts: 54 Rating: (1)	123bb anton.narbut I think I may have found a solution. Request from from client machine (e.g. .NET code) needs to be executed with user credentials that actually exist on server/workstation with WINCC archive database and have administrator privleges. In this case both alarm logs and history data can be accessed remotely via WINCCOLEDBProvider without any issues. Hi ，Can you share how you solved it, I was troubled by this problem for more than a week On the client machine I created the user with the same name and password as on the WINCC machine. I run my .NET app from this user account.

Suggestion To thank Quote Answer

2/4/2021 6:15 AM	Rate (0)
Pavlen Member Joined: 6/1/2018 Last visit: 10/28/2022 Posts: 4 Rating: (0)	Hi We're using the ALARMVIEWEX command to extract alarms via OpenPCS7 on a PS script and receive: "'WinCCOLEDBProvider.1' failed with no error message available, result code: E_FAIL(0x80004005)." The machines are on a domain and user accounts used on the OS server and OpenPCS7 server are the same. We're running WinCC v7.4+SP1+Upd10
	Last edited by: Pavlen at: 02/04/2021 06:15:57
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

Follow us on