Skip to main content
To homepage To homepage

We are having issues running source objects when source is CData BigQuery connector.

Execution of objects run fine when executed individually with Deploy and Execute. When the objects are added to an execution package, the execution package runs fine when executed manually. But when the package is run on a schedule, the package just “hangs” and never finish the job. This prevents next running packages from executing, until we kill the process.

When we look at the running processes on the machine, it seems like the Timextender package is running as a process. But if we look at the ongoing execution processes in SQL Server, nothing is running.

The Event Viewer reports issues with “The application-specific permission settings do not grant Local Activation permission for the COM Server application” at the same time the process started.

How can we fix this issue and ensure BigQuery objects can run as part of an execution package?

Hi @sten.lomme 
 
When you use OAuth a file gets generated when you click Authorize OAuth.
By default this file is stored in a folder starting with %APPDATA%. This will default to the user doing this call and the following path C:\Users\<current user>\AppData\Roaming.

So when the scheduler service attempts to start an exectuion it is looking in the folder for its user account and find no file as it was created for another user account.

The solution to this is to specify a specific folder in the OAuth settings location field for example C:\OAuth\BigQyuery Data Provider\OAuthSettings.txt.

If you have set up multiple environments, are using the LTS (Long Term Support) release and uses a Business Unit, you should make sure it also points to a specific folder or the same issue will happen.

Reply


Terms and ConditionsCookie settings