×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Jobs

Error #12: File does not exist (or already exists)

Error #12: File does not exist (or already exists)

Error #12: File does not exist (or already exists)

(OP)
Hello,

First of all I will apologize that I know nothing about MAS 90. I'm an electrical engineer for a small calibration company. The guy that usually takes care of problems with MAS 90 is on vacation for the next 3 weeks, can not be reached, and we are having a problem with our accountant's computer. I'm trying to get it fixed for her and decided to post the problem here.

Last week at my job there was a problem with the accountant's computer. She was posting in MAS 90 and her computer shut down for some reason. After it came back up she noticed that something was not working correctly. Here is the issue:

Every time she is at a screen that has the option to Print or Preview she gets the following error when she clicks on Preview. Error #12: File does not exist (or already exists). File: ../home/textout/T1431.tmp.

We ran the error information listing and found this further information:

Error #12: File does not exist (or already exists)
Program: SYHEAD
Line: 4030

General Information
File: ../home/textout/T1431.tmp   T1431.tmp
Channel: 0
Key:

Last Channel Opened: 31
Last Channel Accessed: 7

Application: Library Master (3.51)
L/M Level: 3.51

I did a search on her computer looking for file T1431.tmp and could not locate it. I tried to reinstall the program via the instructions I found in the guy's office that installed MAS 90 and that did not fix the problem. I tried a System Restore and that created more problems so I stopped proceeding down that path.

She is running Windows XP SP3. The server where MAS 90 resides runs Windows NT. This problem happens in any module anytime you click Preview versus Print. Any help would be greatly appreciated. I can post more of the error information listing if that would help. I only posted what I thought looked important.

Thanks in advance,

~Andy

RE: Error #12: File does not exist (or already exists)

Andy, first you actually did too much. Most of what you did, you should not have done. Also you should be posting on community.sagemas.com  which is a free board for MAS90/200 users where power users, resellers and Sage tech support post. Here is your answer:

Error 12 SYHEAD 4030, "File ..\Mas90\Home\Textout\Txxx.tmp not found" when previewing reports
Entry Type: Program Issue

Product:
Sage MAS 90 ERP
Sage MAS 200 ERP
Sage MAS 200 ERP - SQL Server Edition

Application: Library Master

Version Reported: 3.x, 4.05

Status:

For current information on this issue, please click the Engineering Status link above. To record the occurrence of this issue, respond Yes to the question, "Did this answer help you?"

Subject:

Error 12 SYHEAD 4030 "File ..\Mas90\Home\Textout\Txxx.tmp not found" occurs when previewing any legacy (non-Crystal) report in Print Preview (xxx = user code).

Possible Resolutions:

For Sage MAS 90 and 200 version 4.x:

The error is connected with a specific user. To resolve, create a new user code.
If error persists, rename the *.tmp file listed in the error message.
For Sage MAS 90 and 200 version 3.x:

This error is more likely to occur in Sage MAS 200, but may also occur in Sage MAS 90.

The file ..\Mas90\Soa\SY0CTL.SOA may be damaged. Change the terminal ID for the workstation. If the report previews successfully, repair or replace Sy0ctl.soa.
If the error persists, the ..\Mas90\ folder might be shared so that the workstation sees only the subdirectories of ..\Mas90. For example, F:\Home\ instead of F:\Mas90\Home\.
Note: This applies to Sage MAS 90 only, not Sage MAS 200.
Remove the share from the \Mas90\ directory, and share the drive or a parent directory above ...\Mas90\. For example, with C:\Apps\Mas90\, share either C:\ or ..\Apps with Full Control permissions.
Remap the workstations to the new share point.
Reinstall Workstation Setup (...\Mas90\Wksetup\Setup.exe) on all workstations. Be sure to replace any Desktop Sage MAS 90 icons with the new icon.
The user may have insufficient network rights. Sage MAS 90 users must have full rights to the ..\Mas90\ directory and all subdirectories. For details, see the Sage MAS 90 Installation Guide.
If this error occurs on one workstation but not others, change the Terminal ID for the workstation.
Notes:

Sage Customer Support is not responsible for assisting with these procedures. Assistance by a qualified network technician may be necessary.
Step 3 is an unlikely cause, as rights issues usually cause Error 0 rather than Error 12. Follow step 3 only when steps above do not resolve the error.
On Sage MAS 200, users inherit the network rights of the User Account running HOST.EXT at the server. Any changes to rights should be made for that User Account only.  This does not apply to graphical forms or Crystal Reports, which depends on the user's individual permissions to the server.

