MIS Systems Thread, SIMS.Net CommandReporter scheduled doesn't work in Technical; I am using CommandReporter to export reports to XML files from SIMS.Net and have put a number of these command ...
8th January 2009, 08:17 AM #1
SIMS.Net CommandReporter scheduled doesn't work
I am using CommandReporter to export reports to XML files from SIMS.Net and have put a number of these command lines into a batch file.
When I run the batch file logged in as an admin on our SIMS.Net server it works fine.
When I schedule the same batch file, the batch file runs (because it makes entries in the Event Logs) but the CommandReporter aspects are not running.
Does anyone have any idea why not? Below is a representation of the batch file:
eventcreate /L Application /T INFORMATION /SO WDX /ID 0001 /D "WDX XML Data Export Process Began"
CD C:\Program Files\SIMS\SIMS .net\
commandreporter.exe /USER:SimsUsername /PASSWORD:SimsPassword /REPORT:SimsReportName /OUTPUT:"S:/Users/Username/My Documents/WDX/Students-StudentData.xml" /QUIET
eventcreate /L Application /T INFORMATION /SO WDX /ID 0002 /D "WDX XML Data Export Process Completed"
Last edited by u8dmtm; 8th January 2009 at 09:28 AM.
8th January 2009, 09:55 AM #2
Is S drive mounted when your batch file is run as a scheduled job? You might have to add a "net use ..." line in to tell the computer to mount the SIMS area first before you run CommandReporter.
Originally Posted by u8dmtm
8th January 2009, 10:13 AM #3
Drive S is a drive letter on the server (not a mapped network drive) and is also where the batch file itself is run from. Just to be sure, I moved everything to C: and tried again, but the same issue persists.
Originally Posted by dhicks
8th January 2009, 10:17 AM #4
perhaps redirect the output to a file.
8th January 2009, 10:20 AM #5
Good idea - might want to catch stderr as well:
Originally Posted by matt40k
8th January 2009, 10:46 AM #6
Thanks, that was useful. The output returned was:
<CommandReporterError>Login failed for user username. Reason: Incorrect F:\Apps\Sims\Connect.ini file</CommandReporterError>
It looks like I will need to log this issue with our LA (who provide SIMS support). Unless anyone knows of a quick fix?
8th January 2009, 10:49 AM #7
What is the contents of that connect.ini file?
8th January 2009, 10:50 AM #8
There is your answer incorrect ini file at F: not S:
Originally Posted by u8dmtm
8th January 2009, 11:02 AM #9
8th January 2009, 11:07 AM #10
Excellent, thanks to all.
Drive F: is a mapping so needed to use NET USE to map it for SIMS and it then worked without a problem.
By maplay in forum MIS Systems
Last Post: 3rd October 2009, 05:44 PM
By CadlaM in forum MIS Systems
Last Post: 13th January 2009, 02:20 PM
By DaveS in forum MIS Systems
Last Post: 27th February 2008, 11:44 AM
By russdev in forum General Chat
Last Post: 8th September 2006, 07:32 AM
By projector1 in forum Hardware
Last Post: 7th July 2006, 02:21 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)