Skip to main content
Solved

Exporting the project is not permitted. Items that don't exist or are inaccessible by you

  • August 20, 2024
  • 2 replies
  • 66 views
sam_appleton
Contributor
Forum|alt.badge.img+7

Hi All,

 

I get the following error when trying to export a project where there is an issue with a dependency:

This project contains items that don't exist or are inaccessible by you.

 

My user is a superuser and I can see the file however when I click the link to take me to the file, I can see that the link is different. Is there a problem with the link?

Link returned by project:

/fmeserver/resources/lookup?path=FME_SHAREDRESOURCE_DATA%5CEDM_CSV

expected link:

/fmeserver/resources/browse?path=FME_SHAREDRESOURCE_DATA%2FEDM_CSV&name=Data

I noticed that @kate-safe mentioned in a recent ticket that this was a known bug (

)

Is there anyway to fix this without upgrading FME flow? It’s put a halt on all of our deployments.

Flow installation details:

FME Flow 2023.1
Build 23619 - win64

 

Many thanks!

 

Sam

Best answer by siennaatsafe

Hi @sam_appleton, 

There is a workaround. The workaround to this is to either run the workspace with the Job Submitter service first to ensure the resource path is created before creating the project.  Another option is to have the default path point to an existing data resource folder. 

However, there isn’t a patch. If you’d like a permanent solution you’ll have to upgrade.

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.

2 replies

siennaatsafe
Safer
Forum|alt.badge.img+12
  • siennaatsafeSafer
  • Safer
  • 214 replies
  • Best Answer
  • August 21, 2024

Hi @sam_appleton, 

There is a workaround. The workaround to this is to either run the workspace with the Job Submitter service first to ensure the resource path is created before creating the project.  Another option is to have the default path point to an existing data resource folder. 

However, there isn’t a patch. If you’d like a permanent solution you’ll have to upgrade.

sam_appleton
Contributor
Forum|alt.badge.img+7
  • sam_appletonContributor
  • Author
  • Contributor
  • 21 replies
  • August 22, 2024

Thanks @siennaatsafe the default values were set to this:

:$(FME_SHAREDRESOURCE_DATA)\EDM_CSV

Changing the value to forward slashes and re-running the workbenches has fixed the issue:

:$(FME_SHAREDRESOURCE_DATA)/EDM_CSV

 

Thanks for your help :D

 

Community Stats

32,100
Posts
121,895
Replies
39,746
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.