Dynamics Search Engine

Wednesday, December 30, 2009

My last day in Tectura

Hi All,

Today is my last day in Tectura.

In my leisure time very often I remember the wonderful moments we had when we started our career in Ax with Euroinfo Systems (this company is acquired by Tectura). Euroinfo Systems changed my professional life. I am really thankful to Euroinfo/Tectura.

In this company I got the opportunity to work with the best, most talented and professional group of people.

I've enjoyed having exposure to so many different points/technologies/products.

Always in challenging time I got great help/cooperation.

The below image shows the fellow of our Ax group. This photo was taken on 28th July, 2005 during our initial Ax career. It recalls our wonderful old memories.


Euroinfo family

Monday, October 26, 2009

To show upcoming birthday in Sharepoint

I was looking for a facility to display upcoming birthdays in MOSS 2007 but there is no availability of such webpart.It can be done by customizing in MOSS 2007 or a webpart can be developed. I was looking for a shortcut way to fulfill my requirement. Finally I got a webpart from http://www.sharepointology.com/.


This webpart has been developed to display upcoming birthdays where name of user and date of birth to be displayed. Yes, there is a provision to set the number of days as a range for upcoming day(s). For example, if you want to display the name of user(s) whose date of birth is coming within next 3 days.


Additionally the user name is having a link to its profile.
Actually date value is coming from user’s profile and name is coming from active directory (AD).



Download link for this webpart: http://www.sharepointology.com/general/web-part-to-show-upcomming-birthdays-in-sharepoint-v20/


The above link can be changed without any notice.

Note: There is no business relation between me and http://www.sharepointology.com/

Monday, September 21, 2009

Microsoft Dynamics Ax 2009 web project template is not available / visible in visual studio 2008



This article explains
How to make available Microsoft Dynamics Ax Web Project template for all users.
How to resolve Microsoft Dynamics Ax Web Project template missing issue / problem.
How to resolve Microsoft Dynamics Ax Web Project template visible or availability issue even through Ax EP development tool is installed.


Symptom:
One user can see Dynamics Ax Web Project template when he/she creates a new web project but the other user can’t see it on the same server.

Reason:
If a user can see Microsoft Dynamics Ax Web Project template it’s because in his/her profile on system the template is available. In general the template is located on a windows 2003 server at C:\Documents and Settings\[user id ]\My Documents\Visual Studio 2008\Templates\ProjectTemplates\Visual Web Developer\CSharp\ AxWebProject.zip

Resolution:
To make Microsoft Dynamics Ax Web Project template available for other users copy the Templates folder from the user who can see template and paste it to other users’ profile It assumed that your templates are available in the default located as mentioned in above path

Step1:
Go to C:\Documents and Settings\[user id ]\My Documents\Visual Studio 2008\

Step2:
Copy Templates folder

Step3:
Open the other users’ profile and go to C:\Documents and Settings\[user id ]\My Documents\Visual Studio 2008\

Step4:
Paste the Templates folder. If system says to overwrite it click on yes option.


NOTE: Use at your own risk. There is no warranty on this article.

Saturday, September 19, 2009

Microsoft Dynamics Ax 2009 SRS Reports Deployment error (AL.EXE) not found

This article explains how to resolve AL.EXE error or exception during Microsoft Dynamics Ax 2009 SRS reports deployment.

Applied on:
Windows Server 2008 SP1
SQL Server 2008
Microsoft Dynamics Ax 2009 SP1

When attempting to deploy Microsoft Dynamics Ax SRS reports, you may have received the following error message:

Unable to load one or more of the requested types.
Retrieve the LoaderExceptions property for more information.
Error: The following components have not been installed or are not configured correctly:
AL.exe
Please consult your administrator or the documentation.
System.InvalidOperationException: The following components have not been installed or are not configured correctly:
AL.exe
Please consult your administrator or the documentation.



This error message indicates that the following software components are not installed:


  • Windows SDK for Windows Server 2008 and .NET Framework 3.5
  • Microsoft Visual Studio 2008 Shell (isolated mode)

You can download above prerequisites from following links:
Windows SDK for Windows Server 2008 and .NET Framework 3.5
Microsoft Visual Studio 2008 Shell (isolated mode)



