AXForum  
Вернуться   AXForum > Microsoft Dynamics AX > DAX Blogs
All
Забыли пароль?
Зарегистрироваться Правила Справка Пользователи Сообщения за день Поиск

 
 
Опции темы Поиск в этой теме Опции просмотра
Старый 28.07.2009, 16:05   #1  
Blog bot is offline
Blog bot
Участник
 
25,475 / 846 (79) +++++++
Регистрация: 28.10.2006
emeadaxsupport: The mystery of blank Enterprise Portal pages
Источник: http://blogs.msdn.com/emeadaxsupport...tal-pages.aspx
==============

In Dynamics AX 4.0 when you are browsing for an Enterprise Portal page you might get a blank or half blank page. So instead of your Menus, Web Forms and WebLets with data you only receive a white background with no or only some content.

A blank Enterprise Portal page is an indicator that something unplanned has happened, most often an unhandled X++ exception.

As in Dynamics AX 4.0 the generation of the Web Form's and the WebLet's HTML code is also happening in X++ any unhandled X++ exception can interrupt the HTML code generation. This can effect not only the current Web Form / WebLet but also the other Web Forms / WebLets on the same page, depending on the method that is currently executed when the exception is raised.

Side note:
An unhandled X++ exception is an exception that is raised but not cached in a try-catch block.

When you are running into a blank Enterprise Portal page or have a Web Form that does not show up usually the Application event log contains information about the reason. If you place for example the X++ code throw error('This exception is raised by intention!'); in a Web Form method the following events will be written to the event log:

Microsoft Dynamics Business Connector Session #.

An X++ exception has occurred.
This exception is raised by intention!

and:

The Microsoft Dynamics session get object call runWebletItem failed.

This exception is raised by intention!

Microsoft.Dynamics.BusinessConnectorNet.XppException
at Microsoft.Dynamics.BusinessConnectorNet.AxaptaObject.Call(String methodName, Object[] paramList)
at Microsoft.Dynamics.WebParts.SessionItem.AxaptaObjectImpl.Microsoft.Dynamics.WebParts.IAxaptaObject.Call(String methodname, Object[] paramlist)

You can of course also use the Dynamics AX Debugger to locate the cause of the exception. If you never have debugged Enterprise Portal content before, the following articles are a good start:



Источник: http://blogs.msdn.com/emeadaxsupport...tal-pages.aspx
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
 

Похожие темы
Тема Автор Раздел Ответов Посл. сообщение
emeadaxsupport: AxUpdatePortal.exe does not update Enterprise Portal when not running from an elevated command prompt Blog bot DAX Blogs 0 26.07.2009 15:07
Solutions Monkey: Microsoft Dynamics AX 2009 Enterprise Portal / Role Centers - Deployment Tips-n-Tricks – 3 Blog bot DAX Blogs 0 27.10.2008 08:05
Solutions Monkey: Enterprise Portal Screencasts at Channel9.msdn.com Blog bot DAX Blogs 6 01.07.2008 19:38
jinx: Microsoft Dynamics AX 2009 Enterprise Portal Entwicklung Samples Blog bot DAX auf Deutsch 0 27.06.2008 04:06
Solutions Monkey: Customizing Master pages in Enterprise Portal Blog bot DAX Blogs 0 21.08.2007 04:31

Ваши права в разделе
Вы не можете создавать новые темы
Вы не можете отвечать в темах
Вы не можете прикреплять вложения
Вы не можете редактировать свои сообщения

BB коды Вкл.
Смайлы Вкл.
[IMG] код Вкл.
HTML код Выкл.
Быстрый переход

Рейтинг@Mail.ru
Часовой пояс GMT +3, время: 16:28.
Powered by vBulletin® v3.8.5. Перевод: zCarot
Контактная информация, Реклама.