Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This section describes information that may be useful when troubleshooting issues in the Eagle Portal.

Manage Error Messages

The Eagle Portal is a Windows Internet Information Services (IIS) application that uses parent pathing. If you see any of the following types of error messages, check the pathing settings for the Eagle Portal IIS server:

  • An error occurred on the server when processing the URL. Please contact the system administrator

  • The Page Cannot Be Displayed

  • Server.MapPath()error 'ASP 0175: 80004005' Disallowed Path Characters

  • ASP error 0131 The include file cannot contain '..' to indicate the parent directory. //, line

By default, parent pathing is disabled in IIS in some versions of the Windows operating system, such as Windows 2003. For the Eagle Portal to work, you must enable this setting.

View Eagle Portal’s Diagnostics Window

To use the Diagnostics window to quickly view the Eagle Portal configuration settings, add common/diagnostics.aspx to the end of your Portal URL. This provides you with some information on options configured in PortalConfiguration located in \Portal NxG\Web\ from the application, without having to go to where the Eagle Portal is installed.

The following figure shows the Eagle Portal configuration settings. The Get Config Files and Logs link is displayed only if you are an Eagle Portal Administrator with access to managing Eagle Portal's settings. Click this link to download a PortalConfig zipped file that contains eagleportal.config, Web.config, and portal.log. These files are very helpful for troubleshooting.

Portal Configuration Settings

Locate the IIS Log Files

If the files in PortalConfig.zipped did not provide you with enough information, you can also locate the IIS log files for more detailed help with troubleshooting. These log files are created in the windows/system32/logfiles directory. A subdirectory is created for each Website created on the Web server. Look at the contents of the files to locate the log files for the Portal Website.

Separate log files are created inside each log directory for each day that there is activity on the Website. The file names contain the date of activity.

To enable IIS logging in IIS Manager:

  1. Right click the Website for which you want to enable logging and click Website.

  2. Verify Enable Logging is enabled.

  3. Click Home Directory.

  4. Verify Log Visits is enabled.
    Log files are buffered in 64-kilobyte (kbyte) pieces by default and Windows IIS does not write the content until the buffer is filled.

Troubleshoot XML Tags

The Eagle Portal requires xml_tags for all fields and that each XML tag is unique. If you see errors while running the Eagle Portal, put the Eagle Portal into debug mode and check the xml_tags for the appropriate debug files.

Check the contents of the element name in the XML files. If the name has double-quote characters ("") beside it, then you are missing the tag. You might also get the following error in the portal.log file:

COM error: To create nodes of type 'ELEMENT', a valid name must be specified.

The following is an example of a field missing the xml_tag:

<field_attribute id=P1859 name= description=Price comments=

type=0 precision=2 user_data=/>

In this example, the element beside name is null. This means the tag is missing.

The following is an example of what the XML code should look like:

<field_attribute id=P1859 name=PRICE description=Price comments=

type=0 precision=2 user_data=/>

In the example above, the element for name is now PRICE.

Any time an xml_tag is missing, errors occur in the Eagle Portal. To resolve this problem, you can add XML tags to the Eagle Portal XML code.

To add xml_tags to the Eagle Portal XML code:

  1. From any Eagle window, click the Eagle Navigator button to access the Eagle Navigator.

  2. Enter PACE Inventory of Fields in the Start Search text box.

  3. Click the PACE Inventory of Fields (System Management Center) link.
    You see the System Management window.

  4. Click the Eagle Navigator button to access the Eagle Navigator again and enter PACE Inventory of Fields in the Start Search text box.
    You see the PACE Inventory of Fields window.

  5. Find the table that contains the field for which the tag is missing.
    If the field is already listed in the inventory of fields for the table, select the field and click Edit. You can then add the tag. Spaces are not permitted. A good practice is to populate the xml_tag with the field name. Try using all upper-case letters for xml_tags.
    If the field is not in the list, click Get Fields. The field is populated automatically with an xml_tag.
    If the table you are looking for is not in the drop down list, add it, and perform a Get Fields operation.

  6. After fixing the xml_tags, select Refresh Server Cache or wait 5 minutes.

Track Portal Users

If your company requires you to track your users' activity in the Eagle Portal, you can enable the tracking feature from System Parameters with Sys Item 87.

Eagle Portal user tracking enables you to log user activity into the user_activity_log and the user_activity_log.detail in the pace_master database.

Set the System Parameter 87, Database user activity logging, to the value 1 to enable this feature. By default, this system parameter is disabled (set to the value 0).

You can access this parameter in the System Parameters window of the System Management Center.

  • No labels