Witango-Talk: Frustrating Mystery Continues - User Scope Variables Dissappear

[Dave Machin]

I'm having serious problems with User scope variables dissappearing from one page to the next.  The always reappear if I click 'back' and submit a form again.  I've added <@userreferenceargument> to all the links.  This has been a perpetual problem for us.   We're running WiTango 5, W2K Server, IIS5, MS-SQL   I've been looking at the log files and am confused by something I see - any help would be appreciated.  Here's the pertinant parts of the log file:   I request a page successfully and we see the following"   07/02/2003 15:30:37   716 1 1  [Thread] Start processing 07/02/2003 15:30:37 192.168.0.113 USR@026B31CB867A71993E444199 716 1 2  [Thread] Getting network file c:\inetpub\wwwroot\ebay\reports\reports.taf 07/02/2003 15:30:37 192.168.0.113 USR@026B31CB867A71993E444199 716 1 4  [Thread] Got file 07/02/2003 15:30:37 192.168.0.113 USR@026B31CB867A71993E444199 716 1 43  [Thread] Network file loaded: c:\inetpub\wwwroot\ebay\reports\reports.taf 07/02/2003 15:30:37 192.168.0.113 USR@026B31CB867A71993E444199 716 1 43  [Application File] START  /ebay/reports/reports.taf Witango_Server_5  _UserReference=026B31CB867A71993E444199 07/02/2003 15:30:37 192.168.0.113 USR@026B31CB867A71993E444199 716 1 43  [user$ Vars] variableTimeout=30; csr_name=Machin; csr_id=467; 07/02/2003 15:30:37 192.168.0.113 USR@026B31CB867A71993E444199 716 1 43  [Results Action] Results1 This page loads fine.  Notice that the [user$ Vars] exist.   From that page, I click a link to another page and get the following:   07/02/2003 15:30:39  USR@__313570130DF60E8B3E443E78 2296 1 0  [Thread] Start processing 07/02/2003 15:30:39 192.168.0.113 USR@__313570130DF60E8B3E443E78 2296 1 1  [Thread] Getting network file c:\inetpub\wwwroot\ebay\reports\reports.taf 07/02/2003 15:30:39 192.168.0.113 USR@__313570130DF60E8B3E443E78 2296 1 4  [Thread] Got file 07/02/2003 15:30:39 192.168.0.113 USR@__313570130DF60E8B3E443E78 2296 1 43  [Thread] Network file loaded: c:\inetpub\wwwroot\ebay\reports\reports.taf 07/02/2003 15:30:39 192.168.0.113 USR@__313570130DF60E8B3E443E78 2296 1 43  [Application File] START  /ebay/reports/reports.taf Witango_Server_5  _UserReference=026B31CB867A71993E444199&tab_click=General%20Support&change=yes 07/02/2003 15:30:39 192.168.0.113 USR@__313570130DF60E8B3E443E78 2296 1 43  [Results Action] Results1 Here's where I'm confused - the USR@ value no longer matches the UserReference value.  Plus, the [user$ Vars] entry is missing!  At this point the page fails (doing what it should do given the csr_id value is missing).   The link I clicked definitely has the <@userreferenceargument> in it.  (the link is http://mirror2000/ebay/reports/reports.taf?_UserReference=026B31CB867A71993E444199&tab_click=General Support&change=yes)   Now, I click 'back' and click the exact same link and get what I expected in the first place:   07/02/2003 15:30:49   2248 1 1  [Thread] Start processing 07/02/2003 15:30:49 192.168.0.113 USR@026B31CB867A71993E444199 2248 1 2  [Thread] Getting network file c:\inetpub\wwwroot\ebay\reports\reports.taf 07/02/2003 15:30:49 192.168.0.113 USR@026B31CB867A71993E444199 2248 1 4  [Thread] Got file 07/02/2003 15:30:49 192.168.0.113 USR@026B31CB867A71993E444199 2248 1 43  [Thread] Network file loaded: c:\inetpub\wwwroot\ebay\reports\reports.taf 07/02/2003 15:30:49 192.168.0.113 USR@026B31CB867A71993E444199 2248 1 43  [Application File] START  /ebay/reports/reports.taf Witango_Server_5  _UserReference=026B31CB867A71993E444199&tab_click=General%20Support&change=yes 07/02/2003 15:30:49 192.168.0.113 USR@026B31CB867A71993E444199 2248 1 45  [user$ Vars] variableTimeout=30; csr_name=Machin; department=Belgium; csr_id=467; 07/02/2003 15:30:49 192.168.0.113 USR@026B31CB867A71993E444199 2248 1 46  [Results Action] Results1 This is driving me absolutely crazy - I really need help!   Dave Machin   ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body