Python script shows it failed, but it really didn't

JeffreyWilkerson — Thu, 06 Jun 2019 15:59:52 GMT

When I run a tool from a Python toolbox the results show that it failed, but in reality it seems to have worked. The python script is an old script that I used to run stand-alone that copies all features of a geodatabase to another one. It also used to clear out any empty shapes and change curves to small line segments, but those operations are remarked out for now. But in the Pro Catalog History it shows a red 'X' to start and one at the end, and then says that it failed.

There is a lot of logging and I am wondering if Pro is thinking that the logging is representative of an error. Everything seems to have been copied so I'm stumped as to why the script is considered a failure. Any help would be greatly appreciated.

This is a what the history looks like:

Parameters
Input workspace T:\Census.gdb
Output workspace T:\Projects\Administration\GDB_Copy_to_Production\Census on W-SQL01(2).sde
Log File T:\Projects\Administration\GDB_Copy_to_Production\2019-06-05_16-11.log

Messages
Start Time: Wednesday, June 5, 2019 4:11:39 PM
Running script GDB2GDB...
[INFO] [06/05/2019 04:11:39 PM] [131] - Script: modpython
[INFO] [06/05/2019 04:11:51 PM] [143] - Source Geodatabase: T:\Census.gdb -- Feature Count: 168
[INFO] [06/05/2019 04:11:53 PM] [146] - Target Geodatabase: T:\Projects\Administration\GDB_Copy_to_Production\Census on W-SQL01(2).sde -- Feature Count: 13
[INFO] [06/05/2019 04:11:54 PM] [155] - Pulling in lists of Datasets, FeaturecClasses, and Tables
[INFO] [06/05/2019 04:12:50 PM] [249] - ...Copied ACS_Census_Archive to T:\Projects\Administration\GDB_Copy_to_Production\Census on W-SQL01(2).sde\ACS_Census_Archive...
[INFO] [06/05/2019 04:12:54 PM] [257] - ...Registered ACS_Census_Archive As Versioned...
[INFO] [06/05/2019 04:13:14 PM] [240] - ...Deleted existing file in destination DB
[INFO] [06/05/2019 04:14:24 PM] [249] - ...Copied ServiceAreaData to T:\Projects\Administration\GDB_Copy_to_Production\Census on W-SQL01(2).sde\ServiceAreaData...
[INFO] [06/05/2019 04:14:45 PM] [257] - ...Registered ServiceAreaData As Versioned...
[INFO] [06/05/2019 04:16:48 PM] [249] - ...Copied ACS2013_VehcileHouseholds_Tract to T:\Projects\Administration\GDB_Copy_to_Production\Census on W-SQL01(2).sde\ACS2013_VehcileHouseholds_Tract...
[INFO] [06/05/2019 04:16:52 PM] [257] - ...Registered ACS2013_VehcileHouseholds_Tract As Versioned...
[INFO] [06/05/2019 04:17:16 PM] [249] - ...Copied ACS2013_SchoolEnrollment to T:\Projects\Administration\GDB_Copy_to_Production\Census on W-SQL01(2).sde\ACS2013_SchoolEnrollment...
[INFO] [06/05/2019 04:17:21 PM] [257] - ...Registered ACS2013_SchoolEnrollment As Versioned...
...
[INFO] [06/05/2019 05:32:02 PM] [268] - Completed replication of T:\Census.gdb -- Feature Count: 168
[INFO] [06/05/2019 05:32:02 PM] [284] - --------------------------------------------------
[INFO] [06/05/2019 05:32:02 PM] [285] - Script Completed After: 01:20:22
[INFO] [06/05/2019 05:32:02 PM] [286] - --------------------------------------------------
Completed script GDB2GDB...
Failed to execute (GDB2GDB).
Failed at Wednesday, June 5, 2019 5:32:02 PM (Elapsed Time: 1 hours 20 minutes 22 seconds)

The script is enclosed.

topic Python script shows it failed, but it really didn't in ArcGIS Pro Questions

Python script shows it failed, but it really didn't