Sage 100

Working on a 4.2 to 2013 test upgrade. Launched VI Import Job Maintenance for the first time. There are 32 import jobs and 20 export jobs listed in the lookups. 16 hours later, it's still ""Checking framework job file linkages"". Except, I think it's in an endless loop. I don't think I can do anything but kill it. Before I hold my breath and do that, anyone had this experience and have an idea what's going on?

Here's a previous thread: https://90minds-com.socialcast.com/messages/13592242

Thanks Therese - rebooting server now (that VI Job Conversion task doesn't want to die). Will report back.

Ok, so I can find VI1JOB.SOA, but there is no file named VI_JobHeader.M4T. I didn't find one in my local 4.5 either. I looked at our company 4.5 and 2013 also. Although the 2013 File Layouts has one. What am I missing?

VI1Job.soa is empty.

Found VI_JobHeader.M4T in MAS_System. No null records or ones that look ""off"" to my eyes.

At this point, would it be simpler to reinitialize the VI file, then import the jobs from v4.2. I think you have to rekey any job involving IM, BOM and PO's don't you?

Sounds like a good idea. Which file(s) need to be re-initialized?

Now you ask the hard questions..... Not really sure.

@AlnoorCassim ?

When you go to Import Job Maintenance, it first looks for VI0JOB.soa (3rd letter is zero and 5th is O like Oh crap!) . If not found, then it goes through the ""1st time routine"" of preparing V/I. I think if you just force a VI0JOB.soa you can then at least get into Import Job Maintenance and assess the situation. Since it always stays an empty file you can just copy in the one from your 2013 system. Otherwise you can run this from SYZCON to create one: ? %SYS_SS'CreateTable(""VI0JOB.SOA"",""VI"") It should return a 1 and create it in the VI folder. Then type BYE to exit.

@AlnoorCassim , I did the SYZCON step and got a 1, but VI0JOB.SOA is still empty. I didn't check it first and launched Import Job Maintenance again and now it's out to lunch again. Did I miss something?

It should stay empty. It's just a placeholder file. But if it's out to lunch still then something else is wrong. Hard to tell without taking a closer look.

After determining which jobs are active, I used DFDM to remove unwanted job records from VI_JobHeader.M4T. Import Job Maintenance now launches.