Skip to main content
Solved

Workbench fails when run from Flow Apps - Runs fine with "Run Workspace"

  • December 17, 2024
  • 3 replies
  • 43 views

sam_appleton
Contributor
Forum|alt.badge.img+7

Hi,

When I run a workspace via an App I get the following error:

Microsoft Azure SQL Database Non-Spatial Writer: A suitable Microsoft SQL Server OLE Driver is not found. Install Microsoft OLE DB Driver for SQL Server from http://www.microsoft.com/en-ca/download/details.aspx?id=56730

 

I can see from earlier on in the logs that it failed to connect :

Microsoft Azure SQL Database Non-Spatial Writer: Failed to connect using Microsoft OLE DB Driver 19 for SQL Server. Provider error ''.

 

When I run the same workspace from “Run workspace” it connects and runs fine:

Microsoft Azure SQL Database Non-Spatial Writer: Trying to connect using Microsoft OLE DB Driver 19 for SQL Server…

Microsoft Azure SQL Database Non-Spatial Writer: Starting execution of BEGIN_SQL commands

 

I tried deleting the app and creating it again but that didn’t seem to work.

 

TIA

Best answer by sam_appleton

Hi ​@virtualcitymatt,

The original server app and dependencies were imported via project file. I manually re-published the workbench and re-created the server app which looks to have solved the issue

View original
Did this help you find an answer to your question?

3 replies

virtualcitymatt
Celebrity
Forum|alt.badge.img+34

Could it be somehow related to the database connection?

I wonder if the connection being used is the same by the app as when you run the workspace. For example does the user/token running the app have permission to use the connection deified in FME Server?

What kind of authentication are you using on the database connection?


sam_appleton
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • December 19, 2024

Hi ​@virtualcitymatt,

I’m using a database connection and I can see that the server app is trying to reference the same  connection. I can see from the warnings that user/ID/Server might be empty: 

 

Is that what the logs are showing?


sam_appleton
Contributor
Forum|alt.badge.img+7
  • Author
  • Contributor
  • Best Answer
  • December 19, 2024

Hi ​@virtualcitymatt,

The original server app and dependencies were imported via project file. I manually re-published the workbench and re-created the server app which looks to have solved the issue


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings