Friday, February 24, 2012

EP and Roll Center Installation AX 2009

Installation steps for Enterprise Portal and Roll center in Microsoft Dynamics AX 2009.

  1. Install the prerequisite for the EP installation
  2. Run the setup and select EP and Roll center at first stage
  3. Click Next, if any prerequisite yet to be install it will sugget u and select the path of the sharepoint exe to install and configure it at the same time of installation.
  4. In the next stage it will show u the default web site for selection and to check box for configure and create a new website. Select Default Web site from drop down list and chek both the checkbox.
  5. Install the EP and Roll center.
This will show you the successfully complition of the setup. For further configuration follow the steps as given below.
  1. Go to the inetmgr (From Run) and check for new website has been created or not.
  2. if u have workflow on the same server then u have to first create new website with the same configuration of default web site and after installation u have to change the port number of new created web site to another.(You can change the port number from "Binding" option at the right side in inetmgr).
  3. Now Reset IIS.
  4. To check the successful installation of Ep and RC --> go to Sharepoint Central administrator from inetmgr then browse the it and select the tab Application Management. Then select site collection list and then copy the URL and check from browser.
  5. Run The Sharepoint Product and Technologies from Administrative tools (Control panel). No need to change any setting ..just nexrt....
  6. Run Configuration wizard form ERP Administration and check for websites.
  7. Add users to EP if needed.

Analysis Extension Installation in Ax 2009 Troubleshooting

While Installing the Microsoft Dynamics Ax 2009 Analysis Extension the following error has been raised which is resolved with the following solution.

After applying the KB article SSAS Extensions still will not install.  Further research seems to indicate that the problem might be with some 9.0 SSAS assemblies in the GAC.
Setup does not recognize that SQL Server 2008 Analysis Services is
installed If you have SQL Server 2008 Analysis Services installed and you are
installing the analysis extensions, you might receive an error that says you
must install SQL Server 2005 Analysis Services with Service Pack 2. This
error message indicates that there is an Analysis Services 2005 version of
the Microsoft.AnalysisServices.dll file in the Global Assembly Cache.
Microsoft Dynamics AX does not support running Analysis Services 2005 and
Analysis Services 2008 on the same computer. To resolve this issue, uninstall
the Microsoft.AnalysisServices.dll file that has a version number of 9.0 from
the Global Assembly Cache (typically located at C:\Windows\assembly).
Important: Be sure that you do not uninstall the
Microsoft.AnalysisServices.dll file that has a version number of 10.0
I checked and sure enough there were.  So I looked and found SQL Server 2005 Express installed on the machine, not sure why.
Anyway, I uninstalled SQL Server 2005 Express and also the SQL Server 2005 Analysis Services ADOMD assemblies.
I checked the GAC after uninstalling the 2005 components and I had a clean GAC, only 10.0 references.
On to install again…and the Analysis Extensions can now be installed!

Oh how beautiful it is:

Friday, February 10, 2012

Bank Deposite, Payment has been cancelled

While Canceling Payment by system through Customer Transaction (Account Receivable>customer detail>Transactions>Cancel Payment)
Error accoured : "Payment xxxxxxxx has already been canceled"
1. Open BankDeposite Table
2. Change MaxAccessMode property of table from View to EDIT
3.Find out the DepositeNum (which mention in Error)
4.Untick the field Cancelled
5.That's done. Now save the table and again change the MaxAccessMode to View


Tuesday, February 7, 2012

AX 2009 Workflows: A Quick overview

Here is a quick overview on AX 2009 Workflow...a feature long awaited :)

Workflow - "Machine readible code for a business process"-Feature of Base AX 2009
-Workflow components reside on a Web Server
-Utilizes the Windows orkflow Foundation (.NET 3.0)
-Utilizes the AX Batch framework
-Requires AD User for Workflow
-Requires exclusive site on IIS to function
-The Workflow components on the Web server use the .NET BC to communicate with the AOS using Workflow system account(existing AX user).
Architecture overview:-

Setup (Steps):-
-Setup AD User for Workflow Account & configure in AX
-Setup & Configure IIS on Web Server
-Setup Workflow Component using AX installation option
-Run the Workflow Infrastructure Configuration Wizard {Batch Jobs, Workflow site}
-Configure the Workflow in AX
Workflow Objects:
Workflow templates:
Workflow templates capture information about workflow categories , what business document the workflow will operate over, what workflow elements (Tasks and Approvals) are required in the workflow configuration,which application event handlers will handle the events that are raised as the workflow executes etc.The first step in creating a workflow is to add a workflow Template. A Workflow Template can be said to be the metadata A workflow template provides information on:
• Which workflow document to use.
• Tasks and approvals that can be configured by the user.
• Workflow categories used for assigning a workflow template to a specific module.
Workflow category:
The workflow category determines whether a workflow template is available in a specific module. After a workflow
category is created, it is possible bind the workflow category to a workflow template.

Workflow Configuration:
A Workflow Configuration is bound to a single Workflow Template, and there can be multiple Workflow Configurations
for the same Workflow Template. Only a single Workflow Configuration for each WorkflowTemplate can be the default WorkflowConfiguration. The Workflow Configuration captures what tasks will be executed, who the tasks are assigned
Workflow Query:
Dynamics AX workflow uses a query to set up conditions for a workflow. The query identifies which data is available to workflow users. Queries are bound to Workflow templates. Once the query is created, a Workflow class needs to be created which contains the query name & any calculated fields.
Workflow Tasks:
AX workflow tasks are used to track documents or tasks from the start to the end of a work process. A workflow may
contain one or many tasks. Each task contain one step.

Workflow Approvals:
Workflow Approvals are used to track ststus of Workflow documents . The fixed outcomes are ‘Approve’, ‘Reject’, or
‘Request Change’.

After you create a task, approval, or outcome in a AX workflow, it must be added to a menu item. The end-user can then start the task or approval using the menu item as a part of the workflow process.
Workflow can be activated throughout the various lifecycle stages of a business document: Create, Update, Delete, Post. The Workflow runtime will execute the Workflow and assign Tasks to users. Users interact with theWorkflow through Alerts/Workflow Tasks, from where they can take action (Approve, Reject) or they can navigate to the business document and view all details before taking the workflow action.
Apart from these basic concepts, there are concepts like Implement Providers, Event Handlers which I will explain in a later post.

Monday, February 6, 2012

HTTP Error 404.17 - Not Found

HTTP Error 404.17 - Not Found
The requested content appears to be script and will not be served by the static file handler.
Error in IIS 7.0

This Problem occures due to installation of .NET Framework 4.0 is available on your machine.
You can back up your web.config and web content, then revert your site's mappings to parent's, it should work for you
IIS Manager->high-light you web site->click Handler Mappings icon on the home pane->click Revert to Inherited... on the right Actions pane.