Showing posts with label Error handling techniques. Show all posts
Showing posts with label Error handling techniques. Show all posts

Thursday, 13 August 2015

Custom barcode and MICR fonts on SSRS reports from AX 2012 display correctly but will not print or export

So with AX 2012 you may want to display a custom, barcode, or micr font on a report to print for the bank or factory floor. By default a lot of these fonts get installed but some do not. What I have found out is that it will display correctly within the report window but whenever you try to print it or export it does not export the font correctly. In order to resolve the issue the following needs to be done
  1. Install font on AOS
    1. If you are running an AX Cluster be sure to install it on all AOS's
  2. Install font on SQL/SSRS box
    1. If you are running a SQL cluster be sure to install it on all AOS's
  3. When installing be sure to install the font thru the control panel>fonts and not C:\windows\fonts for some odd reason windows server 2012 R1+ does not always install the font correctly when you copy to the specific folder but it does if you use the control panel
  4. Reboot SQL boxes
  5. Reboot AX AOS boxes


If this does not work try reinstalling the font thru the control panel.

Wednesday, 22 April 2015

Error While Activating The Inbound Port In AX2012 R2



                             


Solution :
Stop AOS
Delete all files from XPPIL folder
Start AOS
Full compile the Dynamics AX application object (Should have zero error)
perform full CIL compilation
I hope this will solve your problem

AX2012 R3 CU8 – AOT Compile Errors on Payroll Classes related to Symmetry DLL

Event Log:

The error we received in the event log was:
“The description for Event ID 110 from source Microsoft Dynamics AX cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Microsoft Dynamics AX Business Connector Session 7.
Failed loading assembly ste-net, Version=1.0.1.74, Culture=neutral, PublicKeyToken=5542884f620dbde5″

Compiler output:

SeverityPathLineColError message
Error\Classes\PayrollCalculatePayStatementBenefits\classDeclaration125Syntax error.
Error\Classes\PayrollCalculatePayStatementTaxes\classDeclaration425Syntax error.
Error\Classes\PayrollSetup\refreshWorkerTaxRegionTaxes255Variable Symmetry has not been declared.
Error\Classes\PayrollTaxCalculation\classDeclaration75Syntax error.
Error\Classes\PayrollTaxEngineUtil\checkInTaxEngine737Syntax error.
Error\Classes\PayrollTaxEngineUtil\checkOutTaxEngine715Syntax error.
Error\Classes\PayrollTaxEngineUtil\getGNISLocations405Variable Symmetry has not been declared.
Error\Classes\PayrollTaxEngineUtil\getMunicipalities395Variable Symmetry has not been declared.
Error\Classes\PayrollTaxEngineUtil\getPoliticalSubDivision315Syntax error.
Error\Classes\PayrollTaxEngineUtil\getPoliticalSubDivisionByTaxCode205Syntax error.
Error\Classes\PayrollTaxEngineUtil\getSchoolDistricts415Variable Symmetry has not been declared.
Error\Classes\PayrollTaxEngineUtil\getTaxEngineLocationCodeList385Variable Symmetry has not been declared.
Error\Classes\PayrollTaxEngineUtil\getTaxEngineVersion1039Syntax error.
Error\Classes\PayrollTaxEngineUtil\getTaxTableVersion1038Syntax error.
Error\Classes\PayrollTaxEngineUtil\money2Real1140Syntax error.
Error\Classes\PayrollTaxEngineUtil\real2Hours1122Syntax error.
Error\Classes\PayrollTaxEngineUtil\real2Money1122Syntax error.
Error\Classes\PayrollTaxEngineUtil\real2Rate1122Syntax error.
Error\Classes\PayrollTaxEngineUtil\taxCalculation2TaxCode1162Syntax error.
Error\Classes\PayrollTaxTypeInitialization\classDeclaration85Syntax error.
Error\Data Dictionary\Tables\PayrollEmployerTaxRegion\Methods\retrieveGNIS125Variable Symmetry has not been declared.
Error\Data Dictionary\Tables\PrlTmpGNIS\Methods\populatePrlTmpGNIS135Variable Symmetry has not been declared.

