This content has been marked as final. Show 8 replies
Can someone please look into this issue?
Which version you are on ?
I have seen this error in 220.127.116.11 for planning database refresh mostly. like in 1st hit it abort and soon we kick again it gets completed successfully.
We use 9.3.1.
second timne when you run the job do you run it manually or again through the scheduler ????
It is a common thing that while running the automation job through the scheduler , the job is run using System user and not the user used to configure the job, This System user might not have access to the requested file or folder.
Second time also we run it from scheduler.
This issue comes up once in 2 weeks. Couldn't able to figure out the reason.
I am sure that no other jobs in scheduler are running at that time.So, there are no concurent operations going on the respective App.
Edited by: 985303 on Feb 4, 2013 4:00 AM
Are you importing thru Maxl???? Can we have a code here...
What is happening when your loading thru EAS?
Have u noted the time every week when u noticed the error?
We appreciate if you paste complete log file of maxl script..