Richten Sie die Microsoft Access Steckverbinder
Ob eine Access-Verbindung funktioniert, hängt von zwei Faktoren ab: der Datenbank-Engine auf dem Rechner des Agenten und einem Dateipfad, den der Agent öffnen kann. Beides wird auf dieser Seite behandelt.
Was am Ende dabei herauskommt
Eine Microsoft Access-Verbindung in Datenagenten das testet VerbundenDer Agent ist bereit für Excel, Google Sheets, einen KI-Assistenten oder die REST-API. .accdb oder .mdb Die Datei befindet sich an ihrem ursprünglichen Speicherort; es wird nichts kopiert oder konvertiert.
Was der Agent benötigt
Ein Windows-Computer, auf dem der Agent ausgeführt wird
Access-Dateien können nur unter Windows gelesen werden. Falls der Agent noch nicht installiert ist, folgen Sie den Anweisungen. Installieren Sie den Agenten unter Windows Erste.
Die 64-Bit-Access-Datenbank-Engine
Microsofts kostenlose Access Database Engine 2016 Redistributable64-Bit, auf demselben Computer. Das Portal prüft dies, sobald Sie Microsoft Access auswählen, und zeigt es an. Laden Sie die Engine herunter und erneut prüfen buttons if it is missing. It cannot go on a computer that has 32-bit Office; if yours does, run the Agent on a different computer.
Ein Pfad, den der Agentendienst öffnen kann
Der Agent läuft als Windows-Dienst, nicht als Benutzer. Ein lokaler Ordner oder ein \\server\share Pfad funktioniert; ein zugeordneter Laufwerksbuchstabe wie z. B. S: does not. If the share only lets in named users, you store a sign-in for it on the connector. Details unten.
Installieren Sie die Datenbank-Engine
The engine is required even when Microsoft Access or Office is already installed. Office installed through Click-to-Run registers its engine for Office alone, so the Agent cannot use it. If the Agent’s computer has 32-bit Office, do not install anything on it: read If the installer stops with a message about 32-bit Office Erste.
-
Laden Sie das 64-Bit-Installationsprogramm herunter.
Öffnen Microsoft Access Database Engine 2016 Redistributable on Microsoft’s site, on the Agent’s computer if you can. The page shows a Select language drop-down (leave it on English) and a red Herunterladen button. Click Herunterladen.
A box titled Choose the download you want opens with two files and a tick box beside each. Tick nur accessdatabaseengine_X64.exe. The other one, accessdatabaseengine.exe with no X64, is the 32-bit file and will not work with the Agent, even on a computer with 32-bit Office. Then click the Herunterladen button in that box.
Edge and Chrome show the download at the top right of the browser window; it lands in your Downloads folder as accessdatabaseengine_X64.exe. If you clicked Download without ticking anything, or you see a file called just accessdatabaseengine.exe, you probably got the 32-bit file: delete it and do this step again.
-
Führen Sie es auf dem Computer des Agenten aus.
Double-click the downloaded file. If Windows asks Do you want to allow this app to make changes to your device?, klicken Ja. Then click Weiter, tick the licence box and click Weiter again, click Installierenund klicken Sie OK oder Beenden when it says the installation is complete.
If instead it stops with a message that starts You cannot install the 64-bit version of Microsoft Access Database Engine 2016 because you currently have 32-bit Office products installed, klicken OK to close it and delete the file you downloaded. This computer cannot run the Access connector: the Agent has to go on a computer without 32-bit Office. Follow the steps below. Do not try to force the installer through.
-
Klicken Sie im Portal auf „Erneut prüfen“.
Zurück im Verbindungsformular klicken Sie erneut prüfenDas Banner färbt sich grün und zeigt den Namen des gefundenen Motors an, zum Beispiel Microsoft.ACE.OLEDB.16.0Der Verbindungstest hat letztendlich das letzte Wort, also fahren Sie mit dem Dateipfad fort.
If the banner stays grey and says Die Access-Datenbank-Engine konnte nicht verifiziert werden., the Agent is not connected. Follow Is the Agent online?Klicken Sie dann erneut prüfen again.
Is the Agent online?
Re-check, Browse and Test connection all run on the Agent’s computer, so they need the Agent connected: a green dot by its name in Datenagenten means Online. If it is red and says Offline, follow Is the Agent online? (computer asleep, service stopped, or no internet), then come back and click erneut prüfen.
If the installer stops with a message about 32-bit Office
This happens on many computers that have Word, Excel or Outlook installed, because Office is often the 32-bit kind. When the Agent finds 32-bit Office, the connector form says so too, before you install anything.
Why it happens. 32-bit Office comes with a 32-bit database engine. The Agent is a 64-bit program and can only use the 64-bit engine. Microsoft does not support both engines on one computer, and forcing the 64-bit one in can stop Microsoft Access from opening. So the Agent cannot read Access files on this computer.
The fix: run the Agent on a different computer. Use a computer without 32-bit Office, install the Agent and the 64-bit engine there, and point the connector at the database over the network. Nothing changes on the computer with 32-bit Office.
Do not force the 2016 engine with a /quiet switch. Older advice, including an earlier version of this page, said to do that. On many computers it stops Microsoft Access from opening. If you already did it and Access no longer starts, see getting Access back unten.
Not comfortable with this? Ask whoever looks after your computers to install the Agent on a server for you, or reply to support and we will do it with you.
-
Choose a computer without 32-bit Office
Pick a Windows computer that stays switched on and can reach the folder that holds the database. A Windows server is ideal. A desktop computer with 64-bit Office, or with no Office at all, works too. If the database already sits on an office file server, that server is often the best choice: the file is then a plain local path to the Agent.
To check which Office a computer has, open Word or Excel on it, click Dateidann Kontodann About Word (oder About Excel). The box that opens shows the version followed by 32-bit oder 64-bit.
-
Install the Agent there
On that computer, follow Installieren Sie den Agenten unter Windows. When it finishes, the new Agent shows a green dot in Datenagenten.
Each Agent counts toward your plan. If setup says all of your plan’s Agents are in use, delete the Agent you no longer need in Datenagenten Erste.
-
Install the 64-bit engine there
On the same computer, do steps 1 and 2 above: download accessdatabaseengine_X64.exe and run it. This time the installer finishes without the 32-bit Office message.
-
Point the connector at the database by its network path
In Datenagenten, add the Microsoft Access connector on the neu Agent. In Datenbank-Dateipfad, enter the database as a share path, \\server\share\folder\file.accdb, Zum Beispiel \\FILESERVER\Shared\Accounts\orders.accdb. A drive letter like S: does not work; here is how to find the path behind it. If the file is on the new computer itself, a local path such as D:\Data\orders.accdb is fine.
If the share only lets in named users, click the chip under the path and store a sign-in for that server: Signing in to the file server. Then click erneut prüfen und Testverbindung; wenn es liest Verbunden, klicken Speichern Sie.
If the database sits on the computer with 32-bit Office, its folder has to be shared on the network first, or the file moved to the new computer. Whoever looks after your computers can do either.
Your Office does not change. Nothing is installed on the computer with 32-bit Office. People keep using Access there as before, and the Agent reads the same file over the network.
Getting Access back if the 2016 engine broke it
If Microsoft Access stopped opening after a 64-bit 2016 engine was installed next to 32-bit Office, undo it in two steps. Both are in Settings → Apps → Installed apps (on older Windows 10, Apps & features).
-
Uninstall the 2016 engine
In the search box type Access database engine, click the … (or the entry) beside Microsoft Access database engine 2016, and choose Uninstall.
-
Repair Office
In the same list find Microsoft 365 oder Microsoft Office, wählen Modify, wählen Quick Repair und klicken Sie Repair. It takes a few minutes. Open Access to confirm it starts. If it still does not, run Modify again and pick Online Repair (slower; needs internet).
-
Run the Agent on a different computer
Do not install any engine on this computer again. Set the Agent up on a computer without 32-bit Office instead: follow the steps above.
If any of this does not match what you see, stop and reply to our support email with a photo of the screen. We will walk you through it.
Wo die Datei sein kann
Der Agent öffnet die Datei als Windows-Dienst. Dadurch ändert sich, was als gültiger Pfad gilt:
| Standort | Funktioniert? | Was einzutragen ist |
|---|---|---|
| Ein Ordner auf dem Computer des Agenten | Ja | C:\Data\orders.accdb |
| Netzwerkfreigabe | Ja | Der Freigabepfad, nicht ein Laufwerksbuchstabe: \\server\share\folder\orders.accdb. If the share only lets in named users, store a sign-in for that server on the connector: Signing in to the file server. |
| Ein zugeordneter Laufwerksbuchstabe (S:, Z:) | Nein | Use the real network path behind the letter instead. How to find it, step by step. |
| OneDrive or Google Drive in streaming mode | Nein | Make the folder a real copy on the computer: in File Explorer right-click the folder that holds the file and choose Dieses Gerät immer eingeschaltet lassen (OneDrive) or Offline access → Available offline (Google Drive for desktop). A green tick appears on the folder; then use the path as normal. |
Signing in to the file server
If the share only lets in named people, store a username and password for that server on the connector. The Agent signs in to the server with it and reads the live database file there.
Why this is needed: the Agent runs as a Windows service under the built-in Local System account, not as you. On a company domain the file server sees it as the computer’s own account, the computer name with a dollar sign, for example RECEPTION$. On a home or small-office network without a domain it is nobody the server knows. Either way, a share that is permissioned per user turns it away, and the path check under the file box says:
Access denied for the agent's service account. Add share credentials to this connector, or grant the agent's computer account read access.
There are two ways to fix it:
| Fix | When to use it |
|---|---|
| Store share credentials on the connector Empfohlen | Almost always. It takes a minute in the connector form, needs nothing changed on the server, and affects only connectors that read that server. Steps below. |
| Let the Agent’s own account in Advanced | For whoever runs the server. On a domain, give the Agent’s computer account (RECEPTION$) read access on both the share and the folder. Or change the Log On account of the Query Streams Dataverse Agent service in the Services app. That changes the identity for every connector on the Agent, so only do it knowingly. Opening the share to guests is not a fix on current Windows: Where the Agent can read files from. |
-
Type the share path
In Datenbank-Dateipfad, enter the full network path, for example \\192.168.1.125\Access\TestDB.accdb. As soon as the path starts with two backslashes, a small chip appears under the box, followed by the server name. It reads Service identity while nothing is stored, meaning the Agent tries its own Windows account. If the path check already said access was denied, a rose button Enter credentials for \\192.168.1.125 appears next to it.
-
Click the chip and fill in the box
Click the chip, or the rose button. A box titled Credentials for \\192.168.1.125 opens, with the line Credentials for this file’s server under the title.
- Domain
- Your company’s Windows domain, for example CORP. For an account that exists only on the file server itself, leave it blank or type a full stop (.).
- Benutzername
- Required. An account that can read the share. As the box says, Use a least-privilege, read-only account. A dedicated account such as svc-qs-readonly is better than a person’s login, because it will not change when someone leaves. It does need one write permission, explained in the note below.
- Passwort
- Required the first time. It is Used only to read this file; stored with the connector.
Klicken Sie auf Speichern Sie. The chip now shows the account, for example .\systemz oder CORP\svc-qs-readonly.
-
Check the line under the path
The Agent checks the path again with the new account. A green tick and File is reachable with the stored credential means the server let the account in and the file is there. Then click Testverbindung. On success the result adds a line such as Reading the live file on \\192.168.1.125 as .\systemzKlicken Sie auf Speichern Sie on the connector.
The Agent reads the real file, live. It signs in to the server and opens the database where it sits on the share. Nothing is copied, so there is no sync delay: a query sees what is in the file at that moment. With Nur-Lese-Modus on, the Agent opens the file read-only alongside everyone else, and people keep using Access as normal.
The account still needs to create the lock file. Every program that opens an Access database, Access itself included, creates a small .laccdb lock file in the same folder, even when it only reads. So the account needs Modify permission on that folder, the same as any Access user. Without it the test says: The agent cannot write to the folder containing the Access database. Access requires creating a lock file (.ldb/.laccdb) next to the database even for read-only connections. Grant the agent’s account Modify permission on the folder, or move the database to a folder the agent can write to.
One account per file server. Windows lets one computer sign in to a given server as only one account at a time. If another connector on the same Agent already signs in to that server as a different user, the test names it: Another connector on this agent already signs in to \\server as CORP\user. Windows allows one identity per server, so use that credential here too, or change it on every connector that reads this server.
Changing or removing the sign-in. The password is stored with the connector and never shown again. To change it, click the chip: the password box says Leave blank to keep current, so type a new one only if it changed. When the account’s password is changed on the server, the test reports that the credentials were refused; open the chip and enter the new password. Use service identity in the same box removes the stored sign-in. Stored share credentials work on Windows Agents, which the Access connector needs anyway.
If your file is on a drive letter like S: or Z:
The easiest way round all of this. If the file lives on an office server and you are allowed to install programs on it, install the Agent on that server instead. The file is then a plain local path to the Agent, like D:\Data\orders.accdb, and none of the steps below apply.
A drive letter like S: is a shortcut that exists only while you are signed in. The Agent runs in the background as a Windows service, before anyone signs in, so it has never seen that shortcut. The real location behind the letter, a network path that starts with two backslashes like \\FILESERVER\Shared, works for both of you. The steps below find that path and put it in the right place.
Not comfortable with this? Ask whoever looks after your computers for the network path of the S: drive and, if the share needs one, an account that can read it, or reply to support and we will find it with you.
-
See what the letter points to
Öffnen File Explorer (the yellow folder icon on the taskbar, or press the Windows key and E together) and click This PC in the list on the left. Scroll to the heading Network locations. Each mapped drive is listed there with its real path in its name, in this shape: Shared (\\FILESERVER) (S:). The two parts you need are the server name inside the brackets, FILESERVER, and the share name before them, Gemeinsam. Write both down.
If the name has been changed to something like Accounts drive (S:) and the brackets are missing, use one of the other two ways:
From the address bar. Open the folder that holds your Access file. At the top of File Explorer, click once in the empty space of the address bar; it changes from This PC › Shared (S:) › Accounts to a typed path. If the path starts with two backslashes, that is the one you want: select it all and copy it. If it still shows S:\Accounts, use the next way.
From Command Prompt. Klicken Sie auf Start, type cmdund klicken Sie Command Prompt (a normal click this time; no administrator needed). In the black window, type the line below and press Enter:
Type this, then press Enternet use
A short table appears. Find the row whose Lokal column says S:; its Remote column is the network path, for example \\FILESERVER\Shared. Write that down and close the window.
-
Build the full path to the file
Take the network path from step 1 and add everything that came after the drive letter, folders and file name included:
- Was Sie sehen
- S:\Accounts\orders.accdb
- What to type
- \\FILESERVER\Shared\Accounts\orders.accdb
Nur die S: part changes; the folders and the file name stay exactly as they were.
-
Put it in the Portal
In the connector form, type or paste the full path straight into the Datenbank-Dateipfad box. Or click Browse: the Browse dialog does not list mapped letters (it says Mapped drives (like Z:) are not shown and explains why). Click in the box at the bottom that reads Type a folder or full file path on the agent, type the share part, \\FILESERVER\Shared, and press Enter. The folder opens through the Agent and you can click down to the file.
-
Testen Sie die Verbindung
Klicken Sie auf Testverbindung. Verbunden means you are done; click Speichern Sie.
If the line under the path says Access denied for the agent’s service account, the Agent reached the server but was not let in. The mapped drive worked for you because Windows signed you in to the server; the Agent has to sign in on its own. Click the chip under the path and store an account that can read the share, as described in Signing in to the file server, then test again.
If any of this does not match what you see, stop and reply to our support email with a photo of the screen. We will walk you through it.
Füge die Verbindung hinzu.
Öffnen Datenagenten (unter Daten (im oberen Menü) klicken Anschluss hinzufügen Wählen Sie in Ihrem Agenten aus Microsoft Accessund füllen Sie Folgendes aus:
- Datenbank-Dateipfad
- The file’s location on the Agent’s computer, as described above. Click Browse and click down to the file. To type it instead: in File Explorer hold Shift and right-click the file, choose Copy as path, paste into the box, and delete the quotation mark at each end.
- Share sign-in chip
- Appears under the path only for a \\server\share path. Leave it on Service identity unless the share needs a named account (details).
- Passwort
- Only if the database itself has a database password set in Access. This is not the share password; that one goes in the chip.
- Nur-Lese-Modus
- Standardmäßig aktiviert. Lassen Sie es aktiviert; dadurch kann der Agent eine von einem anderen Programm geöffnete Datei lesen.
- Verbindungstimeout (Sek.)
- 30 ist in Ordnung. Erhöhen Sie den Wert nur bei einer langsamen Netzwerkfreigabe.
Klicken Sie auf TestverbindungWenn es liest Verbunden, klicken Speichern Sie.
Wird die Datei von Access, einem Kassensystem oder einem Buchhaltungsprogramm verwendet? That is normal. With Read-Only Mode on, the Agent reads alongside it. If the test still says the file is locked, the other program opened it exclusively. In Access: click Dateidann Options (bottom left), then Client Settings in the list on the left, scroll down to the Advanced heading, under Default open mode wählen Gemeinsam, klicken OK, then close the database and open it again. Test the connection once more.
Test fehlgeschlagen?
Die Meldung unter dem Testergebnis verrät Ihnen, um welchen Test es sich handelt.
| Nachricht | Ursache | Fix |
|---|---|---|
| Microsoft Access Database Engine (x64) is not installed oder Der Anbieter „Microsoft.ACE.OLEDB.16.0“ ist nicht registriert. | The engine is missing, or only the 32-bit engine that comes with 32-bit Office is present. | Installieren Sie die 64-Bit-Engine, then Re-check. If the computer has 32-bit Office, do not: run the Agent on a computer without it. |
| Die Microsoft Access-Datenbank-Engine auf diesem Rechner kann vom Agenten nicht verwendet werden. | Office wurde per Click-to-Run installiert; seine Engine ist ausschließlich für Office registriert. | Installieren Sie trotzdem die Redistributable (Schritt 1); it lives beside 64-bit Office. If that Office is 32-bit, run the Agent on a computer without it stattdessen. |
| This computer has 32-bit Office. The agent needs the 64-bit Access Database Engine, which cannot be installed safely next to 32-bit Office | The Agent found 32-bit Office. The 64-bit engine it needs can stop Access from opening if it is installed beside that Office. | Do not install the engine there. Install the Agent on a dedicated computer without 32-bit Office, install the 64-bit engine on it, and enter the database by its \\server\share path: the steps. |
| Die Access-Datenbank-Engine konnte nicht verifiziert werden. (graues Banner vor dem Test) | The Agent is not connected, or it is an older build that cannot answer the check. | Check the dot by the Agent’s name in Data Agents and follow Is the Agent online?, then click Re-check; the connection test is the final word. |
| Verzeichnis nicht gefunden: S:\ | Ein zugeordneter Laufwerksbuchstabe, den der Dienst nicht erkennen kann. | Use the network path behind the letter: If your file is on a drive letter like S: or Z:. |
| Access denied for the agent’s service account. Add share credentials to this connector, or grant the agent’s computer account read access. oder Share \\server: access denied — add credentials for this server | The share only lets in named users, and the Agent’s own Windows account is not one of them. Or the stored account has no permission on that share. | Click the chip under the path and store an account that can read the share: Signing in to the file server. If an account is already stored, ask whoever runs the server to give it read access. |
| Share \\server: the credentials were refused — check the username and password | The server rejected the stored sign-in: a typo, the wrong domain, or a password changed since it was saved. | Click the chip and type the username, domain and password again. For an account local to the file server, leave Domain blank or type a full stop. |
| Share \\server: server unreachable from the agent machine | The Agent’s computer cannot reach the file server at all: a wrong server name, the server is off, or a firewall blocks file sharing. | On the Agent’s computer, open the same \\server\share path in File Explorer. If that fails too, it is a network problem for whoever runs the network. |
| Share \\server: file not found on the share | The Agent got in, but there is no file at that path. | Check the folder and file name. Use Browse and click down to the file instead of typing. |
| Another connector on this agent already signs in to \\server as … | Windows allows one account per file server per computer, and another connector on this Agent uses a different one. | Store the same account the other connector uses, or change it on every connector that reads this server. |
| The agent cannot write to the folder containing the Access database. | The account can read the file but cannot create the .laccdb lock file beside it. | Give the account Modify permission on that folder, the same as any Access user has. |
| This agent build cannot sign in to \\server with stored credentials. | The Agent is an older version that cannot use stored share credentials. | Update the Agent, then test again. |
| Die Access-Datenbankdatei ist von einem anderen Prozess gesperrt. | Ein anderes Programm verwaltet die Datei exklusiv. | Keep Read-Only Mode on. In Access: File → Options → Client Settings, under Advanced set Default open mode zu Gemeinsam, klicken OK, close and reopen the database (details above). Or close the file in that program. |
| Die Datei muss eine gültige Access-Datenbank sein (.accdb oder .mdb). | Der Pfad verweist auf etwas anderes, beispielsweise eine Abkürzung oder eine Sicherungskopie. | Zeigen Sie auf den .accdb oder .mdb Die Datei selbst. |
Nächster Schritt: die Daten nutzen.
- Microsoft Access zu Excel
- Microsoft Access zu Google Tabellen
- Microsoft Access in Claude und anderen KI-Assistenten (MCP)
- Microsoft Access als REST-API
Verwandte Leitfäden
Setup trouble?
- Agent shows Offline, or Test connection and Browse are greyed out? Check that the Agent is online → Is the Agent online?
English 
Spanish 
German 
French 
Portuguese 
Japanese 
Korean 
Chinese 
Italian 
Dutch 
Indonesian 
Polish