Example Code containing error:

“Symmetry.TaxEngine.BenefitInfo benefitInfo401_403;”
“Symmetry.TaxEngine.STEPayrollCalculator             ste;”
“Symmetry.TaxEngine.STEPayrollCalculator             ste;”

Solution:

On AOT\Reference node, add again the library ste-net.dll

You can find on C:\Program Files (x86)\Microsoft Dynamics AX\60\Client\Bin folder.

Tuesday, 7 April 2015

Field ‘Item number’ must be filled in. when release a product

Reason:
System don’t find any record in EcoResProductIdentifier table.
Solution: 
Use the excel-addin to fill the data in EcoResProductIdentifier table. Make sure to use the same Product number.

Wednesday, 1 April 2015

Cannot delete an unused main account in Dynamics AX 2012 R2

After creating a new financial dimension (about a week elapsed), a decision was made to delete the newly created financial dimension.
We knew these dimension values weren’t used on any posted or un-posted transactions, so the expectation was that we could simply delete these without any issues. So you can imagine the surprise when we tried to delete the dimension values only to receive the following error message:
A financial dimension value is based on the <dimension value> record and has been used on a transaction. You cannot delete the <dimension value> record.
                                    
This error is displayed by the system if records exist within the DimensionAttributeLevelValue table for the given Dimension Value.

So before I move on and explain how the issue was resolved, let me start off with a little caveat…
The description below isn’t a comprehensive breakdown that covers all possible scenarios that result in records being inserted into the DimensionAttributeLevelValue table, but it illustrates the use case scenario that caused the above-mentioned issue.

So when does the system create records in the DimensionAttributeLevelValue table?
One of the use cases that result in records being created in this table is when a user, as an example, creates a new general journal line and enters in the financial dimensions on that line.
At this stage the system creates (if it doesn’t already exists) an entry in the DimensionAttributeValueCombination for the financial dimension combination specified on the general journal line. The make-up of the specified financial dimension combination is then stored in the DimensionAttributeLevelValue table.
For Example:
If the financial dimension combination reads 0100-OU_1-OU_3566, (where 0100 represents the Main Account Id, OU_1 the Department Financial dimension, and OU_3566 represents the Cost Centre Financial dimension), the system will create 2 records in the DimensionAttributeLevelValue table, namely
  • One record will be for the Department Code OU_1
  • The second record will be for the Cost Centre OU_3566.


So knowing this, we were able to deduce that a Journal Line was created to test financial dimension structures and hierarchies. The Test journal line was deleted (not posted), but the action of entering in the journal line resulted in records being created in the above-mentioned tables.

To resolve this, and allow the Dimension Value to be deleted, the records created in the above-mentioned tables would need to be manually deleted.

I’m very interested to know if there is a tool that can be used to ‘clean-up’ any un-used Financial Dimension combinations i.e. financial dimension combinations that were created in the system, but that aren’t associated with any posted or un-posted transactions.
Does anyone know of a tool that does this? (Feel free to leave some comments)


Wednesday, 7 May 2014

Missing SYP labels after upgrading to AX2012 R2 CU7

In some situation could happen that after upgrading to AX2012 R2 CU7 there are missing some SYP labels.
Resolution:
  1. Stop AOS
  2. Delete ALD files from Microsoft Dynamics AX\60\Server\<instance>\bin\Application\Appl\Standard folder
  3. Start AOS again.

The model store has been modified

Solution : After upgrading Microsoft Dynamics AX 2012 you will get the following dialog upon starting the AX client:

When you have performed the appropriate upgrade actions (AOT compile, code check, CIL compile, synchronize, upgrade scripts), the dialog still might pop up every time you start the client. Selecting "Skip" will not solve this.