The above link can be changed without any notice.

Note: Use at your own risk. There is no warranty on this article.

Saturday, August 15, 2009

How to grant User Access to a SSRS Report Server (Report Manager)

How to grant User Access to a SSRS Report Server (Report Manager)

This article describes:
  • How to give access of report server (report manager) to user or grant user access to a report server (report manager).
  • How to get solution for SSRS report access denied exception / error in Microsoft Dynamics Ax 2009 Role Center (Enterprise Portal).
  • How to solve the insufficient permission exception as shown below:

Applied on: SQL Server 2005 SP2 and Microsoft Dynamics Ax 2009 SP1.

Reporting Services use role-based security to grant user access to a report server. On a new report server installation, only users who are members of the local Administrators group have permissions to report server content and operations. To make the report server available to other users, you have to create role assignments that map user or group accounts to a predefined role that specifies a collection of tasks.



To add a user or group to a system role

1. Start Report Manager.

2. Click Site Settings.


3. Click Security.

4. Click New Role Assignment.


5. In Group or user, enter a Windows domain user or group account in this format: [domain name]\[account]. If you are using forms authentication or custom security, specify the user or group account in the format that is correct for your deployment.


6. Select a system role, and then click OK.


If you select both System Administrator and System User, a user or group will be able to perform the tasks in both roles.




To add a user or group to an Role

1. Open Report Manager.



2. Click the Properties tab.

3. Click the Security tab.

4. Click New Role Assignment.

5. In Group or user, enter a Windows domain user or group account in this format: [domain]\[account].

6. Select one or more role definitions that describe how the user or group should access the item, and then click OK.


Note: Use at your own risk. There is no warranty on this article.

Tuesday, July 14, 2009

How to resolve Ax 2009 SRS reports deployment error or exception

This article explains how to remove

  • While deploying AX SRS reports from AX client (AOT->Report Libraries), system gives below error / exception
  • While deploying AX Reports Deployment tools , system gives below error / exception
Symptom:
In case of SQL Server 2008
One or more libraries built with warnings. Please see MSBuild log at C:\Documents and Settings\Administrator\Local Settings\Temp\tmp.tmp
Deploying 0 data source(s) and 63 design(s) in 42 culture(s) (2521 item(s) total)...
Unable to connect to http : // [your system name] /ReportServer/ReportService2005.asmx as specified in the config file for the report server at C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\RSReportServer.config. If this url is not correct please update the config file, otherwise make sure the report server is configured correctly. The deployment log file can be found at "C:\Users\Administrator\AppData\Local\Temp\1\tmp.txt"



In case of SQL Server 2005
One or more libraries built with warnings. Please see MSBuild log at C:\Documents and Settings\Administrator\Local Settings\Temp\tmp.tmp
Deploying 0 data source(s) and 63 design(s) in 42 culture(s) (2521 item(s) total)...
Unable to connect to http : // [your system name] /ReportServer/ReportService2005.asmx as specified in the
config file for the report server at C:\Program Files\Microsoft SQL Server\ MSSQL.3\Reporting Services\ReportServer\RSReportServer.config. If this url is not correct please update the config file, otherwise make sure the report server is configured correctly.
The deployment log file can be found at "C:\Users\Administrator\AppData\Local\Temp\1\tmp.txt"


Resolution:
Check following:
1) Is your report manager working from IIS or Internet explorer? If no then make it workable. If it works then you can see Report Manager Home.
2) Is web service http : // [your system name] /ReportServer/ReportService2005.asmx working?

To make the default Report Manager workable, you can see the installation and configuration guidance.

If you are using SQL server 2008, open the C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\RSReportServer.config file in an editor (Notepad is perfect).

If you are using SQL server 2005, open the C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\ rsreportserver.config file in an editor (Notepad is perfect).

Now you have to modify this config file. Before you do this I do recommend you to make a copy of this file as a backup.Press Ctrl + F and find ‘SQLCommandTimeoutSeconds’. By default the value is 60. Increate the value upto 300 and save the file.

Now restart the IIS.
Launch AX SRS report deployment tool. I hope it will work.

Once the AX SRS Reports deployment is finished go back to the above mentioned config file and decrease the value 60 from 300.

Note: Use at your own risk. There is no warranty on this article.

Cheers!

Tuesday, May 12, 2009

How to resolve Stopped (error): Target date not found in work calendar error in Microsoft Dynamics Ax 2009 Workflow





This article explains how to resolve Stopped (error): Target date not found in work calendar error in Microsoft Dynamics Ax 2009 Workflow.

Symptom:
If you see the Tracking details of your workflow process it shows "Workflow stopped (error)" and : Stopped (error): Target date not found in work calendar.

Reason:
A work calendar is missing in workflow setup.

Resolution:
The workaround on this, create a work calendar in Ax.
To do this:
Go to Basic-->Calender and create a calender. If you have already created a calender you can use that one.

Once the Calender is created, assign the calendar to the workflow setup. Lets say you are running workflow for Purchase Requisition then Go to the Accounts Payble-->Setup-->Workflow Configuration. On this form go to Details tab, select a Workflow element, in the buttom part (Approval Details) select Overview tab, check the check box "Set a time limit for the approval process". Here you will get the calender lookup to select a work calender. Assign a calender and do any other setup if you require. Save your work and make transaction for workflow to check.

I hope this will remove your
Stopped (error): Target date not found in work calendar error.

Other related articles:
How to install and configure Microsoft Dynamics Ax 2009 workflow step by step
How to resolve SysWorkflowMessageQueueManager-run error in Microsoft Dynamics Ax 2009 Workflow


Warning:
There is no warranty on this article. Use at your own risk.

How to resolve SysWorkflowMessageQueueManager-run error in Microsoft Dynamics Ax 2009 Workflow



This article explains how to resolve SysWorkflowMessageQueueManager-run error in Microsoft Dynamics Ax 2009 Workflow.

Error:
ClrObject static method invocation error.
Exception has been thrown by the target of an invocation.

Applied on:
Ax 2009 SP1

The workaround- the above mentioned error there are few things to be checked.
1) Make sure the .NET Business Connector is connected to the correct AOS server or not.
To check this:
  • a) Start --> Administration tool --> Microsoft Dynamics AX 2009 Configuration.
  • b) On the tob change Configuration Traget to: Business Connector (non-interactive use only) on Connection tab check that it is connecting to correct AOS or not. It should be connected.
2) If you shutdown the AOS then you may need to restart the IIS to refresh the connection.
To restart it:
  • i) Start --> Run
  • ii) Type "IISRESET" without quote
  • iii) Click on OK buttonORa) Open command promptb) Type in "IISRESET" without the quote.
3) If you have more than one Workflow website setup for several environment on the same system then except one you are testing stop other websites.
4) Compare the Identity of the Application Pool used by Ax Workflow website with the Business Connector proxy setup in the system. If business connector proxy user id is not configured properly with Applicatoin pool the .NET Business Connector will fail to connect to the AOS.

Warning:
There is no warranty on this article. Use at your own risk.

Other related article:

Saturday, May 2, 2009

Resolution for Microsoft Dynamics Ax 2009 Role Center & Enterprise Portal (EP) Access Denied error

This article explains:
How to resolve Microsoft Dynamics Ax 2009 Role Center & Enterprise Portal (EP) Access Denied error.
How to assign permission to Microsoft Dynamics Ax 2009 Role Center & Enterprise Portal (EP) users.
How to give permission for Microsoft Dynamics Ax 2009 Role Center & Enterprise Portal (EP) users from Microsoft Windows Sharepoint Services or Server.


Problem:
When you open Microsoft Dynamics Ax 2009, the role center shows an error “Error: Access Denied” + “Current User” + “You are currently signed in as: domain name\user id” + “Sign in as a different user”.

Reason:
You don’t have the permission to access AX enterprise portal (website) which is made within windows sharepoint services or server.

Resolution:
The permission to be given to all the users who wants to access Role Center or Enterprise portal.

1)
To give the permission you have to login to the Ax enterprise portal (website) using administrator permission.On the Ax enterprise portal site there would be a button called “Site Actions” on upper right hand side. Click on Site Actions then Site Settings as shown below.


