I would definitely fix your workstation method. But you say they print - so actually go to the printer without popping up on anyone’s screen?
What’s your EpicorData directory look like? And EpicorData\Reports, I typically would have an auto-cleanup to delete old items here, but be vewy vewy careful to list your potential deletes a few times and be sure no one’s using it as archive.
What do your printers look like? Are they installed on both App Server and Task Agent server? or are you using server printers (can’t recall if that was in 10.2 yet). Is it always the same printers?
What about your retention settings in system monitor/agent?
1 Like
When I changed the Workstation Method, no one was able to print anything! I had to change it back. Our managed ERP vendor did notice that we had 2 versions of the SAP Crystal Reports runtime engine for .NET framework. One is for 32 bit, the other is for 64 bit. We are thinking this could be the issue. Maybe the version we have just needs to be uninstalled and updated to a newer version. Just wanted to keep everyone in the loop. Doubt this will happen to anyone else, but I wanted to document what we are trying and the outcomes of said solutions.
Which settings did not allow them to print? Did you try multiple options? Did the jobs process through system agent but never popped up on user screens? I’m assuming users started new sessions as they’d have to know that setting to pass the right info.
Curiouser and curiouser. Both versions of Crystal Runtime shouldn’t make a difference in my experience.
Are these usernames supposed to match? I am so confused. Are we thinking that this could possibly be an issue if they do not match? Epicor is also saying that in the Max Concurrent Tasks field should be set to at least 20 and I cannot see that anywhere. Just trying to figure it all out.
Typically they do match, most likely to reduce the number of service accounts one has to manage. IIRC as it’s been awhile, but the Max Concurrent Tasks is in the task agent setup in the admin console on the app server.
Depending on your user count and your reporting server resources (if you’ve split it out), you may want to go substantially higher than 20 on Max Concurrent Tasks. This includes scheduled tasks, so not many if you have scores of users, more than enough if you’re a 20 user system.
For username, I believe you’re saying you want tasks under that specific rule to run as manager, while everything else runs as ‘print’. Shouldn’t be a problem if passwords are updated here when they are changed! Typically, ‘print’ would be marked as a service account with 16 char random password that does not expire. manager you will want to expire if many people have or have had access to it. For heaven’s sake don’t leave the password manager!
1 Like
I know this is an old post I made, but I have tried a few things that I thought had worked. I moved the test task agent over to app02 and that seemed to fix things for a while. I came in today though, and people are getting prints that were printed on Halloween, so about 20 days or so. How can that even be possible? The servers reboot every weekend.
