This tutorial shows how to use the Ping Server action in Advanced ETL Processor. Use it before file transfers, backups, remote imports, or other steps that depend on a reachable server. If the server is down, it is better to stop early than let ten later actions fail in interesting ways.
What You Will Learn
- Configure a Ping Server action in a package workflow.
- Check whether a host is reachable before running dependent actions.
- Use variables when the server name changes by environment or schedule.
- Review the execution log when connectivity checks fail.
Before You Start
Use a test repository or safe sample data while following the tutorial. Production jobs are a poor place to experiment.
Ping Server Action Docs
This tutorial uses the Ping Server action to check whether a network server is active and responsive. It is a simple guard step before a workflow depends on a remote machine, shared folder, FTP server, or other network resource.
The Ping Server docs cover common use cases, the parameters tab, variables tab, execution log tab, and calculated server name examples.
For package troubleshooting, also review debugging actions and working with variables. If the check is part of a larger workflow, the default error action and linked actions docs help decide what should happen next.
Need Advanced ETL Processor First?
Download the Advanced ETL Processor trial before following the tutorial, or review Enterprise if you need scheduled unattended execution.