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.

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

[Imported] MS SQL Server Linked Server to ClearSCADA 'Access denied'

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.

Janeway Janeway

[Imported] MS SQL Server Linked Server to ClearSCADA 'Access denied'

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: florian, originally posted: 2018-10-25 16:18:27 Id:238
This is a re-posting from the obsoleted (October 2018) "Schneider Electric Telemetry & SCADA" forum.


**_Hey all,_**

**_I'm trying to use an MS SQL Server to do some reporting (using MS SSRS), however when I'm trying to query the linked server for my 2015R1 (or 2014R1.1) ClearSCADA servers I'm getting an Access denied error as such:_**

_Msg 7399, Level 16, State 1, Line 1_

**_The OLE DB provider "ClearSCADA.OleDBProv" for linked server "CLEARSCADA" reported an error. Access denied.
Msg 7350, Level 16, State 2, Line 1_**
**_Cannot get the column information from OLE DB provider "ClearSCADA.OleDBProv" for linked server "CLEARSCADA"._**

**_I'm passing in a valid username / password, the connection all works._**
**_The query I'm trying is:_**

_SELECT TOP(10) FullName_

**_Has anyone seen this before (and resolved it)?_**
**_I'm using SQL Server 2016 CTP2, so it's possible it's a bug somewhere in this... although it would surprise me a bit._**


Got any DBClient logs? Might need to enable them as only DBClientNamed are enabled by default, not DBClient.

I do remember people in the past reporting issues with MSSQL and it assuming a username rather than using what was configured (it is possible that the username it was trying to use was the same as the connection name for some reason, that rings a bell). I can't remember the specific details but the DBClient logging should show which user the connection is trying to use and might explain things.


Thanks for the suggestion. I contacted technical support and they provided an updated article.