Navin Tenani
23rd May 2011, 17:22
Hi,

We are having a peculiar problem. Many of times it is observed that Users are not getting the desired Report, but the Report given by some other user. Take Example

User A had given Print command from Session X.

User B had given a print command from Session Y.

The report output being received is as below :

User A Gets output of Session Y

User B Gets output of Session X.

Many of times it also happens that a user gets reportout which is merged and haing informations from both Session X & Y.

Did anyone of you had ever went through such scenario. If yes, please share the resolution.

Regards

Naveen Tenani

Navin Tenani
24th May 2011, 12:35
Dear Gurus,

Please Help.

Rgds

Naveen Tenani

amitmmokashi
24th May 2011, 13:12
Hi,

Can you provide some more details about the session?
I would like to know your observation on debugging of the session as to how the session behaves. Does it print the correct report or it still prints the wrong report?
If its the wrong report, then how the program script and report triggers are activated?
Kindly let us know some more information on this aspect.

Thanks & Regards,
Amit Mokashi

drcelus
25th May 2011, 11:31
I am facing the same issue. However, it has been impossible to reproduce it since it appears randomly.

My setup :
Porting Set 8.5a.03
Tools 7.6 a5
Windows Server 2003

JaapJD
26th May 2011, 09:31
Can you attach some examples? And also some screenshots from ttaad3520m000 where we can see the data of the printed reports. What happens if you repeat the request in this session?

mark_h
26th May 2011, 15:39
Not sure about LN - but are the temp files created correctly and sent to the correct printer? On baan IV I have ttaad3120m000(Maintain Device Queue) where I can go look at the temp files created by user id and sent to a printer. I assume this is windows printing since I have never seen anything like this with UNIX printing.

drcelus
27th May 2011, 09:28
Will take a look at this sessions when I find an error, I don't have an example at the moment, as I said it is appears randomly and users do not always reports this kind of errors.

We mainly use ttstpconv:POSTSCRIPT and ottstpconv:ASCII for our devices.

pbenven
27th May 2011, 18:23
Maybe append something unique to the output? Like ${LOGNAME}