2)
Click on People and groups under Users and Permissions


3)
Click on New then Add Users.


4)
Add user(s) from domain you are using for AX and WSS. Once the user(s) is added, give permission accordingly as shown below.


5)
From below screen you can search user(s) and add them.


6)
Once the user(s) added and permission assigned, click on OK button.
Now you have given the permission to the user(s). It should not give you any error like Access Denied.
NOTE: There is No warranty on this article, use at your own risk.

Saturday, April 25, 2009

How to install and configure Microsoft Dynamics Ax 2009 workflow step by step

NOTE: There is NO warranty on this article, use at your own risk.

This article explains:
How to install Microsoft Dynamics AX 2009 Workflow step by step
How to configure Microsoft Dynamics AX 2009 Workflow step by step
How to setup Microsoft Dynamics AX 2009 Workflow step by step
About Workflow:
The Microsoft Dynamics AX workflow infrastructure enables user configurable workflows in Microsoft Dynamics AX application modules with specific focus on task and approval workflows. The workflow runtime manages configuration and executation of workflows while the application modules will manage activation and business logic associated with workflows.Microsoft Dynamics AX 2009 workflow uses Windows Workflow Foundation (.Net framework), AX batch framework, Internet Information Services (IIS), Active Directory (AD) users, .Net Business Connector for AX and web services.
Prerequisite:
You should have basic knowledge of AX.Basic AX should be installed on your system.Create two users in AD. One is for workflow another is for business connector proxy. The password should not be expired or changed for these users.If you have already created, no need to create now.Add these users to AX.
Steps to follow:
1) Open AX client then open the System service accounts form and add users for workflow.Go to Administrator > Setup > Security > System service accounts.
2) If you want to use a separate website for workflow then create a website in IIS or you can use the default website. If you use default website the setup process will create a sub site under default website.


I have created a new website called AxWfl as shown above. It’s not mandatory to create a separate website for this but recommended.

3) Run AX setup file and install workflow. If .Net Business Connector is not installed AX setup will install it itself.

4) Once the setup process is done successfully open AX client.

5) From Basic main menu create a Calendar. Here I have created the calendar called 24Hours.


6) Create a batch job for workflow. Go to the Basic > Batch job list – user form and create a batch job. Here I have created a job called Wfl.

7) Go the Administration > Setup > Workflow infrastructure configuration wizard form.Run the wizard and follow the instructions and finish it.

8) Now make a setup for Purchase Requisition. Go to Accounts Payable > Setup > Workflow configurations form. Here configure the workflow with required conditions. A Workflow Configuration is bound to a single Workflow Template. In this process you need to select the calendar you created in step 5.

Once the purchase requisition workflow setup is over go to AOT > Forms > PurchReqTable > Designs > Design. Right click on Design then properties and check whether is Workflow Enabled or not.


9) Once you have done all these then create purchase requisition using respective user, perform all the tasks you instructed during workflow configuration/setup and submit it. After submission you can see the history of workflow.






10) Now open AX client using approver user id and see the task assigned and complete it.

Using approver user id approve it and check that the purchase order has been created or not. I hope it will create a purchase order.

Friday, February 27, 2009

How to write data into an Excel sheet from Microsoft Dynamics Ax

Note: There is no warranty on this article. Use at your own risk.

This article explains
  • How to write data into an Excel sheet from Microsoft Dynamics Ax using X++ language.
  • How to write data into an Excel sheet using COM object in Microsoft Dynamics Ax.
  • How to export Microsoft Dynamics Ax data into an Excel sheet at run time / dynamically /programmatically using X++ language.
I applied it on Dynamics Ax 2009.

Prerequisite:
  • You should have X++ basic programming knowledge;
Open Ax client > AOT > Jobs node, create a new job and copy the below code segment into your job.

