SQL Server Job Agent - The workgroup file is missing

Question

SQL Server Job Agent - The workgroup file is missing

erics44

SSCertifiable

Points: 6311
More actions
November 5, 2021 at 1:33 pm

#3948330

Hi
firstly im sorry if this is in the wrong place, i couldnt find a ssis forum.
I have been working with a mariadb, trying to get the data into sql server. A very long way around it maybe but i found one solution to create a linked table in access and then import the data into ssms using ssis. MariaDB through Access to SQL server by SSIS.
This runs fine from visula studio and from an SSIS catalog.
How ever if i run the package in a job in the sql server agent i get an error.
The first error seems to be -
Source "Microsoft Access Database Engine". Description "Cannot start your application. The workgroup information file is missing or opened exclusively by another user".
Does anyone have any ideas?
Thanks in advance

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Steve Jones - SSC Editor SSC Guru Points: 736478 More actions · Answer 1

I don't know specifically, but often this is a pathing/security issue. What runs from the VS or catalog under your account or the service account for SQL Server is different than the SQL Agent account.

Michael L John One Orange Chip Points: 27060 More actions · Answer 2

erics44 wrote:

Hi
firstly im sorry if this is in the wrong place, i couldnt find a ssis forum.
I have been working with a mariadb, trying to get the data into sql server. A very long way around it maybe but i found one solution to create a linked table in access and then import the data into ssms using ssis. MariaDB through Access to SQL server by SSIS.
This runs fine from visula studio and from an SSIS catalog.
How ever if i run the package in a job in the sql server agent i get an error.
The first error seems to be -
Source "Microsoft Access Database Engine". Description "Cannot start your application. The workgroup information file is missing or opened exclusively by another user".
Does anyone have any ideas?
Thanks in advance

Think through this. You are running this on your PC, which is where Visual Studio and Access is installed. It works fine.

You then create the SSIS package on your SQL Server, and attempt to run this from a SQL Job. The error indicates that a portion of Access is missing.

So, either the parts and pieces of Access that are needed to get this package to run are missing, or, like Steve said, on your desktop the parts and pieces for Access are in C:\SomeFolder and on the server they are in C:\SomeDifferentFolder.

Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/

erics44 SSCertifiable Points: 6311 More actions · Answer 3

Hi

Thanks for the replies

I can run the package from a catalog on the server so I think the path is correct I the package for the server.

There does sound like there's a security issue or there is something missing in access on the server for it to run in a job.

Just not sure what.

I'll keep Googling.

Thanks again

Phil Parkin SSC Guru Points: 246985 More actions · Answer 4

erics44 wrote:

Hi
Thanks for the replies
I can run the package from a catalog on the server so I think the path is correct I the package for the server.
There does sound like there's a security issue or there is something missing in access on the server for it to run in a job.
Just not sure what.
I'll keep Googling.
Thanks again

When you execute a package from the catalog (right-click/execute) it runs under your credentials, whereas the SQL Agent job is running under its own credentials. This is therefore almost certainly a security issue. The SQL Agent user does not have the necessary rights.

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel