mikebah Posted October 24, 2014 Posted October 24, 2014 I would like to run and save the output of a SIMS.net report using the CommandReporter.exe tool included with the package. I have tried running the following command: CommandReporter.exe /user:username /password:password /report:"No Photograph Report" /output:nophotoreport And when I run it, this is displayed: SIMS.net Command Line Report Exporting Utility 7.159.4.0 Copyright ¸ Capita Business Services Ltd 1984-2014. All rights reserved. Logging into to SIMS.net as user username Getting reports for user username Report 'No Photograph Report' found. Running Report Error Running Report. Reason :Incorrect syntax near ')'. Incorrect syntax near 'a0'. Do I have to include parameters aswell? Is it a problem with permissions? Thanks in advance.
LosOjos Posted October 24, 2014 Posted October 24, 2014 That's a new one to me Does the report run properly in SIMS itself?
mikebah Posted October 24, 2014 Author Posted October 24, 2014 Yeah, it's absolutely fine running from the SIMS application. Would you happen to know where the reports are kept in Windows?
Meldrew Posted October 24, 2014 Posted October 24, 2014 Odd error, but 2 things spring to mind. The "/output:nophotoreport" should be a pathname, eg c:\nophoto.xml, might be making it act odd. Also I usually specify /server and /database. Does it work with these specified? Meldrew
chilbs Posted October 24, 2014 Posted October 24, 2014 Is best to use the full path in the output and yes it might be after some parameters if you add /PARAMDEF to your code the output should be a xml file with the default parameters for that report
mikebah Posted October 24, 2014 Author Posted October 24, 2014 Ah, I see. It is only when I run an imported report (that is, not made internally). Other reports generated by staff here run successfully with the current command parameters put in. What should I dictate using /paramdef to get the imported report working?
chilbs Posted October 24, 2014 Posted October 24, 2014 the /paramdef does not require any additional input. Have you looked at the help generated by running CommandReporter.exe on it own with no switches.
Meldrew Posted October 24, 2014 Posted October 24, 2014 My understanding is that you run it once with /paramdef, specifying the output file, eg /paramdef / output:"c:\parameters.xml". This gives you the necessary parameters that you need to populate in the xml file, then you run commandreporter again, specifying /paramdef:"c:\parameters.xml" and commandreporter pulls these values in from the xml file as values for the report. HTH, Meldrew.
chilbs Posted October 24, 2014 Posted October 24, 2014 when running the commandreporter again the switch to input the parameters xml file is /PARAMFILE e.g. /PARAMFILE:"c:\parameters.xml"
mikebah Posted October 24, 2014 Author Posted October 24, 2014 I've chucked /paramdef /output:H:\nophotoreport.xml at the end of the command and it has generated a file successfully. But I can't seem to decipher what it i.e. I can't see any valuable information such as names of students.
chilbs Posted October 24, 2014 Posted October 24, 2014 try running this next. Replace the .csv with the file type the report is supposed to output CommandReporter.exe /user:username /password:password /report:"No Photograph Report" /output:"H:\nophotoreport.csv" /PARAMFILE:"H:\nophotoreport.xml"
mikebah Posted November 3, 2014 Author Posted November 3, 2014 This is still not working. I get the same error after specifying the /paramfile parameter.
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