Remove Sana Add-On from NAV

To remove Sana Commerce from Microsoft Dynamics NAV, you should:

  • Cleanup the Data;

  • Restore the Standard Objects Modified for Sana Commerce;

  • Remove WCF Service (applies to NAS);

Cleanup the Data

At first it is required to cleanup the data used by Sana Commerce in Microsoft Dynamics NAV before the removing of the objects from Microsoft Dynamics NAV. Sana Commerce provides a codeunit SC - Uninstall with ID 11123399 which can be used to clear the data. This codeunit deletes the data from all the custom Sana Commerce tables and clears the Sana Commerce specific fields in the standard Microsoft Dynamics NAV tables. It also performs unpublishing of the SC - NAV Web Service codeunit (object ID: 11123303) and deletes all the custom Sana Commerce objects from Microsoft Dynamics NAV.

Find this codeunit in the Object Designer of Microsoft Dynamics NAV Client and run it by selecting it and clicking the Run button. Close the Microsoft Dynamics NAV Classic Client and open it again in order to see the changes.

Restore the Standard Objects Modified for Sana Commerce

NOTE

If some changes were done to the standard Microsoft Dynamics NAV objects modified by Sana after the Sana Commerce solution has been installed, then skip this step.

Also, if you don't have the backup of the standard Microsoft Dynamics NAV objects, then skip this step too.

In both cases, you must manually remove all Sana changes from the standard Microsoft Dynamics NAV objects modified by Sana.

You can skip the entire paragraph Restore Standard Objects Modified for Sana Commerce in this case.

Step 1: Find the fob or txt file which contains the standard Microsoft Dynamics NAV objects without Sana changes. You had to back up the standard Microsoft Dynamics NAV objects before installing Sana into Microsoft Dynamics NAV.

Step 2: Import the standard Microsoft Dynamics NAV objects without Sana changes from the backup (replace the existing objects when Microsoft Dynamics NAV client requests). By importing the objects from this file, you will roll back the standard Microsoft Dynamics NAV objects changed by Sana to their original state.

Remove WCF Service

NOTE

If Sana Commerce connects to Microsoft Dynamics NAV 2009 via Microsoft Dynamics NAV 2009 Web Service, then this step can be skipped. It is applicable to the installations to use NAS only.

 

NOTE

This step is only needed when there is only one installation of Sana Commerce on the current machine. In case there are multiple Sana Commerce installations on the same machine, then this service component might be shared between multiple Sana Commerce NAV services and the removing it will cause the other Sana Commerce applications to stop working.

Step 1: Unregister the Sana Commerce Microsoft Dynamics NAV service. In order to do this, open the Visual Studio 2008 command prompt and run the following command in it:

Copy 
"C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe" Sana.Commerce.Navision.Service.dll /unregister

NOTE

In the x64 environment, the path to the .NET framework is different, therefore you should run the following command instead:

Copy
"C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\RegAsm.exe" Sana.Commerce.Navision.Service.dll /unregister

Step 2: Uninstall the Sana Commerce Microsoft Dynamics NAV service assembly from the GAC. For this run the following command in the Visual Studio 2008 command prompt:

Copy 
gacutil /u Sana.Commerce.Navision.Service

Step 3: Delete the Sana Commerce Microsoft Dynamics NAV service's URL ACL from the URL ACL store. To do this, run the following command:

Copy 
httpcfg delete urlacl /u #PROTOCOL#://#URL#:#PORTNUMBER#/navision/

Here #PROTOCOL#, #URL# and #PORTNUMBER# are the tags, that should be replaced by their corresponding values. These values should be exactly the same as the ones are used during the installation of the Sana Web service for Microsoft Dynamics NAV:

#PROTOCOL#: protocol type (HTTP or HTTPS)
#URL#: Change to:
+ : when the port registrations in the HTTP Server routing table are placed in the "Strong Wildcard" bucket;
[hostname] : when the port registrations are placed in the "Explicit" bucket;
[IP-address] : when the port registrations are placed in the "IP-bound Weak Wildcard" bucket;
* : when the port registrations are placed in the "Weak Wildcard" bucket.
#PORTNUMBER#: must be replaced by the port number on which the NAS is running.

For more information about routing incoming requests, please check http://msdn.microsoft.com/en-us/library/aa364687(VS.85).aspx.