Hi:

A client has reported that they have started to experience errors similar to the following:
Unable to create directory APRC0002 in C:\DOCUME~1\Bob\Locals~1\Temp\.

The 1st time that they print a report there is no problem but when they re-print it, the error results. If they exit the application & re-enter, they can successfully print the report (1st time only). This appears to happen on a variety of reports, maybe even all reports (this is all 2nd hand information from the client, I haven't seen it).

The folder C:\DOCUME~1\Bob\Locals~1\Temp\ exists.

The environment is Windows 2000 with the data on the server. The applications are GL/AR/AP/GV, all current versions with current Service Packs.

Has anyone seen this before?

Hi Bruce Gardner,

This sounds like a rights issue. Do they have permission to create, delete and empty files on their local hard disk?

Andrew:

It does sound likes a rights issue and yet .... there is no problem on the first pass. It is also the user's personal area on their C: drive. I will contact the LAN Administrator directly and confirm the assigned rights. I will update you then.

Andrew:

The problem is apparently resolved. The client went into her Temp folder and deleted as much as possible and now the reports consistently work.

What is strange is that she has had Admin rights all along.

At about the same time that the problem first appeared, they had a server problem which interrupted a GL batch posting (the damaged data problem was resolved). Does GL posting use any temp folders? Could it have any bearing on later reporting?

Thank you.

Bruce:

All sorts of strange things can happen if the "temporary" files in the \windows\temp folder are allowed to accumulate. It seems that they may, somehow, use some Windows resources.

I usually recommend clearing that folder every few months.

As a general rule, I think that your idea makes very good sense Ralph.

Unfortunately in this case, the problem was not resolved. The client has reported the same problem this afternoon but with one more piece of information. The temporary folder created within the Temp folder is left behind after the report finishes and it cannot be deleted using Windows Explorer. I've asked the client to determine what relases the lock; Re-starting Adagio? Logging back in to the PC? Re-starting the PC?

Bruce:

I have had a few occasions in which the only solution to intractable Windows 2K problems was to add a new user and transfer the e-mail and other settings to him. (Instead of BOB, use ROBERT perhaps.) This also means adding that new user to the server, of course.

You will have to re-run the Adagio workstation setup as the new user.

Ralph:

We are getting closer to the point of re-creating the user as you suggest but can't help thinking that there is a logical answer ... somewhere!

Since my last posting, the following has occurred:
-Client ran Adagio Workstation set-up again -> reporting appeared normal
-Next day the I.T. department reinstalled latest version of NAV ->problem appeared again

The client has determined that the temp folder created by an Adagio reporting process remains for at least 3 minutes after the report is closed. It cannot be deleted manually. Then it disappears on its own.

I know that this is an environment problem, not an Adagio problem. And I suspect that NAV is involved somehow but have found nothing in their knowledgebase.

Has anyone seen symptoms like this with Windows 2000?

Thank you.

Bruce,

I think you are getting a lot closer to tracking down this annoying problem.

I will resist the temptation to post my usual nasty comments about Norton products.

You might see if you can determine the file name(s) used for the temporary report files and see if they can be excluded from the NAV scan. Or perhaps the folder itself can be excluded.

Ralph:

Thank you for your advice on this issue.

I think that Softrak Technical Support shares your nasty comments about NAV because they are suggesting McAfee as an alternative.

NAV is a corporate standard for the client so I've asked them to remove the Temp folder from auto-protection to see if that helps.

I will post the final resolution ... when it finally becomes final!