VMware Horizon Community
Valvaris
Contributor
Contributor

SAP Business One with Addons

Hello at all,

im Evaluating VMThinapp with VMWorkstation 8 and wanted to build a Application our Company is using.

Application Name:

SAP Business One

Addons:

Coresuite - CoreSystems, two self Build Addons, Datev, Elster, FixedAssets, Intrastat, Payment,

Build / Install on a Clean Windows 7 32bit System:

1. MySQL 2008 R2 Client 32bit

2. .Net 4.0 Standalone

3. SAP Business One

4. Started Application - SAP - to install Addons!

5. Closed Application after Install of Addons.

6. Started Application again to start install of Coresuite SIP Files provided by the Server

7. Closed Application and Checked Process List of EXE still opened. If so Forced Close EXEs.

8. Build Application with Msi Package

Result:

Application is running fine but with Addons Enabled, Application becomes unstable in the ThinApp enviroment.

Errors are:

Problemsignatur:

  Problemereignisname:                       BEX

  Anwendungsname:                            PresentationFontCache.exe

  Anwendungsversion:                         3.0.6920.4902

  Anwendungszeitstempel:                  4a174fc2

  Fehlermodulname:                             StackHash_6758

  Fehlermodulversion:                          0.0.0.0

  Fehlermodulzeitstempel:                   00000000

  Ausnahmeoffset:                                034407d0

  Ausnahmecode:                                  c0000005

  Ausnahmedaten:                                00000008

  Betriebsystemversion:                        6.1.7601.2.1.0.256.1

  Gebietsschema-ID:                             1031

  Zusatzinformation 1:                          6758

  Zusatzinformation 2:                          675850d4877285798a99ecefe6fda646

  Zusatzinformation 3:                          f9f8

  Zusatzinformation 4:         f9f8de79e22ea73899c9fb52d477b5bb

Problemsignatur:

  Problemereignisname:                       APPCRASH

  Anwendungsname:                            PresentationFontCache.exe

  Anwendungsversion:                         3.0.6920.4902

  Anwendungszeitstempel:                  4a174fc2

  Fehlermodulname:                             ntdll.dll

  Fehlermodulversion:                          6.1.7601.17514

  Fehlermodulzeitstempel:                   4ce7b96e

  Ausnahmecode:                                  c0000029

  Ausnahmeoffset:                                0009052e

  Betriebsystemversion:                        6.1.7601.2.1.0.256.1

  Gebietsschema-ID:                             1031

  Zusatzinformation 1:                          2535

  Zusatzinformation 2:                          2535552b7ca301fd09d8b5b6b1533859

  Zusatzinformation 3:                          70c7

  Zusatzinformation 4:                          70c7bd7d334fb24a2de692885d88d43f

Problemsignatur:

  Problemereignisname:                       APPCRASH

  Anwendungsname:                            SAP Business One.exe

  Anwendungsversion:                         8.81.315.0

  Anwendungszeitstempel:                  4e28b4ab

  Fehlermodulname:                             StackHash_1c0e

  Fehlermodulversion:                          0.0.0.0

  Fehlermodulzeitstempel:                   00000000

  Ausnahmecode:                                  c0000005

  Ausnahmeoffset:                                603da1b6

  Betriebsystemversion:                        6.1.7601.2.1.0.256.1

  Gebietsschema-ID:                             1031

  Zusatzinformation 1:                          1c0e

  Zusatzinformation 2:                          1c0e288e01cf446a30f20fbe5b57135e

  Zusatzinformation 3:                          20e6

  Zusatzinformation 4:                          20e68ef1a32b315912342653bb2ef0a5

Problemsignatur:

  Problemereignisname:                       APPCRASH

  Anwendungsname:                            SAP Business One.exe

  Anwendungsversion:                         8.81.315.0

  Anwendungszeitstempel:                  4e28b4ab

  Fehlermodulname:                             ntdll.dll

  Fehlermodulversion:                          6.1.7601.17514

  Fehlermodulzeitstempel:                   4ce7b96e

  Ausnahmecode:                                  c0000029

  Ausnahmeoffset:                                0009052e

  Betriebsystemversion:                        6.1.7601.2.1.0.256.1

  Gebietsschema-ID:                             1031

  Zusatzinformation 1:                          dcb2

  Zusatzinformation 2:                          dcb2573e07394b4336655e644661e20a

  Zusatzinformation 3:                          8510

  Zusatzinformation 4:                          8510ee7d69f626ef0c3966e678549f4c

Problemsignatur:

  Problemereignisname:                       APPCRASH

  Anwendungsname:                            SAP Business One.exe

  Anwendungsversion:                         8.81.315.0

  Anwendungszeitstempel:                  4c065b06

  Fehlermodulname:                             ntdll.dll

  Fehlermodulversion:                          6.1.7601.17514

  Fehlermodulzeitstempel:                   4ce7b96e

  Ausnahmecode:                                  c0000005

  Ausnahmeoffset:                                000532ce

  Betriebsystemversion:                        6.1.7601.2.1.0.256.1

  Gebietsschema-ID:                             1031

  Zusatzinformation 1:                          9858

  Zusatzinformation 2:                          985801d65ca4d06e26a94bf3331fe8a6

  Zusatzinformation 3:                          0e52

  Zusatzinformation 4:                          0e52a3d05041a7d388b31d50a170d10e

A resolution would be great since i want to convince my supperiors that ThinApp is the way to go.  Smiley Happy

Best regards and Many thanks in advance

Val.

Reply
0 Kudos
1 Reply
TobyFruthParson
Enthusiast
Enthusiast

Try turning off compression.  Worked for me with Adobe InDesign CS5.  Also, try all the various isolation modes, starting with Merged.

Lastly, you did not specify where you are testing the application.  I suggest that the first test of a troublesome app be run on the VM where is was packaged.  Start by testing on the VM after the application capture and build.  If it runs fine, then move on to testing on the same VM reverted to pre-application condition.  If it does not run fine on the "dirty" VM that has the application natively then more troubleshooting remains.

Here's a list of ThinApp troubleshooting links (listed chronologically):

http://blogs.vmware.com/thinapp/2008/10/creating-window.html

http://blogs.vmware.com/thinapp/2009/05/app-troubleshooting.html

http://blogs.vmware.com/thinapp/2010/01/thinapp-troubleshooting---repost.html

http://blogs.vmware.com/thinapp/2010/10/thinapp-troubleshooting-methods.html

http://blogs.vmware.com/euc/thinapp-troubleshooting/

http://kb.vmware.com/kb/1030313

http://blogs.vmware.com/kb/2011/07/new-mind-map-troubleshooting-thinapp-issues.html

Toby Fruth, Sr. Specialist, The Parsons Corporation
Reply
0 Kudos