Troubleshooting: Enterprise Portal Development
You may encounter some issues when you develop for or customize Enterprise Portal. Use the following information to help resolve issues.
The following solutions can be helpful when you encounter problems in Enterprise Portal.
If you encounter Windows SharePoint Services errors when you develop for Enterprise Portal, look in the Event Viewer for the system that is running Windows SharePoint Services. The errors will be listed in the Application group. In many cases, the details of the error will help you isolate the cause of the problem.
Enterprise Portal caches resources from the AOT and data from tables in Microsoft Dynamics AX. If you make changes in the AOT, the changes may not be reflected immediately in Enterprise Portal. In a similar way, data that has been changed in tables for Microsoft Dynamics AX may not immediately be seen in Enterprise Portal. Stale data in these caches could cause unexpected results in Enterprise Portal. Three commands are available in the Administration group at the bottom of the main page for Enterprise Portal to refresh these caches. The commands are described in the following table.
Flushes cached application object information for all items in the AOT. Use this when changes you made in the AOT that are not immediately reflected in Enterprise Portal.
Flushes cached database records. Use this when changes in the database are not immediately reflected in Enterprise Portal.
Flushes cached application object information for items in the Data Dictionary node of the AOT. Use this when you have made changes to resources in the Data Dictionary node, such as tables or extended data types, but the changes are not immediately reflected in Enterprise Portal.
Resetting IIS may resolve unexpected behavior in Enterprise Portal when you are making significant changes during development. In some cases, cached data may be used, instead of the data that you updated. Resetting IIS causes Enterprise Portal to start with the most current data.
Non-functioning Web Parts
As you create a Web part and add code to it, you may encounter cases where the page that contains the Web part no longer displays because of a problem in the Web part. If you cannot resolve the issue with the Web part by modifying the code for it, you may have to remove the Web part from the page. This may seem impossible because the page cannot be displayed. However, you can use another view of the Web page that allows for you to access the Web parts on it.
To use this view, add "contents=1" at the end of the URL for the Web page. This will display the Web page content as a list. This allows you to remove the non-functioning Web part. For example, the following URL displays the Customers list page content in this list view:
Turning on Debugging
If you are seeing errors in WSS, or Web parts display an error instead of content, turn on debugging for the Web site. Often, this will produce more helpful error information that you can use to resolve the problem.
To turn on debugging, open the web.config file for the site on which you are running Enterprise Portal. Typically, this will be in a location similar to the following:
If you are running Enterprise Portal on a different port, look in the folder for that port. Using a text editor, search the web.config file for the entry compilation. Set the debug attribute to true. The entry will resemble the following:
<compilation batch="false" debug="true">
Save the changes. Use the iisreset command to restart Enterprise Portal.
Viewing Context Information
You may need to troubleshoot passing context information from one page to another page in Enterprise Portal. When context information is passed through the URL for the page being opened, the information is encrypted to enhance the security. To help troubleshoot context problems, you can turn off the encryption so that you can see the values being passed for the context. For information about turning off encryption for the context information, see How to: Connect Dynamics Toolbars and User Controls.
The following solutions can be helpful when you encounter problems when working in Visual Studio.
Reloading the Project
If the Visual Studio project for User Controls has lost the connection to the AOT, you must restart Visual Studio and reload the project.
If the project for User Controls encounters build errors, be sure that you have generated the proxies for the project. Also, be sure that your code has the appropriate using statements to reference the namespaces for the objects, methods, and properties you are using.
Changes Not Reflected in Enterprise Portal
If changes you made to the Visual Studio project are not reflected in Enterprise Portal, be sure that you have saved the changes in Visual Studio. For instance, changes you make to the layout of a User Control will not be reflected in Enterprise Portal until you save the changes in Visual Studio.