This is what I usually call an ID Ten T error ID10t
> -----Original Message----- > From: Wilcox, Jamileh [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 07, 2003 1:57 PM > To: [EMAIL PROTECTED] > Subject: RE: Witango-Talk: User Woes RESOLVED > > > Oho, that's a great idea! I'll have to remember that when I have > problems again. It would have caught this one much quicker. > > I finally hooked up with this guy a little bit ago. So after checking > the button vs. enter key and trying some browser refreshes & such, I > asked him to try a different machine (seemed easier than getting into > browser settings over the phone). > > That certainly clarified the problem, which was that he was trying to > log in to a totally different application. Doh! > > I should have thought to ask - it's one of the first things I usually > check on user calls. I let myself get distracted by the fact that this > guy should theoretically be more computer-savvy than your average joe. > > I must admit that he did apologize profusely, which is a much better > response than I usually get from users who've done something silly. > > So my apologies to y'all, and thanks for the suggestions. I did learn > some new stuff & that's always for the good. > > I'm still slogging on the other problem, but I think I'm getting closer > there as well. > > > > > -----Original Message----- > > From: Dave Machin [mailto:[EMAIL PROTECTED]] > > Sent: Friday, February 07, 2003 12:00 PM > > To: [EMAIL PROTECTED] > > Subject: Re: Witango-Talk: User Woes > > > > > > One thing I do in situations like this is add a Mail action > > to the .taf to email me exactly what the users are entering > > when they try and log in. That way I can see if it's > > something obvious... > > > > ----- Original Message ----- > > From: "Wilcox, Jamileh" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Friday, February 07, 2003 9:02 AM > > Subject: RE: Witango-Talk: User Woes > > > > > > Phil & Scott & Atrix & Brent & John > > > > - thanks for the suggestions. I'm going to call him this > > morning and keep trying things until something works. > > > > He was logging in just fine before from the same machine, and > > I can log in with his username now; nothing in that code has > > changed and no-one else is having problems. It just doesn't > > feel like a coding thing. > > > > I really suspect a PEBKAC, but I want to try everything else > > possible before I get too insistent with him. I appreciate > > the suggestions for things to check on. > > > > I'll let y'all know how it turns out. > > > > Thanks very much! > > > > > -----Original Message----- > > > From: Scott Cadillac [mailto:[EMAIL PROTECTED]] > > > Sent: Thursday, February 06, 2003 5:52 PM > > > To: [EMAIL PROTECTED] > > > Subject: Re: Witango-Talk: User Woes > > > > > > > > > Hi Jamileh, > > > > > > Here's a tip that is usually helpful: > > > > > > In most versions of MSIE, using the "Refresh" button from > > the toolbar > > > triggers MSIE to reload the latest 'cached' content from the > > > "Temporary Internet Files" folder on the user's computer. Typically > > > MSIE will determine cache rules on it's own and usually > > errors on the > > > side of caution and cache things longer than usual. > > > > > > But....if you right-click on your page and choose "Refresh" > > from the > > > popup context menu, it will usually override this and get > > the latest > > > content (that has not expired yet) from your LAN proxy > > cache (if you > > > have one). I find this a bit more helpful, because most > > proxies will > > > expire content when they are supposed to. > > > > > > Learning everything you can about expiring your TAF output via the > > > Local$httpHeader is very important with dynamic applications. > > > > > > > > > As for your CSV thing, try putting the <@assign name="httpHeader" > > > .....> tag on the very first line of the last Results > > Window in your > > > TAF - and on the same line put <@PURGERESULTS> and your CSV output > > > variable afterwards. This will eliminate any garbage spaces > > and such. > > > > > > Oh, and turn debugging off in the file. > > > > > > Hope this helps. Cheers..... > > > > > > > > > ----- Original Message ----- > > > From: "Wilcox, Jamileh" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Thursday, February 06, 2003 3:37 PM > > > Subject: RE: Witango-Talk: User Woes > > > > > > > > > Phil - would having him hit Refresh in his browser do the same > > > thing? (That would be easier over the phone than changing IE > > > settings). > > > > > > On the csv problem, in the WriteFile.taf, I'm doing this: > > > > > > <@assign name="httpHeader" scope="local" value="Content-Type: <@var > > > local$filetype><@crlf>Content-Disposition: attachment; > > > filename=<@dq><@var > > > local$IncomingRFName><@dq><@crlf><@userreferencecookie><@crlf>"> > > > > > > > > > Thank you!! > > > > > > > > > > -----Original Message----- > > > > From: Phil Wade [mailto:[EMAIL PROTECTED]] > > > > Sent: Thursday, February 06, 2003 4:23 PM > > > > To: [EMAIL PROTECTED] > > > > Subject: Re: Witango-Talk: User Woes > > > > > > > > > > > > Jamileh, > > > > Try turning the cache in IE to check for changes "every > > > visit to the > > > > page". This is in the settings of "Temporary Internet files". IE > > > > defaults to automatic, but it has been my experience that > > > with highly > > > > dynamic sites, IE does not always see changes to pages > > > immediately if > > > > set to automatic. Your system may be logging him on and > > > the browser > > > > is returning the error that is now cached in his browser. > > You can > > > > also control this on the server by expiring the content faster. > > > > > > > > With your csv issue, are you modifying the http header? > > > > > > > > Phil > > > > > > > > On 7/2/03 9:12 AM, "Wilcox, Jamileh" > > > <[EMAIL PROTECTED]> wrote: > > > > > > > > > Another oddball case (it's one of THOSE days). > > > > > > > > > > I've got a user (PC technician) who swears he gets an > > > > "invalid login" > > > > > message when he puts his username into this application, > > > > even at the > > > > > 'forgot password' prompt. I can put in his username and > > > > password and > > > > > get logged in just fine; the app mailed him a new > > password when I > > > > > tried the 'forgot password' with his username. > > > > > > > > > > He also swears that he's cutting and pasting the > > username & reset > > > > > password directly from the email, which is what I'm doing. > > > > Of course, > > > > > he was typing the info in when I was on the phone with him. > > > > > > > > > > I've been on the phone with him, and he's been very > > helpful. He > > > > > thinks maybe it's named pipes in SQL, or cookies in his > > > browser, or > > > > > because the browser is sending his username as a token to > > > > the server, > > > > > or ... (he's learning Cold Fusion, can you tell?) > > > > > > > > > > Can anyone think of *any* possibility that I should check > > > > before I go > > > > > across campus to his office and cut & paste the %#$^~! > > fields in > > > > > myself? I'm not very familiar with the logs, but I don't > > > > see anything > > > > > in them that would even touch on this. > > > > > > > > > > Thanks. j > > > > > > > > > > > > > > > > > > > ______________________________________________________________________ > > > > > __ > > > > > TO UNSUBSCRIBE: send a plain text/US ASCII email to > > > > [EMAIL PROTECTED] > > > > > with unsubscribe witango-talk in the message body > > > > > > > > ______________________________________________________________ > > > > __________ > > > > TO UNSUBSCRIBE: send a plain text/US ASCII email to > > > > [EMAIL PROTECTED] > > > > with unsubscribe witango-talk in the message body > > > > > > > > > > ______________________________________________________________ > > > __________ > > > TO UNSUBSCRIBE: send a plain text/US ASCII email to > > > [EMAIL PROTECTED] > > > with unsubscribe witango-talk in the message body > > > > > > ______________________________________________________________ > > > __________ > > > TO UNSUBSCRIBE: send a plain text/US ASCII email to > > > [EMAIL PROTECTED] > > > with unsubscribe witango-talk in the message body > > > > > > > ______________________________________________________________ > > __________ > > TO UNSUBSCRIBE: send a plain text/US ASCII email to > > [EMAIL PROTECTED] > > with unsubscribe witango-talk in the message body > > > > > > > > ______________________________________________________________ > > __________ > > TO UNSUBSCRIBE: send a plain text/US ASCII email to > > [EMAIL PROTECTED] > > with unsubscribe witango-talk in the message body > > > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
