3/12/2024 0 Comments D365 stop aos web service![]() This will also ensure we get rid of any caching issues. I would also delete the AUC and KTI files for the account that is running an AOS Service. Since you are going to stop all AOS Services and have the users out of the system. Before you stop the services you will need to ensure that all users are out of the system as restarting the system will kick them out. This will require that you stop all AOS Services and bring them up on at a time. If you have checked all the items above and the issue still persists, then we have a caching issue. Also verified that the Period Status was set to Open, mentioned in the error message Expand the Fiscal Year and verify that you have a 2016 CalendarĤ. Navigate to General Ledger | Setup | Ledgerģ. Check setup of Fiscal Year and Calendarġ. We did this by following the steps below. We checked the normal setup of the Fiscal Year and Calendar. I was working with a Dynamics AX 2012 client recently and they were getting the error message “Period for xxxx does not exist” and Fiscal Year for xxxx does not exist.” Here is a screenshot of the Fiscal Year error and Period error:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |