Latest Contributions by JoshuaBixby

As Dan points out, the only viable path forward is to download the Pro 2.3 Offline Help through My Esri. If you don't have access to My Esri to download it, you will need to contact someone in your organization that does and have the download it for you.

Just for kicks, try: select_temp = "SELECT object_id, name FROM temp_example"

So this appears to be more of a Model Builder issue than a Calculate Field issue. In terms of Model Builder and an intermediate data source, I am guessing Model Builder isn't allowing the option because it has no idea what the schema will look like when the model is run. When you are pointing to an existing/original data set, Model Builder can lookup the schema of the data set and determine what fields do and don't exist, and hence give you the option to create a new field and set the data type. When working with intermediate data, it is derived and the schema won't be known until runtime so Model Builder isn't allowing that parameter to be set.

With nothing open that access that FGDB, make sure there are no orphaned lock files. If a previous run terminated prematurely or incorrectly, it might be an orphan lock that the script is seeing and not allowing the FGDB to be cleaned up.

Outside of PyCharm, if you open the Pro-created Python stand-alone window and import arcpy, does it give the same error?

Although the date format is standard, it is wrapped in additional text that is causing troubles for the tool. Additionally, some rows have multiple dates, which also will cause issues for the tool. You will need to do some text parsing to extract just a single, valid date format before trying to convert to a date.

ArcGIS Enterprise/Server Python libraries get installed and updated by Esri, not by users. Although it is technically possible to update Python packages (not the Python version itself) manually on the server, it isn't supported and there is a likelihood some functionality of the Esri product may break. Getting back to your script on Pro, Esri puts a lot of emphasis on backwards and forwards compatibility of geoprocessing tools. Given that Pro 2.4 and Pro 2.7 both are Python 3.x, I am surprised to see a script that ran on 2.4 break on 2.7. What exactly broke? In terms of geoprocessing service, a service on the server is completely self contained and does not use any of the binaries or libraries on the Pro client consuming the service.

Refer to your security client documentation. Esri's installers automatically configure a couple ports because those ports need to be open for any deployment, but Esri doesn't automatically open all potential ports for every deployment. For example, opening up inter-machine communication ports for a single-machine deployment would be unnecessary. Since Esri doesn't know how the user will deploy the software, they provide all the ports that need to be open in their documentation, and the user can configure the local security client to meet their needs.

Are you stating the ArcGIS Server installer is automatically configuring the firewall ports for you? If so, why do you need to open them ahead of time if the installer is doing it automatically?

The error ERROR 000208: Error creating output feature class Failed to execute (Project). indicates the problem is creating the output from the Project tool. Since you haven't shared how the script_path variable is set, it is difficult to say anything more specific.

Online Status	Offline
Date Last Visited	5 hours ago

My Ideas

Latest Contributions by JoshuaBixby

Re: Looking for online source of arcpy objectclasses Pro 2.3.3

Re: Is there a way to use temporary tables with arcpy query layer functions?

Re: Define data type when using calculate field

Re: Cannot delete temp gdb on subsequent iterations because of lock

Re: Can't import arcpy in PyCharm

Re: Convert String field to Date Field

Re: what version does ArcGIS Server use regarding arcpy/Pro/Map ?

Re: Issue while opening ports for ArcGIS Server on firewall

Re: Issue while opening ports for ArcGIS Server on firewall

Re: ArcPy Project failing as GP Service

Esri Forestry Group (EFG)