Troubleshooting tips for Windows Forms applications
If
you experience difficulty deploying, running, publishing, or updating
an application, make sure you have installed the .NET Framework
and SDK as described in “System requirements”, then review the suggestions in
this section. Also review the known issues listed in the PowerBuilder Release
Bulletin
.
Runtime errors
The application might
not run correctly when you select Design>Run Project in
the Project painter, when you run the executable file in the deployment folder,
or when a user runs the installed application. When you or a user
runs the executable file, PowerBuilder creates a file called PBTrace.log in
the same directory as the executable. This file can help you trace
runtime errors. It can be configured by editing the appname.exe.config file,
where appname is the name of the executable
file:
|
1 |
<appSettings><br /> <!-- The value could be "enabled" or "disabled"--><br /> <add key ="PBTrace" value ="enabled"/><br /> <!-- The target can be File, EventLog or File|EventLog --><br /> <add key ="PBTraceTarget" value="File"/><br /> <!-- If the Target is File, PBTraceFileName should also be<br /> specified.--><br /> <add key ="PBTraceFileName" value ="PBTrace.log"/><br /> <!-- EventLogId is optional(0 is default), and it only <br /> works when EventLog is enabled--><br /> <add key ="PBEventLogID" value ="1101"/> |
|
1 |
... |
The following problems might also occur:
- If
the application cannot be launched from another computer, make sure the
required PowerBuilder runtime files, pbshr115.dll and pbdwm115.dll, and
the Microsoft runtime files on which they depend, at71.dll, msvcp71.dll,
and msvcr71.dll, are available on the other
computer and in the application’s path.
If the executable file is located on a network path, the .NET
Framework must be configured to have Full Trust permissions at runtime.
See “Full trust requirement”. - If the application cannot connect to a database,
make sure that the required PowerBuilder database interface, such
as pbodb115.dll, has been added to the Win32
dynamic library files section of the Library Files tab page and that
the required client software is available on the target computer.
If the application uses a configuration file, such as myapp.ini,
select it on the Resource Files tab page. For ODBC connections,
make sure that the DSN file is created on the client. - If no data displays in DataWindow objects, select
the PBLs that contain them on the Library Files tab page. - If graphics fail to display, select them on the
Resource Files tab page.
Publish errors
There are two steps in the publication process. First, publish
files are generated, and then they are transferred to the publish
location. Publish errors are displayed in the Output window and
recorded in a file called pbiupub.log in the output
directory.
The following errors might be reported during file generation:
- Failure to create local folder structure Check that you have permission to create a folder in the specified
directory. - Failure to generate application manifest
file Check that the .NET Framework 2.0 SDK bin directory
is in your PATH environment variable. If a certificate file is specified,
check that it exists in the specified location and is a valid certificate.
Use different output paths for multiple projects If you create more than one Windows Forms project for a single application,
make sure you specify a different output path on the General page
for each project. If you do not, the application manifest files generated
for each project conflict with each other.
The
following errors might be reported during file transfer:
- Publish location is a Web server: http://servername/appname Check that servername and the development
computer are in the same network domain and that you are in the
administrators group of servername or have
write access to the wwwroot directory on servername. - Publish location is a file share: \servernameappname Check that servername and the development
computer are on the same network and that you have write access
to the appname directory on \servername. - Publish location is an FTP site: ftp://servername/appname Check that servername can be accessed
using the specified user name and password and that you have write
access to the appname directory on \servername.
You should also check that the publish location name is typed
correctly, that the PBNET_HOME environment variable is
set correctly, and that network connections are working correctly.
Installation errors
If installation on the client computer fails, make sure that:
- The files exist in the location specified on the
server. - The link on the publish page matches the location
where the files have been published. - The user has access rights to the publish server.
- There is sufficient space on the user’s
computer. - The network connection to the publish server is
working correctly. - You have not used localhost as
the publish or install location.
If the publish page fails to open on the client, check the
firewall settings on the publish server. The firewall must be turned
off on the server.
If the setup.exe file is not downloaded
when a prerequisite is selected, open the Properties dialog box
for the HTTP directory in IIS Manager and make sure the script source
access permission is enabled. If the Execute Permissions property is
not set to Scripts only, select Scripts only from the drop-down
list and refresh the server.
Update errors
If update fails, make sure that the update mode has been set
as you intended and that the update files are in the specified location.