How to Create a new “Parameters form” for New Module developed in AX

How to develop a new “Parameters form” in case of New Module developed in AX.

We go through it by considering an example of creating the new module as Payroll.

So now we will create the Payroll Parameters setup form for the payroll module.

Initially create a Parameters table for the Module, the naming convention should be the Module name followed by Parameter as in this case it is PayrollParameters table….and need to have the fields accordingly what is required in the Parameters table.

Set the following properties for the parameter table as…

Create a parameter form by considering the PayrollParameters andNumberSequenceReference as data sources. And set the following properties for the data source in the form level as

First thing is that there shouldn’t be any provision to create the record in the parameters form. The record in the Parameters should be by default and it can be updated as per the functionality required

So when creating the new company in the Axapta, the parameters form should have the default values.

To have the default values in the parameters we need to have the following code in the table  level of find() of PayrollParameters tables .

static PayrollParameters find(boolean _forupdate = false)

{

    PayrollParameters  parameter;

    if (_forupdate)

    parameter.selectForUpdate(_forupdate);

    select firstonly parameter

        index Key

        where parameter.Key == 0;

    if (!parameter && !parameter.isTmp())

    {

        Company::createParameter(parameter);

        NumberSeqReference::construct(PayrollParameters::numberSeqModule()).load();

    }

    return parameter;

}

Source :http://kollidynamics.blogspot.in/2011/08/how-to-develop-new-parameters-form-in.html

Displaying a Message Box

You can display a message in a modal dialog box by using the Box class.

Some methods in the Box class display a dialog box that contains multiple buttons. These methods have a parameter for choosing which button has focus when the dialog box is first displayed. This parameter is of type DialogButtonenum. Most of these multiple-button methods return a value of type DialogButton enum. This returned value enables your program to branch based on which button the user clicked.

Note
The Box application class calls the DialogBox system class. Don't call it directly—always call the Box class instead.

Creating a Message Box

---

The following are guidelines to help you create an effective message box:

• Choose a Box method that matches your purpose.
• Write the information text to match the buttons in the box.
• Choose the button best suited for having initial focus.
• Use the returned DialogButton value to direct the branching in your code.

Box Class Methods

---

The following table describes the Box class methods and their associated DialogBoxType system enum values.

Box class static method name	AssociatedDialogBoxTypeenum value	Description
info	InfoBox	The OK button is the only one that the info method displays in the dialog box. Use this method to display general information messages rather than for warning or error messages.
infoOnce	InfoBox	The infoOnce method is similar to the info method but with the following differences: Your code cannot set the text in the title bar. An additional header section is displayed under the title bar, and you can set the text that displays in the header. A More info button is present. When clicked, it opens a Web browser to the URL string that you supply through a parameter. The infoOnce method returns void, even though it has two buttons.
infoOnceEx	InfoBox	The infoOnceEx method is similar to the infoOnce method but with the following differences: The infoOnceEx method has a parameter that can be passed in to set the text in the title bar. The infoOnceEx method has a Boolean parameter for choosing whether to have the caller thread continue processing while the user reads the message in the dialog box.
okCancel	OkCancelBox	The OK and Cancel buttons are displayed in the dialog box. Call this method when the user must confirm or reject an action.
stop	StopBox	The OK button is the only one displayed in the dialog box. Use this method to display a message when the user should stop attempting their action or when a process has stopped running.
warning	WarnBox	The OK button is the only one displayed in the dialog box. Use this dialog box for a warning message.
yesAllNoAllCancel	YesToAllNoToAllBox	The buttons displayed in this dialog box are Yes, Yes to all, No, No to all, and Cancel.
yesNo	YesNoBox	The buttons displayed in this dialog box are Yes and No. Call this method when you need the user to make a choice.
yesNoNoAllCancel	NoToAllBox	The buttons displayed in this dialog box are Yes, No, No to all, andCancel.
yesNoAxaptaForm	YesNoBox	The yesNoAxaptaForm method is similar to the yesNo method but with the following differences: The yesNoAxaptaForm dialog box has a different image. The yesNoAxaptaForm dialog box is wider.
yesNoCancel	YesNoCancelBox	The buttons displayed in this dialog box are Yes, No, and Cancel. Call this method when the yesNo method is insufficient.
yesNoOnce	YesNoBox	The yesNoOnce method is similar to the yesNo method but with the following differences: The yesNoOnce dialog box has a different image. The yesNoOnce dialog box has a check box that the user can select to suppress any further occurrence of an associated message.
yesYesAllNoCancel	YesToAllBox	The Yes, Yes to all, No, and Cancel buttons are displayed.

