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.
Tuesday, June 7, 2011
Genesys ActiveX Interface for Desktop Tookit 7.2.000.00 on Windows 7 64bit
Sounds straighforward but the install can easily break. The quality of the MSI is debatable.
The media was composed of
setup.exe
setup.msi
setup.cab
read_me.html
ip_description.xml
Copy the media to a folder on the C:
Set the setup.exe for Windows XP SP3 compatibility.
Run the setup.exe
Choose both installation feature options (documentation and libraries)
Change the Destination Folder to C:\Program Files (x86)\GCTI\ActiveX Interface for Desktop Tookit, in this step it is important to add the (x86) piece in otherwise a failure occurs.
The media was composed of
setup.exe
setup.msi
setup.cab
read_me.html
ip_description.xml
Copy the media to a folder on the C:
Set the setup.exe for Windows XP SP3 compatibility.
Run the setup.exe
Choose both installation feature options (documentation and libraries)
Change the Destination Folder to C:\Program Files (x86)\GCTI\ActiveX Interface for Desktop Tookit, in this step it is important to add the (x86) piece in otherwise a failure occurs.
Subscribe to:
Posts (Atom)