Cuando trabajamos con Axapta en ciertas circunstancias podemos encontramos con la necesidad de borrar un objeto del AOT, ya sea por temas de programación o porque este objeto este corrupto y nos da error.
Si nos encontramos con que el objeto está corrupto, no podremos borrarlo de forma manual y lo tendremos que realizar por código, para hacer esto podemos utilizar el siguiente código, en el cual se muestra como borrar una tabla del AOT.
staticvoid DAXBorradoObjeto(Args _args){
UtilIdElements utilElement;
UtilElementName tableName;
UtilEntryLevel Layer;
;
tableName ='Nombre del tabla';
Layer = utilEntryLevel::usr;
ttsbegin;
select utilElement where utilElement.name== tableName
&& utilElement.utilLevel== Layer
&& utilElement.recordType== utilElementType::Table;
if(utilElement){
utilElement.delete();
ttscommit;
info(strFmt('El objeto %1 en la capa %2 ha sido borrado!', tableName, Layer));
}else{ttsAbort;
warning(strFmt('El objeto %1 en la capa %2 no se ha encontrado!', tableName, Layer));
}}
Recientemente Microsoft ha publicado un White Paper con bastantes detalles técnicos, en el cual nos explica como realizar la integración entre Microsoft Project y Dynamics Ax 2009.
Para todas aquellos que os queráis descargar el documento os adjunto el links, el cual no requiere tener acceso a la partnersource.
En alguna ocasión, aunque no es nada recomendable, necesitamos ejecutar sentencias SQL directamente contra la base de datos desde Axapta sin pasar por el framework que utiliza Dynamics para ello.
Es posible que por ejemplo tengamos que hacer un drop table o algo parecido, para ello, crearemos en la clase Global, el siguiente método:
serverstaticvoid DAXExecuteSQL(str _sql){/* Método para ejecutar directamente sql sobre base de datos - www.dynamicsax.es */str ddl ='';
SqlStatementExecutePermission ssep;
Statement statement;
Connection connection;
;
ddl = _sql;
connection =new Connection();
connection.ttsbegin();
ssep =new SqlStatementExecutePermission(ddl);
ssep.assert();
statement = connection.createStatement(ResultSetType::Dynamic, ResultSetConcurrency::Updatable);
// BP deviation documented
statement.executeUpdate(ddl);
connection.ttscommit();
}
Para utilizar el método desde cualquier parte de Axapta, simplemente tendremos que usar la siguiente llamada:
DAXExecuteSQL('Delete custTableTmp');
Esta llamada borrará la tabla CustTableTmp, igual que si lo ejecutáramos desde la consola de SQL Server
Microsoft acaba de publicar en la Partner Source y Customer Source, los objetos para adaptar al 347 según la nueva normativa, también adjunto la hoja de producto con los objetos que se crean nuevos y los objetos que se modifican del estándar.
A continuación os dejo una lista de posibles errores a la hora de implementar Enterprise Portal y como solucionarlos
Issue:
Error trying to deploy reports Microsoft Dynamics AX Reporting Project Deployment: The following components have not been installed or are not configured correctly: AL.exe
Error trying to deploy reports System.InvalidOperationException: The following components have not been installed or are not configured correctly: Microsoft Domain-Specific Language Tools
Error trying to deploy reports Microsoft Dynamics AX Reporting Project Deployment: ClrBridgeLoader: fatal error : Microsoft.Dynamics.ClrBridge.dll cannot be loaded. Fatal error: ClrBridge is note loaded.
Solution:
Ensure you are trying to deploy reports from the SSRS server and that you can validate the SSRS server name in the Reporting Servers from within Microsoft Dynamics AX 2009. If this error appears right after installing the reporting extensions, launch the report deployment tool again.
Issue:
Enterprise Portal (EP) or SSRS Reports don’t run or stop working An attempt has been made to use a data extension ‘AXDATAMETHOD’ that is not registered for this report server. (rsDataExtensionNotFound) or data extension ‘AXQUERY’ and ‘AXADOMD’
Solution:
Installing or Reinstalling Reporting Extensions will resolve this issue. As a precaution make a Backup of: Program Files\Microsoft SQL Server\MSSQL.\Reporting Services\ReportServer folder
NOTE: SSRS updates or Service Packs may remove entries from rsreportserver.config file.
Issue:
Enterprise Portal (EP) Reports don’t run or stop working A ProgressTemplate must be specified on UpdateProgress control with ID ‘AxProgressControl’
Solution:
You can resolve the issue by using one of the three methods below:
Un-install Microsoft .NET 3.5 SP1 and reinstall Microsoft .NET 3.5 without SP1
Issue:
Report deployment tool Crashes Attempted to read or write protected memory. This is often an indication that the memory is corrupt
Solution:
If multiple versions of Dynamics AX are installed on the same server you will need to change your AX 2009 Path in your environment variables ahead of your AX 4.0 path to avoid running the wrong version of DLL’s
Issue:
Error running reports Error during processing of ‘AX_CompanyName’ report parameter. (rsReportParameterProcessingError).
Solution:
Process OLAP the cubes to supply data to the reports or An incorrect Execution account has been specified in the Reporting Services Configuration Manager
Note: For SSRS 2008 the Business Connector proxy account is required to be the SSRS service account and for SSRS 2005 the Business Connector Proxy account should be running as the SSRS application pool in IIS. Also look at application event log for details on other issues.
Issue:
Enterprise Portal (EP) web site runs but not the reports in the EP web parts: Dynamics Adapter LogonAs failed or Microsoft.Dynamics.BusinessConnectorNet.LogonFailedException
Solution:
Leave the Execution account blank on SSRS 2005 or set to BC Proxy account on SSRS 2008 (Microsoft Dynamics AX 2009 SP1 only)
NOTE: SSRS Execution account is set to an account other than BC Proxy Account
Issue:
EP or SSRS Reports don’t run or stop working Dynamics Adapter LogonAsGuest failed or FatalSessionException…
Solution:
The issue is caused by the Reporting Services web site set to anonymous Authentication. Changing the SSRS website to Integrated and/or un-marking Anonymous Authentication will resolve this issue.
Issue:
Double Hop \ Kerberos Authentication An Error has occurred while establishing as connection to the Analysis Server or Reports don’t display in the EP website from a Client Browser not local to the IIS server Cannot read information from SQL Server Reporting Services. Validate that the Report Manager URL is correct
gn=»top»>
Solution:
Setup Service Principle names (SPN) and Delegation to allow the passing of Kerberos certificate
Office Data Connection (ODC) file deployment fails with SQL Server 2008 Microsoft Dynamics AX is searching for the SQL Server 2005 Microsoft.AnalysisServices.dll (v9.0.242.0)
Solution:
Apply one of the following hotfixes:
For Microsoft Dynamics AX 2009 RTM: Apply the fix from KB957312
For Microsoft Dynamics AX 2009 SP1: Apply the fix from KB960158
If the hotfix does not resolve the issue, make sure you are running a Dynamics AX 2009 client on the EP web server when deploying the ODC files. As a workaround you can manually deploy the ODC files by following these steps:
Open the ODC file with Notepad or any other text editor
Edit the odc file with the following changes:
Data Source=OLAPServerName Initial Catalog=OLAPDbName Add SSPI=Kerberos after Initial Catalog if using Kerbersos (in red only required for Kerberos authentication)
«Client found response content type of ‘text/html; charset=utf-8’, but expected ‘text/xml'»
Solution:
Ensure SSRS service is running and are able to connect to instance via SQL Server Management Studio. Note: Additional information can be found in SSRS error log.
Issue:
Exception from HRESULT: 0X80041FFF
Solution:
Change Visual Studio project location to local drive if using a network share
Issue:
The Analysis extension is not seeing the SQL cluster name for Analysis Services when Analysis services is setup on a SQL cluster.
You will get an error similar to this when trying to install Analysis Extension in this environment:
Connecting to SQL Server 2005 Analysis Services on server ‘SQL02’ and instance ‘MSOLAP$ANALYSIS’. A connection cannot be made. Ensure that the server is running. No connection could be made because the target machine actively refused it 127.0.0.1:2383 An error occurred while Setup was connecting to SQL Server Analysis Services instance ‘MSOLAP$ANALYSIS’ on server ‘SQL02’.
An error occurred while Setup was connecting to SQL Server Analysis Services instance ‘MSOLAP$ANALYSIS’ on server ‘SQL02’.
Solution:
The workaround is to manually run the script to create the Dynamics AX OLAP db from the AX 2009 CD.
Navigate to this folder \support\Analysis Services\Scripts on your AX 2009 installation CD. Then run the dynamicsax.xmla script from within SQL Management Studio (connected to the SSAS instance).
This script will create the Dynamics AX OLAP database.
Issue:
BC Proxy account fails to start for the SSRS reports in Enterprise Portal with RPC exception 5
When Enterprise Portal starts for the first time and displays SSRS reports, normally two Business Connectors are started. After a period of time or if the impersonated web user logs out for the SSRS Proxy account you may experience an RPC error 5 access denied and the SSRS reports will no longer display in Enterprise Portal.
RPC error: RPC exception 5 in Ping occurred in session 36
Solution:
RPC error 5 can occur if the SSRS Execution account is set in the Reporting Services Configuration Manager. If the account used is the Business Connector proxy account the first startup of the Business Connector will work, but not any subsequent startups unless the IIS application pool if recycled or an IIS reset is done.
SSRS 2005 Remove the SSRS execution account through Reporting Services Configuration Manager and ensure the Business Connector account is running the IIS Application Pool for the SSRS web site.
SSRS 2008 Change the SSRS service to start as the Business Connector Proxy account and remove the SSRS execution account through Reporting Services Configuration Manager. Note: Changing the SSRS account would require a change in the registered SPN’s if you are using Kerberos authentication
Cargando…
Nota: Objetos probados para Ax 4.0, AX 2009, Ax 2009 + Sp 1