Showing posts with label AX. Show all posts
Showing posts with label AX. Show all posts

Sunday, January 24, 2016

Unable to connect to the AOS specified in the AX Client Configuration in SSRS

Today, I faced a really weird issue while designing a report in VS2012. After designing the report I tried building the solution and got the below error:

Error 1 Unable to connect to the AOS specified in the AX Client Configuration. The configuration could be missing, invalid, or the AOS is not running. To connect to the AOS, check the network connection between the client and the AOS, verify that a valid configuration exists and that the AOS service is running on the server. C:\Program Files (x86)\MSBuild\Microsoft\DynamicsTools\Microsoft.Dynamics.Framework.Design.Reporting.Modeling.targets 103 6 ReportModel2



Error 2 The "GenerateRdlTask" task failed unexpectedly.

Microsoft.Dynamics.Framework.BusinessConnector.Session.Exceptions.NoKernelSessionException: Unable to connect to the AOS specified in the AX Client Configuration. The configuration could be missing, invalid, or the AOS is not running. To connect to the AOS, check the network connection between the client and the AOS, verify that a valid configuration exists and that the AOS service is running on the server. --->


After trying the obvious things like verifying the SSRS & BC configurations and connectivity, I had to move to the boss "Google" and got out a really interesting thing about how Business Connector works:


"The root cause is the SSRS report file size is exceeding the limit, as there are multiple layouts for the report file, and each layout has several pictures embedded. So, the size was over 10M, we tried multiple times, the report can work correctly when the size is relatively small, but once over about 10M, the business connector cannot hold the report effectively and the connect is lost.


The solution is to create another SSRS file to have other layouts."


I had created a copy of the existing design which was exceeding the size so I deleted it and all worked fine.




Source: http://dynamicsuser.net/forums/t/84427.aspx

Monday, August 31, 2015

Delete all transactions Ax2012

There is a class named "SysDatabaseTransDelete" in Axapta which can be used to delete all the transactions from your Ax Db but will not delete the base setups. In that case we can use the same DB as Production Db.
NOTE: It works perfectly with Ax2012 CU3 and above as it is now updated for new DB structure. Otherwise you may face issues with General Journal/Trial balance data.
It deletes all data from tables in the Transaction, WorksheetHeader and WorksheetLine table groups plus the following tables...
       SalesTable
       PurchTable
       WMSPallet
       CustInterestJour
       CustCollectionLetterJour
       ProjControlPeriodTable
       ProjInvoiceJour
       ProjJournalTable
       PdsRebateTable
       PdsBatchAttributes
You can run it from the AOT by right clicking on the SysDatabaseTransDelete class node and selecting "open" - this isn't the sort of thing you would want to put on a menu anywhere.
Here is a job for the same:
static void deleteTransactions(Args _args)
{
SysDatabaseTransDelete delete;
;
delete = new SysDatabaseTransDelete();
delete.run();
}

Saturday, September 14, 2013

CryptoAPI not available

You have set up a new Microsoft Dynamics AX environment and everything works fine but EP(Enterprise Portal). The only thing Event Viewer(eventvwr) says is "CryptoAPI not available". So it's time to check the Business Connector user account under "System Administration->Setup->System->System service accounts" or Application Pool identity of the EP site using Sharepoint Central Administration.

The bcproxy account is either not setup properly or not assigned in AX or in sharepoint. Remember bcproxy account should be a same domain account. So you just need to assign it and you have got your EP back :)

You are not recognized as a recognized user of Microsoft Dynamics Ax

You may this error when you have to import an AX database from some other environment of different domain e.g. your client's DB. In this case once you import the db and start Ax, it will throw the following error:








Now this happens because of the change in domain(new domain and users are not logged in AX DB) so we need to add users of our domain to this DB. For this we need to add an entry with SID of our "Admin" account to the "USERINFO" table.



Follow the steps:
  1. Get the SID of Admin account.
  • You can also get SID from an existing AX DB in your environment by using the SQL command:
select SID, Networkdomain, networkalias from userinfo where networkalias = '<UserAlias>'
  1. Open SQL Server Management Studio.
  2. Run the provided query
update USERINFO
set NETWORKDOMAIN = 'contoso.com', NETWORKALIAS = 'axadmin', SID = 'S-1-5-21-2423567575-2897528880-3809357285-500'
where id = 'admin'

where NETWORKDOMAIN is the DomainName of your environment where you have restored the DB and NETWORKALIAS is the username to which you want to provide access(Admin in this case).