[ISS Support Case] Error Calling SPROC from Python
Last updated: October 17th, 2025Description
Experiencing an issue calling SPROC. Received information for programmatically loading data to Temp table then to Historian table. Having issue firing SPROC from a python application. Error message ProgrammingError: ('42000', '[42000] [Microsoft][ODBC SQL Server Driver][SQL Server]The requested operation could not be performed because OLE DB provider "INSQL" for linked server "INSQL" does not support the required transaction interface. (7390) (SQLExecDirectW)') - loads in temp table no issue - calling SPROC from python gets error Using PY notebook Remote system interfacing with Historian Query works from SSMS - not tested locally - not tested any other SPROC
- Author: Kevin Modlin
- Published: October 17th, 2025
Details:
Product: Historian |
Version: 2020 R2 |
Solution: [Solution is visible below when you're logged in and have a current subscription] |
Date Created: | 07/28/2022 |
Case: | 82127 |
Recommended articles
[ISS Support Case] Historian loses connection after shutting down
If the historian is shut down and disabled then re-enabled it doesn't connect to tags that haven't changed. Reboot re-establishes connection.
Read More[ISS Support Case] Trying to access old history blocks
They have a very old system they're trying to open a trend or see the data, but they don't see a trend program and can't figure out how to open the file. They believe they have the data, but it's running in demo mode and won't show data. This is an offline PC and they want to avoid putting it online, so we can't do a screen share.
Read More[ISS Support Case] Trend SQL Login Failure
Client reached out due to receiving time out error message when logging into SQL to View Trends remotely on Development node.
Read More[ISS Support Case] Wanting to pull 9 months of historized data
-Customer is wanting Historized data from the last 9 months in a .CSV file. Or in SQL. and wants to know the best practices.
Read More