Hi all,
like in most cases our production environment consists of several application servers and a central instance. Now, when we want to schedule a transport into production the following happens.
Upon scheduling a job is created in the production environment, so far so good. However, when we leave it like this and don't take any additional action the actual import fails with a general error message: an internal error occurred.
To avoid this from happening, after scheduling the transport from Development, we have to logon to the production environment and manually change the job and enter the central instance (server name) as Exec. target.
Is there a way or some setting we have to make / change in order to not having to logon and manually change the server name?
Thanks in advance.
Kind regards,
Micky.