We have found by applying the 4.14 update that the problems with the OBJECTS.LSI file goes away. What is happening in the old versions is that multiple jobs are trying to update ONE LSI file and it get corrupted.
I can now run 4 jobs at a time since applying the 4.1.4 patch…
Sincerely,
Thomas Nather
Penske Logistics
email: Tom.Nather@Penske.com
(216)765-5787
Ph: 216-765-5787
Fax: 216-765-5666
Lauren Feldhaus laurenf@BELLATLANTIC.NET 02/17 8:54 PM >>>
Hi friends,
I swear that the Doc Agent has a mind of its own. Can anyone please
help me understand what could be wrong with the setup I have for Doc
Agent. I am currently on 4.1.1 and Oracle 7.34.
My problem is this: I have several users that schedule larger jobs to
run between 3:30 and 7:30 in the morning so they don’t interfere with
normal production jobs. What could be set or missed on my part that is
holding the reports from running till 6:30am? It seems that no matter
what time the jobs are scheduled, they run (all at once I might add) at
6:30 in the morning.
I know the server is up but… what am I missing?
Also, I just recently upgraded another doc agent to 4.1.3 and the
objects.lsi file is generating a “New” objects.lsi file every morning
for some reason. I have a problem with this cause I then get an error
telling me that the User that owns a report that is scheduled to run
cannot access the local security domain. When I put the old objects.lsi
file in the locdata file, the jobs run fine for today, and then tomorrow
the same thing happens all over again. I made the upgrade last Friday
(2/12). Any thoughts?
Thanks in advance for your help.
Listserv Archives (BOB member since 2002-06-25)