static void writeDataIntoExcelSheetFromAx(Args _args)
{
InventTable inventTable;
Container itemIdCon;
COM comRange;
COM comWorkBook;

COM comWorkBooks;
COM comWorkSheet;
COM comCharacters;
COM comAppl;
str test,test1;
int offset = 65-1; //65 means letter 'A'
str 2 columnId;
str fileName;
str time;
int i;
#define.Excel('Excel.Application')

;

comAppl = new COM(#Excel);
comAppl.visible(true);
comWorkbooks = comAppl.workbooks();
WINAPI::createFile('C:\\test.xls');
comWorkbook = comWorkbooks.open('C:\\test.xls',true,true);
comWorksheet = comWorksheet.new('C:\\test.xls');
comWorksheet = comWorkbook.activeSheet(); //Use
comWorkbook.activateSheet(); in case of Ax 3.0
comWorksheet.select();

while select inventTable
{
columnId = num2char(offset + 1);
i++;
test = columnId + int2str(i);
comRange = comWorksheet.range(test);
comCharacters = comRange.characters();
comCharacters.insert(inventTable.ItemId);

columnId = num2char(offset + 2);
test = columnId + int2str(i);
comRange = comWorksheet.range(test);

comCharacters = comRange.characters();
comCharacters.insert(inventTable.ItemName);
}

WINAPI::createDirectory('C:\\AxData');
time = time2str(timenow(),1,1);
time = strrem(time,':');
fileName = 'C:\\AxData\\' + curuserid() + date2str(today(),123,2,0,3,0,4)+ time + 'test' + '.xls';
comWorkbook.saveAs(fileName);

}

Thursday, February 26, 2009

How to debug x++ code for Microsoft Dynamics AX Enterprise Portal

Note: There is no warranty on this article. Use at your own risk.
I have done this on a single system.


This article explains:

  • How to debug X++ code for Microsoft Dynamics Ax 2009 Enterprise Portal
  • How to debug X++ code using .Net Business Connector
  • How to setup and configure to debug X++ code for Microsoft Dynamics Ax 2009 Enterprise Portal
  • How to debug Microsoft Dynamics Ax 2009 Enterprise Portal (EP)
1.
Log in to the server that is running the AOS.


2.
Open the Microsoft Dynamics AX Server Configuration utility. To open Start > Control Panel > Administrative Tools > Microsoft Dynamics AX 2009 Server Configuration.

3.
Create a new configuration that allows debugging.


3.a.

Click Manage then Create configuration. Give a name to the new configuration in the Create Configuration window then click OK.










3.b.
On the Application Object Server tab, select Enable breakpoints to debug code X++ code running on this server. Click on Apply button.



4.
Click on OK button to close the configuration window. You will get a message that indicates AOS is going to be restarted.

5.
Actually debugger works on the server where IIS is running and Enterprise Portal is hosted. I used a single system and all the things are on the same system. If you are accessing a system remotely using Terminal Services then from the Start menu click Run. Type
mstsc /console in the Open text box and click OK
This opens a console session in Terminal Services. Console session is required to debug Ax EP

6.
The World Wide Web Publish Service should be enabled.
6.a.
Open the Services window for the system. To open it Start > Control Panel > Administrative Tools > Services.
6.b.
Right-click the World Wide Web Publishing Service and click Properties.


6.c.
Click the Log On tab.
6.d.
Select Allow service to interact with desktop as shown below.


6.e.
Click on OK button to close the properties window.

7.
Open the web.config file located in :\Inetpub\wwwroot\wss\VirtualDirectories\\, here the port number of the Enterprise Portal site. If you forgot the port then there is a way to check it out. Open Ax client then Administration main menu > Setup > Internet > Enterprise Portal > Web sites, here you can see the port.



8.
Now do the following:
8.a.
Find out the compilation element then set the debug attribute to true.
8.b.
Save the changes.

9.
Reset IIS by typing the iisreset command at the command-line window or type iisreset in Start > Run > Open text box then click on OK button.

10.
Open the Microsoft Dynamics AX Configuration utility. To open it Start > Control Panel > Administrative Tools > Microsoft Dynamics AX 2009 Configuration.

11.
Set the Application Object Server Instance drop-down menu to Business Connector (non-interactive use only).



12.
Create a new configuration to allow debugging.
12.a.
Click on Manage button then click Create configuration. In the Create Configuration window, name the new configuration then click OK button.
12.b.
On the Developer tab, select Enable user breakpoints to debug code in the Business Connector and Enable global breakpoints to debug code running in the Business Connector or client then click on Apply button.

13.
Click on OK button to close the configuration window.

14.
Open the Microsoft Dynamics AX client.

15.
On the Tools menu, click Options to display the Options window.

16.
On the Development tab, select When Breakpoint from the Debug mode list box, and then click Apply. This enables debugging mode on the client.


17.
Close the Options window.

18.
Open the Microsoft Dynamics AX client.

19.
Now decide the element you want to debug. Lets say you want to debug a class method. Open the method in code editor and write breakpoints where you want to set a breakpoint.

20.
Open the Debugger window manually. To open debugger manually click on Tools > Development Tools > Debugger.

21.
Now execute the web form where the method has been invoked. It should work. On my system it is working perfectly.


If there is any problem please let me know. Definitely I will help you.

Saturday, February 14, 2009

How to use User Controls within .Net to develop or customize Microsoft Dynamics Ax 2009 Enterprise Portal -Part I

Note: There is no warranty on this article. Use at your own risk.

This article explains how to develop or customize Microsoft Dynamics Ax 2009 Enterprise Portal using User Control. How to use Visual Studio (.Net) environment to develop/customize Microsoft Dynamics Ax 2009 Enterprise Portal. How to use Microsoft Dynamics Ax 2009 Data Sets within .Net environment. How to develop or customize Dynamics Ax 2009 Enterprise Portal.

To follow this article you should have installed:
  1. Microsoft Dynamics Ax 2009 with Enterprise Portal
  2. Enterprise Portal should be configured with Microsoft Windows Sharepoint Services 3.0 SP1 or Microsoft Windows Sharepoint Server 2007 SP1. A website for Enterprise Portal should be created
  3. Visual Studio 2008.
You should be familiar with
  • X++ Language
  • Microsoft Dynamics Ax 2009 customization
  • .Net development
  • Microsoft Windows Sharepoint Services product
Now I will explain step by step.

1. Open Microsoft Dynamics Ax 2009 application then AOT. Select Data Sets node, right click on it, and select New Data Set.


2. Rename it to SalesInfo (or any other name whatever you wish) as shown below:


3. Add SalesTable and CustTable to the Data Sources of SalesInfo Data Set as shown below. Make a join between these table.


4. Now open your Visual Studio, click on File->New->Web Site… as shown below



5. From web site template select Dynamics Ax Web Project template, Location should be File System, Language should be Visual C#, and .Net Framework 2.0 as shown below. Click on OK.


6. Now see the Solution window where a project has been created in the name “AxWebProject1”. You can rename it.



7. Right click on AxWebUserControl.ascx page in the solution window then click on View Designer as shown above.

8. Now open the Toolbox and find Dynamics Ax tool section. Drag and drop AxDataSource control from Toolbox to the body of the AxWebUserControl.ascx page.


9. Select the AxDataSource1 on the AxWebUserControl.ascx page then assign a DataSet to it from the AxDataSource Tasks dropdown as shown below. Here you need to select SalesInfo DataSet you created in step1.



10. Go to the Toolbox again and add AxGridView control from Toolbox to the AxWebUserControl.ascx form as shown below.



11.Add AxDataSource1 to AxGridView.


12.Now click on Edit Columns… on AxGridView Tasks.



You will get the below field designer.



13. Add those fields you want to display. I added AccountNum, Name, CustGroup and SalesTable!Status. Later on I modified the fields.



14. Now select the AxWebPartPage.aspx in the solution window. Right click on it. Select View Designer.



15. Now drag the AxWebUserControl.ascx page from solution window and drop it to the body of the AxWebPartPage.aspx. Press F5 to execute the page. See the data is being displayed from Ax in the internet explorer.



Grid format(Template) is also available. See step 12. Auto Format is there.


Now your newly created user control is available in Microsoft Dynamics Ax 2009 AOT. To check go to AOT->Web->Web Files->Web Controls->User Controls.


If it's not available in the AOT then you can add it to AOT.
Right click on .ascx control in the Sulution explorer then click on Add to AOT as shown below



Hope this will be helpful for you.
This is Part I.
In Part II I will let you know how to use this .Net made user control within Dynamics Ax 2009 Enterprise Portal (EP).