Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Purchase Order Error

Status
Not open for further replies.

toodamfat

Technical User
Aug 21, 2006
3
US
MAS200 v4.0

I'm getting the following error:
-Record 4000719 in PO1 Purchase Order Entry Header File is in use by another task.

Then I click in Info and it reads:
-Error#0: Record/file busy
Program POWDAB Line 1315

Any idea why this particular PO is being used by another task?
I'm not able to edit/delete the PO nor able to receive it because it gives me the above erro message.

Thanks for your time,
 
This means that someone else has the record open. See if anyone else is in purchase order. If not then you may need to reboot the server to release the locked file.
 
Thanks for the response.

No one else is in the purchas order. I rebooted the server and the problem still persist.

Any other ideas?
 
This is a bit drastic but it might be what you need to do.

Have all users exit Sage MAS 90 or 200.
If running Sage MAS 200 as service, stop the service.
Open Start / Settings / Control Panel / Administrative Tools / Services.
Scroll down the list and locate the 'Sage MAS 200 [port number]' service. Right click and select 'Stop'.
If running Sage MAS 200 as an application exit the 'Application Server Configuration' program
Open 'Windows Explorer' or 'My Computer' and browse to the ..\..\MAS90\MAS_SYSTEM directory.
Rename the SY_CONSOLE.M4T file.
Note: It will be recreated as users begin to log back into the system.
If an error message "Cannot rename SY_Console: There has been a sharing violation." occurs right click on the 'My Computer' icon and select 'Manage'.
Click the Shared Folders / Sessions directory and remove all active sessions going to Sage MAS 90 or 200.
Do the same with the Shared Folders / Open Files directory.
Open Task Manager and verify that PVXWIN32.EXE is not listed in the 'Process' tab.
If it exists, highlight the process and click 'End Task'.
Open 'Windows Explorer' or 'My Computer' and browse to the ..\..\MAS90\MAS_SYSTEM directory.
Rename the SY_CONSOLE.M4T file.
If the "Share Violation" message still occurs, reboot the server to release the locks.
If this is a Sage MAS 200 server running as a service, the service will need to be set to manual prior to rebooting.

Open Start / Settings / Control Panel / Administrative Tools / Services.
Scroll down the list and locate the 'Sage MAS 200 [port number]' service. Right click and select 'Properties'.
Set 'Startup' to manual then reboot.
When server comes back up, open 'Windows Explorer' or 'My Computer' and browse to the ..\..\MAS90\MAS_SYSTEM directory and delete the SY_CONSOLE.M4T file.
Sage MAS 90 users can now begin to log back in.
For Sage MAS 200 server running as a service:

Open Start / Settings / Control Panel / Administrative Tools / Services.Scroll down the list and locate the 'Sage MAS 200 [port number]' service.
Right click and select 'Properties.'
Set 'Startup' to automatic and then click the 'Start' button
 
This is going to take some planning. I'll let you how it goes.

Thank you for taking the time to help a newbie.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top