Sage 100

Client on 4.3 with some mods that make me fearful of reloading anything. System is hanging on Period End processing, Rebuild Files, Rebuild Sort Files. All seems to be related to maybe deleting a file, or renaming? However, cash receipt update went through OK. Hanging is happening on all companies, including a test company. If I try to rebuild just a single itty bitty file, it sits there forever, at about 50% CPU usage, never finishes. If you look in the folder, you can see the .NEW, .NFT, and .NFW but the .M4T still has the original date on it. Period End, in PO, for example, goes through purging, etc, but hangs with no message and never finishes. Turned off AVG while testing. Opened up more disk space. Only thing done recently was a KS upgrade, and I even turned that server off, just in case. BUT, since they haven't rebulit files in ages and last period end was a month ago, whatever it is could have happened any time in the last month. Any suggestions OTHER than reloading programs?

SYOCTL issue? Any old copies lying around you could slip into there to see if they cause the issue to go away? I supposed there are probably 1/2 dozen other report files that maybe are tracking month end reports as well. I'd vote with something more on the overall system side since you are getting the same results in all companies (I'm assuming that implies dummy ABC data).

Have you tried a server reboot?

I'll check out the SY0CTL tonight. Have rebooted twice so far...

Plan B = Make a backup and start swapping system files

It's gonna be a loooooong night.

My impression that this cound be an environmental issue. How healthy is the server? If RAID 5 are all the disks ok?

They were actually in a lightning hit about 6 weeks ago. No RAID. Old server. Could easily be related, but how to prove...

Copy install to local machine and run rebuild.

Are there any other ""MAS90"" directories on the server? Never got an explanation as to why, but apparently having copies of MAS90 around can confuse MAS. If you rename ""MAS90"" in the copies the problem goes away.

did anyone accidentally create a few thousand GL accounts? I had a customer do that once (ended up with a few hundred thousand accounts) and brought period end to its knees.

I'll see if the IT guy can copy - he's local and I'm not.

Have you tried re-naming the Activity Log. If that gets really big it can cause problems.

Good point Louis.

Sent off email to IT - we'll see what we can accomplish tonight. All activity processed and updated with no problems today, strangely enough.

@LouisAraiza wins the prize - it wasn't that the SY_ActivityLog file was too BIG, it was CORRUPT. The size was actually only about 618 KB, which is pretty much impossible right there for someone who has been on 4.3 for 2 years, and when I ran the report it popped right up, but the times all said 00.00:00 and the program had the date in it, etc. I put in a blank file and was able to rebuild files and close periods. YAY LOUIS!!!!!!!!!!!!!!!!!!!!!!!!!!!