Sage 100

We have an issue where the customer experiences an APPCRASH when printing AP checks ONLY.  Payroll checks work just fine and it is definitely not a volume or data issue.  It happens randomly and we were able to replicate the error in a test company for a subset of the checks which printed fine in another test company (after performing some of the usual fixes)

The actual error is:

Problem signature:Problem signature:  Problem Event Name: APPCRASH  Application Name: pvxwin32.exe  Application Version: 9.52.0.0  Application Timestamp: 54820754  Fault Module Name: StackHash_453e  Fault Module Version: 6.3.9600.19629  Fault Module Timestamp: 5e2fc9e7  Exception Code: c0000374  Exception Offset: PCH_A9_FROM_ntdll+0x0003C8EC  OS Version: 6.3.9600.2.0.0.16.7  Locale ID: 1033  Additional Information 1: 453e  Additional Information 2: 453e229cd1b04018bcd5e9c2f20ebddd  Additional Information 3: 5992  Additional Information 4: 599243125ab8b9af8bbcf141a1359ab3

Sage 2015 Standard (5.20.2.0) running on 
Windows Server 2012 R2 Standard as a terminal server

We have already installed the actual printer driver on the server and verified that .Net 3.5 and 4.5 are on the server.  We also ran a repair on the workstation in case any corrupted dlls or registry settings.

Any ideas?

------------------------------
Gary Feldman
President
I-Business Network, LLC
Marietta GA
6786270646 x224
http://www.i-bn.com/
------------------------------

I think we saw this a while back, and it too was inconsistent.

If you look at the check form in question in crystal reports, and verify database, you may find that the functions that support the field that controls printing of the G/L distribution on the stubs are not working properly.  if this is the case, and they don't print the G/L on the stubs, you can just change the formula to return "N"...

Jeff F

------------------------------
Jeff Fiddelman
Exeplex, LLC
------------------------------

@Gary Feldman - check the form itself.  There was that switch within Crystal in 2 fields (4 copies of the one field) as to the formula used.  I seem to remember that you could half-assed get away with the old formula for a while in the first version after it changed, but you would get an error eventually.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------

This could be what Beth is referring to.  Remove the old formulae, don't just REM it out.  When you migrate the form and run the mascrcw.exe, the update will fail because it still reads the REM lines.

Memory errors or other issues with XP when printing v2013 AP checks.

Change these formulae in both the main and the subreports of the Crystal check

Main report:

Formula PrintGLVariable

Old value: formula = StoreStringVar("PrintGL",{@PrintGLDistribution})

New value:

Shared PrintGL As String

PrintGl = {@PrintGLDistribution}

Formula = PrintGL

Subreport:

Formula PrintGLDistribution

Old value:  formula = FetchStringVar("PrintGL") 

New value:

Shared GLPrint as String

Formula = GLPrint

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------

Original Message:
Sent: 05-05-2020 10:29
From: Beth Bowers
Subject: APPCRASH on 2015

@Gary Feldman - check the form itself.  There was that switch within Crystal in 2 fields (4 copies of the one field) as to the formula used.  I seem to remember that you could half-assed get away with the old formula for a while in the first version after it changed, but you would get an error eventually.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625
------------------------------

Thanks Greatly for the help and for the specific detail  ​

------------------------------
Gary Feldman
President
I-Business Network, LLC
Marietta GA
6786270646 x224
http://www.i-bn.com/
------------------------------

Original Message:
Sent: 05-05-2020 10:50
From: Jeff Schwenk
Subject: APPCRASH on 2015

This could be what Beth is referring to.  Remove the old formulae, don't just REM it out.  When you migrate the form and run the mascrcw.exe, the update will fail because it still reads the REM lines.

Memory errors or other issues with XP when printing v2013 AP checks.

Change these formulae in both the main and the subreports of the Crystal check

Main report:

Formula PrintGLVariable

Old value: formula = StoreStringVar("PrintGL",{@PrintGLDistribution})

New value:

Shared PrintGL As String

PrintGl = {@PrintGLDistribution}

Formula = PrintGL

Subreport:

Formula PrintGLDistribution

Old value:  formula = FetchStringVar("PrintGL") 

New value:

Shared GLPrint as String

Formula = GLPrint

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444
------------------------------


