Sage 100

2013 to 2016 standard upgrade crashes during data migration phase. ""prepare failed with the following error""...something about views being invalid. Never ran across it before and Sage is stumped. Not much in the KB related to views but what is there was tried.

Did it give you a file name? If so, rebuild key file, rebuild sort files.

unfortunately it didn't mention a specific file name. the view files all begin with ""pvxview.XXX"" and are not available to the rebuild system files utility. closest kb hit was this: Open each of the following PvxView.* file located under MAS90 folder through Data File Display and Maintenance 1.Open Sage 100 source installation 2.Open Library Master, Utilities, Data File Display and Maintenance (DFDM) 3.Select browse icon (Folder) 4.Open each of the following files one at time through DFDM Note: If you receive the message 'Invalid file type' when opening any of the files listed below proceed to Step 5 ?PvxView.gdp ?PvxView.grp ?PvxView.itm ?PvxView.lnk (note: .lnk extenstion might be hidden) ?PvxView.src ?PvxView.vue 5.Rename the corrupt file(s) to PvxView.xxx.bad (xxx= file extension) 6.Restore the file(s) from a good backup NOTE: If no backup is available, make a copy of PvxView.xxx.old and rename to PvxView.xxx (xxx = file extension) 7.Re-run Migration

Probably not an exact match but this is all I could find: Problem / Description: While trying to apply a SU to Sage 100 v4.4 the following error appears: Prepare failed with the following error: Error 84 opening PvxView.LNK at line 364: No DICTIONARy exists on OPENed file Resolution: Rebuild BIR views under Library Master > Utilities

thanks @WayneSchulz, Thanks @RobertaChase

here is the exact syntax: Error: Prepare failed with the following error: The views import failed with the following error: views error #1512 - ViewCtl: Import() SError writing data source item (pvxview.itm)

Hi- some questions: do you have reports or other uses of the views for this client, do you have MD mods or any other complexities ?

I don't know if under LM / Repair if Rebuild BI Reporter Views is still there but you could try running that on the 2013 system then try remigrating. It rebuilds the pvxview files. You could also look to see if there are BI Reporter reports and if not used anymore remove them.

We uploaded a copy of the MAS90 folder to Sage. They suggest reinstalling update 9. Assuming they tested this on their system. Guess we'll find out.

Reapplying update 9 fixed the problem with migrating the data. Sage came through.