Thursday, May 29, 2008

Uninstall SQL 2005 Embedded Edition SSEE

Looking for how to uninstall SQL 2005 Embedded Edition SSEE? Me too. There are a lot of links in the web but I think the best one is the following from Microsoft TechNet.

Uninstalling WSUS 3.0 does not uninstall the database instance

If WSUS 3.0 is uninstalled, the database instance will not be uninstalled. The instance may be shared by more than one application, and will cause other applications to fail if it is removed.

If it is necessary to uninstall Windows Internal Database, the following commands will uninstall the application:

(on 32-bit platforms)

msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} callerid=ocsetup.exe

(on 64-bit platforms)

msiexec /x {BDD79957-5801-4A2D-B09E-852E7FA64D01} callerid=ocsetup.exe

If you wish to uninstall Windows Internal Database Service Pack 2 from Windows Server 2008, you may do so by means of Server Manager.

However, the removal of the application may not remove the default .mdf and .ldf files, which will cause a subsequent WSUS 3.0 installation to fail. These files can be deleted from the %windir%\SYSMSI\SSEE directory.

Creating additional environment

If you have chosen to create an additional environment by means of copy-paste and backup-restore commands do not forget about one little thing.

1. In MS SQL management utility do backup of the database of the environment that you have chosen as an 'original' one.

2. Create another database and restore your backup to it (restore transactions logs backup too if presented).

2.1. (A litle important thing!) In the database you should find SysServerSessions table and delete all rows there.

3. Copy-paste C:\Program Files\Microsoft Dynamics AX\40\Application\Appl\Standard or other folder where your original application was installed with other appropriate name. E.g.:

C:\Program Files\Microsoft Dynamics AX\40\Application\Appl\Standard_Test

4. From DAX Setup install additional Object Server having pointed this instance to the recently created database and unchecked Start the AOS Windows service as part of installation option.

5. With Microsoft Dynamics AX Server Configuration Utility choose the new instance of AOS, create a new configuration based on the active configuration and set Application instance to the new one.

Wednesday, May 14, 2008

Language in user options

Accidentally changed Language in User options can cause an issue with logging in to the configuration if you have not the appropriate licence for the language. In this case you might see something alike the following.

oror even

The simplest way to fix it is to change the language in User options but if you have no administrator rights or the administrator is yourself... In this case you should use Microsoft Dynamics AX Configuration Utility

Set Configuration command to run at kernel startup parameter to the value, i.g.,


or another correctly licenced language.

It will override the value chosen in the user option and the configuration then works.
Now, you are allowed to say to the system - Speak My Language!

Tuesday, May 13, 2008

How to delete modifications on few layers

As it is well known:

Modifications are saved in an application layer which is also specified in the configuration. All modifications to application objects in a layer are saved in a file named ax.aod.

If you need to brush off you configuration the simplest way is to do that is just to delete all those files on the file server. The only issue may be if the system is running and, therefore, those are locked.

If that case you have the other way. For example you need to dispose everything that was made on VAR and USR layers.

Open the AOT and create a new project, e.g. LayersVarUsr

Open it and use Advanced Filter/Sort tool on the toolbar or Ctrl-F3

Check AOT and open Inquiry form by clicking Select button

Here you should set the rule for utilLevel field, in our case VAR..USP to include all modifications made on these layers with patch ones as well.

Be patient, it can take much time. When the DAX finishes you will get everything to accomplish your seek-and-destroy mission.

By the way, you can take advantage of using Compare tool to decide what will next happen.

Wednesday, May 7, 2008

Refreshing DataSources on Form

If you have added new fields or made any other changes to the table you can reflect all that on the related DataSource using by Restore command on the appropriate Form

Quoted from the manual:

Notice that after accessing the form in the AOT the definition of the data source
is cached locally in the definition of the form. If changes are made when you
create a new field in the underlying table, you must restore the form to access the
new field in the form. Remember to save the form before you click Restore from
the shortcut menu.