Sage 100 locked up twice today. The first time we couldn't determine the PID of the user but we did determine the PID the second time. We hope the next time the lockup occurs it happens to either the same user or on the same computer. Below is the event log that resulted from the lockup. Can anyone make sense of this?
Version=1
EventType=APPCRASH
EventTime=132011968168166599
ReportType=2
Consent=1
UploadTime=132011968232971418
ReportIdentifier=c26426f5-6c22-11e9-80c8-00155d453a02
IntegratorReportIdentifier=c26426f4-6c22-11e9-80c8-00155d453a02
WOW64=1
NsAppName=pvxwin32.exe
Response.BucketId=e1f7d5b3a78f0e198c05fe1c60eefc34
Response.BucketTable=1
Response.LegacyBucketId=2019299405784349748
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=pvxwin32.exe
Sig[1].Name=Application Version
Sig[1].Value=9.60.4.0
Sig[2].Name=Application Timestamp
Sig[2].Value=5a83264f
Sig[3].Name=Fault Module Name
Sig[3].Value=pvxwin32.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=9.60.4.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5a83264f
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000013fa
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.272.7
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=5861
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=5861822e1919d7c014bbb064c64908b2
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=fdca
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=fdca1fbcc5199d38e99bdacef751acf6
UI[2]=E:\Sage\Sage100v60\MAS90\Home\pvxwin32.exe
UI[3]=Sage 100 has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=E:\Sage\Sage100v60\MAS90\Home\pvxwin32.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\apphelp.dll
LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.19291_none_a9f5e0cb013211a1\COMCTL32.dll
LoadedModule[6]=C:\Windows\SYSTEM32\WINMM.dll
LoadedModule[7]=C:\Windows\SYSTEM32\USER32.dll
LoadedModule[8]=C:\Windows\SYSTEM32\GDI32.dll
LoadedModule[9]=C:\Windows\SYSTEM32\WINSPOOL.DRV
LoadedModule[10]=C:\Windows\SYSTEM32\COMDLG32.dll
LoadedModule[11]=C:\Windows\SYSTEM32\ADVAPI32.dll
LoadedModule[12]=C:\Windows\SYSTEM32\SHELL32.dll
LoadedModule[13]=C:\Windows\SYSTEM32\ole32.dll
LoadedModule[14]=C:\Windows\SYSTEM32\MSVCR100.dll
LoadedModule[15]=C:\Windows\SYSTEM32\MSVCP100.dll
LoadedModule[16]=C:\Windows\SYSTEM32\msvcrt.dll
LoadedModule[17]=C:\Windows\SYSTEM32\WINMMBASE.dll
LoadedModule[18]=C:\Windows\SYSTEM32\SHLWAPI.dll
LoadedModule[19]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[20]=C:\Windows\SYSTEM32\RPCRT4.dll
LoadedModule[21]=C:\Windows\SYSTEM32\combase.dll
LoadedModule[22]=C:\Windows\SYSTEM32\cfgmgr32.dll
LoadedModule[23]=C:\Windows\SYSTEM32\DEVOBJ.dll
LoadedModule[24]=C:\Windows\SYSTEM32\SspiCli.dll
LoadedModule[25]=C:\Windows\SYSTEM32\SHCORE.DLL
LoadedModule[26]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[27]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[28]=C:\Windows\system32\IMM32.DLL
LoadedModule[29]=C:\Windows\SYSTEM32\MSCTF.dll
LoadedModule[30]=C:\Windows\SYSTEM32\profapi.dll
LoadedModule[31]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[32]=C:\Windows\system32\uxtheme.dll
LoadedModule[33]=E:\Sage\Sage100v60\MAS90\Home\90wres32.dll
LoadedModule[34]=C:\Windows\SYSTEM32\oleaut32.dll
LoadedModule[35]=C:\Windows\system32\dwmapi.dll
LoadedModule[36]=C:\Windows\SYSTEM32\msimg32.dll
LoadedModule[37]=C:\Windows\SYSTEM32\WSOCK32.DLL
LoadedModule[38]=C:\Windows\SYSTEM32\WS2_32.dll
LoadedModule[39]=C:\Windows\SYSTEM32\NSI.dll
LoadedModule[40]=C:\Windows\system32\mswsock.dll
LoadedModule[41]=E:\Sage\Sage100v60\MAS90\Home\pvxzlib1.dll
LoadedModule[42]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.8387_none_5094ca96bcb6b2bb\MSVCR90.dll
LoadedModule[43]=E:\Sage\Sage100v60\MAS90\Home\pvxocx32.DLL
LoadedModule[44]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[45]=C:\Windows\SYSTEM32\clbcatq.dll
LoadedModule[46]=C:\PROGRA~2\COMMON~1\Sage\COMMON~1\pvxdax.dll
LoadedModule[47]=C:\Windows\SYSTEM32\sxs.dll
LoadedModule[48]=C:\Windows\SYSTEM32\PVXIO.DLL
LoadedModule[49]=E:\Sage\Sage100v60\MAS90\Home\MASEXT32.DLL
LoadedModule[50]=C:\Windows\SYSTEM32\mpr.dll
LoadedModule[51]=E:\Sage\Sage100v60\MAS90\Home\ssleay32.dll
LoadedModule[52]=E:\Sage\Sage100v60\MAS90\Home\LIBEAY32.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Sage 100
AppPath=E:\Sage\Sage100v60\MAS90\Home\pvxwin32.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=DFEC78DA4E2A2DB10D81BAE94FB0BB92
------------------------------
Doug Higgs
Assistant Technical Support / Building Maintenance Specialist
Midwest Commerce Solutions, Inc
------------------------------
Original Message:
Sent: 04-29-2019 18:51
From: Alnoor Cassim
Subject: PVXWIN32.EXE Using All of the CPU
What Kevin said. On the server, cross-reference the PID in the Task Manager with the PID in Master Console to ID the Sage task. I've seen a custom report using CS ODBC driver do that as well. Make sure DEP is turned off too.
------------------------------
Alnoor Cassim
Free Agent Developer and Consultant
CallForHelp.biz
Email: alnoor@callforhelp.biz
Orange County, CA
------------------------------
Original Message:
Sent: 04-29-2019 17:52
From: Kevin Moyes
Subject: PVXWIN32.EXE Using All of the CPU
PID in the Master Console is the value on the Server (Task Manager) for that process thread. I've seen a custom report do that.
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON