(1) Installation of Enterprise portal component, gives the following
error:Error executing code: SysDevelopmentProxy (object) has no valid runable
code in method 'generate'.
a. Go to Ax Client ( on a machine where Business Connector is installed)
b. Open the AOT\Classes node
c. Right click on the SysDevelopmentProxy class node and select compile
and make sure it compiles correctly. Then run the EP deployment.
(2) I have successfully created the EP Site and I can view the site.
But other users are not able to view it.
a. Make sure the user is added to Ax and to the right AX user groups.
b. Make sure the user is configured as Employee or Customer or Vendor in User
Relations form in Ax k
c. Make sure the user is added in EP site using Site Settings
i. Click on the “Site Actions” tab, and select “Site Settings”
from the drop down list
ii. Click the “People and groups” link
iii. Click the “New” button, in the “Add Users” page click the
“Add all authenticated users” and check all the permissions boxes to give all
configured users full rights
iv. Click “OK”
(3) Role Centers are working fine in EP , but are not coming up in
Ax Client
a. Make Sure the "Web site used to dispaly Role Center in the Ax
Client " setting in Administration -> Setup -> Internet -> Web
Sites form at the bottom right is set to the right EP site
b. Navigate to the EP site mentioned in the above setting and verify none of
the web parts are throwing any error. If any web part is not rendering
correctly , either fix the source of the problem for that web part or remove
that web part
(4) After I added “Business Overview WebPart”, I tried to add some
indicators. It gave the error message “An error has occurred while
processing the business overview indicator. Check the web server application
event log for more information.” From Event Viewer:“An unexpected
error has occurred.The period is not valid......"
Did you initialize the profiles? You need to "Initialize Role
Center Profiles" from Basic->Setup->Role Center or Import Time Periods
from Administration -> Setup -> Business Analysis -> OlAP -> Time
Periods
(5) In Enterprise Portal setup BC Proxy
Account cannot be set if the FQDN is not a superset of the short domain name
In Enterprise Portal setup BC Proxy Account cannot be set if the
FQDN is not a superset of the short domain name
if the FQDN is different from the short domain name , for example
If the FQDN = XYZ.microsoft.com
and the short dominname = XYZCORP
then setting the BCProxy user during EP setup fails.
To workaround,
(1) change the app pool in IIS used by the EP Site to to be run by the bc
proxy account with the FQDN specified.
(2) Also blank out the business connector proxy account in Ax.
(3) Then run EP setup and n the BC proxy user dialog , use the FQDN of the bc proxy.
(6)Manage Deployments dialog in Ax Client for Enterprise Portal may
not function correctly on 64 bit machine
Manage Deployments dialog in Ax Client for Enterprise Portal may not
function correctly on 64 bit machine
Administration->Setup -> Internet -> Enterprise Portal -> Manage
deployments on 64 bit machine may give
"Manage Deployment can not run because Enterprise Portal is not deployed
on this computer" even though Enterprise Portal is deployed and working
fine. Manage Deployment is used to update the Enterprise Portal web server with
the changed made in AOT web files and resources. To workaround this probelm,
use the alternate way of publishing these changes to the web server, which is
running Ax Setup and deploy EP without recreating the site.
(7) KPIs and Business Overviw keeps loading all the time and never
ends.
if all the Role Center content in enterprise portal are coming up except the
Business Overview webpart and it keeps displaying loading progress image
for long time with no error msg in the event log, it may be because IE
security setting is preventing the webpart from asynchronously getting the
data. To resolve this issue add the EP site to the intranet site zone in
IE or disable IE Enhanced Security Configuration from Add / Remove programs
-> Add / Remove Widnows Components.
(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/d...displaylang=en
Windows SDK (contains AL.exe) - http://www.microsoft.com/downloads/d...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.
(17) SQL Server reporting services sp2 is not installed, I have
SQL Server 2005 Reporting Services installed and Service Pack 2 was installed also and still getting the error message
The same problem with SQL
Server 2005 SP3, this fix our problem:
Setup does not recognize that
SQL Server 2005 Service Pack 2 is installed When
installing the reporting extensions, you may receive an error message that
states that you must install SQL Server 2005 Service Pack 2. If you have
installed SQL Server 2005 Service Pack 2 and receive this error message,
complete the following steps. 1. Open the registry (regedit command )and find the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server key. 2. Right-click the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft
SQL Server key and choose New > Key. 3. Name the key Reporting Services. 4.
Right-click the Reporting Services key and choose New > String Value. 5. Name the string value Version. The Version string value will have a type of REG_SZ. 6. Double-click the Version string value and enter 9.00.3042.00 as the
value data. Click OK.
(18)Deployment failed unexpectedly with the message:Client found
response content type of 'text/html; charset=utf-8', but expected 'text/xml'.
Check if proxy account was
added to ax db users, and have access right on db. If it is not so add proxy
account to db users
(19) Deployment failedand when check Event viewer found the
following error
Dynamics Adapter Logon failed.
Connection with the Application
Object Server could not be established.
Microsoft.Dynamics.BusinessConnectorNet.LogonFailedException
at Microsoft.Dynamics.BusinessConnectorNet.Axapta.Logon(BC_PROXY_ACCOUNT_INFO*
pBCProxyAccountInfo, String company, String language, String objectServer,
String configuration)
Solution:
1-
Check
business connector configuration using client configuration utility
2-
Change
the active client configuration utility to connect to the AOS as the
configuration of business Connector
(20)“Deployment failed with the following exception:
System.Runtime.InteropServices.COMException (0x80040208)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32
errorCode, IntPtr errorInfo)
at System.Management.ManagementObject.Initialize(Boolean
getObject)
at System.Management.ManagementBaseObject.get_Properties()
at System.Management.ManagementBaseObject.GetPropertyValue(String
propertyName)
at
Microsoft.Dynamics.Framework.Deployment.Reports.SrsWmi.get_ConfigPath()
at
Microsoft.Dynamics.Framework.Deployment.Reports.ReportLibraryDeployer.DeployBusinessLogicAssemblies(IEnumerable`1
businessLogicAssemblies, DeploymentLogger logger)
at
Microsoft.Dynamics.Framework.Deployment.Reports.ReportLibraryDeployer.Deploy(IEnumerable`1
reportLibrariesToDeploy, IEnumerable`1 transitiveReferenceClosure,
IEnumerable`1 cultures, DeploymentLogger logger, Func`2
connectionStringModifier)”
Solution:
·
You just need to
disable the UAC (User Account Control), or to run the Deployment tool with
right-click “Run as administrator”. As it says in the Dynamics
AX installation guide.
(21) Error during
processing of ‘AX_CompanyName’ report parameter.
(rsReportParameterProcessingError)
and furthermore in the Windows Application Event
log on the SQL Reporting server we get the following error logged:
Dynamics Adapter LogonAs
failed.
Microsoft.Dynamics.BusinessConnectorNet.NoIISRightsException
at
Microsoft.Dynamics.BusinessConnectorNet.Axapta.Logon(BC_PROXY_ACCOUNT_INFO*
pBCProxyAccountInfo, String company, String language, String objectServer,
String configuration)
at
Microsoft.Dynamics.BusinessConnectorNet.Axapta.LogonUsingBCProxyAccount(_SEC_WINNT_AUTH_IDENTITY_W*
pImpersonatedUserAccount, NetworkCredential bcProxyCredentials, String company,
String language, String objectServer, String configuration)
at
Microsoft.Dynamics.BusinessConnectorNet.Axapta.LogonAs(String user, String
domain, NetworkCredential bcProxyCredentials, String company, String language,
String objectServer, String configuration)
at Microsoft.Dynamics.Framework.BusinessConnector.Session.DynamicsAdapter.LogonAs(String
user, String domain, NetworkCredential bcProxyCredentials, String company,
String language, String objectServer, String configuration)
Solution :
After further troubleshooting we identified that the user was not
licensed for the "Enterprise Portal Framework" module. SQL Reporting
extensions and integration uses the .NET Business Connector (BC.NET) and BC.NET
requires Enterprise Portal Framework license, even if you are not using Role
Centers and Enterpise Portal. When the business connector connects to the AOS
server if it does not find the license key, it throws the NoIISRightsException error
message as seen in the event log.
No comments:
Post a Comment