Export Set: Giving error

[manoj12398]

Export set Module:

Configured export target using MID Sever location and file path specified to it. but it's showing error "StreamPipeline: Could not resolve given file path"

Tried the same path for other use, working fine. But export set not able to export records to that path. although connection is successful.

What could be the possibilities for this kind of errors. Please help

[jake_mckenna]

{file_path} = the attribute on the target location record file_path. This is not really a full path as much as just folder name or subdirectory in the agent path.

[tim_harris]

Hey guys, I am getting the "StreamPipeline: Filepath must resolve to location within the agent/export folder" error. I have a folder somewhere else on the system symlinked to inside the export folder. As soon as I use the symlink the export bombs out with the error. If I remove the symlink and use a folder it works just fine. Any ideas?

[Stefan Baldhof1]

I have the same issue.

MID Server is running on a Windows Server. User running the MID Server process has write access to the folders. No matter how I address the file path in the export target definition (without slash, forward or backward slash), I always run into an error saying "StreamPipeline: Filepath must resolve to location within the agent/export folder". I only configure the last target folder of the path, after "export".

Every hint appreciated.

[chasec1371]

I had a similar issue on our Geneva Patch 10 Windows MID Server that was just resolved by fixing the "Path to executable" on the MID Server service specified as the Export Target.   Once the path was updated to start with an uppercase C instead of a lowercase c, the Export Set worked fine.

To see the BINARY_PATH_NAME, used sc qc <agentname>

[Stefan Baldhof1]

Hi Charles,

many thanks for this hint, now it works!

Regards

Stefan