Sage 100

Trying to do an SU and keep getting that pvxwin32.exe is in use or user's are in the system. They're not and it's not. It's just Std - what could possibly be the issue? Rebooted server and still the same.

Do they have CRM or any other processes ""connected"" to Sage 100?

Would the PEP program or the Sage Advisor give you that message? Also, Starship would do that, I believe. Sage Intelligence?

No CRM, no Starship, and I stopped Sage Advisor.

Is there anything stuck in master console Beth?

Could some user be pulling data via odbc?

What about checking the SY0CTL file for a uti record that might be stuck there?

Nothing in Master Console. They did have a shipping thing that used ODBC but we shut that server completely down. I'll check the SY0CTL file.

Are you running the SU as administrator? Could there be a rights issue?

Reboot the server???? Is the CRM service running??

Hey Beth, when this happens to me I usually go into the Management Console of the server and close down any open files. It used to be easier before the R2 versions came out but it is still in there somewhere.

Have you checked to see if there is any PVXWIN sessions still in use in task Manager? You can also go to Computer Management and look in the Shared Folders/Open Files and see if any Sage files are in use.

On the server, run FSMGMT.MSC and check the MAS share to see if anyone remotely is touching PVXWIN32.EXE. If there's nothing there, download and run Process Explorer (http://live.sysinternals.com/procexp.exe). When it opens, go to Find \ Handle or DLL, then type PVXWIN32.EXE and hit Search. This should (hopefully) give you the process on the server that is touching the file. If there's nothing there either, then it's a SY0CTL thing...

@SteveIwanowski - I'll try this tonight if still having the issue. Task Manager showed nothing, Management Console showed nothing, was running the SU as Admin, and had rebooted server.

Thanks @SteveIwanowski for the shortcut - I've been meaning to look up that program to use on our Win 2012 servers - so tired of trying to find the dang thing!

Wrong server. Don't ask. All is well now.

I have to ask.............

Client was the one logging me into the server via RDP. Servers were APP1 or ADD1 and he was clicking away so fast I didn't notice the error (probably wasn't wearing my glasses that night).

Gotta love those clients...