(1) Installation of Enterprise portal component, gives the followingerror:Error executing code: SysDevelopmentProxy (object) has no valid runablecode 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 UserRelations 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 allconfigured users full rights
iv. Click “OK”
(3) Role Centers are working fine in EP , but are not coming up inAx Client
a. Make Sure the "Web site used to dispaly Role Center in the AxClient " setting in Administration -> Setup -> Internet -> WebSites 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 ofthe web parts are throwing any error. If any web part is not renderingcorrectly , either fix the source of the problem for that web part or removethat web part
(4) After I added “Business Overview WebPart”, I tried to add someindicators. It gave the error message “An error has occurred whileprocessing the business overview indicator. Check the web server applicationevent log for more information.” From Event Viewer:“An unexpectederror has occurred.The period is not valid......"Did you initialize the profiles? You need to "Initialize RoleCenter Profiles" from Basic->Setup->Role Center or Import Time Periodsfrom Administration -> Setup -> Business Analysis -> OlAP -> TimePeriods
(5) In Enterprise Portal setup BC ProxyAccount 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 theFQDN 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 bcproxy 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 maynot function correctly on 64 bit machine
Manage Deployments dialog in Ax Client for Enterprise Portal may notfunction correctly on 64 bit machine
Administration->Setup -> Internet -> Enterprise Portal -> Managedeployments on 64 bit machine may give
"Manage Deployment can not run because Enterprise Portal is not deployedon this computer" even though Enterprise Portal is deployed and workingfine. Manage Deployment is used to update the Enterprise Portal web server withthe 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 isrunning Ax Setup and deploy EP without recreating the site.
(7) KPIs and Business Overviw keeps loading all the time and neverends.
if all the Role Center content in enterprise portal are coming up except theBusiness Overview webpart and it keeps displaying loading progress imagefor long time with no error msg in the event log, it may be because IEsecurity setting is preventing the webpart from asynchronously getting thedata. To resolve this issue add the EP site to the intranet site zone inIE 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 configuredcorrectly.
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 theminimal 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:\ProgramFiles\Microsoft Dynamics AX\50\Reporting Services to C:\Program Files\MicrosoftDynamics 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 errorhas occurred. Contact your administrator for further assistance."
<!--[if !supportLineBreakNewLine]-->
<!--[endif]-->
"The following components have not been installed or are not configuredcorrectly.
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 theminimal 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:\ProgramFiles\Microsoft Dynamics AX\50\Reporting Services to C:\Program Files\MicrosoftDynamics 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 errorhas occurred. Contact your administrator for further assistance."
<!--[if !supportLineBreakNewLine]-->
<!--[endif]-->
<!--[if !supportLists]-->· <!--[endif]-->Check if Role Center site is set correctly at Administration ->Setup -> Internet -> Enterprise Portal -> Web Sites at the bottomdropdown.
<!--[if !supportLists]-->· <!--[endif]-->Check if the Role Center page comes up correctly in EnterprisePortal in browser. If any of the webparts are throwing error, the page willstill come up in Enterprise Portal , but in AxClient it will give error for theentire page. If there are any errors in the webpart, then either fix it orremove it so that the page will render without any error. Once the page appearswithout any error, then check it in AxClient.
(11) "Home" button (Role Center) in Ax Client is not appearing
<!--[if !supportLists]-->· <!--[endif]-->Check if Enterprise Portal is installed .
<!--[if !supportLists]-->· <!--[endif]-->Check if Role Center site is set correctly at Administration ->Setup -> Internet -> Enterprise Portal -> Web Sites at the bottomdropdown.
<!--[if !supportLists]-->· <!--[endif]-->Chekc if default Role Center page is set corectly atAdminsitration -> 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 statusFalse
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 ofits dependencies. The system cannot find the file specified."
The aboce error msg is misleading. If you go further down in the setup log fileyou will see the SysDevelopmentProxy error . So to resolve this issue, you justto recompile this class in a machine with .NET BC like issue (1)
(13) Update in ManageDeployments 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 generateproxy or Update in Manage deployment , it uses the configuration defined forLocal Client in Configuration Utility. It does not take the configuration filewhich is used to open the Ax Client. This is a bug. So to resolve, make surethe 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 404error
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 isset as the Primary administrator account for the site during Site Creation doesnot 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 whencreating EP site , specify a valid AX user account as the administrator of thesite.
(15)When I create EPsite , 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 BCConfiguration specified in Configuration Utility is incorrect, EP Site creationdoes not report error but creates the site. Since it's not able to connect toAOS, it appears as a team site. To resolve this problem, make sure the .NET BCconfiguration in Ax Configuration Utility is correct and is pointing to a validrunning AOS.
(16) After I installedEP, the IIS Web site on which I installed EP appears to be in stop mode.
When anIIS Web site is not yet extended with SharePoint and when you run EP setup onthis site, EP Setup extends the IIS Web site using SharePoint object model.SharePoint actually creates a new IIS Website using the same port and extendsit and installs EP on it. The old site is stopped because it uses the sameport. SharePoint does it this way, later you have some other system installedon 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. Whenyou install SharePoint on existing IIS Web site, it creates a new IIS web site.
"Entering function Remove40WPPackage
Entering function Is40WPPackageInstalled
Microsoft Dynamics AX 4.0 Web Part package axwebparts.cab installation statusFalse
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 ofits dependencies. The system cannot find the file specified."
The aboce error msg is misleading. If you go further down in the setup log fileyou will see the SysDevelopmentProxy error . So to resolve this issue, you justto recompile this class in a machine with .NET BC like issue (1)
(13) Update in ManageDeployments 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 generateproxy or Update in Manage deployment , it uses the configuration defined forLocal Client in Configuration Utility. It does not take the configuration filewhich is used to open the Ax Client. This is a bug. So to resolve, make surethe 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 404error
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 isset as the Primary administrator account for the site during Site Creation doesnot 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 whencreating EP site , specify a valid AX user account as the administrator of thesite.
(15)When I create EPsite , 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 BCConfiguration specified in Configuration Utility is incorrect, EP Site creationdoes not report error but creates the site. Since it's not able to connect toAOS, it appears as a team site. To resolve this problem, make sure the .NET BCconfiguration in Ax Configuration Utility is correct and is pointing to a validrunning AOS.
(16) After I installedEP, the IIS Web site on which I installed EP appears to be in stop mode.
When anIIS Web site is not yet extended with SharePoint and when you run EP setup onthis site, EP Setup extends the IIS Web site using SharePoint object model.SharePoint actually creates a new IIS Website using the same port and extendsit and installs EP on it. The old site is stopped because it uses the sameport. SharePoint does it this way, later you have some other system installedon 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. Whenyou install SharePoint on existing IIS Web site, it creates a new IIS web site.
(17) SQL Server reporting services sp2 is not installed, I haveSQL Server 2005 Reporting Services installed and Service Pack 2 was installed also and still getting the error message
The same problem with SQLServer 2005 SP3, this fix our problem:
Setup does not recognize thatSQL Server 2005 Service Pack 2 is installed Wheninstalling the reporting extensions, you may receive an error message thatstates that you must install SQL Server 2005 Service Pack 2. If you haveinstalled 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\MicrosoftSQL 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 thevalue data. Click OK.
(18)Deployment failed unexpectedly with the message:Client foundresponse content type of 'text/html; charset=utf-8', but expected 'text/xml'.
Check if proxy account wasadded to ax db users, and have access right on db. If it is not so add proxyaccount to db users
(19) Deployment failedand when check Event viewer found thefollowing error
Dynamics Adapter Logon failed.
Connection with the ApplicationObject 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:
<!--[if !supportLists]-->1- <!--[endif]-->Checkbusiness connector configuration using client configuration utility
<!--[if !supportLists]-->2- <!--[endif]-->Changethe active client configuration utility to connect to the AOS as theconfiguration of business Connector
(20)“Deployment failed with the following exception:
System.Runtime.InteropServices.COMException (0x80040208)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32errorCode, IntPtr errorInfo)
at System.Management.ManagementObject.Initialize(BooleangetObject)
at System.Management.ManagementBaseObject.get_Properties()
at System.Management.ManagementBaseObject.GetPropertyValue(StringpropertyName)
atMicrosoft.Dynamics.Framework.Deployment.Reports.SrsWmi.get_ConfigPath()
atMicrosoft.Dynamics.Framework.Deployment.Reports.ReportLibraryDeployer.DeployBusinessLogicAssemblies(IEnumerable`1businessLogicAssemblies, DeploymentLogger logger)
atMicrosoft.Dynamics.Framework.Deployment.Reports.ReportLibraryDeployer.Deploy(IEnumerable`1reportLibrariesToDeploy, IEnumerable`1 transitiveReferenceClosure,IEnumerable`1 cultures, DeploymentLogger logger, Func`2connectionStringModifier)”
System.Runtime.InteropServices.COMException (0x80040208)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32errorCode, IntPtr errorInfo)
at System.Management.ManagementObject.Initialize(BooleangetObject)
at System.Management.ManagementBaseObject.get_Properties()
at System.Management.ManagementBaseObject.GetPropertyValue(StringpropertyName)
atMicrosoft.Dynamics.Framework.Deployment.Reports.SrsWmi.get_ConfigPath()
atMicrosoft.Dynamics.Framework.Deployment.Reports.ReportLibraryDeployer.DeployBusinessLogicAssemblies(IEnumerable`1businessLogicAssemblies, DeploymentLogger logger)
atMicrosoft.Dynamics.Framework.Deployment.Reports.ReportLibraryDeployer.Deploy(IEnumerable`1reportLibrariesToDeploy, IEnumerable`1 transitiveReferenceClosure,IEnumerable`1 cultures, DeploymentLogger logger, Func`2connectionStringModifier)”
Solution:
<!--[if !supportLists]-->· <!--[endif]-->You just need todisable the UAC (User Account Control), or to run the Deployment tool withright-click “Run as administrator”. As it says in the DynamicsAX installation guide.
(21) Error duringprocessing of ‘AX_CompanyName’ report parameter.(rsReportParameterProcessingError)
and furthermore in the Windows Application Eventlog on the SQL Reporting server we get the following error logged:
Dynamics Adapter LogonAsfailed.
Microsoft.Dynamics.BusinessConnectorNet.NoIISRightsException
atMicrosoft.Dynamics.BusinessConnectorNet.Axapta.Logon(BC_PROXY_ACCOUNT_INFO*pBCProxyAccountInfo, String company, String language, String objectServer,String configuration)
atMicrosoft.Dynamics.BusinessConnectorNet.Axapta.LogonUsingBCProxyAccount(_SEC_WINNT_AUTH_IDENTITY_W*pImpersonatedUserAccount, NetworkCredential bcProxyCredentials, String company,String language, String objectServer, String configuration)
atMicrosoft.Dynamics.BusinessConnectorNet.Axapta.LogonAs(String user, Stringdomain, NetworkCredential bcProxyCredentials, String company, String language,String objectServer, String configuration)
at Microsoft.Dynamics.Framework.BusinessConnector.Session.DynamicsAdapter.LogonAs(Stringuser, String domain, NetworkCredential bcProxyCredentials, String company,String language, String objectServer, String configuration)
Solution :
and furthermore in the Windows Application Eventlog on the SQL Reporting server we get the following error logged:
Dynamics Adapter LogonAsfailed.
Microsoft.Dynamics.BusinessConnectorNet.NoIISRightsException
atMicrosoft.Dynamics.BusinessConnectorNet.Axapta.Logon(BC_PROXY_ACCOUNT_INFO*pBCProxyAccountInfo, String company, String language, String objectServer,String configuration)
atMicrosoft.Dynamics.BusinessConnectorNet.Axapta.LogonUsingBCProxyAccount(_SEC_WINNT_AUTH_IDENTITY_W*pImpersonatedUserAccount, NetworkCredential bcProxyCredentials, String company,String language, String objectServer, String configuration)
atMicrosoft.Dynamics.BusinessConnectorNet.Axapta.LogonAs(String user, Stringdomain, NetworkCredential bcProxyCredentials, String company, String language,String objectServer, String configuration)
at Microsoft.Dynamics.Framework.BusinessConnector.Session.DynamicsAdapter.LogonAs(Stringuser, String domain, NetworkCredential bcProxyCredentials, String company,String language, String objectServer, String configuration)
Solution :
After further troubleshooting we identified that the user was notlicensed for the "Enterprise Portal Framework" module. SQL Reportingextensions and integration uses the .NET Business Connector (BC.NET) and BC.NETrequires Enterprise Portal Framework license, even if you are not using RoleCenters and Enterpise Portal. When the business connector connects to the AOSserver if it does not find the license key, it throws the NoIISRightsException errormessage as seen in the event log.
No comments:
Post a Comment