All reports crash (SAGE Workstation)

SUGGESTED

Hi Guys,

Would a kind soul please help me ?

Here is the case:

I installed SAGE 300 2017 Workstation on a new PC running Windows 10 Pro.

 

The only but about the installation was a warning message as follows: “There was a problem registering the assembly a4wcrinterop.dll during installation”.

The manual installation was successful.

 

Once the installation was complete, I tested several SAGE options in OE and other modules and no problems. However when I tried one of the G/L reports (Trial Balance), nothing happened – the G/L windows was still active and no Crystal Report windows was displayed. No error message … nothing indicating an error.

However I found 2 errors in the Windows Application event log. These errors are:

 

Log Name:      Application

Source:        Application Error

Date:          25/03/2019 22:44:13

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      EUR-DTP-001.Europahq.local

Description:

Faulting application name: A4WCONTAINERXP.EXE, version: 6.4.0.20, time stamp: 0x58e40599

Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f7ce6

Exception code: 0xc0000005

Fault offset: 0x000183f3

Faulting process id: 0x1ae8

Faulting application start time: 0x01d4e35c1fab17eb

Faulting application path: \\ACC2008\Accpac\Programs\runtime\A4WCONTAINERXP.EXE

Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120.dll

Report Id: 086b3fe7-ea33-4fde-850d-c45d1bf62a0a

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Event xmlns="">schemas.microsoft.com/.../event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-03-25T22:44:13.742166200Z" />

    <EventRecordID>7548</EventRecordID>

    <Channel>Application</Channel>

    <Computer>EUR-DTP-001.Europahq.local</Computer>

    <Security />

  </System>

  <EventData>

    <Data>A4WCONTAINERXP.EXE</Data>

    <Data>6.4.0.20</Data>

    <Data>58e40599</Data>

    <Data>MSVCR120.dll</Data>

    <Data>12.0.21005.1</Data>

    <Data>524f7ce6</Data>

    <Data>c0000005</Data>

    <Data>000183f3</Data>

    <Data>1ae8</Data>

    <Data>01d4e35c1fab17eb</Data>

    <Data>\\ACC2008\Accpac\Programs\runtime\A4WCONTAINERXP.EXE</Data>

    <Data>C:\WINDOWS\SYSTEM32\MSVCR120.dll</Data>

    <Data>086b3fe7-ea33-4fde-850d-c45d1bf62a0a</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

 

And:

 

Log Name:      Application

Source:        Application Error

Date:          25/03/2019 22:44:15

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      EUR-DTP-001.Europahq.local

Description:

Faulting application name: A4WCONTAINERXP.EXE, version: 6.4.0.20, time stamp: 0x58e40599

Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f7ce6

Exception code: 0xc000041d

Fault offset: 0x000183f3

Faulting process id: 0x1ae8

Faulting application start time: 0x01d4e35c1fab17eb

Faulting application path: \\ACC2008\Accpac\Programs\runtime\A4WCONTAINERXP.EXE

Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120.dll

Report Id: a5879b63-f6f5-41b2-a555-de33aabcda66

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Event xmlns="">schemas.microsoft.com/.../event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2019-03-25T22:44:15.442956000Z" />

    <EventRecordID>7550</EventRecordID>

    <Channel>Application</Channel>

    <Computer>EUR-DTP-001.Europahq.local</Computer>

    <Security />

  </System>

  <EventData>

    <Data>A4WCONTAINERXP.EXE</Data>

    <Data>6.4.0.20</Data>

    <Data>58e40599</Data>

    <Data>MSVCR120.dll</Data>

    <Data>12.0.21005.1</Data>

    <Data>524f7ce6</Data>

    <Data>c000041d</Data>

    <Data>000183f3</Data>

    <Data>1ae8</Data>

    <Data>01d4e35c1fab17eb</Data>

    <Data>\\ACC2008\Accpac\Programs\runtime\A4WCONTAINERXP.EXE</Data>

    <Data>C:\WINDOWS\SYSTEM32\MSVCR120.dll</Data>

    <Data>a5879b63-f6f5-41b2-a555-de33aabcda66</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>
</Event>

( testing other reports revealed the same result – no reports are printed). By the way , the user profile defines print destination as preview.

 Does any  one would have any idea on  the causes of these errors and how to fix it ?

Many thanks

  • SUGGESTED

    Check to ensure .Net 3.5 is installed (Control Panel / Programs and Features / Turn Windows Features On / Off - upper-left).  If this fails, please search the Kb for 18397.  You'll find information on manually registering the required Crystal interop file.

  • 0

    Bingo!!!! Thank you Shane and Jay. 

    Yes, .NET 4.7 was installed but no 3.5  as I would have expected (at least it was installed for the Windows 10 workstations I installed last year). 

    To help others , I will describe here the 3 different symptoms/errors I've had as follows:

    a) When print reports located in the Program folders as for instance printing invoices or G/L Trial Balance. The symptom was:

          Faulting application name: A4WCONTAINERXP.EXE, version: 6.4.0.20, time stamp: 0x58e40599
          Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f7ce6
          Exception code: 0xc0000005

    b) When printing reports stored in other folders (such as in /reports). In this case, the error was:

         Faulting application name: accpac.exe, version: 6.4.0.20, time stamp: 0x58e40a65
         Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f7ce6
         Exception code: 0xc0000005

    c) Printing using macro. the error occurred on .PrintReport with the following messages:

        Faulting application name: A4WVBA.EXE, version: 6.4.0.0, time stamp: 0x5782c8e2
        Faulting module name: VBE7.DLL, version: 7.1.10.33, time stamp: 0x4f0cb876
        Exception code: 0xc0000005

    Once .Net 3.5 was installed all print problems vanished away.