Skip to main content
Question

Subscription Error: Unexpected value "\\\\networkpath\\" for parameter "value," expected list

  • October 28, 2016
  • 4 replies
  • 32 views

Forum|alt.badge.img

I have a publication that monitors a folder for new files that are created.

I also have a working workspace that takes any number of files from a network location and uploads them where I they need to go.

When trying to set up a subscription I get the following error

I have been able to run the workspace on its own however it fails when initiated by the topic.

I can see the SourceDataset_PATH parameter is missing from the log but.

Published Parameters

Parameter Value SourceDataset_PATH FME_TOPIC_MESSAGE$(FME_SHAREDRESOURCE_SYSTEM)temp/subscriptions/277a9c3190634de39102c05756666082.json FME_TOPICDatasetWatchstatusMessageParameter 'SourceDataset_PATH' must be given a value.

Any ideas?

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

itay
Supporter
Forum|alt.badge.img+18
  • Supporter
  • 1442 replies
  • October 28, 2016

is there a filter specified in the path and directory reader?


Forum|alt.badge.img
  • Author
  • 13 replies
  • October 30, 2016

is there a filter specified in the path and directory reader?

There is only an asterisk(*) in the path filter, so I assume it is looking at all.

 

 


itay
Supporter
Forum|alt.badge.img+18
  • Supporter
  • 1442 replies
  • October 31, 2016
There is only an asterisk(*) in the path filter, so I assume it is looking at all.

 

 

In that case it probably not finding any datasets/files to return, hence the error....

 

 


itay
Supporter
Forum|alt.badge.img+18
  • Supporter
  • 1442 replies
  • October 31, 2016
There is only an asterisk(*) in the path filter, so I assume it is looking at all.

 

 

Could be a case of access rights to the location, can you access the location from the machine where FME Server is installed?