Step GlobalUpdate script for service model: RetailServer on machine: DEV-VM is failing during MsDyn365FO package deployment

-

In the past, I often had the problem that during package deployment of a service update via Lifecycle Services (LCS) the step “GlobalUpdate script for service model: RetailServer” unexpectedly failed. The reason why this was not expected is that I´m not using the RetailServer at all, so the component should be in the same state as it was deployed or updated by the previous service update.

After some research, I found the post from Rahul Sharma in the Dynamics 365 community blog. Because of this blog, I found the solution which “solved” the error several times already.

All you have to do is:

1. Connect to the intended environment.

2. Find the latest deployable package applied to the environment. It will be under folder <ServiceVolume>:\DeployablePackages\

3. Under the deployable package folder, find the following SQL script <ServiceVolume>:\DeployablePackages\RetailServer\Scripts\DropAllRetialChannelDbObjects.sql

This script, when run against the AOS database, will remove all objects related to the Retail Channel Database. Only proceed if you are not using the Retail Channel functionality.

4. Connect to the AxDB database and run the above script. This operation will take several minutes.

5. Resume the package deployment or start the package deployment to have the Retail Channel components recreated correctly.

https://community.dynamics.com/ax/b/d365fortechies/posts/microsoft-dynamics-365-finance-update-error-globalupdate-script-for-service-model-retailserver

Comments

Post a Comment

Popular posts from this blog

D365FO - Data integration by OData

-
Image
There are many ways to integrate with D365F&O OData is one of them. This post show you how to do simple integration.  Simple architecture  of OData with 3rd party application There are 3 main steps: Create a table, data entity, and OData service endpoint  Register and prepare (OData client) application authentication in AAD and D365FO Create OData client application  Create a table, data entity, and OData service endpoint First, we create a sample 'MyCar' table. CarID, BrandName, SerieName and Color declared as string, Price as real, and PurchasedDate as date. Then create an index for CarID and set that index to be table's Primary Index.  Then create a data entity. After finished creating, note some data entities, tables, and security privileges are added into project. Now, re-check what we've just created. Table   https://yourboxmainurl/?mi=SysTableBrowser&TableName=MyCar&cmp=DEMF&limitednav=true&lng=en-us OData https://yourboxmainurl/d...
Read more

Create or Update Product attributes using X++ in D365 F&O

-
This code is to update or insert product attributes for a boolean value. Each item will have its own boolean value. We cannot update the existing boolean value for a new item. For the first time, we have to create the attribute value record id for the item and then you can update if you want to make changes to the value based on the record id.  Please change the code according to your requirement.     /// <summary>     ///  To create or update product attribute     /// </summary>     ///     public void createOrUpdateProductAttribute()     {         EcoResProduct                       product;         EcoResDistinctProductVariant        variant;         EcoResProductInstanceValue          ecoResProductInstanceValue;     ...
Read more

Layers concept in D365

-
Image
Layers : Layers are the traditional AX concept but in D365, there is a new process where we extend layers as shown below. Also when you create your model, you specify which layer the model is going to live in. However the importance of layer is quite minimal for instance, you are not required to provide a key for your model to live in that layer. Previously layers were a single stack of code that over-layered upon each other. This new process uses layers but they are located in independent stacks. This was only an architectural overview of Dynamics AX 365.
Read more