Issues that can arise when executing TimeXtender Data Integration tasks and execution packages in TimeXtender Orchestration:
- TimeXtender Ingest/Execution Service is not running
- Server running TimeXtender Ingest/Execution service firewall issue
- TimeXtender Ingest/Execution service settings
TimeXtender Ingest/Execution Service is not running
Error: TimeXtender Orchestration is still waiting for task to start execution...
For TimeXtender Orchestration to be able to execute the TDI packages, the services need to be running.
To resolve this issue:
- Connect to the server running the TDI ingest/execution service
- Go to Start > Services
- Find TimeXtender Ingest/Execution Service and make sure it is running
Note: TDI services can be installed on multiple servers. Make sure to check the server that is connected to the TDI Instance of the task/package that is failing.
Prepare or Deliver instance has not been setup in TimeXtender Execution Service Configuration
If you are trying to execute an execution package in a prepare or deliver instance via TimeXtender Orchestration but it is not starting, but you have not yet setup the prepare or deliver instance in TimeXtender Execution Service Configuration, you may encounter the below error.
Error: TimeXtender Data Integration task has not started executing yet.
Task timed out after 10minutes. Task's timeout used.
To resolve this issue:
- Run TimeXtender Execution Service Configuration. Ensure that the version is the same as the currently installed version of TimeXtender Data Integration.
- Sign in
- Select the relevant instances
- Click Save
Server running TimeXtender Ingest/Execution service firewall issue
This error will make it appear as if the TimeXtender Ingest/Execution Service is not running. To resolve this issue, ensure the firewall is configured as per Configure your firewall - Service bus
If you encounter errors in Windows Event Viewer (under Windows > Application logs) similar to below, ensure AMQP ports (5671/5672) are open.
Error: Service Bus: Receiving message failed:
Azure.Messaging.ServiceBus.ServiceBusException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond ErrorCode: TimedOut (ServiceCommunicationProblem). For troubleshooting information, see https://aka.ms/azsdk/net/servicebus/exceptions/troubleshoot. ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.Azure.Amqp.AsyncResult.End[TAsyncResult](IAsyncResult result)
at Microsoft.Azure.Amqp.Transport.AmqpTransportInitiator.<>c.<ConnectAsync>b__17_1(IAsyncResult r)
at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
Execute the attached PowerShell script TimeXtenderTLSTest.ps1 to test whether AMQP ports (5671/5672) are open.
The following result indicates that AMQP ports (5671/5672) are not open.
The following results indicates that AMQP ports (5671/5672) are open, and the issue should now be resolved.
TimeXtender Ingest/Execution service settings
Sometimes your services contain incorrect settings.
To resolve this issue, follow these steps:
- Connect to the server running the TDI ingest/execution service
- Run the ingest/execution service configuration
- Finish the wizard
- Try restarting the ingest/execution service
