@Malin Norgren Which version is this in?In 22R2 the change we needed for this was part of the odata config, which is configured in the relevant yaml file (e.g. custom-values.yaml). When restarting the pods if you have a non-standard yaml file name you need to explicitly include the path+file in the command line, but if it is in the standard IFS filename I think it will pick up the file by default.For reference, here’s our 22R2 config that was added to extend the user query timeout:ifsappodata: queryTimeout: 899s maxQueryTimeout: 15m HTH,Nick
You don’t have any unit of measure on it… perhaps that’s the difference? As you can see in my example I can define it as seconds or minutes using s or m but you don’t have either. I’m not sure whether that will parse correctly without.
Like @Rukmal Fernando said, I would just run IFS and put the lobby into full screen mode, and set the lobbies to auto refresh every 5 minutes or so.I would also suggest that:The dedicated account used to connect to the lobby only has minimal access to what it needs Keep the PC itself with no screensaver and keep it locked in a secure location/cabinet so nobody can get to it to use it for other things (if you don’t want anyone in production changing the actual lobby or e.g. streaming the football match during the day) Set the IFS account to have no idle timeout. I’m not sure whether an automatically refreshing lobby will keep the active session alive indefinitely. Add the lobby page URL to the PC auto-start so that when the PC is restarted it will automatically return to IFS.Nick
Hi @KKSloane :)It may be due to the configuration of the parameters that the job is using. Can you provide those?e.g. the percentage and the schemas being included.Nick
2 questions:Is the PDFEMAILER logical printer assigned to one of your Report Print Task Templates inside IFS? I suspect it is but worth checking. Is the PDFEMAILER included in the ifs-printagent-config.xml file on the mws? I suspect this is perhaps your problem. Even if it is not printing to a physical printer you still need an entry in this file, like the PDF_PRINTER does. The mapping for each logical printer in the file should be something like this: <PRINTER_MAPPING> <LOGICAL>PDF_PRINTER</LOGICAL> <PHYSICAL>DUMMY</PHYSICAL> </PRINTER_MAPPING> HTH,Nick
What is the error you get when you map the logical printer to the DUMMY physical in the config file?
Also, you may need to set up a fake physical printer (really, a local print queue on the server) so it actually can be seen as a “printer” on the server, which is then just used in the PHYSICAL mapping in the file as noted before.For example, we have a local printer defined on our server which provides a local print queue on that server which doesn’t do anything, and that is what the logical is mapped to in the config file.I’m sure this is what your issue is… you need something mapped in the file.
Yes, see my last note above.
For this kind of scheduling where the timing is not equally spread out in the day (e.g. at specific times and not every x hours), I would schedule them as 3 different tasks. This is simple to do and will give you the control you need, as well as making it easiest to adjust just one of the jobs in the future.Nick
For this kind of scheduling where the timing is not equally spread out in the day (e.g. at specific times and not every x hours), I would schedule them as 3 different tasks. This is simple to do and will give you the control you need, as well as making it easiest to adjust just one of the jobs in the future. Nick Hi @NickPorter, yes, I agree. But you will have too many jobs to manage. Well, that really depends on how many of these you will have that need to run at irregular times. In your example your asked about there would be only 3 jobs (rather than 1) so that is still the approach I would recommend. In reality I would be really surprised if you truly have such a large number of jobs that MUST run at irregular times during a day that requires this kind of split into different jobs. If so, I would really try to align the execution times to specific minutes and implement similar to what @dsj suggested. But again, I really can’t foresee why you would get to ‘
My guess (and it is just that) is that the SMTP service in o365 is not allowing the account being used (s_azure.smtp) to send out as a different account regardless of what you tell it to do. Most mail services can be configured to prevent sending as someone else during a message relay, which is part of how spam email works, and this might be what you’re seeing.Can you or someone on the o365 look into that configuration on the mail service side?Nick
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.