Monday, March 20, 2017

mPOS Offline Provision



I'm sure we all get frustrated when creating an offline database for mPOS only to find out that it wasn't able to provisioned, and the process drop your newly created offline database completely. ¯\_(ツ)_/¯ this is the look I generally make when that happens. Then I asked myself what went wrong and go back to the drawing board to trace the error. Luckily Brian Storie from Microsoft have given a breakdown of the steps we need to take in order to create AND provision our offline database correctly. All credits are given to Brian Storie. The steps sometimes works, but it's definitely a good place to start.


Open Windows File Exporer
1. Go to: C:\Program Files (x86)\Microsoft Dynamics AX\60\Retail Database Utility
2. Click File > Open Command Prompt > Command Prompt with Admin
    Enter the following command (Please change the highlighted values to the name of the SQL  
    Server hosting your channel DB, and the name of your Channel DB)

RetailDbUtilityCmd.exe DeprovisionChannelDB /StoreServerName:YOURSERVERNAME /StoreDatabaseName:YOURCHANNELDATABASE

3. After this command completes, open SQL Server Management Studio, connect to the Channel DB.
4. Expand Tables under the Channel DB
5. Verify any table that ends with _tracking are all deleted in YOURCHANNELDATABASE. (if one does exist then manually delete it)
6. Verify the following three tables do not exist (dbo.schema_info dbo.Scope_config dbo.Scope_info) if they do manually delete them
7. Open “Retail Channel Configuration Utility” as an admin. Go to “Create offline database” section. Enter correct channel database and offline database information. Then click “Apply”.



If all goes well you should be able to create and provision your offline database successfully. hopefully this should help those who are having provisioning problem when creating a new offline database. If you want to know more details on the error, the log file is located in

C:\Program Files (x86)\Microsoft Dynamics AX\60\Retail Database Utility\RetailDatabaseUtility.log

No comments:

Post a Comment