Message d'erreur "(record limit reached)" sur serveur lors de la lecture de fichiers

Question

Bonjour

un workflow lit plusieurs fichiers stockés sur un répertoire réseau

ils sont bien accédés via \Serveur\Répertoire\NomFichier.ext

le workflow fonctionne parfaitement sur un poste

en l'exécutant depuis le serveur, le message d'erreur

\Serveur\Répertoire\NomFichier.ext|0 records were read from "\Serveur\Répertoire\NomFichier.ext" (limit reached)

apparait pour chaque fichier lu

5 fichiers sont lus, 5 fois la même erreur

le serveur a bien les droits d'accès au répertoire

les fichiers sont des excel ou des .txt parfaitement lisibles sans lignes vides, de petite taille (ex: 50 lignes)

une idée ?

Merci

dougperez · Answer

Hi Olivier,

You can verify this at the publishing step from Designer.

When you save the workflow to Server:

* Go to File > Save As > Alteryx Server
* In the Save Workflow window, look for the section usually called Workflow Assets or Manage Workflow Assets
* Expand that section and check whether your input files are selected as assets to be included with the workflow package
* If the files are on a network share and should be read directly from there, try unchecking those Excel/TXT files before saving/publishing

The idea is that the workflow should keep the UNC reference:

\Server\Directory\FileName.ext

and not use a copied/packaged version of the file.

You can also check this before publishing in Designer:

Options > Advanced Options > Workflow Dependencies

There you should see each Input Data dependency. Alteryx documentation mentions that this window lets you review and edit file dependencies, including converting paths to UNC or absolute paths.

One additional check: after saving to Server, download/open the workflow again from Server in Designer and verify the Input Data tools. If the path still shows the UNC path and the files were not included as workflow assets, then Server should be trying to read the real network file.

If the issue remains after that, I would then focus on the execution identity: the account used by the Alteryx Server worker/service or the workflow credentials may not have the same network permissions as your desktop user.

olivierMPW · Answer

Thanks for the answer

the files are referenced thru UNC

How can I verify this point ?

Check whether Server is reading a packaged copy instead of the network file

dougperez · Answer

Hi,

This message makes me think the issue is more likely on the Server side than with the file contents, especially if the same workflow runs correctly from Designer on a local machine.

A few tests I would suggest:

* Check the Workflow Dependencies before publishing

In Designer, go to:

Options > Advanced Options > Workflow Dependencies

Then confirm that the files are referenced with the full UNC path:

\Server\Directory\FileName.ext

Also make sure they are not being packaged or localized when the workflow is published to Server.

* Test with a single file

Create a very simple workflow with only one Input Data tool pointing to one of the network files, then publish and run that workflow on Server.

This helps confirm whether the issue is related to network access or to some logic in the main workflow.
* Check the execution user on Server

Even if “the server” has access to the directory, the important point is which account is actually running the workflow.

Depending on the configuration, this could be the Alteryx Service account, a Run As user, or the credentials provided during publishing.
* Test with user credentials

If possible, try publishing/running the workflow using your own credentials, or ask the Server admin to temporarily enable that option for testing.

If the workflow works with your credentials but not with the Server/service account, that would confirm a permissions or execution identity issue.
* Check whether Server is reading a packaged copy instead of the network file

When publishing, Alteryx may package input files with the workflow. Make sure the published workflow is still pointing to the real network file and not to an embedded/stale copy.

My first checks would be Workflow Dependencies, then a minimal test workflow with one Input Data tool using the same UNC path, executed from Server with the same account used by the Alteryx service.