How to change the terminal ID (TID)
Entry Type: Informational

Product:
Sage MAS 90 ERP
Sage MAS 200 ERP
Sage MAS 200 ERP - SQL Server Edition

Application: Library Master

Version Reported: 3.00

Subject:

How to change the terminal ID (TID)

Possible Resolutions:

Sage MAS 90 or 200 4.0 and later:

Delete all records for the computer name from SY_Workstation.M4T in Data File Display and Maintenance (DFDM).

Notes:

Changing the TID may not resolve issues on level 4 that were fixed on earlier versions by this method, due to changes in the way the TID is used.
Deleting rather than changing the TID is recommended, as it is difficult to determine which TIDs are already being used, and there is no advantage to changing the TID rather than deleting it.
As of Level 4.0, the TID is based on the computer name and user key combination. More than one TID exists for a workstation if multiple users access Sage MAS 90 from that workstation.
Obtain the workstation's computer name:
Open Sage MAS 90 from the workstation.
Open Library Master / Setup / Printer Preferences, or select File / Run / *INFO.
Note the computer name.
If Sage MAS 90 or 200 cannot be launched from that workstation, the computer name can be obtained from Windows.
Note: Sage Software Support is not responsible for assisting with this issue and takes no responsibility for changes made to your computers. Consult your computer administrator before making changes.
From any workstation, open Library Master / Utilities / Data File Display and Maintenance.
Open the ...\Mas_System\SY_Workstation.M4T file.
In the 'Key No' field, select "KPrimary".
Use the 'Browse' button to scroll to the first record that contains the 'Computer Name' and the 'Terminal ID' (field 3, 'Terminal ID$').
Note: The 'Key' lookup button may not display properly.
Click the 'Delete' button. Click 'Yes' at the confirmation prompt.
If necessary, repeat until all of the records for the 'Computer Name' have been deleted.
Click 'OK'.

The new TID is created automatically when Sage MAS 90 is accessed from the workstation. If the change is made at that workstation, the change occurs as soon as DFDM is closed.
Sage MAS 90 or 200 3.71 and earlier:
In Windows, Terminal ID numbers are automatically assigned by Sage MAS 90 and 200 and written into the ...\Mas90\Home\FID0MAP.INI file, with a value from 101 through 400.

Note: Values 105 and 328 are redirected to 401 and 402. Sage Software recommends assigning 105 and 328 to an unused computer name. For example, enter "Do not use" (without quotes) to prevent the system from automatically assigning those numbers in the future.

Open ...\Mas90\Home\FID0MAP.INI file and change the Terminal ID for the workstation to the next available value from 101 through 400. If this resolves the error, the original teminal ID record is damaged in SY0CTL, and SY0CTL should be repaired or replaced. For more information, see How to repair, rebuild, restore, or replace SY0CTL.SOA.

To change the Terminal ID number:

Close Sage MAS 90 on the workstation.
In Windows Explorer, open the ..\Mas90\Home\FID0MAP.INI file in a text editor, for example, Notepad.
Locate the workstation's computer name.
Change the value after the semi-colon to an unused value from 101 through 400. Verify that the value is not already being used.
Note: If any additional characters (for example, asterisks) exist, another user may have modified that line so that it is not used by the system. It can probably be deleted from FID0MAP.INI.

For example:
For computer USER_01, the corresponding line in ..\Mas90\Home\FID0MAP.INI reads as follows:
USER_01 ; 101 auto assigned 8/10/98.

Change to:
USER_01 ; 111 auto assigned 8/10/98.

Save and close the FID0MAP.INI file.
Restart Sage MAS 90 on the workstation.
Sage MAS 90 should prompt for a company code. This indicates that the Terminal ID has not been used before.
Auto-assignment may not work properly on some Novell Networks. Use the following procedure if the workstation is not being assigned a unique Terminal ID:

To manually override the Auto-Assignment:

Open the C:\AUTOEXEC.BAT file.
Insert SET MAS90FID=Txx (xx = 01-99) as the first line of AUTOEXEC.BAT.
Save and close AUTOEXEC.BAT.
Reboot the workstation. This overrides all other settings.  
Terminal ID numbers were identified as "SET PVXFID0=Txxx" (without quotes, where xxx is an integer between 0 and 400), in the AUTOEXEC.BAT file of each workstation running Sage MAS 90. To change terminal ID in this scenario, edit AUTOEXEC.BAT and change Txxx to a new number between 0 and 400.

How to repair, rebuild, restore, or replace Sy0ctl.soa
Entry Type: Informational

