Workstation unable to run Inventory Valuation Report (T2351.tmp) 1

[kgauvin]

I have one PC that appears to be the proud owner of a hung process. This workstation is unable to run modules>inventory management>reports>inventory valuation report. The exact message is [ Error #12 File does not exist (or already exists) ]. I believe the fix lies in "Data file Display and Maintenance"...if for no other reason than the fact that I cannot delete the respective file from the "textout" directory. This program is not my forte .....any help would be greatly appreciated.

Keith G. Gauvin
(A+,Server+,MCSA,SCSA)

 

[PgmrChris]

You may want to check user rights to that directory. Some MAS90 reports build work files and they are named with the workstations internal terminal ID + ".TMP"

 

[mzenzer]

I'm getting the same error and this thread is one of about 3 hits on google when I searched the error. My error takes place when accessing modules>Library Master>Common>Sales Tax Class Maintenance.

The funny thing is, it's a small network with 5 PC's and a server. 4 of the PC's are win98 and 1 is XP. The XP machine works fine, but NONE of the win98 machines work. The server is a win2k server.

The default security on the mas90 directory was as follows:
Everyone: Full Control

I changed it to:
Everyone: Full Control
(The user) Full Control
Administrator: Full Control

I told it to propagate downward, and check files deep in the folder tree and they had the above security settings.

Any thoughts?

 

[CsaintAZ]

Keith,

If the process is hung, you may be able to delete the share on the file in question. If that does not work, and it is not an inconvenience, take the server down and restart it. That usually resolves any really stubborn locks.

If you still experience the problem, you may have a corrupt workstation file. To fix this, get the Computer Name having the problem, go to the mas90\home directory on the server and edit the fid0map.ini file with notepad or any text editor (fid"zero" not fid"Oh&quot. You will find the computer name with a terminal ID next to it. Change the terminal ID to another one not being used by another workstation. Be sure to just backspace out the old number, and type in your replacement. Then save the file. Don't hit enter or add any other characters, spaces, etc. Go back into MAS using that PC. You will have to select the default company since MAS thinks this is a new PC logging in for the first time. You may also have to change any preferences for that workstation using file, preferences. Then rerun your report.

One final note: We have experienced a similar situation when we access a client network through Terminal Server and modify a file. For some reason, the file security is changed. Even though the folder and specific file is set to inherit rights from parent folders, which by the way have full rights, a look at the file's security properties shows that the Everyone group has been dropped. We edit the file right as Admin and everything works fine. (At least until we modify it through terminal server again)

Hope this helps. If not, let us know what the results were from the above suggestions. Also, the name of the offending file would be helpful.