Monday, October 3, 2011

License is not exist for language en-in

SOLUTION- This is commen error when we create new instanse and upload licence in different language
to license language. following steps help u to find out right solution administrator tools
 2.choose Microsoft Dynamics Ax configuration utility
 3.write language=en-in in configuration command to run at kernal startup(where en-in is license language)
 4.but once u login put right option (language) from tools->option->language
 5.and now clean kernal startup

 Keep on right coding!!!!!!!!

Wednesday, September 14, 2011

Mail Through Code

static void sendEmailThroughOutlook(Args args)
SmmOutlookEMail smmOutlookEMail = new SmmOutlookEMail();
Object smmSendEmail;
args = new Args();;
smmSendEmail = classfactory.formRunClass(args);

if (smmSendEmail)

Import XPO With Code

static void ImportXPOthroughCode(Args _args)
SysImportElements sysImportElements = new SysImportElements();

sysImportElements.newFile("D:\\Axaptacorner.xpo");// XPO filename

Wednesday, August 10, 2011

Drop Down Not Open in EP

Issue: Drop down shows processing instead of open

Solution: Its live issue which i have faced, when clicked at dropdown it shows processing in stead of open in EP. But is browser related issue set IE as your default browser it  will work fine

Hope it help u!!!!!!

Sunday, July 24, 2011

Not enough rights to use table 'Signature log' (SIGSignatureLog)

“Not enough rights to use table 'Signature log' (SIGSignatureLog).”

  (Some time this problem is occurred when we want to see record info of any record)
SOLUTION: After installing AX5 SP1, it creates a new configuration key which it leaves unticked. go into Administration > Setup > System > Confiugration and tick the Electronic Signature tick box

good luck!!!!!!

Wednesday, July 13, 2011

Shrink Data Base Log file upto 1 mb

Error: SQL Error occurred and current voucher not Saved because some data are not saved
Solution: This type of error occurred n many cases but one major error is lack of space in drive where data base installed , so we have to shrink data log file.but it is critical job to do this on live data
so safe side is to done this task through the query.which is as----
(but use this query on test environment before use)

USE  <DatabaseName>


-- Truncate the log by changing the database recovery model to SIMPLE.




-- Shrink the truncated log file to 1 MB.

DBCC SHRINKFILE (<Name>_Log, 1);


-- Reset the database recovery model.




Tuesday, May 31, 2011

Unable to create ActiveX Control. cmx phone Control

Basically this error(Unable to create ActiveX Control. cmx phone Control) is occured when we unstall Microsoft Dynamicx Ax 4.0 and AX 2009 Still in System
and when we open AX this Error(Unable to create ActiveX Control. cmx phone Control) occure .
Solution: For Remove this error just copy smmphone.ocx from other System where AX 4.0 installed
and put this on same path as-Installed Drive\Program Files\Microsoft Dynamics AX\40\Client
 thats all.

Phase of Implemantation

Partner accomplishments during phase
·                       Evaluates a customer's business processes and infrastructure
·                       Prepares a proposal
·                       Analyzes the current business model
·                       Produces a gap/fit analysis
·                       Creates the requirements documentation
·                       Feature design
·                       Data migration design
·                       Test criteria
·                       Technical design
·                       Develops the features
·                       Tests the features and functions
·                       Creates and tests the user documentation
·                       Sets up the production environment
·                       Configures the system
·                       Migrates data
·                       Tests the system
·                       Trains the end-users
·                       Gets the system up "live"
·                       Clears pending issues
·                       Finalizes the user documentation and knowledge transfer
·                       Conducts a post-mortem of the project
·                       Provides on-going support
The activities involved in this phase are on-going activities performed after project close and throughout any future involvement with the client.
·                       Analyzes the system to determine how it can best be optimized for the customer's needs
·                       Performs the optimization
·                       Tests
The purpose of this phase is to help the customer refine the benefit they get from the business solution. Many times, after the implementation project is complete, customers desire minor changes to their system. This phase understands that need and supports the Customer for Life scenario.
·                       Reviews the customer's business processes
·                       Aligns the business processes to new functionality
·                       Sets the systems in place to support the upgrade
·                       Creates value to maintain a Customer for Life scenario

