SOLVED

Error related to the newest Acces 2016 update

Copper Contributor

Hello experts,


I hope someone can help me with the following problem:

In our company we use PowerBI. We acces our data shown in PowerBI using Access. Since the new Access 2016 update, the following error message appears when trying to synchronise Power BI Online:


Error: -2147467259
Errormessage: Could not use 'Minas.accdb'; file already in use.
DM_ErrorDetailNameCode_UnderlyingHResult: -2147467259
Microsoft.Data.Mashup.ValueError.Detail: Minas.accdb
Microsoft.Data.Mashup.ValueError.Reason: DataFormat.Error
URI cluster: WABI-WEST-EUROPE-B-PRIMARY-redirect.analysis.windows.net
Time: 2021-12-15 09:55:07Z


We use the following:

- Windows server 2012 R2 Standard

- On-premises data gateway (3000.106.11 (November 2021))

- Microsoft Access database engine 2016 (English)


Our problem is that the on-premises data gateway locks the Acces-files. To unlock those files, the service needs to be stopped, then all the gateway processes need to be stopped on the server and then the service needs to start again. After the gateway unlocks the files, we can acces the files again. Unfortunately, if we synchronise again online, the gateway locks the files again and shows the errormessage given above.


I've done some researche and the problem has to be somewhere around the new Access 2016 update.

Cause: The update on 14-12-2021 with the following names:

KB4504745

KB5002033

KB5002099


The temporary solution we used to fix this problem manually:

Reinstalling Microsoft Access database engine 2016 (English) and holding off the updates.

This is inconvinient and I hope someone has a great idea on how to fix this problem.


Can anyone help me with this problem? If there is any extra information needed to help me with this, please contact me.


Kind regards,

Jennifer

1 Reply
best response confirmed by JenniferDMS (Copper Contributor)
Solution

@JenniferDMS 

 

More information here.

 

Note this additional comment recently added.

Officially From Microsoft

We have an update as of 2021-12-16 at 19:00, a fix has started to roll out!

New builds with the fix have started rolling out for some channels:

 

Current Channel: 16.13801.21092
Current Channel (Preview): 16.0.14729.20170
Semi-Annual Channel (Preview): 16.0.14326.20272
Semi-Annual Channel: 16.0.13801.21092
Semi-Annual Channel (Extended): 16.0.13127.21846
Shane Groff - Access Dev Team

So update your systems and things should be back to normal.

1 best response

Accepted Solutions
best response confirmed by JenniferDMS (Copper Contributor)
Solution

@JenniferDMS 

 

More information here.

 

Note this additional comment recently added.

Officially From Microsoft

We have an update as of 2021-12-16 at 19:00, a fix has started to roll out!

New builds with the fix have started rolling out for some channels:

 

Current Channel: 16.13801.21092
Current Channel (Preview): 16.0.14729.20170
Semi-Annual Channel (Preview): 16.0.14326.20272
Semi-Annual Channel: 16.0.13801.21092
Semi-Annual Channel (Extended): 16.0.13127.21846
Shane Groff - Access Dev Team

So update your systems and things should be back to normal.

View solution in original post