Example

---

The following example displays a message box that contains buttons labeled Yes, No, and Cancel. The No button has initial focus. When a button is clicked, a message is displayed in the Print Window to indicate which button was clicked. Run this example as a job in the Application Object Tree (AOT).

static void JobBoxDemo(Args _args)
{
    DialogButton diagBut;
    str strMessage = "The No button should have initial focus.";
    str strTitle = "Title";
    ;
    diagBut = Box::yesNoCancel(
        strMessage,
        DialogButton::No, // Initial focus is on the No button.
        strTitle);
    if (diagBut == DialogButton::No)
        {
            print "The No button was clicked.";
        }
    else
        {
            print "The button that was clicked was: ", diagBut;
        }
    pause;
}

Source : http://msdn.microsoft.com/en-us/library/aa860308(v=ax.50).aspx

Create Bat file to execute commands in AX

Hi,

I wanted to execute the close ax application on certain conditions, so that i have used the .bat file to execute the same.

1) How to create bat file?

1. Open notepad and enter the command that you have to execute.
2. As I have to execute the close command for ax i used the following line of code.

         @echo off
          taskkill /F /im Ax32.exe

     3. "Save As" the notepad file with selection of "Save As Type:" : "All files" and enter file name with .bat extension.

2) How to call bat file from ax application ?
    I have executed the "Close application code" on the button click.
 
        void btnCloseAppl()
   {
       str path;
       ;
       path="C:\TestFileToCloseAppl\Axclose.bat";  
       //Kindly check the path may be have to add '\' in between the path  
       winapi::shellExecute(path);
   }

Thanks,
Kishor

User Login and password Form design in AX 2009

If you need to store passwords in AX there are some application objects, classes and attributes that you can use.  This post details the steps you can take to allow entry of a password in a form, which will be stored in the database.



1.  Add the password field to your table. This field should be of type ‘CryptoBlob’ which is a container that contains binary data:



2. Add an edit method for the password to your table:

view source

print?

01	//BP Deviation Documented

02	edit Password editPassword(boolean _set = false, Password _pwd = '')

03

{

04	CryptoBlob cryptoBlob = connull();

05

;

06

07

if (_set)

08

{

09	this.Password = WinapiServer::cryptProtectData(str2cryptoblob(_pwd));

10

}

11

12	return (this.Password == connull()) ? '' : 'xxxxxxxx';

13

}

3. Drag and drop the edit method to your form and ensure that the attribute ‘PasswordStyle’ is set to ‘Yes’:

4. To retrieve the password you will need a method similar to the following:

view source

print?

1	static Password getPassword(UserId _userId)

2

{

3	CryptoBlob cryptoBlob = TutorialPasswordTable::find(_userId).Password;

4

;

5

6	return (cryptoBlob == connull()) ? '' :

7	cryptoblob2str(WinapiServer::cryptUnProtectData(cryptoBlob));

8

}

Disclaimer
The safest way to handle passwords is not to store them in the database. The steps described in this post are better than storing the password in the database as plain text, but far from bulletproof. Please ensure that AX security is fully considered if using this method (Table level security, access to code / development etc)
You can download the tutorial as an xpo here from axaptapedia

Restrict multiple times user login in AX 2009

Hie,

Currently in Ax 2009 the user can login  multiple times in application, so to restrict users to open Ax 2009  multiple times we can use the following code.

** Before implementing this please take backup of your application files

Open Classes --> info --> StartupPost metod 

and copy following code into this method

void startupPost()

