Known Issues for Miscellaneous Items

Learn about known issues and apply workarounds for miscellaneous items in PowerBuilder.

Miscellaneous issues in PowerBuilder
CR# Description
572522 Problem Starting SySAM License Server

If your Windows license server host has IPv6 enabled, the served license does not perform correctly. http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc71335.1550/doc/html/ate1274477728881.html provides more details.

640509 WPF SmartClient fails to install if name has uppercase letters.

The names of WPF SmartClient applications are always generated using all lowercase characters. Consequently, if the manifest specifies an application name that contains uppercase letters, the installation fails to install.

Workaround: Use only lowercase characters when you specify the WPF application executable name in the Project painter General page.

Fixed in 12.1 EBF.

626344 Inconsistent Save Behavior.

In Windows 7, PowerBuilder .NET behavior is inconsistent when saving objects, depending on the type of object and the type of Windows user. For example, PowerBuilder might clear the layout view after an administrator saves a window painter, but not if a regular user launches the IDE using Run As Administrator.

624291 Publishing SmartClient applications on Windows Vista and Windows 7.

On Windows Vista and Windows 7, standard users and users in the Administrator group cannot publish SmartClient WPF applications.

Workaround: Choose Run as Administrator to launch the PowerBuilder .NET IDE and enable the publication of SmartClient applications.

Fixed in 12.1 EBF.

623684 Error creating project with standard user login.

If the current user does not have write permission for the directory assigned to the TMP environment variable, an error message appears in the Output window after the user attemps to create a project with a target or project wizard.

Workaround: Set the TMP variable to a directory for which the current user has write permission.

617268 GetLatestVersion does not get all files added to Perforce by another user.

If two users add the same solution from a Perforce 2008 depot, then the first user checks in a new object for the solution, the second user can select Get Latest User (Recursive) to add the new object. However, although the new object is visible in the Solution Explorer of the second user, it is not added to that user's PBL directory.

Workaround: The second user must close and reopen the solution to complete the GetLatestUser action and get all the updates.

616577 Double-clicking resource items on FDCC-certified XP computers.

Although double-clicking a resource item in the Solution Explorer should open the editor associated with the item's file type, on FDCC-configured Windows XP computers, the Move dialog box opens instead. This does not occur on non-FDCC computers or on FDCC-configured computers using the Windows Vista operating system.

Workaround: To enable the correct editor to open:
  1. In the Solution Explorer, right-click the resource item.
  2. Select Add to open the Add Program dialog box.
  3. Browse to the program you want to use to open files of the type you right-clicked in step 1.
  4. If necessary, change the Friendly Name of the program you selected in step 3 and click OK.
  5. In the Open With dialog box, select the friendly name from step 4, click Set as Default, then click OK.
  6. Repeat this process for all other types of resource items you want to open from the Solution Explorer.
569483 New targets in root path of the c: drive are not visible.

In PowerBuilder .NET, if you create a workspace in the root path of the c: drive, then create a target in the root path, the target does not appear in the Solution Explorer.