Sage 100

Have a client on 100 Advanced 4.4.6 using work order. About every 4 transactions or so, they are unable to update the transaction register due to the message below. According to the user, she is the only one using it and when you look at Master Console, there is no one else accessing it. We have to get everyone out, stop the service and end all phantom pvxwin32.exe processes which clears it but it happens again and again. Could be user error but just looking for other ideas.

Do they get this right away, or after it's started processing?

They print and then when they should get the prompt to update, they get this message. No update starts.

Do they always end out? Have they ever let it sit a second and do a retry?

Good question! I'm not sure but I'll suggest they try that next time it happens.

Seems like I've seen it somewhere else - maybe Payroll register? where it just seems that it goes to the prompt before it's done doing some processing in the background and the file is still in use.

Makes sense. I told the client to give it a chance to catch up with her - gotta love those legacy modules!

I have seen this when the user will have more than one transaction window open and not realize it and then try to do an update.

An update on this issue: It appears WOK_TransRegisterSortofWOR (WOR_TransEntryCloseWo or W/O Transaction Entry Header File) is not gettiing cleared after a transaction register is updated. WOK only contains the transaction type and number and the info that was in it for this customer was for a transaction they updated this morning (Geez, I love paperless journals and registers for digging into these issues!). I was able to delete the record through DFDM and the user can now update the register but I'm wondering WHY it is not getting cleared OR if I'm totally misinterpreting what is happening here. @BethBowers are you familiar with this file?

Any possibility of installing PU 10? There are 12 patches related to WO released since PU 6 plus there may be another fix in another module that may impact it also. Just a thought? When a client starts reporting wierd stuff, I always suggest the latest PU. It works more often than not.

Worth a shot @JeffSchwenk. It's just that this client has SO much going on right now, I hate to throw something else in there.

Completely understand about limiting the variables. I hate PU's that fix one thing but break two others.

If they are not using batches, clearing a file like that usually means deleting it and recreating it. I have had situations with an AP invoice entry file that was caused by the Anti-Virus - in that case, it would delete the file but the AV prevented it from being recreated, so the file was MISSING. Perhaps in this case your AV is keeping it from being deleted...

I'm trying to figure out what this file does. I think it may keep track of close transactions where you get the prompt for additional reports as in, if you don't print them, you'll get prompted for them after the next transaction? (Totally guessing here.) @DebThomas (the other mfg guru) are you familiar with this?

Even more bizarre, it is NOT deleting the record from WOK - it is simply copying the data to another company, then going to that company and back again that clears the lock. WTH???

Calling all MD's...........

As in Medical Doctors since I'm about to have a breakdown??? Or I'm about to have a beer, can't decide....

Perhaps I meant Miller or Michelob Draft? When I have difficulty with the Sunday crossword, I put it down, do something wild and fun, then come back to it. Seems those answers just appear before my eyes then.

Here's a stab. When the condition ocurrs, everyone needs to exit and pvxwin32 processes killed. Could this indicate that a file is locked by the OS or AV and creating the issue? On the other hand, if this was the issue, you'd expect to see other updating having the same issue. Here's an idea, when this happens have eveyone exit and look at which MAS files are open and by who/what.

We've done that - had all users exit, stop the service, end all pvxwin32 processes - and there are several. Yesterday, I copied the company, deleted what I thought was a rogue record in WOK, and was then able to update the register in said company. Went back into live company, did the same thing and was then able to update the register so I THOUGHT it was WOK. Happens again later, I try deleting the record in WOK but it doesn't let me update. Hmm, what did I do differently? Well, I copied the company AGAIN, switched companies and back again and NOW I can update. I'm thinking switching companies is what released the lock - but WHY would that do it??? Or is the copying???

I am no expert in Work Order but here is a couple thoughts. 1.You could try turning off opportunistic locks on the server. We usually do this to fix a Cascading Lockup when an opportunistic lock occurs on a MAS system file; however, we have also used it when things seem to just lockup in a certain operation. 2.As Beth mentioned, a Delete and Manual Re-initialization of the data entry files sure can't hurt. We have had situations where DFDM called a file empty but delete and re-initialize got rid of the junk.

Hi @ThereseLogeais, sorry for the tardy chime in...was out all day yesterday. My suggestion would have been the same as John's second note. Too often it appears that things are clear, but they really aren't. Reinit all the WO Trans related files, then try again. It's worked for me in the past. But I'd also see if you can do a ""quick"" update to PU10. They broke a few things and this maybe one of the fixes. Haven't really reviewed them in detail, but certainly worth a shot.

It just happened again. I connected to her desktop and now I think I know the problem - they have ACS's Multi-Bin enhancement and I think that is what is locking it up. They do completions to bins and I think if they cancel the transaction, the bin record is locking WOR (at least that's my latest guess!). She said she entered one then had to cancel it. When she went back in to enter it, she could but it wouldn't let her update it. I""M SO GLAD IT'S FRIDAY!!!

Very honorable for you to post that there was a MD enhancement installed...

I didn't realize it until I went to reinitialize the WO transaction entry files and saw two of them had asterisks in front of them. Looked at the installed apps listing and saw the mod. Once I cleared the lock, I watched her enter a completion and saw the bin field. Yesterday, I wasn't looking at the transaction detail, only that there were transactions entered. My bad, I know...

Say ""hi"" to Ron C for us! Are there any early bird specials at TGIF's?

We have a special waitress at TGIF's - we had her one time and she was good. We ended up getting her a second time and she remembered everything about us - what we liked to drink, how we liked our food cooked, etc. We started asking for her and now we're like buds. She gives us great deals all the time. Now I'm hungry for TGIF's, haven't been there in a while.... Alas, BBQ'ing steaks for my son's birthday tonight...

I think we all have our ""special"" hang out restaurants. When the bacon, egg and cheese biscuit was first introduced at McD's, I would stop on my way to work to pick up one. It got to the point at the drive up order spot, when they said ""welcome to McDonalds, May I take your order"", I would just say, ""I'll have the usual"". In retrospect, since it was McD's, I should have been embarrassed.......... Then there was the local pizzaria that addressed their Christmas card to ""The Watsons"" and taped it to the pizza box when I came in for our Friday night Sausage and Mushroom pizza. I always gave my wife's maiden name because Schwenk was usually mangled by the order taker (before caller ID)...............

Yeah, we've spelled our name Lojay when asked for it, otherwise, we miss our name being called. It's not technically phonetic but it's closer than hearing Lojuss or Logayus.