{
// To restrict user login form second login
xSession                    session;
SysClientSessions    SysClientSessions;
UserId                      currentUserId;
int                             counter;

;

currentUserId = curUserId();

if(currentUserId!=”Admin”)                     // Allow Admin User to login multiple time
{
    while select SysClientSessions
    where SysClientSessions.userId == currentUserId  

    && SysClientSessions.Status == 1   // 1 : Login 0 : Logout

    {
        session = new xSession(SysClientSessions.SessionId, true);

        if (session && session.userId())
        {
              counter++;
        }
    }

    if(counter>=2)
    {
         Box::stop(“Already Logged-in : The same user id can’t log in twice.”);
         infolog.shutDown(true);
     }
}
}

Debug Assertion Failed Error

Hi Friends,

While opening the "open transaction editing" from Customer Details Form --> Functions the error raised in debug mode as

Debug assertion failed

The debug window shows the code as Debug::assert( variableName or condition)
For this i debug all the classes and table methods which are included in it and at the end luckily resolve the error.

Solution: 
1) Go to class CustVendOpenTransManager
2) Go to method new()
3) Comment the line this.initMarkedTransBalances(); or you can skip this line while debug this class. ( i prefer for skipping the line of code while debugging the class because editing class will leads to import export of that class which will again taking a time.)
4) The next line of code which includes this.initMarkedPayment(); execute this with F11 and further code till you get window mentioned in point 5.

I have attached the screen shot of that class and hi-lighted the line.

5) Skip all the code execution till this window appears to you. Execute the last line of code i.e.  this.refereshMarkedTransactionsBalances();

6) After this just run the remaining code of classes and you will get the following window.

7) Click on Yes and the error is resolved.

Regards,

Kishor Jadhav

How to put Ax 2009 machine back to a clean state (remove the usr layer)

1. Stop the AOS (default service name is AOS50$01 for AX5).


2. Delete the user layer aod file (…\Microsoft Dynamics AX\50\Application\Appl\AXDB_App\axusr.aod) and *.aoi files.


3. Delete the metadata file in client %userprofile%\AppData\*.auc


4. Start the AOS.


5. Run AX client and do a synchronize on the Data Dictionary node on the AOT tree.

History of Dynamics Ax(Axapta)

 

Axapta is a highly respected accounting system and ERP solution which wasoriginally brought to the United States from Europe in IBM in 1996. Axapta wasfirst created in 1983 by brothers Erik and Preben Damgaard in Copenhagen,Denmark. The company claims that from the start, Axapta wanted to create aninternational product that was integrated, scalable and flexible so that theywould be able to build one CD for all markets and platforms. It was ErikDamgaard's vision to build a platform that could evolve with technology andmarket demands. Written completely in Java, Axapta is designed to be a complete ERP solutionwhich includes advanced distribution, process and discrete manufacturing,built-in CRM capabilities, and outstanding customization. The product grewsteadily throughout Europe and in 1996, IBM brought Axapta to the United Statesmarket. It is important to note that IBM s motivation behind teaming up with asuccessful software application is primarily for marketing leverage. Most peoplewon t attend a seminar on hardware, databases, or infra-structure and IBM has along standing history of using various software applications to attractprospects. For example, IBM teamed up with Business Management Series in 1988,Platinum Software in 1990, Lotus Notes in 1994, Axapta in 1996, and ACCPAC in1999. This is a marketing strategy that works well for IBM, but the point isthat IBM s primary focus was never on Axapta. After the IBM/Axapta relationshipplayed out in 2000, Axapta (Damgaard Software) merged with their long-timeDanish rival Navision Software.

1998 - Axapta 1.0 is released in March.

• Released in the US and Denmark
• Financial, trade, inventory management, logistics and production, Microsoft SQL Server 6.5

1998 - Axapta 1.5 - Early release in Norway, Sweden, Germany, UK, Netherlands, Austria, Switzerland, Belgium Spain and the European Union.

• Publishing Manager
• Call COM
• Service Pack technology
• Microsoft SQL Server 7.0

1999 - Axapta 2.0 - July:

