Advertisement

Tip Jar:

One-Time Donation

Recurring Monthly $2 Donation Appreciated

The tip jar is to help contribute to keeping this site going. If you like what you see... feel free to help out!

U.S. Partner Executive Program News for Microsoft Dynamics: November 2009

Go directly to Source
This newsletter delivers critical program updates for Microsoft Dynamics partners in the U.S., including activities surrounding the MBS Competency, Microsoft Dynamics partner training and readiness events, launch, partner program updates, resources, recognition opportunities, and much more.
Make sure to visit the author of this post!

Microsoft Calls On Azure for New Dynamics ERP Services

Go directly to Source

Microsoft Corp. has launched a collection of online services for Microsoft Dynamics ERP customers who want to move certain applications like expense report processing into the cloud while keeping their ERP (enterprise resource planning) systems on-premise.

Microsoft said it can best serve its customers by offering a flexible deployment model so they can implement their ERP systems in the environments that are best for them. Microsoft said currently over 150 partners worldwide offer customers this hybrid option.

The online services that can be attached to its Microsoft Dynamics ERP platform including a new Azure-based service called Sites, new Commerce Services, and an expansion of…

read more

Make sure to visit the author of this post!

MSSQLFDLauncher Service Error while installing Dynamics AX 6.0 CTP Build

Go directly to Source
I was recently installing 6.0 build and got this error during the creating database stage of the installation.

After some initial research, found that I missed Full Text Search Engine installation component while installing SQL Server 2008. Re-ran the Setup wizard for SQL Server 2008 and installed Full Text Search component by selecting add features to an existing installation wizard.

This helped solving the issue

Make sure to visit the author of this post!

Error in var.aod file Error Code 50109 The check digit read in data is illegal

Go directly to Source
I came across this weird error as I was refershing a pre-prod evnironment with prod’s aod and label files. There was no error at the time of starting of the AOS Service. But, when I imported a Project (.xpo) into the Pre-Prod during the process of import, this error came. See the screenshot below.

Resolution:
Initially, I tried restarting the AOS service, but it didn’t help. Soon, without wasting much time and effort, I stopped the service, deleted the axapd.aoi file (this is the index file which AX builds everytime when it starts up, if the file is present it won’t build, else it will create a new one.) I guess this file might have some old definitions due to which I was getting this error. After deleting the file and restarting the AOS Service made this error disappear.

Make sure to visit the author of this post!

Error in var.aod file Error Code 50109 The check digit read in data is illegal

Go directly to Source
I came across this weird error as I was refershing a pre-prod evnironment with prod’s aod and label files. There was no error at the time of starting of the AOS Service. But, when I imported a Project (.xpo) into the Pre-Prod during the process of import, this error came. See the screenshot below.

Resolution:
Initially, I tried restarting the AOS service, but it didn’t help. Soon, without wasting much time and effort, I stopped the service, deleted the axapd.aoi file (this is the index file which AX builds everytime when it starts up, if the file is present it won’t build, else it will create a new one.) I guess this file might have some old definitions due to which I was getting this error. After deleting the file and restarting the AOS Service made this error disappear.

Make sure to visit the author of this post!

Deciding on Reporting Architecture (SSRS + Dynamics AX 2009) for a new Implementation

Go directly to Source
A few days ago, we were brainstorming on the reporting architecture for a new implementation.

We had the following options on the table:

 
1. SSRS fetching data through EP
Pros: 
  •  Ax Security (Configuration key, Security key etc.) set at table levels can be leveraged 
  •  No bypass of Business Logic as the communication is through AOS
  •  Leverage data methods in Reports  

Cons:

  • Tight integration of Reporting IDE with AOT
  • AX Resource need to spend time learning SSRS
  • Additional components such as EP and Role Centers needs to be configured

2. SSRS fetching data from Ax Database using Stored Procedure
 Pros:
 
  • Ax team and SSRS team can simultaneously work on Data and Report design resp
  • Additional component such as EP does not have to be installed 
  • It provides an option of writing logic inside Ax or in SQL store procedure
  • Stored Procedures provide faster access to data
  • Reports can be loosely coupled and extendable say tomorrow if you want to extract data from another data source say for that matter SAP, you need to just write one more SP inorder to do that

 

 Cons:
  •         Internal AX Security is bypassed as SP directly access the data
  •         In case of an upgrade, the metadata or the field names used in SP needs to be modified if they change    

3. AX Client

         Client was not interested in using AX thick client as it will be tedious job to install AX Client on each PC just for reports purpose and then tomorrow if the client is upgraded, then again the setup has to be done on each PC. Client preferred web based UI.

 

So, our vote was for the second option as it’s loosely coupled and provides flexibility to have multiple datasources

Make sure to visit the author of this post!

Deciding on Reporting Architecture (SSRS + Dynamics AX 2009) for a new Implementation

Go directly to Source
A few days ago, we were brainstorming on the reporting architecture for a new implementation.

We had the following options on the table:

 
1. SSRS fetching data through EP
Pros: 
  •  Ax Security (Configuration key, Security key etc.) set at table levels can be leveraged 
  •  No bypass of Business Logic as the communication is through AOS
  •  Leverage data methods in Reports  

Cons:

  • Tight integration of Reporting IDE with AOT
  • AX Resource need to spend time learning SSRS
  • Additional components such as EP and Role Centers needs to be configured

2. SSRS fetching data from Ax Database using Stored Procedure
 Pros:
 
  • Ax team and SSRS team can simultaneously work on Data and Report design resp
  • Additional component such as EP does not have to be installed 
  • It provides an option of writing logic inside Ax or in SQL store procedure
  • Stored Procedures provide faster access to data
  • Reports can be loosely coupled and extendable say tomorrow if you want to extract data from another data source say for that matter SAP, you need to just write one more SP inorder to do that

 

 Cons:
  •         Internal AX Security is bypassed as SP directly access the data
  •         In case of an upgrade, the metadata or the field names used in SP needs to be modified if they change    

3. AX Client

         Client was not interested in using AX thick client as it will be tedious job to install AX Client on each PC just for reports purpose and then tomorrow if the client is upgraded, then again the setup has to be done on each PC. Client preferred web based UI.

 

So, our vote was for the second option as it’s loosely coupled and provides flexibility to have multiple datasources

Make sure to visit the author of this post!

US Sales and Marketing News: November 12, 2009

Go directly to Source
This newsletter provides US Microsoft Dynamics Partners with all the latest sales and marketing opportunities designed to accelerate marketing efforts and generate revenue goals for both new and existing customers.
Make sure to visit the author of this post!

Error in var.aod file

Go directly to Source
I came across this weird error as I was refershing a pre-prod evnironment with prod’s aod and label files. There was no error at the time of starting of the AOS Service. But, when I imported a Project (.xpo) into the Pre-Prod during the process of import, this error came. See the screenshot below.

Resolution:
Initially, I tried restarting the AOS service, but it didn’t help. Soon, without wasting much time and effort, I stopped the service, deleted the axapd.aoi file (this is the index file which AX builds everytime when it starts up, if the file is present it won’t build, else it will create a new one.) I guess this file might have some old definitions due to which I was getting this error. After deleting the file and restarting the AOS Service made this error disappear.

Make sure to visit the author of this post!

VAT2010 for Microsoft Dynamics AX

Go directly to Source
Between October and December 2009, Microsoft will release various software updates, depending on when tax authorities in each country/region make their requirements publicly available, to help customers comply with the new regulations. 
Make sure to visit the author of this post!

« Previous PageNext Page »

MCP Logos