To resolve mentioned error we have following options.
Solution 1:
Do incremental CIL compile.
Not succeeded?!
Solution 2:
Do full CIL compile.
Still not succeeded?!
Solution 3:
Stop AOS service.
Rename XppIL folder to XppIL_old. form the following location.
<Drive letter>:\Program Files\Microsoft Dynamics AX\60\Server\<Instance Name>\bin
Start AOS service.
Do full CIL compilation.
Now your face should be filled with SMILE :)
Have any question?! Please comment.
Solution 1:
Do incremental CIL compile.
Not succeeded?!
Solution 2:
Do full CIL compile.
Still not succeeded?!
Solution 3:
Stop AOS service.
Rename XppIL folder to XppIL_old. form the following location.
<Drive letter>:\Program Files\Microsoft Dynamics AX\60\Server\<Instance Name>\bin
Start AOS service.
Do full CIL compilation.
Now your face should be filled with SMILE :)
Have any question?! Please comment.
Hi, I completed all the steps, stop the AOS, deleted folder, complete CIL compilation .. and still shows the same error.
ReplyDeleteAn error in complete CIL was the problem..
ReplyDeletethank you!
Best regards!
Tried all those things but the issue still exists.
ReplyDeleteFound out the solutions :
- AIF | Inbound ports | Activate sysworkflow services
- AIF | Inbound ports | Deactivate AXClient service & AIF service | then Reactivate them again
- Refresh WCF configuration (from AX Client) | then export it into xpo file
Thanks ds for update. Yes, This should be solution 1) to try.
DeleteIf Re-Activating above mentioned AIF service does not work, we should go for all above mentioned solutions and then check again for these AIF services.
hi can you explain me why we are changing the name of folder, i would like to know exactly what happening behind.
ReplyDeleteThank
Raghunath Chintala
Raghu nath,
DeleteAim is to recreate file in mentioned folder after CIL Compilation.
If files are not available in mentioned folder while starting up services, AOS will recreate it.
So, either you rename or take backup of folder, then delete all file.
Thanks mehul,
ReplyDeleteAfter following these steps i resolved the error.