• Project Accounting module
• WMS
• External OLAP
• Option Pack concept
• ActiveX support
• COM-connector and an early release of Axapta Object Server

2000 - Axapta 2.1 - January: Market demands from Germany, Austria, Switzerland and Spain.

• Web tools and CSS (The first WebApp)
• Microsoft SQL Server 2000, database log.
• Receives Microsoft Windows 2000 logo.

2000 - Axapta 2.5 – December: Complete Web applications development environment.

• Auto upgrade tool
• ESS (Project)
• Banking
• First step of Load’n’Go
• OLAP within Axapta
• XML support
• FA to Denmark, Austria and UK. Domains and ASP support
• DBCS Support.

2001 - Axapta 2.5 Market Pack – October: Released in France and Italy.

• Marketing Automation (CRM)
• Commerce Gateway
• Product Builder (Web application as well), training
• Event Management (Web application as well).

2002 - Microsoft Axapta 3.0 - October:

• Microsoft Axapta Enterprise Portal, intercompany collaboration.
• New security and configuration keys.
• Expanded geographical reach (more countries).
• Demand planning.
• Enhanced partner productivity tools.

2006 - Dynamics AX 4.0  - March:  The seventh major Axapta release brought with it an updated look and feel. As the first version that Microsoft was involved in from the beginning it attempted to integrate better with existing Microsoft technologies.

• AOS became a true Windows service
• .Net business connector was provided
• CLR Interoperability was introduced
• XML data exchanges were supported through a set of code classes (Application Integration Framework)
• Full Unicode support was introduced
• Service Management module.

2008 - Dynamics AX 2009  - June: Originally named AX 4.1, later renamed to AX 5.0 (and finally AX 2009), the eighth major release of Axapta brings with it yet more improvements to the UI. This new version adds role-based concepts to both the Enterprise Portal and windows clients, support for timezones (utc), a new Site inventory dimension, and Enterprise Portal development through Visual Studio projects.
2011 - Dynamics AX 2011  - Q1: Sometimes dubbed AX 6, it is said to include additional improvements to the user interface and application enhancements focused on specific industries like Retail, Media & Entertainment, and Public sector. Originally AX 2011 was due to be released toward the middle of 2010, but this has since been put back to Q1 2011.

Error messages returned by Setup of Dynamics Ax

The following table lists the error messages that Setup can return, and possible causes for each.

