Greetings! Welcome to my Dynamics AX 7 and related MS Technologies blog.
Total Pageviews
Search This Blog
Friday, December 24, 2010
Wishing you Merry Xmas and A Happy 2011
Wishing you all my blog readers Merry Xmas and A Very Happy 2011.
Dynamis AX Integration with QAS for Address Verification
Introduction
QAS is a third party address verification service which gets the full address from a given postcode and street. You can find more details in their website
http://www.qas.co.uk/products/capture-name-and-address-data/pro.htm
We had to do integration for Australian Post Codes and Street Addresses. So, we were given the web service by QAS which we needed to plug in to AX
Integration with Dynamics AX
a. Consume the QAS Web Service by going through Tools > Development Tools > Application Integration Framework > Add Service Reference
b. Once the Service Reference is added, write a class to instantiate the proxy and pass the zip code and street name
c. Here is a sample code snippet which does the call to QAS and retreives the full address
We are calling this class from different forms like Customers, Sales Orders, CRM wherever we need to validate address with QAS
QAS is a third party address verification service which gets the full address from a given postcode and street. You can find more details in their website
http://www.qas.co.uk/products/capture-name-and-address-data/pro.htm
We had to do integration for Australian Post Codes and Street Addresses. So, we were given the web service by QAS which we needed to plug in to AX
Integration with Dynamics AX
a. Consume the QAS Web Service by going through Tools > Development Tools > Application Integration Framework > Add Service Reference
b. Once the Service Reference is added, write a class to instantiate the proxy and pass the zip code and street name
c. Here is a sample code snippet which does the call to QAS and retreives the full address
We are calling this class from different forms like Customers, Sales Orders, CRM wherever we need to validate address with QAS
Thursday, December 23, 2010
Dynamics AX Troubleshooting AOS Error Internal Error occured executing stored procedure when creating session for the AOS
Issue
One of our AOS suddenly stopped working and it won't restart any more. Learned that there was a database refresh the last night.
The error I found in event viewer was Object Server 01: Internal Error occured executing stored procedure when creating session for the AOS (Screenshot below)
Solution
http://daxdilip.blogspot.com/2010/09/object-server-01-internal-error-occured.html
One of our AOS suddenly stopped working and it won't restart any more. Learned that there was a database refresh the last night.
The error I found in event viewer was Object Server 01: Internal Error occured executing stored procedure when creating session for the AOS (Screenshot below)
Solution
http://daxdilip.blogspot.com/2010/09/object-server-01-internal-error-occured.html
Wednesday, December 15, 2010
[Updated] How to Debug Batch Jobs running on Dynamics AX 2009 with AOS Server on Windows Server 2008
I'm having a hard time debugging batch jobs on server, my batch job executes but it never hits the breakpoint.
I followed all the steps mentioned in this blog post http://blogs.msdn.com/b/x/archive/2009/06/25/step-by-step-checklist-for-debugging-batch-jobs-in-dynamics-ax.aspx
and additionally installed the hotfix as our AOS Server runs on Windows Server 2008, but still unable to hit the breakpoint.
Just wondering, if anybody out there has achieved success in debugging batch jobs on AOS Server (which runs Windows Server 2008)? If yes, would be glad if they can share their experiences or email me on maildotdilipnATgmaildotcom or put a comment below. Thanks
Thanks to all who replied me via emails and comments. Appreciate it.
Solution (If you debugging batch jobs on Windows Server 2008)
a. Make sure you have checked all the steps http://blogs.msdn.com/b/x/archive/2009/06/25/step-by-step-checklist-for-debugging-batch-jobs-in-dynamics-ax.aspx
b. Run the hotfix mentioned in the blog link above
c. Logon to your remote desktop using (mstsc /console)
d. Run the Debugger As Administrator i.e. right click AxDebug. exe and Run as Administrator.
Observation - It's not necessary to logon with the same account as your AOS Service account, I logged in with my network alias which happened to be the admin on the box and it worked well for me, Usually in strict environments we won't get access to the service account's password.
In my scenario, I missed Steps c and d. This is required if you run on Win Server 2008
I followed all the steps mentioned in this blog post http://blogs.msdn.com/b/x/archive/2009/06/25/step-by-step-checklist-for-debugging-batch-jobs-in-dynamics-ax.aspx
and additionally installed the hotfix as our AOS Server runs on Windows Server 2008, but still unable to hit the breakpoint.
Just wondering, if anybody out there has achieved success in debugging batch jobs on AOS Server (which runs Windows Server 2008)? If yes, would be glad if they can share their experiences or email me on maildotdilipnATgmaildotcom or put a comment below. Thanks
Thanks to all who replied me via emails and comments. Appreciate it.
Solution (If you debugging batch jobs on Windows Server 2008)
a. Make sure you have checked all the steps http://blogs.msdn.com/b/x/archive/2009/06/25/step-by-step-checklist-for-debugging-batch-jobs-in-dynamics-ax.aspx
b. Run the hotfix mentioned in the blog link above
c. Logon to your remote desktop using (mstsc /console)
d. Run the Debugger As Administrator i.e. right click AxDebug. exe and Run as Administrator.
Observation - It's not necessary to logon with the same account as your AOS Service account, I logged in with my network alias which happened to be the admin on the box and it worked well for me, Usually in strict environments we won't get access to the service account's password.
In my scenario, I missed Steps c and d. This is required if you run on Win Server 2008
Tip How to Encode URL for Dynamics AX 2009 Enterprise Portal Link
Issue
Some of our Enterprise Portal links which points to SSRS reports were not getting saved when we input it through "Manage Links" option when you edit the page via Sharepoint
For e.g. one of the link which gives the problem was http://servername/Reports/Pages/Report.aspx?ItemPath=%2fMAX+Reports%2fPromotions+Claims+Report+Rebates
When saved, it spits out an error saying "The URL Property is not well formed"
Resolution
Replace the “+” character with “%20” (which is used for space) and that works like a charm!
Some of our Enterprise Portal links which points to SSRS reports were not getting saved when we input it through "Manage Links" option when you edit the page via Sharepoint
For e.g. one of the link which gives the problem was http://servername/Reports/Pages/Report.aspx?ItemPath=%2fMAX+Reports%2fPromotions+Claims+Report+Rebates
When saved, it spits out an error saying "The URL Property is not well formed"
Resolution
Replace the “+” character with “%20” (which is used for space) and that works like a charm!
Subscribe to:
Posts (Atom)


