+3If I run each reader individually (one-at-a-time) then I get correct output from each of the readers. If I choose 'Run Entire Workspace' then one reader only processes one record and the other reader processes normally. All feature classes are in the same file geodatabase.
Any ideas why 'Run Entire Workspace' doesn't give the expected results?
Thank you.
Best answer by daveatsafe
The failure seems to be occurring on the GDB writing - the error is due to an inability to lock the schema in the output GDB. I would check to see if FMETraining_DataInterOp.gdb is opened in ArcGIS, or you could try writing out to a different GDB than one the workspace is reading from.
+20The yellow inspection icons on the feature types and transformers point to a failure in the workspace during the 'Run Entire Workspace' process. Please post the resulting log from 'Run Entire Workspace', so we can see what is causing the failure.
+3I have attached the log file from running the 'Run Entire Workspace' process. Thank you for taking a look.
+20I have attached the log file from running the 'Run Entire Workspace' process. Thank you for taking a look.
The log file reports that FME can't find the geodatabase:
C:\\Users\\e125818\\OneDrive - City of Houston\\Utils\\FME\\FME_Training\\FMETraining_DataInterOp\\FMETraining_DataInterOp.gdb
Please check that the GDB file is present on your system.
Does SpatialETLTool have a .fmw or .fmwt extension?
+3Thank you for your response.
fmw is the file extension.
Yes. The geodatabase does exist at that path.
The process works fine if I run the components individually. The geodatabase is found. It's the 'Run Entire Workspace' that seems to have a problem finding the geodatabase.
As another test, I created a new file geodatabase in c:\\temp to see if a simpler path would help. It didn't help.
+20Thank you for your response.
fmw is the file extension.
Yes. The geodatabase does exist at that path.
The process works fine if I run the components individually. The geodatabase is found. It's the 'Run Entire Workspace' that seems to have a problem finding the geodatabase.
As another test, I created a new file geodatabase in c:\\temp to see if a simpler path would help. It didn't help.
This is quite strange. Please send me a copy of the workspace, and I will see if I can reproduce the problem.
+20The failure seems to be occurring on the GDB writing - the error is due to an inability to lock the schema in the output GDB. I would check to see if FMETraining_DataInterOp.gdb is opened in ArcGIS, or you could try writing out to a different GDB than one the workspace is reading from.
+3That worked. I created a second GDB just for the output and wrote everything to that one. Can you tell me how you knew that the issue was that it couldn't lock the schema?
Thank you very much.
+20That worked. I created a second GDB just for the output and wrote everything to that one. Can you tell me how you knew that the issue was that it couldn't lock the schema?
Thank you very much.
The log file noted the error number returned by ArcObjects, so I looked that up. It's not always easy to find, though.
