For tips 1-7 , refer to http://blogs.msdn.com/solutions/archive/2008/06/23/microsofty-dynamics-ax-2009-enterprise-portal-role-centers-deployment-tips-n-tricks-1.aspx 

(8) Report Deployment is giving below error
"The following components have not been installed or are not configured correctly.
AL.exe
Microsoft Domain-specific Langugage Tools..."

You need to install VS 2008 or the VS 2008 Shell.
If you install VS 2008 that should be good enough. If you want to install the minimal component required, then You can get VS Shell at
VS Shell - http://www.microsoft.com/downloads/details.aspx?FamilyId=ACA38719-F449-4937-9BAC-45A9F8A73822&displaylang=en
Windows SDK (contains AL.exe) - http://www.microsoft.com/downloads/details.aspx?FamilyId=E6E1C3DF-A74F-4207-8586-711EBE331CDC&displaylang=en

(9) Report Deployment gives CLRBridge Loader error.

The workaround for this problem is to copy the AxReports.exe from  C:\Program Files\Microsoft Dynamics AX\50\Reporting Services to C:\Program Files\Microsoft Dynamics AX\50\Client\Bin
And run it from C:\Program Files\Microsoft Dynamics AX\50\Client\Bin

(10) "Home" button (Role Center) in Ax Client gives "An error has occurred. Contact your administrator for further assistance."

  • Check if Role Center site is set correctly at Administration -> Setup -> Internet -> Enterprise Portal -> Web Sites at the bottom dropdown.
  • Check if the Role Center page comes up correctly in Enterprise Portal in browser. If any of the webparts are throwing error, the page will still come up in Enterprise Portal , but in AxClient it will give error for the entire page. If there are any errors in the webpart, then either fix it or remove it so that the page will render without any error. Once the page appears without any error, then check it in AxClient.

(11) "Home" button (Role Center) in Ax Client is not appearing

  • Check if Enterprise Portal is installed .
  • Check if Role Center site is set correctly at Administration -> Setup -> Internet -> Enterprise Portal -> Web Sites at the bottom dropdown.
  • Chekc if default Role Center page is set corectly at Adminsitration -> Setup -> User Profiels  at the bottom dropdown

 


(12) EP installation fails with below error msg

"Entering function Remove40WPPackage

               

Entering function Is40WPPackageInstalled

                Microsoft Dynamics AX 4.0 Web Part package axwebparts.cab installation status False

                Leaving function Is40WPPackageInstalled

                Leaving function Remove40WPPackage

               

                Leaving function RemoveOldWebPartPackage

                Could not load file or assembly 'Microsoft.Dynamics.AX.Fim.PaymentService, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified."

 

The aboce error msg  is misleading. If you go further down in the setup log file you will see the SysDevelopmentProxy error . So to resolve this issue, you just to recompile this class in a machine with .NET BC like issue (1)

 

(13) Update in Manage Deployments or Generate Proxy gives No .NET Business Connector Session found error.

 

Some times , users open AxClient by click on a configuration file ( for example ,  Test.axc). The Ax Client opens with configuration file, but when you generate proxy or Update in Manage deployment , it uses the  configuration defined for Local Client in Configuration Utility. It does not take the configuration file which is used to open the Ax Client. This is a bug. So to resolve, make sure the Local Client  confoguiration is set correctly in Ax Configuration Utility

 

(14) EP Deployment is successful but when I try to navigate the site, I get 404 error

When EP Site is created, it activates number of EP features and one of them registers the site with Ax  ( adds an entry in WebSite table) and sets the master page. If the user that is set as the Primary administrator account for the site during Site Creation does not have access to Ax, this fails but site creation does not return error. After the site is created, it gives 404 error.

So if you get 404 error, make sure EP is deployed correctly and then when creating EP site , specify a valid AX user account as the administrator of the site.

(15)When I create EP site , it creates immediately and when I navigate it displays a team site

At the time of EP Site creation, if AOS is down or if .NET BC Configuration specified in Configuration Utility is incorrect, EP Site creation does not report error  but creates the site. Since it's not able to connect to AOS, it appears as a team site. To resolve this problem, make sure the .NET BC configuration in Ax Configuration Utility is correct and is pointing to a valid running AOS.

(16) After I installed EP, the IIS Web site on which I installed EP appears to be in stop mode.

When an IIS Web site is not yet extended with SharePoint and when you run EP setup on this site, EP Setup extends the IIS Web site using SharePoint object model. SharePoint actually creates a new IIS Website using the same port and extends it and installs EP on it. The old site is stopped because it uses the same port. SharePoint does it this way, later you have some other system installed on the old site, you could just change the port and restart it.

So this is not an error. This is the behavior of SharePoint installation. When you install SharePoint on existing IIS Web site, it creates a new IIS web site.