Error message	Possible cause
You must be an administrator on the local computer to run Microsoft Dynamics AX Setup	Your domain account is not a member of the local computer group Administrators.
An error occurred while the log file {0} was initializing. Confirm that you have rights to the folder that contains the log file. You might need to be an administrator to access some folders. The following messages would have been written to the log if you had rights to it:	Your domain account does not have rights to write to the directory where the log files are placed (Documents and Settings\All Users\Application Data\Microsoft\Dynamics AX\Dynamics AX Setup Logs\Date Time\AxSetupLog.txt). Contact a system administrator.
An unexpected exception occurred. See the log file {0} for details.	An unexpected error occurred. Review the messages below this line to determine the problem.
The parameter {0} was not recognized.	A parameter sent to the Setup program was not recognized. Review the syntax you are using.
The parameter {0} contains the invalid value {1}. Cause: {2}.	A value included for a Setup parameter was incorrect. Review the syntax you are using.
The parameter file {0} was not found.	The location of the file in the parmfile parameter passed to the Setup program could not be found.
An error occurred while parameter file {0} was being read. Error:	The parameter file passed by the parmfile parameter could not be read. Review the file to identify the error.
Setup cannot install from this location because the.NET security level for this security zone is not set to Full Trust. You can change the .NET security level for a zone in .NET Framework Configuration in Control Panel.	Setup cannot install from this location because the .NET security level for this security zone is not set to Full Trust. You can change the .NET security level for a zone in Control Panel > .NET Framework Configuration.
The parameter {0} contains the invalid value {1}. Specify 0 for False or No. Specify 1 for True or Yes.	An invalid value has been passed to a parameter. Specify 0 for false or no. Specify 1 for true or yes.
The parameter {0} contains the invalid value {1}. The value must be one of the following: {2}.	An invalid value has been passed to a parameter. Review the syntax you are using to pass the parameter values.
The parameter {0} contains the invalid value {1}.	An invalid value has been passed to a parameter. Review the syntax you are using to pass the parameter values.
You must set a value for the parameter {0} if the parameter {1} is set to {2}.	The parameter you set is dependent on the value of another parameter. Review the Setup parameters documentation.
The required Lists file {0} was not found.	The AxSetupLists.txt file could not be found. It is part of a standard Microsoft Dynamics AX installation, and should be available on the DVD. Copy the file to the share you are installing from.
An error occurred while reading the AxSetup Lists file {0}. Error:	The AxSetupLists.txt file could not be read. It is part of a standard Microsoft Dynamics AX installation, and should be available on the DVD. Copy the file to the share you are installing from.
An invalid record format was found in file {0}, line {1}. The line should contain {2} values separated by tabs. Found: {3}	The file contains an invalid record format. Re-create the file and try again.
An invalid record format was found in file {0}, record {1}, section '{2}'. Field {3} cannot be: '{4}'	The file contains an invalid record format. Re-create the file and try again.
The LicenseTerms section is missing from file {0}.	The LicenseTerms required for this installation could not be found in the AxSetupLists.txt file. It is part of a standard Microsoft Dynamics AX installation, and should be available on the DVD. Copy the file to the share you are installing from.
The license file {0} was not found.	The License file could not be found. It is part of a standard Microsoft Dynamics AX installation, and should be available on the DVD. Copy the file to the share you are installing from.
An error occurred while reading License file {0}. Reason {1}	The License file could not be read. It is part of a standard Microsoft Dynamics AX installation, and should be available on the DVD. Copy the file to the share you are installing from.
The LicenseTermsVersion code {0} is not valid. Valid codes can be found in the LicenseTerms section of file {1}	The parameter file contains an invalid LicenseTermVersion code. Refer to the AxSetupLists.txt file on the DVD for valid codes.
The ClientLanguage code {0} is not valid. Valid codes can be found in the Language section of file {1}.	The parameter file contains an invalid ClientLanguage code. Refer to the AxSetupLists.txt file on the DVD for valid codes.
The ApplicationRegion code {0} is not valid. Valid codes can be found in the Region section of file {1}.	The parameter file contains an invalid ApplicationRegion code. Refer to the AxSetupLists.txt file on the DVD for valid codes.
The ClientHelpLanguages code {0} is not valid. Valid codes can be found in the Language section of file {1}	The parameter file contains an invalid ClientHelpLanguages code. Refer to the AxSetupLists.txt file on the DVD for valid codes.
The Language section is missing from file {0}.	The Language section is missing from the AxSetupLists.txt file. The file is part of a standard Microsoft Dynamics AX installation, and should be available on the DVD. Copy the file to the share you are installing from.
The Region section is missing from file {0}.	The Region section is missing from the AxSetupLists.txt file. The file is part of a standard Microsoft Dynamics AX installation, and should be available on the DVD. Copy the file to the share you are installing from.
The name of the SQL Server instance cannot include blanks or spaces.	The name of the Microsoft SQL Server instance cannot include blanks or spaces. Review the name of the SQL Server you are connecting to, and try again.
You do not have permission to create a new database. For more information, contact the database administrator.	To create a database, you must be a member of the DBCreators role on the database server.
You do not have permission to configure the database server {0} to allow the Application Object Server (AOS) to connect to it. For more information, contact the database administrator.	To allow another user to connect to a database, you must be a member of the Security Administrators role on the database.
The database name cannot include blanks, spaces, or any of the following characters: \ / . , : [ ] ( ) - ;	The name of the SQL Server instance cannot include blanks, spaces, or any of the following characters: \ / . , : [ ] ( ) - ;. Review the name of the SQL Server you are connecting to, and try again.
The DbConnectionTimeout value must be from 10 through 999.	The SQL Server database connection time out value is invalid. Contact the database administrator for help.
The path {0} contains invalid characters.	The path contains invalid characters. Review what you have entered, and try again.
You must enter a complete path for the application file installation directory. Valid formats for the path include: c:\\pathname \\\\MyServer\\SharedPath	The path you entered for the application file installation directory was incomplete. Valid formats for the path include:
	C:\\ pathname
	\\\\ MyServer \\ SharedPath
