office 2013 et windows server 2019 : publipostage

Question

Bonjour,
Suite à la migration d'un serveur de fichiers de Windows Server 2008R2 vers Windows Server 2019, les publipostages ne fonctionnement plus car il n'arrivent plus à charger la source de données.
Les chemins d'accès sont bons et les droits sur le partage et au niveau du dossier sont en FULL CONTROLE pour l'utilisateur qui test depuis son poste.
Source : un fichier modele word et un fichier source de données word
Serveru 2008 R2 + office 2013 : les fichiers sont stockées sur le partage et le publipostage fonctionne

Robocopy pour migrer les données avec récupération des droits NTFS

Tous les fichiers de ce type sont impactés

Sur serveru windows 2019 , sur le meme PC, mm session et mm droits NTFS la soruce de données n'est plus trouvé.
Cela sur des centaines de publipostage.
Si je teste le fichier modèle sur le partage du serveur avec le fichier source stocké sur le PC, ça passe.

Auriez-vous une piste ? Est-ce un bug ?
Merci.
Cordialement,
Mathieu

Answer 1

@SERVICE INFORMATIQUE DES ARDENNES

Currently in Microsoft Q&A we only support English, could you please edit your question into English？
This action can help us understand your issue better, thanks for your understanding.
I get the following content via Translation tools.

Do you mean that you could not load data from shared file on server for mail merge in Word?
If yes, is there any error message shown on screen?
Here is a thread, "Mail Merge cannot find data source", maybe you could have a look.
In addition to loading data sources, can you browse and open some shared Office files directly on this server through File > Open in Office apps?

How did you access the shared file on server?
Such as via a mapped drive, the UNC path or others.
If there is a mapped drive, I would like to suggest you unmap it and add the path of the server as trusted locations into Office.

To add Trusted Locations, please go to File > Options > Trusted Center > Trusted Center Settings > Trusted Locations, then please tick the box of "Allow trusted locations on my network", then click "Add new location" to check this issue.

---

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hello,
Thank you for your feedback, I just did a test by approving the network path and all the subfolders of my share but it does not work only on this server
En savoir plus sur ce texte source
Vous devez indiquer le texte source pour obtenir des informations supplémentaires
Envoyer des commentaires
Panneaux latéraux

Answer 3

I can access documents without problem from the Office menu
It is a mapped drive
It does not show me the message loading the data source as when the source is on another share of another server or on the workstation itself. When it works, I have the "SELECT * FROM ..." pop-up
But there, I have nothing with the new configuration of the approved share netword

Answer 4

I just gave it a try. On windows server 2008R2, if the data source is stored in a share, it is functional with a drive mapped to a letter \ servername \ share => U: \
On the other hand on WIndows Server 2019, it does not work. It works fine if I go through a network location \ servername \ share