Share
ReportGot this error message:
A save operation on table 'MOP_ITEM_MASTER_' failed accessing SQL table. Looking for possible reasons why?
Thanks.
*This post is locked for comments
You’re offline. This is a read only version of the page.
730
Got this error message:
A save operation on table 'MOP_ITEM_MASTER_' failed accessing SQL table. Looking for possible reasons why?
Thanks.
*This post is locked for comments
The table in question is the PK010033. This table contains the picking tickets for manufacturing.
Is this a new install? Have MOs been released? The auto procs load and unload this file but will not rebuild it. Try running reconciles and checklinks against the manufacturing tables. If necessary, you may need to un-release all MOs (completing any that you cannot) and rebuild this file using SQL utilities to rebuild indexes, et cetera.
Richard, is this the script you're referring to?
No, it applies always if you are restoring one company to another db. Each db in GP is numbered uniquely and that number usually ONLY resides in SY01500. However, some of the manufacturing tables carry the company number. So if you restore company 1 to company 5 then some of the tables in company 5 refer to company 1 and errors occur. This script sets all company numbers to the correct number for the firm. HOWEVER, if you run the application and open company 5 (for example) before running this script, the script will find both company 1 and 5 records and Multiple Records Returned when One Was Expected (or some such message) occurs. You will need to edit these tables and remove the offending record.
Send me your email addresses and I will send the script. It was sent to me by Microsoft and works great.
Good afternoon Richard,
We get the same error and we have been running GP/MFG for over a year.
What I understand from your answer is that I should check that the item number in my MO should be created in both tables IV00101 / PK010033, I am correct ?
Also, anything in particular I should check in that table ?
Tx
Sebastien
Richard,
Is this script you mention only applicable if you are changing the name of the company that you are restoring to? We regularly restore GP databases to our test servers, but we only change the server name, not the database/company name.
Thanks,
Peter
That adds another twist. When you backup a db and restore it to a different company with manufacturing installed, you get a variety of errors. There is a script that MUST be run after the restore but before the restored database is accessed to fix a number of problems.
Email me at richardwhaley@hotmail.com and I will send it to you. It was provided to me by MS and works great.
The system could not read the data. It usually is caused by corrupt data. The MOP Item Master is a duplicate item master table and records there should generally match records in IV00101 (they should have the same items but some different fields).
Has the system been running long or is this a new installation of manufacturing?
You either have missing records or records that are only partially completed.
Hi, could be data corruption in the table, corrupt sprocs, or a user rights issue.
Get everyone out of GP and backup your company and Dynamics databases.
First port of call is to run a Grant.sql against the company database (and the Dynamics database for good measure).
(The Grant.sql script isfound in the Utils subfolder of the GP appliction folder)
If this does not resolve, you could try dropping and re-creating the Auto Proce (Tools >> Maintenance >> SQL..make sure you tick the last two options - Drop Auto Procedure and Create Auto Procerure - ONLY).
After that it could be data corruption. A select * against the table might reveal something.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
All responses (
Answers (