The application files installation path is not valid. The root location of the path ({0}) must exist before you install the application files.	The root location of the path for the application file installation directory must exist before you install.
The application files installation folder does not exist. The path must reference a location where application files have been installed.	You are attempting to connect to an application files folder that does not exist. The path must refer to a location where application files have been installed.
Setup detected existing files in the application files installation folder. The folder must be empty for Setup to proceed. To ensure that the folder is completely empty, in Windows Explorer, on the Tools menu, click Options. Select the View tab, and in the list of advanced settings, select the Show hidden files and folders option and clear the Hide protected operating system files check box. Then open the installation folder.	The application files directory you are installing to contains files. To install using a parameter file, the directory must be empty. Copy the application files to another location if you want to save them.
Setup detected existing files in the installation folder for the application files. The folder must be empty for Setup to proceed. Deleting the existing application files will remove all application customizations. To save your customizations, move the application files to a different folder. Do you want to delete the files currently in the folder?	The application files directory you are installing to contains files. If you continue to install, they are deleted. Application files contain all customizations.
The name of an application instance cannot include any of the following characters: \ / . , : [ ] ( ) -	The application instance name contains one of the following invalid characters \ / . , : [ ] ( ) -. Review what you have entered, and try again.
You must provide a value for {0}.	You cannot proceed with Setup without providing a value for this parameter.
A database named {0} already exists on the server {1}. Enter another name.	You have attempted to create a database that has the same name as an existing database. Enter a new database name, delete the existing database and begin again, or in the Setup wizard select the option to connect to an existing database.
Setup cannot find the database {0} on the server {1}. Check that the name is correct.	Setup cannot locate the database you entered. Validate the name, and try again.
The Application Object Server cannot be installed on this operating system. Install it on a server running Windows Server 2003.	You cannot install the role you selected on a computer running this operating system. For details, see Hardware and software requirements.
Setup has detected that this computer is running Windows Server 2003 without Service Pack 1. We strongly recommend that you install Service Pack 1.	Service Pack 1 for Windows Server 2003 provides security enhancements. We strongly recommend that you install it. Installing on Windows Server 2003 without Service Pack 1 is not a supported configuration.
The Application Object Server (AOS) port number must be four digits long.	The TCP/IP value you provided is not valid.
An Application Object Server (AOS) instance name cannot have more than {0} characters and may not contain spaces or the characters / or \.	The name you entered contains invalid characters. Review what you have entered, and try again.
Setup detected an existing Application Object Server (AOS) instance named {0}. Instance names must be unique. Enter another name.	Setup detected an existing Application Object Server (AOS) instance named {0}. Instance names must be unique. Enter another name.
Setup cannot install another Application Object Server (AOS) instance on this computer. No more than {0} AOS instances can be installed on a single computer.	Setup cannot install another Application Object Server (AOS) instance on this computer. No more than {0} AOS instances can be installed on a single computer.
Bitmap You must enter a fully qualified path for the {0} installation directory. Valid formats for the path include: c:\\pathname.	You must enter a fully qualified path for the {0} installation directory. Valid formats for the path include: C:\\pathname.
	Note
	You cannot install to the root directory—you must install to a named folder.
