Sage 100

Weird error accepting a VI Job in VI Job Maintenance. ""Error 200 in VI_ImportJobCompile.pvc, Line 1638 while generating the import program."" I click OK to ignore and the VI works but I am just wondering what it is? Anyone seen this error?

What version and service update ?

It appears that it is failing to create the SY_Task_bus object which it needs to be able to add the V/I job to the menu or to run it from the File / Run prompt. I have no idea why creation of that object is failing, though. The error 200 is very generic, basically saying ""Oops! Something happened"".

V2015 SP1 (Premium)

Have seen similar errors when I already had the job open and then updated a second instance of it...

Thanks @PhilipWhirley So I checked the Sy_Task table and looks like it has a 999 records in it .... Very suspicious... I bet there is a limit of records in the SY_TASK table in the SY_Task_bus program.

Speaking with Sage Support now. Might be a corrupted SY_TASK file.

The issue turned out to be a missing Sy_menu table in premium. Now the tough part is recreating it.

Since MnuMod.txt and Sy_Task are in tact, use MnuMod.txt as your starting point. All ""regular"" task records in there (e.g. Vendor Maintenance) have the TaskKey (omit the leading 0). From there you can lookup the Sy_Task record. Between the data in Sy_Task (e.g. Name and Description) and counters and variables you maintain reading thru MnuMod, you can recreate most/all of Sy_Menu. Determining the ParentTaskKey could be a bit challenging. Probably need to make multiple passes reading thru as well.