Original Message:
Sent: 05-05-2020 10:29
From: Beth Bowers
Subject: APPCRASH on 2015

@Gary Feldman - check the form itself.  There was that switch within Crystal in 2 fields (4 copies of the one field) as to the formula used.  I seem to remember that you could half-assed get away with the old formula for a while in the first version after it changed, but you would get an error eventually.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625

We have also found that it helps to remove any remarks in the formula box when changing the formulas.  Delete the lines with the old formulas instead of  leaving "REM" or "//" .

------------------------------
alan niergarth
Velosio LLC
------------------------------

Original Message:
Sent: 05-05-2020 11:24
From: Gary Feldman
Subject: APPCRASH on 2015

Thanks Greatly for the help and for the specific detail  ​

------------------------------
Gary Feldman
President
I-Business Network, LLC
Marietta GA
6786270646 x224
http://www.i-bn.com/
------------------------------


Original Message:
Sent: 05-05-2020 10:50
From: Jeff Schwenk
Subject: APPCRASH on 2015

This could be what Beth is referring to.  Remove the old formulae, don't just REM it out.  When you migrate the form and run the mascrcw.exe, the update will fail because it still reads the REM lines.

Memory errors or other issues with XP when printing v2013 AP checks.

Change these formulae in both the main and the subreports of the Crystal check

Main report:

Formula PrintGLVariable

Old value: formula = StoreStringVar("PrintGL",{@PrintGLDistribution})

New value:

Shared PrintGL As String

PrintGl = {@PrintGLDistribution}

Formula = PrintGL

Subreport:

Formula PrintGLDistribution

Old value:  formula = FetchStringVar("PrintGL") 

New value:

Shared GLPrint as String

Formula = GLPrint

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444


Original Message:
Sent: 05-05-2020 10:29
From: Beth Bowers
Subject: APPCRASH on 2015

@Gary Feldman - check the form itself.  There was that switch within Crystal in 2 fields (4 copies of the one field) as to the formula used.  I seem to remember that you could half-assed get away with the old formula for a while in the first version after it changed, but you would get an error eventually.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625

Moved thread from Urgent to Sage 100 Community.

------------------------------
Moira Goggin
Executive Director
90 Minds, Inc.
------------------------------

Original Message:
Sent: 05-05-2020 11:42
From: alan niergarth
Subject: APPCRASH on 2015

We have also found that it helps to remove any remarks in the formula box when changing the formulas.  Delete the lines with the old formulas instead of  leaving "REM" or "//" .

------------------------------
alan niergarth
Velosio LLC
------------------------------


Original Message:
Sent: 05-05-2020 11:24
From: Gary Feldman
Subject: APPCRASH on 2015

Thanks Greatly for the help and for the specific detail  ​

------------------------------
Gary Feldman
President
I-Business Network, LLC
Marietta GA
6786270646 x224
http://www.i-bn.com/


Original Message:
Sent: 05-05-2020 10:50
From: Jeff Schwenk
Subject: APPCRASH on 2015

This could be what Beth is referring to.  Remove the old formulae, don't just REM it out.  When you migrate the form and run the mascrcw.exe, the update will fail because it still reads the REM lines.

Memory errors or other issues with XP when printing v2013 AP checks.

Change these formulae in both the main and the subreports of the Crystal check

Main report:

Formula PrintGLVariable

Old value: formula = StoreStringVar("PrintGL",{@PrintGLDistribution})

New value:

Shared PrintGL As String

PrintGl = {@PrintGLDistribution}

Formula = PrintGL

Subreport:

Formula PrintGLDistribution

Old value:  formula = FetchStringVar("PrintGL") 

New value:

Shared GLPrint as String

Formula = GLPrint

------------------------------
Jeff Schwenk
FORMER 90M Board Member
Bottomline Software, Inc.
Waynesboro VA
540-221-4444


Original Message:
Sent: 05-05-2020 10:29
From: Beth Bowers
Subject: APPCRASH on 2015

@Gary Feldman - check the form itself.  There was that switch within Crystal in 2 fields (4 copies of the one field) as to the formula used.  I seem to remember that you could half-assed get away with the old formula for a while in the first version after it changed, but you would get an error eventually.​

------------------------------
Beth Bowers
Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
Beth Bowers
269-445-1625