The Application Object Server (AOS) installation path is not valid. The root location of the path ({0}) must exist before you install the AOS.	The root location of the path for the AOS installation directory must exist before you install.
Warning: Setup could not connect the Application Object Server (AOS) instance to the database because it could not add the AOS account {0} to the database server as a login account. Installation of the AOS instance was completed, but the AOS instance cannot run without a connection to the database. You might not have permission to modify security on the database server. A database administrator can grant permission manually, and then AOS setup will be complete. For more information, see the installation log file for the error message returned by the database.	Setup could not connect the Application Object Server (AOS) instance to the database because it could not add this computer’s AOS account (a domain account, or the Network Service account of the computer running the AOS instance) to the database server as a login account. Installation of the AOS instance was completed, but the AOS instance cannot run without a connection to the database. You might not have permission to modify security on your selected database server. A database administrator can grant permission manually, and then AOS setup is complete. For more information, see the installation log file for the error message returned by the database.
Setup has detected that this computer is not running the recommended service pack for this operating system. We strongly recommended that you run this computer on Windows 2000 Server with Service Pack 4 or Windows XP with Service Pack 1.	Service Packs provide security enhancements. We strongly recommend that you keep your computers fully up-to-date with the Service Packs for the operating system you are running. Installing on a system without the appropriate service pack is not a supported configuration.
The client installation path is not valid. The root location of the path ({0}) must exist before you install the client.	The root location of the path for the client installation directory must exist before you install.
The name of the Application Object Server (AOS) instance to connect to {0} cannot include blanks, spaces, or any of the following characters: ` ~ ! # $ ^ & * ( )	The name of the Application Object Server (AOS) instance to connect to {0} cannot include blanks, spaces, or any of the following characters: ` ~ ! # $ ^ & * ( )
To install a client, .NET or COM Business Connector, or any application that uses Business Connector, you must provide the name of an Application Object Server instance (AOS) to connect to.	To install a client, .NET or COM Business Connector, or any application that uses Business Connector, you must provide the name of an Application Object Server instance (AOS) to connect to.
Setup cannot find the client configuration file {0}.	Setup cannot find the client configuration file specified in the setup parameters you passed. Check to be sure that the file is in the location specified.
SQL Server Reporting Services must be installed before a Microsoft Dynamics AX reporting server can be set up.	Microsoft SQL Server 2005 Reporting Services was not detected on this computer.
Setup cannot find the SQL Server Reporting Services instance. Check that the name is correct.	Setup cannot find the SQL Server Reporting Services instance. Check that the name is correct.
You must configure the Report Server virtual directory and Report Manager virtual directory for SQL Server Reporting Services instance {0} before you install a Microsoft Dynamics AX reporting server. Use the SQL Server Reporting Services Configuration Tool.	You must configure the Report Server virtual directory and Report Manager virtual directory for SQL Server Reporting Services instance {0} before you install a Microsoft Dynamics AX reporting server. Use the SQL Server Reporting Services Configuration Tool. For more information, see Install and configure a reporting server for ad hoc reporting.
Setup could not connect to the database server {0}.	The database server may be unavailable. Check with the database administrator.
The database to be referenced by the reporting server {0}, does not exist on the server {1}.	The database that the reporting server is attempting to connect to cannot be found. Check that you have entered the path correctly.
The database server {0} does not contain any databases.	The database that the reporting server is attempting to connect to cannot be found. Check that you have entered the path correctly.
Setup could not add the account {0} to the database server {1}as a login. The reporting server was installed on this computer without permission to access this database. It cannot run without a connection to the database. You might not have permission to modify security on the database server. A database administrator can grant permission manually, and then the reporting server setup will be complete. For more information, see the installation log file for the error message returned by the database.	Setup could not add the account {0} to the database server {1} as a login. The reporting server was installed on this computer without permission to access this database. It cannot run without a connection to the database. You might not have permission to modify security on the database server. A database administrator can grant permission manually, and then the reporting server setup is complete. For more information, see the installation log file for the error message returned by the database.
An error occurred during registration of the data source in SQL Server Reporting Services. See the log for details.	An error occurred during registration of the data source in SQL Server Reporting Services. See the log for details.
Setup could not find an installation of Windows SharePoint Services to support Enterprise Portal. Either it is not installed, or the version is outside the expected range of 6.0.2 to 7.0.0. If you continue, Enterprise Portal will not function until you have set up Windows SharePoint Services.	Setup could not find an installation of Windows SharePoint Services to support Enterprise Portal. Either it is not installed, or the version is outside the expected range of 6.0.2 to 7.0.0. If you continue, Enterprise Portal will not function until you have set up Windows SharePoint Services.
Enter the {0} domain account {1} in the format domain\account.	The domain account you entered was not recognized.
The {0} account {1} cannot be your own account. Contact your system administrator to create a dedicated account.	You cannot use your own domain account to connect to databases. Contact a system administrator for a domain account to use.
You cannot set the account for {0} to a local computer account {1} when the Microsoft Dynamics AX database is not located on the same computer. Use a domain account instead.	If the Microsoft Dynamics AX database is not located on the same computer as the AOS, you cannot use a local computer account to connect to it.
The {0} account {1} was not found on the local computer, or the password is incorrect.	The domain account you entered was not recognized by the local computer, or the password is incorrect.
The {0} account {1} was not found, or the password is incorrect.	The domain account you entered was not recognized, or the password is incorrect.
The application integration server installation path is not valid. The root location of the path ({0}) must exist before you install the application integration server.	The root location of the path for the application integration server directory must exist before you install.
Setup could not create the local Windows security group {0} on this computer. This group must exist, contain the current user {1}, and have rights to update the folder {2} before the application integration server can run. See the log for related messages.	Setup could not create the local Windows security group {0} on this computer. This group must exist, contain the current user {1}, and have rights to update the folder {2} before the application integration server can run. Setup completes without setting up this account.
The application integration framework (AIF) Windows security group {0} already exists. No changes will be made to it.	During installation Setup found that the application integration framework (AIF) Windows security group {0} already exists. No changes are made to it.
The application integration framework (AIF) Windows security group {0}, user {1} already exists. No changes will be made.	During installation Setup found that the application integration framework (AIF) Windows security group {0}, user {1} already exists. No changes are made.
Setup could not create the shared folder /security {0} which the application integration framework (AIF) tools must use when copying files from a client to the AIF VRoot folder. You can set this up manually. The folder on the client is {1}, and the user or group being given access is {2}. See the log for related messages.	Setup could not create the shared folder /security {0} which the application integration framework (AIF) tools must use when copying files from a client to the AIF VRoot folder. You can set this up manually. The folder on the client is {1}, and the user or group being given access is {2}. See the log for related messages.
The shared folder already exists. No changes will be made to it.	The shared folder already exists. No changes are made to it.
Setup could not create the shared folder {0} (code {1}).	Setup could not create the shared folder.
The shared folder was not deleted because it does not exist.	The shared folder was not deleted because it does not exist.
Setup could not delete the shared folder {0} (code {1}).	Setup could not delete the shared folder.
Provide the name of a SQL Server. To specify an instance, use the format MyServer\MyInstance. To specify the SQL Server instance on this computer, enter (local).	Provide the name of a SQL Server. To specify an instance, use the format MyServer\MyInstance. To specify the SQL Server instance on this computer, enter (local).
Setup could not connect to the database server {0}.	Setup could not connect to the database server specified.
If you install files in a location other than the default, work with your system administrator to ensure that access to the folders is appropriately restricted.	If you install files in a location other than the default, work with your system administrator to ensure that access to the folders is appropriately restricted.
A required file is missing from the source location {0}.	Setup could not find a required file. It is part of a standard Microsoft Dynamics AX installation, and should be available on the DVD. Copy the file to the share you are installing from.
A required folder is missing from the source location {0}.	Setup could not find a required file. It is part of a standard Microsoft Dynamics AX installation, and should be available on the DVD. Copy the file to the share you are installing from.
A required folder for region {0} is missing. It should be under {1} and have a name that starts with the letter {2}. See the file AxSetupLists.txt for a list of regional files that should be included in the installer files.	A required folder for the region is missing. See the file AxSetupLists.txt for a list of regional files that should be included in the installer files.
The default Application Object Server (AOS) instance has previously been installed as name {0}	The default Application Object Server (AOS) instance has previously been installed with a different name.
An Application Object Server (AOS) instance {0} has previously been installed as name {1}. Enter another name.	AOS instances cannot be installed on the same computer with the same name.