0

I'm distributing a Python script tool with folks outside of my organization.

I had always assumed the .tbx file and the script were self contained. But when someone else tried to run the tool, they got the error:

Error 000576: Script associated with this tool does not exist.

Sure enough, if I go to properties of the script, it's pointing towards an absolute path on my network drive. I see there is an option under general to "store relative path names" but in the case of distributing this tool outside of my organization, this probably won't work either

Is my only option to send folks the .tbx file along with the raw python file, and have them add the script to the toolbox on their own?

Improve this question

1 Answer 1

Reset to default
2

You can embed the script into the tool itself for easy distribution. See this link.

Improve this answer
3
  • hmm. I only see a way to "add" a script, not import. Am I missing something? Commented Oct 20, 2021 at 17:59
  • I think so. Add the script as normal, set the parameters as normal, when ready, right click the script and import it. Commented Oct 20, 2021 at 19:39
  • Even though (IMHO) the linked Esri info appears vague and counterintuitive, this is the correct answer. I went back and found that the "Import Script" option was avaiable in my Script's context menu (not in the Toolbox's context menu). After selecting "Import Script" the Source tab in the Script Properties indicated "<<Imported>>". After doing this, I reviewed the context menu, and "Import Script" was greyed out. I then saved the Toolbox (again) and imported the Toolbox on a different machine and confirmed that this solution was correct. @DiamondJoe12 please mark this as the answer Commented Feb 3, 2023 at 17:49

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.