Custom Service in Ax 2012 R3

Finance and Operations/AX Developer Forum
1

Hi Guys

I have created custom service in ax 2012 r3 and deployed as well.

while try to access the service from visual studio console application, the service stopped in ax 2012 R3.

anyone know how to fix the issue.

regards

syed abuthahir

2

Please give us more information. Above all, I’m not sure what you mean by “the service stopped”.

3

hi martin

First of all , I have created custom service (by own logic) and deployed as well in service group.

When i want to consume AX service through external application (visual studio console application).

The service of the AX stopped automatically.

regards

Syed Abuthahir

4

You merely repeated the same thing and didn’t explain anything. I can’t help you if you don’t explain your problem.

5

we have planned to integrate AX with CRM .

I have written logic in AX for update AX field as per the parameter send by the CRM team.

when the CRM team to access the ax serives from visual studio mean time Ax service stopped instead of value update.

also the dirparttable can’t edit for udpate opertion issue are coming bacuae we are trying to update the first name and middle name…etc

did u understand my point or else i will give more info regarding same.

Thank & regards

syed abuthahir

6

My last attempt before leaving this thread: Again, what do you mean by “service stopped”? What service? What happened?

7

i have attached screen shot for the service.

the above picture has field status which has value 'started ’ after the service consumed by the external application(CRM) status will be stopped and dynamics closed automatically. again we could’t open dynamics.

Service.jpg
Service.jpg1364×768 233 KB

8

All right, so you mean Dynamics AX AOS windows service, not your custom service.

If AOS server crashed, your first step should always be looking into event log. It contains information about why it crashed.

9

you are right martin but i couldn’t understand the issue . the following information from event log.

Faulting application name: Ax32.exe, version: 6.3.1000.309, time stamp: 0x546925bc

Faulting module name: KERNELBASE.dll, version: 6.3.9600.16408, time stamp: 0x523d4548

Exception code: 0xe0434352

Fault offset: 0x00012eec

Faulting process id: 0x14e0

Faulting application start time: 0x01d10fbac1638128

Faulting application path: C:\Program Files (x86)\Microsoft Dynamics AX\60\Client\Bin\Ax32.exe

Faulting module path: C:\WINDOWS\SYSTEM32\KERNELBASE.dll

Report Id: 0d70eabe-7bb0-11e5-825d-28e3475fa757

Faulting package full name:

Faulting package-relative application ID:

10

You can analyze a memory dump to understand where exactly it crashed, what was the call stack, variable values etc. If you’re not familiar with WinDbg, upload the dump to LCS crash and hand analysis - it will do a basic analysis for you.

Another approach is making sure that your service is created correctly (including CIL etc.) and debugging it. Again, you can see where it fails, the call stack, variables etc.

11

Now I noticed that what posted is about AX client, not AOS.

Either you’re looking at a wrong log entry, or - if a client is somehow involved - your forgot to give us some information.