Sage 100

Record in use error at just one workstation. This is Sage100 Standard version 2014 User #1 ran the cost rollup register yesterday nobody was in Sage100 and he received the attached ""Record in use error"" The error comes after the preview and after he clicks YES to update the cost rollup register. The error comes after the preview and after he clicks YES to update the cost rollup register. I've determined the cost rollup worktable is being populated. I've outlined the steps I've taken below, but it points to something specific to one workstation. Any thoughts on what I should do next would be GREATLY appreciated. (I'm going to call Sage when they open) I logged into their term server, verified nobody was in Sage100 I then tried to reproduce the error, but the cost rollup register ran fine. I then had user #1 try again Same error I connected to User#1 and logged into Sage100 with my login and got the same error I had User #1 reboot his workstation Same error I had User #1 go over to user #2's workstation and try NO error I rebooted their Sage100 application server last night User #1 tried again this morning same error I had User #1 log into User #2's workstation using his network login and try NO error

permissions??

Is there a file in the Lock folder for this company? If so, delete it and try again.

Are they accessing Sage 100 via the Term Serv? If so, probably worth rebooting that also. Or maybe first just check the Term Serv Windows Task Mgr for any hung processes (e.g., pvxwin32.exe).

Also, have you taken a look at that Work file via DFDM? Any leftover/bad records? Maybe worth just reinitializing it.

David, I'm having this same problem at a 2014 client. It has to do with the workfile not being able to be initialized. It has something to do at the workstation level. I've tried to get resolved with Sage in the past and they cannot help. Try previewing something else from that workstation, like the GL Trial Balance. Then close out of the preview and close out of the task. Then check the company GL directory and I bet the workfile did not delete. Normally temporary workfiles delete after you exit out of preview, or after the report is printed if you chose to directly print. I was just working on this issue yesterday with my client's IT guy. They have this problem ONLY when running Sage at the Sage server (which I do when I'm helping them remotely). I've been trying to get customers renumbered in a test company where nobody is in but me, and I get an Error 0 that the file is in use - which I had a MD programmer look at the code yesterday and he determined it was the workfile that it could not clear. As soon as I tried this renumber task from another workstation at the client (I'm on site), the renumber worked just fine.

the users are not logging in through the term server they are logging in directly and I thought permissions at first but the user logged into another workstation with his network login and did not get the error. I did look at the work file and it is populated correctly during the preview and it gets cleared out after we kill the error message.

Any temporary WRK files in existence? If so, delete them?

@JaneScanlan thanks, that is interesting. one thing about this cost rollup is that is does not even create a temporary worktable it just populates the BM_CostRollupWork.M4t then clears it back out. It would be good to test some other preview and see if it leaves the temp table stranded.

@JeffSchwenk same as above there are no temp tables created - I found that by looking for them in DFDM even when I had the preview screen up there is no temp table created so I looked in the BM_CostRollupWork.M4T and was surprised to see the records in that table.

@DavidOverholt yeah, some of the processes like that Rollup as well as renumber and merge utilities don't create temp workfiles - they use the base workfile - but either way it's trying to initialize it and it can't which I wish I could figure out where/why/who yada yada.

@DavidOverholt that's why I wanted you to see if printing a regular report doesn't delete the temp workfile because that would be your verification that the workstation isn't deleting (or reinitializing) workfiles.

What is you print, not preview?

@JaneScanlan - BINGO I see a LOT of WRK files for this user, they only date back to 9/17 so something recent changed which fits in with everything else I've learned. The user was able to run this at the end of August without errors. @JeffSchwenk good idea - I'll have him try that and update everyone.

Print or preview - didn't matter in my case - same Error 0.

No luck on Printing - still gets the error. I'm going to check with IT and see if anything changed on his workstation around the middle of September. This is the controller so leaving a boatload of stranded .WRK tables lying around it less than ideal.

As I noted in the earlier post, delete all of the temporary work files. del *wrk*1*.m4t and del del *wrk*0*.m4t does the trick for me. Of course IT will come back a big negative.

Maybe a MSFT update????

Have IT check their antivirus settings and make sure the Sage exclusions have been made.

also maybe worth deleting that Work file and manually reinitializing it to create a new one.

Deleting the workfile and creating a new one isn't the solution, because if you try this from another workstation it isn't a problem. If the workfile was bad, it would be a problem no matter which workstation you run the task from.

Can they preview other items, such as a sales order? If not, try and create a blank text file in the Sage 100 directory and see if it lets you. I had a similar error the other day and when I tried to do this it would not let me. I am thinking that either the profile of the user is corrupt on the workstation or the trust relationship with the server has been trashed.

This user can preview other things and Jane is correct that the *wrk.m4t tables are getting created but then they are left behind. I had him test one just now and that was what happened. anti-virus is going to be next. Profile and trust relationship sounds like a likely problems but that will have to be IT's job - way over my head.

@DavidOverholt I sure hope you are able to get resolution to this .. this wasn't so much of a problem for me previewing/printing reports and forms and then having the workfiles remain (other than a nuisance to have those temp files grow and grow), but when the error 0 occurred and I had an MD look at the code just yesterday, the lighbulb went on when he told me it was the workfile it couldn't reinitialize; that's when I told him about the stranded workfiles from reports and forms and we concluded that the workstation was not deleting and/or reinitializing workfiles.

Agreed, @JaneScanlan. I was just thinking that maybe there was something workstation-specific stuck in the Work file. Long shot, I know.

just to update everyone that I have not forgotten to post an answer to this. our internal network team worked on this computer for just over 5 hours yesterday uninstalling and changing about every network setting they could find and/or think of without any success. They changed policy of user, trust connection of the workstation removed the computer from the domain and re-added it. nothing worked to correct this problem so far.

@DavidOverholt I have a resolution finally to this problem. If the user has Crystal Reports installed, they need to install a CR Runtime service pack 14. Sage had an article posted about a related issue but said to install SP 12, which does not resolve. Once I installed SP14 I was able to run a delete/merge listing and proceed with the update. This also resolved the additional issue I was having with documents merging into another when previewing Crystal Reports or Forms. Attached is the Sage article, but you need to install a service pack higher than 12.

Thanks @JaneScanlan As far as I know this user has been going to another workstation since we worked on this almost a year ago, I'll give him a call; if this resolves it I bet he will be thrilled