u8dmtm Posted January 8, 2009 Posted January 8, 2009 (edited) 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" C: 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" Edited January 8, 2009 by u8dmtm
dhicks Posted January 8, 2009 Posted January 8, 2009 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. 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. -- David Hicks
u8dmtm Posted January 8, 2009 Author Posted January 8, 2009 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. 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.
matt40k Posted January 8, 2009 Posted January 8, 2009 perhaps redirect the output to a file. >>c:\output.txt 1
dhicks Posted January 8, 2009 Posted January 8, 2009 perhaps redirect the output to a file. Good idea - might want to catch stderr as well: >>c:\output.txt 2>&1 -- David Hicks 1
u8dmtm Posted January 8, 2009 Author Posted January 8, 2009 Thanks, that was useful. The output returned was: Login failed for user username. Reason: Incorrect F:\Apps\Sims\Connect.ini file It looks like I will need to log this issue with our LA (who provide SIMS support). Unless anyone knows of a quick fix?
bossman Posted January 8, 2009 Posted January 8, 2009 Login failed for user username. Reason: Incorrect F:\Apps\Sims\Connect.ini file There is your answer incorrect ini file at F: not S: 1
u8dmtm Posted January 8, 2009 Author Posted January 8, 2009 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.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now