x Want to participate? Join the group to interact
Options
  • Replies 9 replies
  • Subscribers 109 subscribers
  • Views 6916 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
47
topics
95
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
965
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
HOWI

"The current file's data dictionary definitions do not match those of the new file."

Posted By

We have just installed a new server and moved MAS90 4.30.0.12 to this location. After running Rebuild Key Files in Library Master Utilities we are seeing this message (see subject) in some of the files. I have researched the knowledge base and the forums and find the same "resolution":

 

The current file's data dictionary definitions do not match those of the new file:

Possible Resolution:Update the User-Defined Field (UDF) in the table that received the error message. Perform the following:1.     Expand Modules, Custom Office, and Main. Double-click User-Defined Field and Table Maintenance. 2.     Double-click the module that received the error. 3.     Double-click the table that received the error. 4.     Click Add. In the Field Name field, type a new field name. Fill out the rest of the fields. 5.     Click OK. Close User-Defined Field and Table Maintenance. 6.     Expand Modules, Custom Office, and Main. Double-click User-Defined Field and Table Maintenance. 7.     Double-click the module with the new UDF. 8.     Double-click the table with the new UDF.

9.     Click the UDF. Click Update.

  

I may be a slow learner but would someone please explain to me why this is the fix? I am seeing this statement for files in modules that do not have any UDF's. If this is the fix do I need to set up UDF's for all of the 30+ affected files and just leave them to collect dust?

Your time and feed back will be appreciated.

Bill

  • Uno - Welcome to the Sage Community

    Dos - Update the data dictionaries in Custom Office. Rebuilding the Keys has NOTHING to do with data dictionaries.

  • BigLouie wrote:

    Uno - Welcome to the Sage Community

    Dos - Update the data dictionaries in Custom Office. Rebuilding the Keys has NOTHING to do with data dictionaries.

     

    Except that the rebuild key files would need the info in the dictionaries to interpret the files.

  • When you moved MAS to the new server, did you delete the uninstall info directory on the new server and then reinstall from CD's and service updates over the top?

     

    Note that in moving you should have copied the entire MAS 90 directory, not just the data directories.

    Message Edited by TomTarget on 06-11-2009 08:57 AM

  • We did a "fresh install" of MAS on the new server... installed the latest service pack... and then, we brought over the company data. Not sure what you mean by "did you delete the uninstall info directory on the new server". However, ultimately I think I understand your point about the data directories.

     

    It still appears as though reinitializing the data files is the way to correct at this point.

  • HOWI wrote:

     

    It still appears as though reinitializing the data files is the way to correct at this point.

    NOOOOOO!!!!!!!!!!!!!!!!!!  Re-initializing the data files would have absolutely NO impact on the error message. At this point I would suggest a call to your reseller.

     

    Can I ask one question. In the old install did you have UDFs?

  • BigLouie wrote:

    NOOOOOO!!!!!!!!!!!!!!!!!!  Re-initializing the data files would have absolutely NO impact on the error message. At this point I would suggest a call to your reseller.

     

    Can I ask one question. In the old install did you have UDFs?

    We did (do have) UDF's but not in the all the modules that received the same errors. (ie SO does not have any UDF's but has 14-.M4T files with this error)

  • Ouch!  Could be bad news because of not doing correct procedures for the transfer.

     

    When UDF's are added, the data dictionaries are modified.  A fresh install and copying data files would not necessarily update the data dictionaries for the UDF's.  I suspect that adding them back after the transfer would not necessarily put things back correctly.

     

    Hope you have not done a lot of data input already in the new system.

     

    AND TO DOUBLE EMPHASIZE -  DO NOT RE-INITIALIZE DATA FILES!!!  THAT MEANS DESTROYING ALL THE DATA CONTAINED IN THE FILES!!

     

    I concur with BigLouie.  Get your reseller involved sooner rather than later.  You are flirting with disaster.

  • Just for closure...

    We ended up having to restore the providex.(dll,dde,ddf,prm) from the original locations files. Also restored ###.### from the Custom folder. No data loss or no need to redo any data entry.

    Thanks for all the responses.

  • in reply to HOWI

    This is a very old thread but we ran into identical error on ERP2014: for unknown reasons data dictionary was damaged or mismatched on a dozen random tables. Solution was to restore providex.* files from backup, along with DDICTS folder (not ###.###). THEN add/edit UDF in each affected table to force update of data dictionary for that table. So far no data loss/corruption discovered... we'll keep our fingers crossed.

*Community Hub is the new name for Sage City