Product: Sage MAS 90 ERP, Sage MAS 200 ERP

Application: Library Master

Version Reported: 3.30

Subject:
How to repair, rebuild, restore, or replace Sy0ctl.soa.

Possible Resolutions:
Note: When this file becomes damaged, underlying cause(s) should be determined prior to or after applying the suggested workarounds below. Obtain all necessary information from the Installation Troubleshooting Templates on the Sage Software web site in order to properly determine probable causes of damage to this file. If this is a recurring problem, keep an undamaged backup copy of SY0CTL.SOA in the ..\Mas90\Soa directory for ease of replacement. Be sure to update the backup every time Sage MAS 90 is upgraded to a new version.

Perform one of the following procedures (listed in order of preference):

Rename and restore ..\Mas90\Soa\Sy0ctl.soa from a backup.
Note: Be sure the backup is the exact same version as the file being replaced. (for example, do not replace Sy0ctl.soa for Sage MAS 90 3.61 with a backup from Sage MAS 90 3.60 or prior.
Note:  Sage Software Customer Support is not responsible for assisting with this procedure.  Assistance by a qualified computer technician may be necessary.


Rebuild Sy0ctl.soa with SVXBLD.
Have all users exit Sage MAS 90.
Open Windows Explorer and go to ..\Mas90\Home
Double-click PVXWIN32.EXE (or right-click the file and select 'Open').
Click the 'Ok' button on the splash screen.  A blank screen with a 'Greater Than' ( > ) prompt should appear.
Type RUN "SVXBLD" (with the quotes) and press 'Enter'.  SVXBLD should open.
Select SY0CTL.SOA and follow the instructions.


Rename SY0CTL.SOA and reinstall Library Master and all modules.
Note: Before proceeding, print the 'Install Applications' listing and 'Product Registration'. If modifications or enhancements to Sage MAS 90 have been made by a third party Master Developer, the consult the Master Developer before performing this task.
Rename ..\Mas90\Soa\Sy0ctl.soa.
Reinstall Library Master only.
Note:  If desired, all other modules can also be installed if testing the new Sy0ctl.soa is not necessary.
Start Sage MAS 90 to verify that the error no longer occurs. If the error has been resolved, exit Sage MAS 90 and reinstall all other modules listed in the 'Installed Applications' listing.
Start Sage MAS 90.
Re-enter company codes in 'Company Maintenance' to relink data files.
Re-register all applications, including 'System Activation', in 'Product Registration'.
Reenter any other customizations necessary, depending on the installation.
Note: Be sure to reinstall the correct version of Sage MAS 90. Edit Ssread.txt and Lmread.txt in ..\Mas90\Soa to determine the last version installed. Every module has its own XXREAD.TXT file in the ..\Soa directory (xx=application, e.g. AR, GL). Be careful not to install a prior version of SS, LM or any of the modules or more errors will occur.


Change the terminal ID (TID) for that workstation in ..\Mas90\Home\Fid0map.ini.
Note: This may not be applicable for all errors or issues. Use this method only if errors occur at one workstation which indicates a damaged TID record in SY0CTL.
Note: This is only a workaround for the error. It does not repair the damaged record. The SY0CTL is still damaged and should be repaired or replaced.
Open ..\Mas90\Home\Fid0map.ini.
Locate the computer name for that workstation.
Copy the entire line to the bottom of the list.
Change the TID number in the original line to a previously unused number between 101 and 400.
Change the computer name on the copied line to a computer name that is not used on the network (e.g. "xxxxx").  This will prevent Sage MAS 90 from automatically assigning that terminal ID number to a new workstation.
Save and close Fid0map.ini.
Start Sage MAS 90 from that workstation.
Verify that Sage MAS 90 prompts for the company code during startup. This indicates that Sage MAS 90 has no record of this TID.
If the company code prompt does not appear, close Sage MAS 90 and select a different TID for the workstation.
Note: If the company code prompt does not appear, the TID is either being used by another workstation or has been used in the past and was replaced

RE: Error #12: File does not exist (or already exists)

(OP)
Thanks BigLouie and sorry for posting this in the wrong place. I was able to get this issue fixed this morning. All I had to do was restart the server and this fixed the problem. Thanks again,

~Andy

RE: Error #12: File does not exist (or already exists)

Restarting the server fixed the issue because the TMP file was locked by the server.  So when she went to preview/print a report, it could not create the temp file for her terminal ID.

Dawn

Visit Sage's Online Community
http://community.sagemas.com/sagemas/?category.id=SageMAS90and200Disc

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close