We attempted to create an App-V package for this software as initially it appeared to be a good sequencing candidate. Problems occured however, during runtime and the operation of its graphics generation. When installed normally certain operations would generate graphical representations of data within the application. A "graphics engine" called GSW32.exe gets installed to C:\Windows\Syswow64 (W7 64-bit) and is called upon to generate graphics. It launches as a process in the background and the process closes again afterwards. When running within the bubble the application failed to launch the GSW32.exe and caused the error shown: "Graph Control" "Failed to open Graphics Server". It was possible to workaround the problem by prelaunching the GSW32.exe process however this was not a viable solution because the GSW32.exe did not shut itself down when the application was closed. This meant that the bubble persisted in perpetuity. Post run scripts were unable to manage the shutdown of the GSW32.exe process. Other options were attempted such as providing GSW32.exe in the application folder and ensuring paths were correct but no solution was found.Thursday, June 30, 2011
MSCI Barra Aegis - App-V error
MSCI Barra Aegis 4.2 is a vendor application that has an MSI installation. It is not well designed software though, and among other things writes settings into the win.ini file.
![]()
We attempted to create an App-V package for this software as initially it appeared to be a good sequencing candidate. Problems occured however, during runtime and the operation of its graphics generation. When installed normally certain operations would generate graphical representations of data within the application. A "graphics engine" called GSW32.exe gets installed to C:\Windows\Syswow64 (W7 64-bit) and is called upon to generate graphics. It launches as a process in the background and the process closes again afterwards. When running within the bubble the application failed to launch the GSW32.exe and caused the error shown: "Graph Control" "Failed to open Graphics Server". It was possible to workaround the problem by prelaunching the GSW32.exe process however this was not a viable solution because the GSW32.exe did not shut itself down when the application was closed. This meant that the bubble persisted in perpetuity. Post run scripts were unable to manage the shutdown of the GSW32.exe process. Other options were attempted such as providing GSW32.exe in the application folder and ensuring paths were correct but no solution was found.
We attempted to create an App-V package for this software as initially it appeared to be a good sequencing candidate. Problems occured however, during runtime and the operation of its graphics generation. When installed normally certain operations would generate graphical representations of data within the application. A "graphics engine" called GSW32.exe gets installed to C:\Windows\Syswow64 (W7 64-bit) and is called upon to generate graphics. It launches as a process in the background and the process closes again afterwards. When running within the bubble the application failed to launch the GSW32.exe and caused the error shown: "Graph Control" "Failed to open Graphics Server". It was possible to workaround the problem by prelaunching the GSW32.exe process however this was not a viable solution because the GSW32.exe did not shut itself down when the application was closed. This meant that the bubble persisted in perpetuity. Post run scripts were unable to manage the shutdown of the GSW32.exe process. Other options were attempted such as providing GSW32.exe in the application folder and ensuring paths were correct but no solution was found.