avpatil
27th August 2007, 20:19
Hi,
SOme of our users are expericing slowness in opening the ttstpsplopen when a report is printed. Any reason for this to happen?
Thanks
Arvind Patil
mark_h
27th August 2007, 20:24
Actually the first thing I do is always delete user defaults for ttstpsplopen. :)
avpatil
27th August 2007, 20:29
Mark,
The issue is when the user selects the printer and click continue, after that it takes long times (around 2 min). We tried different version of BW, made the user local admin on the machine.As you can notice we are in windows enviroment, so what could be the possible issue?
Arvind
mark_h
27th August 2007, 22:48
Well - what I recommended is the first thing I do no matter what when dealing with printing and user problems. I have seen the "saved defaults" cause some weird problems. So having said that.
Is this "some users" always the same users? Is it always consistent for this same set of users? Is it slow for one user and fast for another in the same location(same office)?
What if they use a machine configured for someone else that has normal response times? You could have them logon to the machine with their id and test. If it is fast then it may be the machine setup. If it is slow for them on both machines then the user that prints fast can log into the machine. Then the slow users can log into Baan and see if it is still slow. I think at this point you need to try to isolate it to a problem on the machine or a problem for a user-id?
sisira
22nd May 2010, 11:27
We have Baan IV with service pack 20. this issue started couple of day ago. System get stuck when a user is trying to print something. It takes more than 10 minutes to prompt the 'select Device' screen (ttstpsplopen). After selecting device even system takes a long time to display or print the output.
Does anyone have the same experience and know the solution for this? Please let me know.
Thanks,
Sisira
Amit_Jain
22nd May 2010, 15:28
check the disk space and delete files from $BSE/tmp folder. Hopefully problem should get resolved
jclju1
24th May 2010, 09:45
It is fine if you regularly run session Purge Device Queue.