Task Scheduler problem
Hi
I have setup my client for reports to be automated by emailing them a copy and also saving a copy on the server. When I run the report from within SAI it works fine.(all emails are sent and a copy is saved).
I then created a task scheduler to automate this on a weekly basis but it does not want to work.
Where could the problem be ??? I have set the scheduler to run when logged on or not and also given highest privileges. I am logged on as administrator to that server.
It almost seems like it does not launch the SAI. If I go to the SageAccBI56.exe and run that it opens BI launcher which has not been filled in. If I click on Launch Report Manager it says please select a database type.
Any advise would help.
Views: 105
Replies to This Discussion
-
Permalink Reply by David Briggs on -
Rainer,
Do you have access to the directory SAI is installed in? If so, check BXDATA/SageAccBI56Unattended.log. As far as I can tell, this is the log for scheduled tasks. It may help you figure out what the problem is, or if you post it here, someone may be able to help.
I'm having the same issue, and the log says the following:
Native Errror Number: [1004]
Source Library: []
Error Text: [Microsoft Office Excel cannot access the file '\\LOCKHAVEN1\AccPac\Sage\Sage Accpac\BXDATA\SQL\Templates\Salesman Report.xlt'. There are several possible reasons:
• The file name or path does not exist.
• The file is being used by another program.
• The workbook you are trying to save has the same name as a currently open workbook.]It seems like an Excel permissions issue, but I can't figure out the cause.
-
Permalink Reply by David Briggs on
-
Looks like it was a permissions issue: checking 'Run with highest privileges' in Task Scheduler solved the problem.
-
Permalink Reply by David Briggs on
-
I'm using Windows 7 Pro 32-bit, SP1. Also Office 2007, if that makes a difference.
-
Permalink Reply by Ralph on
-
David, your issue does seem like it might be a permissions issue.
Rainer, I am running SMI instead of SAI, and I'm running the client on a Terminal Server, but I have a hunch the solution I found might point you in the right direction. Here is some text I sent to a colleague after I figured it out. I hope it helps.
"The only way I was able to schedule a batch job using Windows Task Scheduler in W2008 SP2 32-bit was to click the “Change User or Group..." button and set it to run as ServerName\Administrators. That’s right, Administrators plural, as in the local Administrators GROUP. It makes absolutely no sense, but when you do this the option to “Run whether user is logged on or not” actually becomes grayed out, and then it works! The job will run as scheduled. I am now able to schedule reports to be written to disk or emailed, unattended."
-
Permalink Reply by Ben Trent on
-
Hi Ralph,
I also have David's issue and your solution does work but only if a user is logged on, that is part of the Administrator group on that server.
For me this problem only seems to occur for reports that need to use a template. Any other raw data reports run fine under a user with the option of not being logged on.
This really is a pain as the whole idea of unattended reports with template is so that you dont have do any editing or emailing each time it runs.
Follow Alchemex on twitter
Like Alchemex on facebook
© 2012 Created by Admin.
