When attempting to read features from Salesforce via FME Server (2021.2) the job fails after warning:
WARN |MULTI_READER(MULTI_READER): Skipping to next Reader
ERROR |A fatal error has occurred. Check the logfile above for details
The workspace runs to completion on FME Desktop (2021.2) and reads data successfully. Troubleshooting hasn't provided any further information or progress.
Is there a reason that the skipping occurs on FME Server?
Hi @milo89 , are FME Server and FME Desktop the same build number? If both applications are the same version and build, they use the same engine and should produce the same results. However, differences in connection parameters, user parameters, permissions, or networking can still produce results between applications.
If you enable debug logging, is there any additional information recorded?
To best understand the differences between the two platforms, we'd need to compare the two job logs. If the issue remains unresolved, please download and send a translation log from both desktop and server to our Support team for review. Thank you!
Hi @milo89 , are FME Server and FME Desktop the same build number? If both applications are the same version and build, they use the same engine and should produce the same results. However, differences in connection parameters, user parameters, permissions, or networking can still produce results between applications.
If you enable debug logging, is there any additional information recorded?
To best understand the differences between the two platforms, we'd need to compare the two job logs. If the issue remains unresolved, please download and send a translation log from both desktop and server to our Support team for review. Thank you!
Hi @sanaeatsafe,
Thanks for your response. The build numbers are both:
Current FME version: FME 2021.2.6.0 - Build 21821 - WIN64
The server was updated to this build through an engine upgrade as previously the differing build versions resulted in a reader failure with different errors.
Doing some further reading, I believe the issue could be related to the notes in 'Accessing Salesforce' section of the Salesforce reader documentation.
If all else fails, will reach out to the support team.
Thanks.