Sage 100

Anyone recall the super secret command to launch the system files rebuild utilities? I have an error in the SY0CTL file (MAS200v4.50.0.6) and IT hasn't been able to find a good back-up. Working to resolve error 1 WOWDBB 7455, error 11 WOWUBE 1015, error 1 WOWUBE 2455. All error point to the SY0CTL WO Company Record. If I can't repair the SY0CTL, the next step is to re-install the System and Library Modules. Not fun...

Rebuild Sy0ctl.soa with SVXBLD. 1.Have all users exit Sage MAS 90. 2.Open Windows Explorer and go to ..\Mas90\Home 3.Double-click PVXWIN32.EXE (or right-click the file and select 'Open'). 4.Click the 'Ok' button on the splash screen. A blank screen with a 'Greater Than' ( > ) prompt should appear. 5.Type RUN ""SVXBLD"" (with the quotes) and press 'Enter'. SVXBLD should open. 6.Select SY0CTL.SOA and follow the instructions.

Thanks Doug, I'll try it later today.

I think SVXBLD was replaced by SY_RebuildSystem.m4p.

Thanks Robert

Confirmed in 2013

If it doesn't work there is still *ufar just make a backup of file first and right arrow to select D Wrong and E Wrong when you get to the question about the assumptions

Here is the article&link: https://partners.sagenorthamerica.com/irj/go/km/docs/sageKM/Sage%20MAS%2090%20and%20200/Gated%20Customers/Warr_Svc_Support%20Plan/529083.html . Or you can type in the Sage KB search field: 529083.html

*ufar has worked well for me in the past.

Humm...the sy_rebuildsystem utility thought something was still accessing sy0ctl, even after a server reboot and ensuring MAS services were off. *Ufar ran OK, but the error was not resolved. Seems like a re-install is on the schedule. Are there any other suggestions?

That happened to @ThereseLogeais too with Sy_RebuildSystem of Sy0ctl - must be a bug. Looking at the Error 1's they are all WRITE's of the ""W/O"" + COMP$ key to SY0CTL (that is it's writing back the options record). An Error 1 would occur if the length of what's being written is the same or longer than the record size of sy0ctl. So on one of the Error 1's, click on Info / Debug then type ? LEN(WOOPT$) If it's 256 or higher, that's the problem. I am presuming the record size of your sy0ctl is the standard 256. Perhaps you have some extra garbage in the [W/Occc] key of the WO0ccc.SOA file (ccc = company code).

I should give you another ""You Rock!"" since you have an excellent memory as well @AlnoorCassim !!

And because he does rock.

Well, after looking at both the SY0CTL and WOccc records they seem the same size and content. @AlnoorCassim the record length came up 255. This seems like a wild goose chase / red herring error.

I created a back-up company and copied all modules except WO. I re-set-up WO Options the same at the erroring company. After testing it did not create an error. I then copied the WO0ccc file from the working back-up company into the erroring company. I was prompted to ""set-up the work order module"". I copied all setting setting from the back-up company. After testing the error is now gone. I would conclude the WO0ccc.soa file was damaged (not SY0CTL). Case closed....for now :)