Skip to Content
avatar image
Former Member

Crystal Reports 2011 crashes after start

Hello,

the application crw32.exe stops working right after start (first start after install) with an exception:

"the instruction at 0x010d8ada referenced memory at 0x00000000. the memory could not be read".

No log files are available (except the installation log files).


Specs:

- Windows 8.1 64 bit

- 16 GB RAM

- Crystal Reports 2011

- Admin rights

- First installation


What I have already tried:

- reinstall (multiple times with cleanup)

- restart the pc after install

- start with admin rights


The install log file 'setupengine.log' shows some dependency units are missing:

17:04:38.391 Missing du: tp.apache.tomcat.actions-6.0.24-core.

17:04:38.392 Missing du: tp.apache.tomcat.restart-6.0.24-core.

17:04:38.394 Missing du: tp.sap.introscope.jni-822-core.

17:04:38.412 Missing du: tp.documentation.crystalreports.help-4.0-core.

17:04:38.414 Missing du: tp.documentation.crystalreports.charthelp.help-4.0-core.

17:04:38.417 Missing du: tp.shared.usp10.cpp-4.0-core.

But my colleagues can start the application without errors using the same install package running on Windows 8.1 64 bit too. So this should be not critical.

Thank You for your help.

Greetings,

Vitali

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jan 07, 2015 at 04:15 PM

    Hi Vitaly

    I'm not sure that the dependencies are an issue here. However I do not know what Service Pack for CR 2011  you are using. Use the following link to obtain the latest SP and apply that to your install:

    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/bobj_download/main_public.htm

    Check if %TEMP% has read / write permissions.

    - Ludek

    Senior Support Engineer AGS Product Support, Global Support Center Canada

    Follow us on Twitter

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Ludek,

      thank You for your response. Installing of Crystal Reports 2013 could solve my problem. Perhaps the issue was just a corrupt installtion package or an obsolete SP.

      Thanks,

      Vitali