I have potential overlapping schedules on Mondays, Saturdays and first day of the month. But on a daily basis, I put 10 reports in folder 1 and another 10 in folder 2. Using a single batch file, I run the reports in those 2 folders:
Autopilot /M UPDATE /I "C:\DAILY REPORTS 1" /O "C:\Report Results"
Autopilot /M UPDATE /I "C:\DAILY REPORTS 2" /O "C:\Report Results"
I am sure with this setting, the reports are running one after another. One thing is that this problem started at the same time when some reports are running much longer than normal (One report normally runs for 10 minutes and suddenly runs for more than 1 hour - but when I re-run it, it runs normally again). By the way, I just rescheduled the Monday/Saturday/Monthly reports to minimize the overlap.
17 comments
-
Jet Reports Historic Posts It's been 2 years we are running some of daily reports using Jet Report version 10 on an XP machine with 3 GB of RAM and 2.6 GHz quad core CPU.
But for the last 2 weeks, the scheduled reports start giving me headache. They give me #VALUE errors on all cells with Jet formulas. When I re-run them manually, they run perfectly and give me the correct results. The problem is that it does not happen only on specific reports, it changes every day, and it happened only for 1 or sometimes 2 reports out of 19 reports. The changes we made lately on that PC were installing new anti-virus (NOD32) about 2 month ago, and a monitoring software (Spice works). We tried to disable the anti-virus but to no avail. We checked the activities around the time that the report gave us errors and found anything suspicious and our network admin did not find any problem in the connection. Any suggestions will be appreciated. Thank you. -
Jet Reports Historic Posts Hello,
Have you tried setting up logs for the scheduled reports? You could get some useful information.
Elena -
Jet Reports Historic Posts Thanks Elena,
I have never used that option before, but I will try it tonight. -
Jet Reports Historic Posts I have the same problem, even scheduling them.
I have localised the problem - it appears that for some reason, the Jet Reports add-in gets unloaded somehow and subsequently #VALUE's start appearing.
Sometimes I "End Task" on EXCEL.EXE processes while the Task Scheduler runs them, and that seems to be the cause.
Just wish it did not happen.
Nothing is popping uo in the debug logs. -
Jet Reports Historic Posts Is it possible that some scheduled tasks on the machine are overlapping others? For example, you have a report scheduled to run at 11:30 pm and another 12:00 am. Previously, the first report was running for only 20 minutes, so no overlap occurred but now it is running for 40 minutes so there is an overlap between the 2 report runs. Sometimes when multiple scheduled reports are running simultaneously this can cause problems. Could this be the case?
Regards,
Hughes -
Jet Reports Historic Posts I often have overlapping reports but this rarely causes issues for me as I find that there are separate Excel sessions running. What I do to get around this is setting the maximum running time of the report in the scheduled task to time out 1 min between each run. So, if I run a report every five minutes, time it out after 4 minutes.
So, could it be clarified that the should not be a problem being able to run multiple seperate instances of Excel with different Jet Reports? -
Jet Reports Historic Posts Last night, I added the log option and tried running only 1 batch of reports in one folder, which means no overlap.
This morning, I found two of the reports gave me #VALUE. I don't see any error message on the log file.
Another thing I have tried, disabled completely the new anti-virus program that might create problem (after trying to use just the exclusion). I will try one more thing that I could think of, change network connection from a separate old switch to the main switch. What else could I do??? -
Jet Reports Historic Posts Let me put on my sysadmin hat for a second…
Update Windows and Office via Microsoft Update.
Make sure you are using a recent version of Jet Reports/Essentials, and maybe a newer install of C/FRONT (hotfixes, etc.)
Make sure you have about 20% space free in your database file (if you are using a native DB).
I'd fix the network speed and duplex between the NAV server, the file server your Jet Reports are stored on, and the PC running the Jet Reports, to Full Duplex, and the highest speed (100/1000) that each can support.
Check updates to your AV and firewall - sometimes these can interfere. Maybe turn off On Access scanning for these reports. and schedule the files to be scanned when they are not going to be run.
Just so you know, I had two reports that were acting up on me - one had black diamonds with question marks appearing inside them (!) and the other had excel.exe running as a process - even after the report ran, closed, saved and emailed!
In both cases, I created new sheets in the workbooks, and copied (in Design view) only the cells that were in use. Then I Paste Special - Formulas, and then Paste Special - Formats into the new sheets, and deleted the old sheets. Both reports run perfectly now.
Just a thought. -
Jet Reports Historic Posts Maybe the anti-virus program is noticing the monitoring software.
-
Jet Reports Historic Posts Hi,
So I guess there are a few issues to address here. First, as far as overlapping reports go, it doesn't usually cause problems because they are in separate Excel processes as noted. However, in some cases it can. For example, if you have a limited number of NAV sessions, you will be using more sessions at once, which will cause everything in that report to come back as #VALUE if you don't have enough sessions to support it. Also, if Jet logging is turned on, the overlapping reports could be trying to write to the same log file at the same time. This is unlikely but I've seen it happen before and cause problems.
Most of the sysadmin things you suggest are good, but not installing a newer version of C/Front. Jet can and will only ever use a matching version of C/Front (or the closest one it can find to matching). If you are using NAV 5.0 on, installing the 5.0 SP1 C/Front will do absolutely no good because Jet will just use the 5.0 C/Front. All the major versions of C/Front get installed along with Jet, so installing one yourself isn't even necessary anymore unless you are on a NAV hotfix version which doesn't work with any of the major released versions we ship.
So what you should do here is turn on Jet logging before running your next set of scheduled reports. Note, this is different from AutoPilot logging. You turn on Jet logging in the Jet Application Settings, not in the AutoPilot scheduled task. Then you may be able to see in the log files created what is causing the #VALUE's. If you can't figure out the log files, you should actually just start a support case with Jet support, since the purpose of this forum is educating people how to use Jet Reports, not troubleshooting issues like this. Jet support should be able to help interpret the log files and what's going wrong.
Regards,
Hughes -
Jet Reports Historic Posts This is the update for the problem. I moved all reports to a different computer which is running on windows server 2003 and it worked fine until last week (it means they had been working well for almost 7 months).
I did not change anything on the reports/schedule for the last couple of months, and last week one of the reports (a very small one - running under 1 minute) gave me the #value all all cells. It is the same problem as before, If I re-run it again, it works fine.
So, I recreated the report and I get the same problem again. Yesterday morning, I got another two reports with the same problem (a longer one but still under 3 minutes). I recreated the report and this morning I still get the same #value for one report and one line result from another one. When I re-ran the one that gave me one line result manually, it gave me the correct result with multiple lines.
There is no overlapping schedules. Today, I will try to separate those 3 reports on three different batch files, and I will update you with the result. -
Jet Reports Historic Posts Could it be that you are running out of sessions in your NAV license? Remember that Jet requires a NAV session to run. If you have users who are leaving themselves logged into NAV overnight, it is possible that NAV is running out of sessions at some point, especially if reports running via the Scheduler did overlap (even by a few seconds) since the overlapping report runs would each be using a session. This would explain the #VALUE errors and why reports come out okay when you run them later and why there would be no errors in the log file.
Regards,
Hughes -
Jet Reports Historic Posts All reports are running between 4:00 AM to 7:00 AM. Our office opens at 7:00 AM with only under 10 people working.
We have 90 nav licenses and some of the users are accessing nav remotely, but I am very sure this is not the case. -
Jet Reports Historic Posts Okay well it was worth asking given the nature of the problem. I should have said in the previous post that you can prove whether this is the problem by just looking at the contents of the Session table with a formula like =NL("Table","Session"). Given the nature of this problem I don't think we're going to fix it on the community site. You should probably create a ticket on the Jet support site for it.
Regards,
Hughes -
Jet Reports Historic Posts I will wait for a few days and if the problem stays I will send a ticket.
Thank you. -
Jet Reports Historic Posts I moved those 3 reports on 3 different folders and run them on 3 separate lines on the same batch file.
It's been 2 days now, and I have been getting the correct results.
i am still not sure if this will fix the problem permanently. -
Jet Reports Historic Posts It's been almost 3 weeks now and everything looks ok . . . .