Skip to main content
  • EN

Hi!

 

I´m having problems getting a scheduled task to run with a service account. I get the following error: 

2020-12-04 10:33:51|  0.7| 0.0|INFORM|Microsoft SQL Server Spatial Reader: Opening `omnia_' for read operation
 
2020-12-04 10:33:51|  0.7| 0.0|INFORM|Microsoft SQL Server Spatial Reader: Trying to connect using Microsoft OLE DB Driver for SQL Server...
 
2020-12-04 10:33:52|  1.0| 0.3|WARN |Microsoft SQL Server Spatial Reader: Failed to connect using Microsoft OLE DB Driver for SQL Server. Provider error '(-2146824582) Det gick inte att hitta den angivna providern. Den kanske inte Ã¤r ordentligt installerad.'. Connection string 'Provider=MSOLEDBSQL;DataTypeCompatibility=80;Data Source=;Initial Catalog=omnia_;User ID=;Password=********'
 
2020-12-04 10:33:52|  1.0| 0.0|INFORM|Microsoft SQL Server Spatial Reader: Trying to connect using SQL Server 2012 Native Client...
 
2020-12-04 10:33:52|  1.0| 0.0|WARN |Microsoft SQL Server Spatial Reader: Failed to connect using SQL Server 2012 Native Client. Provider error '(-2147217843) Invalid authorization specification'. Connection string 'Provider=SQLNCLI11;DataTypeCompatibility=80;Data Source=;Initial Catalog=omnia_;User ID=;Password=********'
 
2020-12-04 10:33:52|  1.0| 0.0|ERROR |Failed to open reader

I have tried some measures such as making the connection public, logging in with the service account and starting FME. It works if i use a regular account (the account that created the workspace)

 

What seems to be the resolution to this issue?

Hi @eriblan​ 

Thank you for your question, I would recommend checking out this article, there a few possible reasons for Provider error '(-2147217843) to appear. Let me know if this was helpful.

Regards,

Daragh

Hi @eriblan​,

I've come across the same issue.

In our instance the service account doesn't have the permissions that your regular account has. This is essentially what's mentioned in the article from @daraghatsafe​'s post.

 

To solve our issue, we weren't able to provide the necessary credentials to our service account, therefore scheduled tasks had to be executed as a specific user.

Similar had to be done with our FME Server system services. (https://docs.safe.com/fme/html/FME_Server_Documentation/AdminGuide/Running_System_Services_Under_Different_Accounts.htm)

 

Hope this helps.

Reply


Community Stats

30,019
Posts
114,002
Replies
37,640
Members
Terms & ConditionsCookie settings