Known AppWave Issues

From AppWave
Jump to: navigation, search

Go Up to AppWave Readme


Known AppWave issues are divided into the following categories:

AppWave Enterprise

  • For the AppWave 4.2 release the protocol has been changed from app:// to appwave://. Because of this change, the user with the 4.2 release will not be able to launch apps from a regular web browser navigating an older host. A host earlier than the 4.2 release only uses the app:// protocol. But because the 4.2 browser only “listens” to the appwave:// protocol it cannot launch the app from the older host.
  • In its default configuration, anyone can access your AppWave and run the applications broadcasted by it. To secure your AppWave, set Restricted Mode to On and Allow client to register user to off. You should also edit the All Users group and the folders this group has access to, and the user to limit the licenses available for that user. For more information, see "System Management", "Folder Management", "Group Management", and "User Management" in the AppWave Administrator Guide.
  • AppWave does not work properly on Windows configurations using non-English characters in machine and file-system path names.

AppWave Browser

  • AW-956: When a new folder is add from the Managed Folders it doesn`t appear automatically in the AppWave Brower or after clicking the Refresh button. The user needs to exit the Browser and start it again to see the new folder.
  • AW-3059: Delphi app maximizes the CPU usage when accessing a virtualized folder in File Explorer.
  • AW-3133: When upgrading to AppWave Browser 3.0 / 3.1, after OS reboots the AWB is not started automatically.
  • AW-3917: AppWave Browser is not compatible with Fiddler Web Debugger, and possibly other packet sniffing applications. When an app is launched a content-length mismatch error occurs. To resolve this issue, quit the packet sniffing application and try again to run the app. (5.0)
  • AW-3694: If while running an app such as DB Artisan, which requires the MSVC 2008 plugin, you locally install an application, such as ER/Studio Data Architect, the MSVC plugin ER/Studio DA requires is not installed. This prevents the natively installed application from launching when AppWave Browser is not running or if in AppWave Browser you remove the other apps which use the MSVC 2008 plugin. To resolve this problem, exit AppWave Browser so the MSVC 2008 plugin is not detected by the application installer and reinstall the application. (5.0)
  • AW-3752: While not connected to a Private AppWave, if you connect to the AppWave Store and then try to access a non-existent Private AppWave a connection failed page displays. This failure display persists when you again try to access the AppWave Store. You will not be able to see the content of the AppWave Store until you access another node, such as Notifications or Activity. Then, when you return to the AppWave Store node the AppWave Store content will once again display. The same problem occurs when you perform an invalid search such as entering only AND or OR as the search criteria.
  • AW-3758: Reviews submitted from the channel of an app accessed through the Store Apps node are not accepted for moderation. To submit a review of an AppWave Store app, click the AppWave Store node and then click the app to access its channel.
  • AW-3779: "Streaming player failed to initialize properly" after switching Turbo Option to ON for an AWB installed with -turbomodeoff parameter.
  • AW-3794: Search results are not sorted by relevance when searching for apps by entering search criteria in the Search/Address bar. You may have to scroll through the results to find the app you're looking for. (5.0) KI
  • AW-3984: Severe performance issues appear when launching apps from AppWave Browser on a machine having Karspersky Antivirus 2012.
  • AW-4028: In some cases clearing cache dor not succeed even if no apps are really running.
  • AW-4653: If you lose connection to your private AppWave and you previously launched Embarcadero apps while connected to both the AppWave Store and your private AppWave, then when you try to launch Embarcadero apps from the AppWave Store a licensing error message will display. Restart AppWave Browser when it loses connection to your private AppWave and you will be able to launch Embarcadero apps on the AppWave Store.
  • AW-4986: Problems with StreamingCore and Static Cache location when using Run as to launch apps.
  • AW-6088: "Invalid url" error when launching an app from Private Store with a earlier version of AWB installed and choosing not to upgrade.
  • AW-6248:[Regression] "F1" no longer works when AWB is not connected to private server; AWB help web page is no longer displayed.
  • AW-6781: When a user log into Windows with standard user privileges (non-Admin) they cannot elevate to Admin privileges using "Run As Administrator" within Appwave.
  • AW-7121: AppWave Browser does not support connection to Non-Anonymous proxies that require authentication.
  • AW-7863: If AppWave is running, ADB (Android Debug Bridge) reports the emulator device -5566 is offline. However ADB detects it and reports it as a device running on port 5567 (incorrectly). If you then run RAD Studio/HTML 5 Builder, and attempt to deploy an application to a running emulator device, it fails because there are certain ADB commands that count on only one emulator device running. If there are multiple devices running, or if ADB thinks multiple devices are running, an error is thrown.
This conflict is caused by AppWave. If the AppWave service is running, ADB reports port 5566 [incorrectly] as an available Android emulator.
So the problem is with ADB which incorrectly reports our server, or in fact any server that listens to a port in 5554-5584+1 range, as Android device. In case of multiple emulators, the option -s should be used to specify what emulator to use.
Note: The issue of the ADB switches has been addressed in RAD Studio/HTML 5 Builder.
  • AW-7972: AW-Browser 4.1.1 - Streaming App of DB Change Manager 6.1 does not recognize Network Named License.
  • AW-8184: In 5.0 browser there are "ADD" buttons instead of "INSTALL" buttons with Native installer applications.
  • If you are using a Proxy server to connect to the internet you must specify the proxy settings specified in
    • Internet Explorer Tools\Internet Options\Connections\LAN settings or in the
    • Internet Options applet of the Windows Control Panel
      • Windows XP: Start > Settings > Control Panel > Internet Options > Connections > LAN settings
      • Windows 7: Start > Control Panel > Internet Options > Connections > LAN settings
You can also access the LAN settings dialog on the Gear menu of the AppWave Browser > Options > Proxy Settings
  • Some apps may not run if mastered in a Virtual Machine environment due to dependencies of DirectX or Video Card drivers.
  • Existing ToolBox users should not run AppWave Browser and ToolBox at the same time.
  • For some applications, if the application is already running, launching the AppWave equivalent or another version may just bring the currently running application into focus.
  • Restarting the system is required when uninstalling or upgrading AppWave Browser.
  • AppWave Browser must be restarted in order for changes to user privileges to take effect.
  • AppWave Browser does not support Internet Protocol Version 6 (IPV6).
  • Switching connection to multiple servers is not supported (user is allowed to change connection settings, but this may cause problems with license and apps management).
  • Licensing and folder settings may not be all updated at refresh on AppWave Browser, sometimes reconnecting to AppWave is required.
  • In some cases, AppWave Browser may become sluggish due to poor network performance. If this happens, changing the network connectivity option from wininet to HttpIndy may resolve the issue. This change may also remedy the "MS XML DOM parse error" and is required in order to configure AppWave Browser to use a proxy server to connect to AppWave. Since AppWave Browser requires authentication and Internet Explorer does not, AppWave Browser will not be able to connect to AppWave unless the proxy server settings in Internet Explorer are overridden. Add the following lines: [InternetConnection] and HttpTransportType=HttpIndy to the AppWave Browser configuration file, which is located at:
    • Windows Vista, Windows 7 and Windows 8: C:\Users\Local Settings\Embarcadero\AppWaveBrowser\Toolbox.ini
    • Windows XP: C:\Documents and Settings\Local Settings\Application Data\Embarcadero\AppWaveBrowser\Toolbox.ini
  • When uninstalling AppWave Browser, all data may not be removed. You will need to manually delete the dynamic cache folder, located at
    • Windows 7 and Windows 8: C:\Program Data\Embarcadero\Product Repository\StreamingCore\Profiles\[user]\Applications.
    • Windows XP: C:\Documents and Settings\All Users\Application Data\Embarcadero\StreamingCore
  • The AppWave Browser uninstaller may become unstable if a non-admin user attempts to remove an instance of AppWave Browser that was installed by an admin user. In this case, the admin user should uninstall AppWave Browser.

AppWave Admin

  • AW-8190: Cannot change AppWave port number after installation.
  • AW-6186: Concurrent licenses are automatically added when a new group of user is created. If the admin wants to apply named licenses he needs to remove concurrent licenses first.

AppWave Studio

  • AppWave 3.0.1 or higher is required to master with the following templates: Adobe Creative Suite 5.5, Microsoft Project, and Microsoft Visio.
  • AW-2883: When the user is trying to master a custom app, sometimes AW Studio auto-detects and applies an existing tempalte from a free app. For example application using Ghostscript.
  • AW-3727: Sometimes broadcasting an app results in an "Operation failed" error even though the application has been successfully deployed to the AppWave Server.
  • Some applications that appear on the Embarcadero AppWave take advantage of Studio features in AppWave Browser 3.0 and later, such as multi-entry and complex scripting. To master this type of complex application, such as Microsoft Office, you need to update your AppWave (the host installation) and AppWave Browser to version 3.0 or later.
  • Record and install is not supported on 64-bit systems. However, you can capture data from an existing installation using a template.
  • In order to master an application in Windows 7 or Vista, you must launch the AppWave Browser as an Administrator, close the AppWave Browser, and open it again by right-clicking the AppWave Browser shortcut, and select "Run as Administrator."
  • When mastering large applications on Win 7 32-bit systems, Appwave Browser might enter into a non-responding state for a limited period of time. When this happens, the Mastering window will go to the background, behind the Studio window and it needs to be explicitly brought to the front.
  • Sub-processes created during testing of an App will block AppWave Studio from overwriting the .app file if they are still running when you attempt to master.

App Specific

  • AW-7693: [App Specific] no native oracle clients are installed message when Oracle client is installed.
  • Delphi and C++ Builder: Applications created using the Delphi or C++ Builder apps may not run outside of the Delphi or C++ Builder apps IDEs. This may be because the application you created is missing the required runtime libraries. You need to copy the required libraries from the virtual space in which the Delphi or C++ Builder IDE app runs, into the same folder as your application. This can be done in the Delphi or C++ Builder IDE by either of the following two methods:
  1. Select View > File Browser.
  2. Navigate to the files required and copy them into the same folder as your application.
    or
  3. Select Tools > Configure Tools > Add.
  4. Under Title, enter Command Prompt .
  5. Under Program, enter C:\Windows\system32\cmd.exe .
  6. Click OK.
  7. Click Close.
  8. Select Tools > Configure Tools and select Command Prompt .
  9. Use this command prompt window to copy all the files you need from the C:\XE3\bin folder in the virtual space into the same folder as your application.
  • Change Manager: Command line invocation is supported with the App. Right-click the App icon and select Open Terminal. Command line terminal can be used only for the last App launched. Scheduler is not currently supported, so you will not be able to plan a script.
  • .Net reliant Apps:
    • On Vista and Windows XP systems, to master applications that require .Net, make sure that captured application had the .Net runtime included during mastering. For the Apps mastered using templates, the correct runtimes are selected automatically.
  • Toad: To use Toad for DB2, you must install the DB2 client from the operating system and connect to it outside of AppWave Browser.

See Also