Thursday, March 10, 2011

Spelling Checker in Axapta

This is very simple and quite interested code to check spelling in Axapta from Job

Try it !!!!!!!!!!!!

 static void Jit_Spelling_Checker(Args _args)
    SysSpellChecker sp = SysSpellChecker::newLanguageId('en-us');

In Next post we will test Spelling and print possible Suggetion .

Create Form Through Job

This is simple code to Create form through job

static void CSL_FormUsingCode(Args _args)
    Form                                       form;
    FormRun                                 formRun;
    Args                                        args;
    FormBuildDesign                     formBuildDesign;
    FormBuildControl                    formBuildControl;
    FormBuildTabControl              formBuildTabControl;
    FormBuildTabPageControl      formBuildTabPageControl;
    FormBuildGridControl            formBuildGridControl;
    FormBuildDatasource             formBuildDatasource;
    FormBuildStringControl          formString,formString1;

    form = new Form();
    formBuildDatasource         = form.addDataSource(tableStr(PurchTable));
    formBuildDesign                = form.addDesign('design');
    formBuildTabControl         = formBuildDesign.addControl(FormControlType::Tab, 'Tab');
    formBuildTabPageControl  = formBuildTabControl.addControl(FormControlType::TabPage,'General');
    formBuildGridControl        = formBuildTabPageControl.addControl(FormControlType::Grid, 'Grid');
    formString                         = formBuildGridControl.addDataField(, fieldNum(PurchTable,PurchId));
    formString1                       = formBuildGridControl.addDataField(, fieldNum(PurchTable,PurchName));
     args = new Args();
    formRun = classFactory.formRunClass(args);

Friday, March 4, 2011

Restore Ax Environment(Ldf,Mdf) to Unavailable Domain

Problem :
If u restore the Axapta Backup to unavailable Domain , Then U find following error

Even the domain administrators do not gain access.
User in Ax are link to the domain controller for which the system is installed. The users are ‘imported’ into Ax, resulting in the user actually be able to startup an Ax client, logging into Ax and performing actions for which the user has been granted access in Ax. 
This information, which user in which domain is allowed to perform which action is part of the Ax database. This includes any trusted domains, for example in case of a traditional perimeter network. 
But what if you restore an Ax database that was part of another domain? Even if you are the domain administrator, you will get the ‘You are not a recognized user of Microsoft Dynamics Ax. Contact your system administrator for help.’ message.  
The reason for this error is that the system only recognizes users from the old domain. This can be solved to updating the data directly using the database manager. In case of MS SQL server:
- Go to the Ax database. You can determine which database instance and database is used by checking the AOS configuration. 
- Find the dbo.USERINFO table
- Open this table and find the record with ID value ‘Admin’. This user has in a normal scenario all rights, but may differ per installation. You can also use SQL to update the record, what ever makes you happy. 
- Update the following fields to reflect the current domain credentials. Bottom two lines can be ignored in this screenshot, the top line has the ID ‘Admin’ in this example:
- SID – The Security Identifier of the account specified in the networkdomain and networkalias. See section ‘Get your SID’.
- NETWORKDOMAIN – you current login domain
- NETWORKALIAS – your current windows login name
- You might want to make sure the field ‘ENABLED’ has the value 1. Otherwise the user is disabled, and you will still not be able to login. 
- Save the record
- Open Ax
- Create your own users / import from the Domain. 

Get your SID
Create a file with the extension .VBS. Copy the following info:
strComputer = "." 
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2") 
Set objAccount = objWMIService.Get("Win32_UserAccount.Name='<user>',Domain='<domain>'") 
Wscript.Echo objAccount.SID
Replace <user> with your user name, and <domain> with the domain. This script can be run from any computer in the domain, it does not have to be the domain controller.  A popup will appear with your SID: