Search This Blog
Showing posts with label Hotfixs and Updates. Show all posts
Showing posts with label Hotfixs and Updates. Show all posts
January 13, 2024
QuickFix: Stop script for service model: AOSService on machine:
If you are getting errors while upgrading your tier-1 environment, trust me you are not alone, many of us facing this error say,
Error 1:
Stop script for service model: AOSService on machine
If you remember this is the same issue we had with the earlier version, and to fix this you have to update the VC++ runtime. You can download this from the below link and run it on our tier-1 environment (s).
Error 2:
GlobalUpdate script for service model: RetailServer on machine:(VM Name)
Let's understand why, (Or let's see what the fix is :) )
Whenever you Apply any update from LCS, it will create a package on VM local disk normally at the below location
ServiceVolume\DeployablePackages and you have to select the most recent folder (in case you already tried a few times with this error).
Navigate to RetailServer\Scripts and find the file name 'DropAllRetialChannelDbObjects'.
Here is the entire path in case you need it (ServiceVolume\DeployablePackages\RetailServer\Scripts\DropAllRetialChannelDbObjects), run this SQL query on AXDB on VM and try again to apply the update.
Tip: This SQL script sometimes takes hours and hours to finish, you can try to stop this execution and select one query at a time from the script.
October 16, 2020
Power automate loopback issue
Hello There,
Power
automate is a really powerful tool for integration requirement in Dynamics 365
FO, I have been using power automate for a long time by now. Recently faced an
issue while trying to call a D365FO trigger, the system was calling twice.
While contacting MS, they have suggested the below hotfix to apply to the
target FO environment. That worked for me.
Happy to share the details in this post, Login into your LCS account, select
the project. Now go to the Issue search tool and search by KB 4556115,
you should get the below details.
Pl, note while creating a deployable package,
double-check your environment version from where you are creating this package
and the target environment version.
-Harry
Follow us on Facebook to keep in rhythm with us. https:fb.com/theaxapta
May 16, 2018
How deploy a metadata or X++ hotfix [D365FO]
[Edited: Oct 16, 2018]
Hi Folks,
Here I’m going to share how to deploy a metadata or X++ hotfix using Visual Studio menu. Follow below steps to get this done. I strongly recommend using VSTS check in once hotfix deployed. Of course, you don't have RDP access other than DEV environment so this option should be for DEV servers only.
Let's start by getting into your dev machine (RDP access).
1. Open Visual studio as admin
2. GO to D365> addins
![clip_image002 clip_image002](https://lh3.googleusercontent.com/-HNuSymt9szM/WvxYEH1a2YI/AAAAAAAACLc/LRkH8BrsWVojg7ALnleq-rsDlC3PtI0QwCHMYCw/clip_image002_thumb%255B6%255D?imgmax=800)
3. Next windows
![clip_image004 clip_image004](https://lh3.googleusercontent.com/-3qIGjwzRHbI/WvxYF8cH8VI/AAAAAAAACLk/mmQbir9ogxEXF9NYEt4du44AAqOgBqa2ACHMYCw/clip_image004_thumb%255B6%255D?imgmax=800)
Browse metadata hotfix file
![clip_image006 clip_image006](https://lh3.googleusercontent.com/-BZGhlKIavlk/WvxYHnkmm3I/AAAAAAAACLs/xjbNwWYzkhIwF3zw8qd9ZWzo_uYdrhOVwCHMYCw/clip_image006_thumb%255B3%255D?imgmax=800)
The file must be unzipped from a folder.
4. Click on prepare button
![clip_image008 clip_image008](https://lh3.googleusercontent.com/-eqeTpEr7FUQ/WvxYJBZHx7I/AAAAAAAACL0/J9L_gfWVFx0KGJMphO46ULA-uBecXhs7ACHMYCw/clip_image008_thumb%255B4%255D?imgmax=800)
You will get an info log for completion
5. Now close this dialog box and As a next step, you need to check-in all affected object in VSTS. Its a mandatory step in the process so in case anything goes wrong you will have the option to revert the hotfix changes.
if you missed this step and you need to revert the changes, the system may delete the object itself as these objects were never part of VSTS.
6. After this intermediate code check-in, repeat step 2 and 3 and this time click on apply directly.
![clip_image010 clip_image010](https://lh3.googleusercontent.com/-50bWC-27GUM/WvxYK-3LasI/AAAAAAAACL8/kleMvfJn13cRuaxqYzRLymAUHq9m84dfQCHMYCw/clip_image010_thumb%255B3%255D?imgmax=800)
Get Infolog once complete
7. Do application build with DB synch and test the hotfix. If the hotfix is working expected than you need to check-in the objects again.
8. Sometimes these changes don’t come in pending changes for VSTS. In that case, you may need to add manually in VSTS branch. Go to Source control > <VSTS branch> > Metadata folder> Right click and select “Add Items to folder”. Don’t create any folder manually, the system must create respective folders automatically when you add an item.
![clip_image012 clip_image012](https://lh3.googleusercontent.com/-LQWgMLmFXjo/WvxYM2MQndI/AAAAAAAACME/UurSeV1YfLEuamqPKPBvQZ-Wv1zM7zPsACHMYCw/clip_image012_thumb%255B10%255D?imgmax=800)
9. Now the same can be added in the next deployment package to get this hotfix to change in further environment (another dev box or UAT/SIT/QA).
[Updated on Oct 22, 2018]
Here is a link for further reference,
https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/migration-upgrade/install-metadata-hotfix-package
Thanks, Guys, Enjoy….
Harry.
Hi Folks,
Here I’m going to share how to deploy a metadata or X++ hotfix using Visual Studio menu. Follow below steps to get this done. I strongly recommend using VSTS check in once hotfix deployed. Of course, you don't have RDP access other than DEV environment so this option should be for DEV servers only.
Let's start by getting into your dev machine (RDP access).
1. Open Visual studio as admin
2. GO to D365> addins
3. Next windows
Browse metadata hotfix file
The file must be unzipped from a folder.
4. Click on prepare button
You will get an info log for completion
5. Now close this dialog box and As a next step, you need to check-in all affected object in VSTS. Its a mandatory step in the process so in case anything goes wrong you will have the option to revert the hotfix changes.
if you missed this step and you need to revert the changes, the system may delete the object itself as these objects were never part of VSTS.
6. After this intermediate code check-in, repeat step 2 and 3 and this time click on apply directly.
Get Infolog once complete
7. Do application build with DB synch and test the hotfix. If the hotfix is working expected than you need to check-in the objects again.
8. Sometimes these changes don’t come in pending changes for VSTS. In that case, you may need to add manually in VSTS branch. Go to Source control > <VSTS branch> > Metadata folder> Right click and select “Add Items to folder”. Don’t create any folder manually, the system must create respective folders automatically when you add an item.
9. Now the same can be added in the next deployment package to get this hotfix to change in further environment (another dev box or UAT/SIT/QA).
[Updated on Oct 22, 2018]
Here is a link for further reference,
https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/migration-upgrade/install-metadata-hotfix-package
Thanks, Guys, Enjoy….
Harry.
June 14, 2015
Dynamics AX 2012 R3, CU9 is out in market.
Hi Folks,
Finally CU9 is released this week.
Here is some more details about this Cumulative update.
New Highlights
1. Introduced new features into HR, Transportation Management,Warehouse Management and Retails modules.
2. Many county-specific regions updates including US, UK, INDIA, Poland, Belgium, Brazil, Europe, Germany, India, Italy, Lithuania, Mexico, Netherlands, Russia, Spain, Austria and Poland
General Information
1. Installation Guide
2. What’s new in CU9
3. Build No: 6.3.2000.326
Kernel: 6.3.2000.326
Download Option:
1. From LCS
2. From Partner/Customer resource
- Harry
Finally CU9 is released this week.
Here is some more details about this Cumulative update.
New Highlights
1. Introduced new features into HR, Transportation Management,Warehouse Management and Retails modules.
2. Many county-specific regions updates including US, UK, INDIA, Poland, Belgium, Brazil, Europe, Germany, India, Italy, Lithuania, Mexico, Netherlands, Russia, Spain, Austria and Poland
General Information
1. Installation Guide
2. What’s new in CU9
3. Build No: 6.3.2000.326
Kernel: 6.3.2000.326
Download Option:
1. From LCS
2. From Partner/Customer resource
- Harry
Subscribe to:
Posts (Atom)