Troubleshooting Tips for Web Forms Applications

Review the suggestions in this section if you experience difficulty deploying, running, or updating a Web Forms application.

Also review the known issues listed in the PowerBuilder Release Bulletin.

• Web Forms Deployment Errors
  Inadequate write permissions for a deployment directory, or a deployment computer with a hyphen in its name, may prevent you from deploying Web Forms applications.
• Browser Error Messages
  Runtime errors for Web Forms applications are often posted in the client browser.
• Failure to Connect to a Database
  Limited access rights for ASP.NET users is a common cause for the inability to connect to a database from a Web Forms application.
• DataWindows Are Not Visible
  Make sure the PBL files that contain the DataWindows used by a Web Forms application are copied to the directory specified by the PBLibDir global property.
• Pictures Are Not Visible
  Before you deploy a .NET Web Forms project, make sure you add all picture files used by the application to the resource file list for the project.
• Excessive Flickering on Web Page
  A Web Forms application user might encounter excessive flickering in an application if a default browser setting has been changed.
• Posted Events Are Not Executed
  If you post an event in a response window that closes the response window, and call posted events in the Open event for a main window that displays when the response window is closed, the posted events in the Open event are not executed.
• External DLLs Do Not Load
  Make sure the DLLs you want to load are copied to the bin subdirectory of the main Web Forms application directory in the server’s virtual file system path.
• Print Failure
  Some PowerScript print functions are not supported in the current release. If your applications saves or exports DataWindows as PDF or XSL-FO files, make sure you read the instructions for installing the appropriate printing software on the Web Forms server.
• Log Files
  A PowerBuilder application that compiles successfully with the PowerBuilder native compiler might not compile successfully with the PowerBuilder to .NET compiler. Log files help you trace compiler and runtime errors.
• Problems with IIS 7.5
  When you deploy a PowerBuilder Web Forms application to IIS 7 or later, the application is deployed to a PowerBuilder-specific application pool named PBDotnet4AppPool.