AX 2012 R2 - Installing new databases from setup

maqk® by MAQ Khan | 7:43 PM

Their can be scenarios when you want multiple databases on the same service. For example having a separated testing environment, development environment, staging and production.

I mentioned one such scenario in one of my previous posts in which I installed the new databases only to see the face of another error :) The 110 error code. 

The thing is, when you install new databases from the AX 2012 R2 setup, it does install new databases quite successfully. However, it misses two critical stored procedures on the database, the CREATESERVERSESSIONS and CREATEUSERSESSIONS

You can get these stored procedures from any dynamics ax 2012 r2 database and an apply on to your new database to fix the error.

Dynamics AX 2012 R2 Fatal SQL condition during login

maqk® by MAQ Khan | 6:26 PM

An interesting yet dangerous thing happened in my AX life today. Actually in one of our environments, we had previously upgraded to CU6. Now somehow the AX server VPC got restored to the earliest snapshot available forcing us to install a new fresh AOS service instance. The service was installed in no time but only to give the following error at each start and failing each time.

A peep into the event log yield the following information:

Object Server 01: Fatal SQL condition during login. Error message: "The internal time zone version number stored in the database is higher than the version supported by the Kernel (4/2). Use a newer Microsoft Dynamics AX kernel."
I have the following roadmap for the resolution now :)

  1. Install clean databases with new names
  2. Connect installed service to new database and start AOS service
  3. Compile application code and sync database
  4. Upgrade to CU6
  5. Connect AOS service with existing CU6 compatible databases
  6. Resume from whatever we left
To my retro suprise, the service failed to start with error code 110 after configuring to connect with new databases. This matter was resolved menrioned in another blog.

Now resuming from point 3 :) 

DAX 2012 R2 CU6 SYP Labels issue fix

maqk® by MAQ Khan | 12:26 PM

I recently upgraded my local environment from Dynamic Ax 2012 R2 (Flat: build no# to CU6 (6.2.1000.1437 - 2012 R2 Cumulative Update 6 (CU6)). The process was seamless however one issue arrived. The lable files. A lot of labels (in various mnodules including GL etc) started appearing as just flat label IDs 

Info log after CU6 upgrade

I found the solution in one of Ing. Karel Fischl's msdn blog: Missing SYP labels after upgrading to AX2012 R2 CU6 with just a minor adjustment, the two types of files to be removed from the location: are 

  • ALC files (Label description)
  • ALD files (Label data)
And thats it, worked 100% on my production :)

Dynamics AX 2012 - Workflow not working properly

maqk® by MAQ Khan | 3:56 PM

While doing some customizations, I needed to use the purchase requisition workflow. However after submitting the purchase requisition, the workflow wont proceed and no work items would create.

Batch job and Batch groups

Workflow is dependent on batch groups. Perhaps all tasks appearing under the 'Periodic' heading are. The development environment I was working on had an empty named batch group. But the problem is not with a no name or empty name thing. It is the details the batch group carries, if it carries any :)

A Batch Group represents a Batch Server (AOS Server)

Its all about distributing workload and responsibility, for load balancing. A batch group posses no significance if it has no AOS servers associated to it. See the picture below;
System Administration > Setup > Batch Group

Hence if the workflow activities and tasks generated are being dependant on an empty batch, such activities wont occur / complete.

The Story

In my case, the empty batch group was really empty (rotfl) and I dont know for what reason it was like that. What really happened was that first I went to sys Adm > Inquiries > Batch Jobs. There I tried to tweak with multiple waiting, error status jobs. I came to find that only the With Hold status jobs are modifiable. Once that was known, I started putting the jobs on this status and doing things with them. There I saw no name appearing in the batch. This also raised the question if this empty batch associated has issues with it. Later I went to see no server is associated with the group. I associated the default and only AOS server  on the VM to the group and there you go :) Happy workflowing

Some useful links for your reference are attached below;


DAX - Some useful links regarding debugging

maqk® by MAQ Khan | 3:41 PM