Tam Error Interp Help

[Alice]

There is an error showing up repeatedly in the except.err log for one user who says she is not seeing anything pop up ever. I've searched the KB using just about every combo of search I can think of and nothing matches. If I use the Error Text alone there are 200+ and I really don't want to look at each one.
I've done the

Has anyone seen this and maybe knows what the user is doing to make it happen?

EXCEPTION DETAIL REPORT

Title      : Clntfile
Error Text : An error occurred while displaying detail.

Process          : F:\WINTAM\clntfile.exe 10.3.0.0
ASTamSvr Version : 10.4.0.6
Computer Name    : CIT41000016529
User Name        : luser
Time/Date        : 08:45:47 05/13/2011
Operating System : Windows XP Professional Build 2600 Service Pack 3
CPU              : Intel FUTURE Lev[15] Rev[4303] Num[2]
Physical Memory  : 58% free of 1964296 KB
Paging File      : 74% free of 3903388 KB

Sequence of Preceding Exceptions

  Source : clntfile.frmEntityList.LoadDetailScreen
  Number :   2147745799 (Decimal)   80040007 (Hex)
  Desc   : Out of memory

  Source : clntfile.frmEntityList.LoadDetailScreen
  Number :   2147745799 (Decimal)   80040007 (Hex)
  Desc   : Out of memory

  Source : ClntFile
  Number :            7 (Decimal)   00000007 (Hex)
  Desc   : Out of memory

[Lance Bateman]

What would this person normally be working with - client files, prospect, accounting?
It could be too many "stickies" on a file being retrieved.
I've had it happen when there are too many records in the client policy history (over 1000).
I've also seen it happen on pc's and it had nothing to do with TAM - seemed to disappear if work station rebooted at least when finish work for the day.

[Andrew Carrick]

We've also had that Number 214... happen occasionally but just put it down to network problems, and it doesn't happen often. However my records note that it was associated with "ASWintamWord". Alice, is this the same user who didn't have an asword.dot file?

[Alice]

Lance - this is one of the data techs that only enter new customer info, new policy screens and new business attachments. No other areas accessed. I thought maybe she had multiple clients open b/c a while back the limit used to be 5 before errors would start or the computer would lock. But when I monitored her open files on the network, I didn't see anything unusual. There's been a round of viruses (virii?) in the insurance area so I'm also wondering if something is going on that may be using up the memory make that error happen.

Andrew - this user is in-house not remote, and she doesn't do letters. It's like this error is a combination or just parts of the errors I found in the KB.
I'm going to turn this over to 1st level support here and have them check the computer before I go any futher. Want to eliminate some stuff before contacting Applied since the user cannot provide me with any info. Just threw this out there to see if anyone had seen this error and under what circumstances.
Thanks guys!

[Jan Regnier]

Alice has this person been doing the same type of work a long time or is she "new" ?  Sounds like items may be being setup incorrectly.  Has anyone watched her workflow?

[Alice]

She's been here just about a year. And...ummmm...what's this "workflow" thing you speak of?
Still burns me that "they" don't have any. I once suggested to the supervisor that she have someone sit with a new user after 3 months, six months and a year, I got the same response I've been getting since I've been here - too busy, no time not enough staff to have one off the phone (or whatever they're doing). I once asked how Tam work is reviewed when performance review time comes around and was told it's not considered b/c there are no workflows to prove someone is not doing something right.
Sorry I go off like this every time it comes up. It just plain hurts to see the inefficiencies and I'm forced to look the other way.

[Jeff Zylstra]

Check and see if she has enough environment space, and make sure that Config.NT and Autoexec.NT are configured to Applied's specifications.  The shell command in config.NT is the important one.  Also, make sure that you delete all of the temp files as well.  I've seen some weird things happen because of corrupted and/or too many temp files, cookies, etc...


P.S.  I also think that this user may be offended by her user name too.  "luser" isn't a very nice name.  

"User Name        : luser"

[Jan Regnier]

She's been here just about a year. And...ummmm...what's this "workflow" thing you speak of?
Still burns me that "they" don't have any. I once suggested to the supervisor that she have someone sit with a new user after 3 months, six months and a year, I got the same response I've been getting since I've been here - too busy, no time not enough staff to have one off the phone (or whatever they're doing). I once asked how Tam work is reviewed when performance review time comes around and was told it's not considered b/c there are no workflows to prove someone is not doing something right.
Sorry I go off like this every time it comes up. It just plain hurts to see the inefficiencies and I'm forced to look the other way.

Maybe you need to look "the other way" in regard to the error report - until she's in such a knot she can't work....  Management seems to be focused on the non-important things.  Suggest going back to typewriters! and paper files if they don't want to take the time to instruct employees on the correct workflows and usage of TAM.  They don't see the $$ wasted in the investment of the system by allowing it to be used so ineffectively? 

[Jan Regnier]

/quote]

I noticed that too, Jeff....and had the same thought....or maybe it really is applicable? (sorry - that wasn't very nice of me....)

[Alice]

I originally replaced her user name with "user" and stuck the "l" in there to see if any one would notice. I certainly didn't mean any disrespect and I would not send it to Applied like that.
emo kid - no one understands me...too mainstream

[Orlando Alonzo]

Also check the path statement. TAM gets a little wacky if the Path gets too long.

[Alice]

Thanks Orlando. now on my list to check along with the config.nt and autoexec.nt. Possible a typo in there somwhere.

[Lance Bateman]

Alice - it sounds like your agency is well along the path of becoming the mess I was hired to clean up here.  Best wishes.  It sounds like much of supervisory/management staff need to be replaced or at least sent to E&O school - WITH A TEST!

(Talk to Marcia Priest, she saw much of what I was plopped into when she was brought in for a consult before they hired me).

[brinkerdana]

I've seen it, too, Lance!  Nice work for consultants...lots of hours doing clean-up!

[Alice]

well now...isn't this special.  Apparently this computer was relaoded because viruses could not be removed. No one thought to look at the documentation for reloading insurance computers and nothing was done in the autoexec, config and nothing added to Path statement. Very disheartening that I take the time to write all this stuff up and 1st level support doesn't use it. Then they pass it to me because they can't fix something. I shouldn't need to check the basics - our help desk is supposed to do that. Same thing with the remote user not being able to do Tam letters b/c no asword.dot where it needed to be.
Thank you guys for pointing me in the right direction.