Uninstall Sana Commerce

Remove Sana Add-on from NAV

To remove Sana Commere from 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 SC in NAV before the removing of the objects from 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 SC tables and clears the SC specific fields in the standard NAV tables. It also performs unpublishing of the 'SC - NAV Web Service' codeunit (object ID: '11123303') and deletes all the custom SC objects from NAV.

Find this codeunit in the Object Designer of NAV Client and run it by selecting it and clicking the 'Run' button. Close the 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 objects specified in the list of the changed objects in the 'Changed Objects Overview' chapter after the Sana Commerce solution has been installed, then skip this step.

Also, if you don't have the 'fob' or 'txt' file, which is described in the 'Backup Standard NAV Objects' paragraph, then skip this step too.

In both cases you must manually remove all the SC changes from the standard NAV objects modified by SC. In order to do this, refer to the 'Microsoft Dynamics NAV Changes' page on the help site. Remove the SC changes from the objects specified in the 'Changed NAV Objects' section and then remove the SC specific code.

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 NAV objects and which was created during the installation of SC according to 'Backup Standard NAV Objects' paragraph of the 'Import NAV Objects' chapter. Open the help wizard, select your scenario and move to the needed chapter.

Step 2: Import the objects from this file (replace the existing objects when NAV client requests). By importing the objects from this file you roll back the objects changed by SC to their state before SC had been installed.

Remove WCF Service

 NOTE

If Sana Commerce connects to NAV 2009 via 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 SC on the current machine. In case there are multiple SC installations on the same machine then this service component might be shared between multiple Sana Commerce NAV services and the removing of it will cause the other SC applications to stop working.

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

 NOTE

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

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

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

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

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 Commerce NAV web service:

#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.