I have a lot of scripts that all write to point feature classes in a 10.4.1 SDE Database in SQL Server 2012. The source comes from one of 3 databases types, SQL 2012, SQL 2014, or Oracle 11G. They all are the same as far as errors go so either it's my SDE or FME itself.
I even inspected everything I could and on a few I did get error while running and cleared up those small data issues, but they all produce the same error codes on crash dialog box I show at the bottom of this post when I close the Inspector app.
I have tried to redo from scratch a few of my scripts but they ALL are crashing like I show below. I am using the latest version 2017.7.27.17725, I had 2017.7.27.17539 and it did the same exact thing and I thought upgrading would do the trick, but no....
I have redone all my readers and writers, fished through all my data and data types, redone queries, redone my writer feature classes in my SDE, and even filtered the coordinates to fit in the state because we are using UTMs in the final feature class and I know a funky number can produce problems when reprojecting to UTM. I have gone through everything I can think of for troubleshooting. I turned on the debugging log and have only the errors below but I don't think they are worth anything.
I also put in a filename for the "Failed Feature Dump filename" in the Advanced Parameters of my Writer and nothing was rejected or written to this file.
The only thing that comes to mind that changed was an upgrade to ArcGIS 10.5.1 on this machine. There are no backward compatibility issues on ArcGIS between 10.4 and 10.5, but perhaps FME doesn't like something in 10.5?
Note that my translations all error at the end of the summary when everything had been written and long after these errors appear in the log.
BADNEWS: File C:\Program Files\FME2017_1_2_1\metafile\MULTI_WRITER.fmf could not be opened (tabrdr.cpp:161)
BADNEWS: No MULTI_WRITER dataset name was specified (couldn't find a value for `MULTI_WRITER_DATASET') (writrimp.cpp:773)
BADNEWS: File C:\Program Files\FME2017_1_2_1\metafile/geodatabaseDefline_.fmi could not be opened (tabrdr_classic.cpp:2715 - tabrdr::ClassicTableReader::TableReaderSource::open) - (tabrdr_classic.cpp:1739 - tabrdr::ClassicTableReader::getRow)At the end of the log it's like this: (cleaned it up a bit for readability)
...blah blah
Features Written Summary
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
STATS |SDE.BCA_ALL_SITES_2 2801
SDE.Update_record 1
==============================================================================
STATS |Total Features Written 2802
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
INFORM|Microsoft SQL Server Non-Spatial Reader: Closing `ProjectTracking' . Read operation complete
Translation was SUCCESSFUL with 0 warning(s) (2802 feature(s) output)
INFORM|FME Session Duration: 14.5 seconds. (CPU: 5.4s user, 2.4s system)
INFORM|END - ProcessID: 23452, peak process memory usage: 1105512 kB, current process memory usage: 1078264 kB
Error running translation.Then this crash box pops up EVERY SINGLE TIME after the error above.
Problem signature:
Problem Event Name: BEX64
Application Name: fme.exe
Application Version: 2017.7.27.17725
Application Timestamp: 5a601aaa
Fault Module Name: StackHash_2264
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 000007fe7f93124b
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 6.1.7601.2.1.0.274.10
Locale ID: 1033
Additional Information 1: 2264
Additional Information 2: 2264db07e74365624c50317d7b856ae9
Additional Information 3: 875f
Additional Information 4: 875fa2ef9d2bdca96466e8af55d1ae6e