Skip to main content
  • EN

ok. so there have been a lot of questions about running a workspace through the task scheduler (and the fact that it doesn't work) with running it manually.

I have tried all the solutions suggested.

Problem:

I have a workspace that logs onto an AGOL account, retrieve the data and create an excel.

I have no problem running this workspace manually when I am logged on to the server.

The issue is when I schedule this to run using a service account. I get this error:

ArcGIS Online Feature Service Reader: Connection 'Esri ArcGIS Online' does not exist. Check connection parameter and connection definitions in FME options and try again

 

Solutions I've tried:

I will literally try anything. Please help!

@tnarladni

I had this same problem. The account running the workspace needs to have access to the defined connections. It's like setting up a new user with workbench.

What I did to resolve was:

-log onto the machine with the service account

-open the desktop app [fme workbench]

-go to tools>fme options> default paths and map the named_connections 'keys' and 'data path' for the service account

@tnarladni

I had this same problem. The account running the workspace needs to have access to the defined connections. It's like setting up a new user with workbench.

What I did to resolve was:

-log onto the machine with the service account

-open the desktop app [fme workbench]

-go to tools>fme options> default paths and map the named_connections 'keys' and 'data path' for the service account

@tnarladni

Make sure you can see the connection through workbench while logged in with the service account. If you can't then it may still be a permissions issue or you can try creating a connection with the same name through workbench.

@tnarladni

I had this same problem. The account running the workspace needs to have access to the defined connections. It's like setting up a new user with workbench.

What I did to resolve was:

-log onto the machine with the service account

-open the desktop app [fme workbench]

-go to tools>fme options> default paths and map the named_connections 'keys' and 'data path' for the service account

The 'keys' and 'data path' were mapped to the public folder but when i opened the workspace, it was still complaining that the connection file is missing. The only way I got it to work was to export the connection file as me then logged on as the service account and import it. It is working now. Thanks.

I finally got it to work by exporting the web connection and importing it as the service account that will use it. So I'm guessing it is saved to the AppData folder even though the default path is to the shared location? Not sure which one it is reading, but it is working now. The export/import was the one solution I didn't try and the one that did work. :|

@tnarladni

Make sure you can see the connection through workbench while logged in with the service account. If you can't then it may still be a permissions issue or you can try creating a connection with the same name through workbench.

please post this as an answer so I can give you credit. I essentially did this with the export/import

Make sure you can see the connection through workbench while logged in with the service account. If you can't then it may still be a permissions issue or you can try creating a connection with the same name through workbench.

Reply


Community Stats

30,110
Posts
114,302
Replies
37,745
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.