Anybody experience that on the desktop, adding the AFT Application type, loading the account information, that it times out?
Help will be apprecaited...
On thge Configuration Manager, the CM's are picked up and the account can be viewed and modified from there..
Regards
Trompie
AFTransfer 6.3.01 problem on Enter Account Load Time out
- Henk Trumpie
- Nouveau
- Posts: 22
- Joined: 27 Jul 2007 12:00
i try to understand :
1- you create a new Skeleton on control-m with a specific Application Type like SAP, Oracle Application, People Soft, etc ...
perhaps you must install the Forms on your Desktop
1- find the forms configuration file and install this configuration with the desktop interface go to tools onglet and click on Import Application Forms
if not you can have a network problem ( if it's the first time you use this server connexion )
1- you create a new Skeleton on control-m with a specific Application Type like SAP, Oracle Application, People Soft, etc ...
perhaps you must install the Forms on your Desktop
1- find the forms configuration file and install this configuration with the desktop interface go to tools onglet and click on Import Application Forms
if not you can have a network problem ( if it's the first time you use this server connexion )
The account is loaded from the agent to your machine.
There is a comunication timeout but this means that the network is very loaded.
Or you are not in the users that can read the list of accounts (or this lint is very long).
But if you know exactly the name of the account, and the path origin and destination you can type it, save the job and try to run it.
Infact can be that to your machine the comunication failed but when run the job the load of the account works.
There is a comunication timeout but this means that the network is very loaded.
Or you are not in the users that can read the list of accounts (or this lint is very long).
But if you know exactly the name of the account, and the path origin and destination you can type it, save the job and try to run it.
Infact can be that to your machine the comunication failed but when run the job the load of the account works.