To avoid the dialog from appearing, you can do one of the following:

  1. If you have started one of the checklists, check that you have marked alle the actions as complete by clicking the link "Mark as complete" on each action.
  2. Prevent the dialog from appearing by clicking
    System administration > Setup > Checklists > Prevent startup of checklists
  3. Even after above steps still the pop up is coming then write a job containing this line
         SysCheckList_Update::finalizeMinorUpgrade();

        Hint: AX uses info.startup() to check, if checklist must be opened.    

I would prefer the first alternative, since it will require you to confirm that you actually performed all the necessary upgrade steps.

Tuesday, 3 December 2013

Error “For more information about this error navigate to the report server on the local server machine, or enable remote errors” when opening SSRS Report in AX

Error “For more information about this error navigate to the report server on the local server machine, or enable remote errors” when opening SSRS Report in AX


Resolution:  Generate Incremental CIL


1. First Check Local business connector is  correct.
2. And Check Domain business connector is  correct.
3. Then Put increment CIL


For me it had solve the problem

Monday, 2 September 2013

Unable to find appropriate service endpoint information in the configuration object

Error:  "An  occurred during setup of Reporting Services extensions. Reason: Unable to find appropriate service endpoint information in theconfiguration object"
Cause : BIServices port is not deployed.
Resolution :
  • Activate inbound ports BIServices (System Administration > Setup > Services and AIF > Inbound ports)
  • Delete the WCFCONFIG entry in registry under the Dynamics AX current user hive key (HKEY_CURRENT_USER\Software\Microsoft\Dynamics\6.0\Configuration\Orig)
  • Restart the box
  • Try installation again.  If fails then continue with
  • Make the BC proxy user a local admin on the SRS box.
  • Redeploy BIServices services: AOT > ServiceGroups > Right Click BIServices and deploy.
Enviorenment Details  - Dynamics ax 2012 R2

Explanation: Reporting services Extension is a service that occupies a port in Dynamics AX 2012. When ever you use Reporting services extension you need to activate a port BIServices. 

Steps For Registry :

1.     Click Start, and then click Run.
2.     In the Open box, type cmd and then press ENTER.
3.     In the Open box, type regedit and then press ENTER.
4.  Locate the following subkey in the registry: 
         HKEY_CURRENT_USER\Software\Microsoft\Dynamics\6.0\Configuration\Orig
    5.  Delete the file "WCFCONFIG" file




Tuesday, 23 July 2013

Unable to log on to Microsoft Dynamics AX

Error: Unable to log on to Microsoft Dynamics AX.
It can happen that even though AOS and SQL Server seem to be running fine and with no errors in the EventLogs, you get an "Unable to log on to Microsoft Dynamics AX" error message when opening the AX client. This is a problem with stored passwords in the client machine.

Solution

Please navigate to "Control Panel-->User Accounts-->Manage Password" ,select the particular user and change to 'Advanced' tab and click 'Manage Passwords' and change the existing password (or) Remove the Password.

Wednesday, 26 June 2013

Project Invoice Proposal Approvals in Microsoft Dynamics AX 2012 R2

Hello Everyone,
Here is a quick post on an update on the approval process of project invoice proposals in Microsoft Dynamics AX 2012 R2 release.
In the AX 2012 feature pack release(Until Cumulative Update 4), the project invoice proposals were always forced or required to go through the workflow for approval.
I came across many situations where customers did not want their invoice proposals to go through the workflow approval process as it is not required as per their business policies and rather have them posted directly. But in AX 2012 feature pack release, there was no way to have the invoice proposals not go through workflow approval.
Microsoft has introduced a design change in AX 2012 R2 release, by which we can now have project invoice proposals not routed through the review and approval process in workflow.
If you unmark the “Enable processing invoice proposals in workflow checkbox”, then you can directly post the invoice proposals without having it to go through the workflow process.

image