Welcome to the Calyx Software Message Boards where you can share ideas and solutions with other Calyx users! Calyx personnel including Tech Support, Development, QA, and Business Planning often visit these message boards unofficially to better understand our customers' needs. To submit your suggestions Click Here.
This discussion forum is a service provided by Calyx Software. Calyx Software does not endorse any particular point of view expressed in this forum or any information provided in it. The use of the information provided by other users in this message board is at your own risk.
Calyx Software Message Board
Home      Members   Calendar   Who's On
Welcome Guest ( Login | Register )
      


12»»

Odd Print ErrorExpand / Collapse
Author
Message
Posted 1/13/2006 11:33:37 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 5/16/2007 9:26:29 AM
Posts: 6, Visits: 14
I've come across a very odd error.

Station A: When trying to print a custom form for Mr. Smith, it prints the form with Mr. Jones' information.

Station B: When trying to print a custom form for Mr.Smith, it prints the form with Mr. Bells information.

If I logon as Administrator on any of the stations it prints fine, but when the users login to the domain with their information, it does not print correctly.

Any Ideas?

Running 5.2 on Windows 2000 Advanced Server.

Network installed onto client machines. 

Post #2110
Posted 1/14/2006 5:10:03 PM


Supreme Being

Supreme Being

Group: Moderators
Last Login: 12/21/2008 11:16:31 PM
Posts: 837, Visits: 1,901
The data for the custom form is merged from the temp.brw in the \winpoint\work folder. From what you've said, my guess is the temp.brw is referencing someone else's data. You should give "Everyone" Full Control on the \winpoint\work folder. This should ensure that Point is able to overwrite the temp.brw on the next custom form print.

Bryan
Point Product Manager
Post #2133
Posted 2/2/2006 9:50:48 AM
Junior Member

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member

Group: Forum Members
Last Login: 2/16/2006 1:23:37 PM
Posts: 13, Visits: 46
This is happening with our system now, would you say that clearing the work folder on a nightly basis is what should happen? How can this be stopped??

Ryan Reeber
SLM Financial
IT Support
ryan.reeber@slma.com
Post #2427
Posted 2/2/2006 8:42:47 PM


Supreme Being

Supreme Being

Group: Moderators
Last Login: 12/21/2008 11:16:31 PM
Posts: 837, Visits: 1,901
You could clear the Work folder, but it won't get to the root cause of the issue. 

Are you using Terminal Server?  If you're not using TS, it's possible the problem is due to not having enough rights on the Work folder if a single machine is being used by different user logins. The temp.brw file that was created by user A cannot be overwritten by user B on the next print. Giving Full Control to "Everyone" on the Work folder should stop the problem.

Bryan
Point Product Manager

Post #2442
Posted 2/6/2006 12:25:14 PM
Junior Member

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member

Group: Forum Members
Last Login: 2/16/2006 1:23:37 PM
Posts: 13, Visits: 46
Well after making sure that we have our security setting set to full access on the winpoint folder down. We still see the problem persist (randomly).  Have you seen this problem before on TS? Im trying to get a grasp on this problem as this is a potential huge security risk!

Ryan Reeber
SLM Financial
IT Support
ryan.reeber@slma.com
Post #2474
Posted 2/6/2006 1:02:07 PM


Supreme Being

Supreme Being

Group: Moderators
Last Login: 12/21/2008 11:16:31 PM
Posts: 837, Visits: 1,901
So you are using TS?  Do you have every user on the same winpoint folder?

Bryan
Point Product Manager
Post #2475
Posted 2/6/2006 1:36:11 PM
Junior Member

Junior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior MemberJunior Member

Group: Forum Members
Last Login: 2/16/2006 1:23:37 PM
Posts: 13, Visits: 46
The setup we have is the following:

the end users "user" folder is going to there local home drive called W: which also has the windows folder with the winpoint.ini, if your asking if everyone uses the winpoint folder on the server side yes that is the case. That is where the actual program is...

Ryan Reeber
SLM Financial
IT Support
ryan.reeber@slma.com

Post #2476
Posted 2/6/2006 2:03:04 PM


Sepal

Sepal

Group: Moderators
Last Login: Yesterday @ 9:52:28 AM
Posts: 1,183, Visits: 9,258
 don't share the winpoint folder and every thing will work.

Disclaimer:  This post carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this post is accurate. It is offered in the hopes of helping others, but you use it at your own risk. The author will not be liable for any damages that occur as a result of using this post.
Post #2477
Posted 2/28/2006 5:14:59 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: Forum Members
Last Login: 3/20/2006 7:27:59 PM
Posts: 2, Visits: 6
Is there a fix for this issue? My legal dept is forcing me to move off Calyx if this issue isn't resolved soon. They see it as a huge NPI data risk.


5.2 install on Win2000..... blah,blah, blah....

Regulators!!!
Post #2681
Posted 2/28/2006 6:57:46 AM


Sepal

Sepal

Group: Moderators
Last Login: Yesterday @ 9:52:28 AM
Posts: 1,183, Visits: 9,258
Are you seeing this issue under Terminal services or Citrix?  If not and this is just a windows 2k box are you sharing the winpoint directory?

Disclaimer:  This post carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this post is accurate. It is offered in the hopes of helping others, but you use it at your own risk. The author will not be liable for any damages that occur as a result of using this post.
Post #2682