Dynamics AX
  RSS Feed  LinkedIn  Twitter
Want to turn you're data into a true asset? Ready to break free from the report factory?
Ready to gain true insights that are action focused for truly data informed decisions?
Want to do all of this across mutliple companies, instances of Dynamics and your other investments?
Hillstar Business Intelligence is the answer then! (www.HillstarBI.com)

Hillstar Business Intelligence for Microsoft Dynamics AX and NAV on Mobile, Desktop, Tablet

Let us prove to you how we can take the complexity out of the schema and truly enable users to answer the needed questions to run your business! Visit Hillstar Business Solutions at: www.HillstarBI.com

Wednesday, October 26, 2005

Strange Event log entry, and hung C# code

In my current work, I do a lot of connecting to Axapta 3.0 through C# and the Axapta Business Connector. I recently had to make some changes to the X++ classes that are called through the Business connector from C#. When these changes took place the code stopped working.

Further analysis turned up the following Application Event Log entry on the machine that is running the Business Connected C# code:

Event Type: Warning
Event Source: Axapta COM Connector
Event Category: None
Event ID: 110
Date: 10/26/2005
Time: 11:40:12 AM
User: N/A
Computer: MMI200307
Axapta COM Connector Session 65535.

The breakpoints for user '' will not be used, since debugging is not enabled due to one of the following reasons:

1) The user does not have access rights to the development environment.
2) The debug mode is set to 'No' for the user.

Microsoft Axapta Business Connector only:

3) Debugging is not allowed for code running in the Microsoft Axapta Business Connector.
4) The Microsoft Axapta Business Connector is not running as the interactive user. Please use Component Services in the Control Panel to configure the Microsoft Axapta Business Connector to run under the identity of the interactive user.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

This error does not tell you much, but basically it means that there is an error when calling one of the methods of an X++ class through C# and the business connector. It took a few times running this, but for me this means a 'best practice' of testing your code from within Axapta first to make sure there are no loops, or errors. Also make sure that the data types being passed into Axapta are of the correct format. A Data Type changed on me, but the C# code was still passing in the old data type.

Needless to say, if you get a similar event log entry please make sure to test out your X++ code / class within Axapta first, it will save a lot of time and unkown issues!

Find a job at: www.DynamicsAXJobs.com


Blogger Pieter said...

Right now, I develop integration between axapta and c#. But when I want to passing date parameter to a class in axapta, I get nothing in axapta.

I want to ask u, if we use date type in axapta, what type should we used in C#?

Thx U....

1:41 AM  

Post a Comment

<< Home

Copyright 2005-2011, J. Brandon George - All rights Reserved