Role centers and enterprise portal on Ax 2009

During installation of role centers and enterprise portal I got this error:

Setup cannot connect to the Application Object Server instance (AOS) by using the Business Connector. Confirm that the AOS is running, and that your account (domain\username) is a valid Microsoft Dynamics AX user. See the log file C:\Documents and Settings\All Users\Application Data\Microsoft\Dynamics AX\Dynamics AX Setup Logs\2008-09-11 11-27-45\DynamicsSetupLog.txt for more information.

I have checked that the user already exists in Axapta. Then I tried changed the service account with the same user and it works.
The service account is in Administration > Setup > Security > System service account. Put the username and domain in the alias and network domain fields.

I post this with hope to save time just in case others get the same problem.

Referenced account is currently locked out

Recently I experienced a problem accessing a network share. Each time I go to start > run > \\networkshare I always get this error message :
\\networshare is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
The referenced account is currently locked out and may not be logged on to.

I have checked with the administrator and unlock my AD account but the error persist.
Seems that there is a cache on my user profile accessing the network share using wrong password.
The solution is then I force using this in command prompt :
net use \\networkshare\ipc$ /user:domain\user

Then it asks for password and later I can access the networkshare again.

Trace Parser for Dynamic Ax

I am about to install Trace Parser to see how it can help solving performance issue. This tool can be downloaded here

Axapta : unable to load page error

Recently I got an error "unable to load page" when opening report. After googling I found this . The solution is to use newer client kernel.
However weird that I don't experience the problem using diferent pc as client, using old kernel.

Sharepoint service log files grow rapidly

Recently I noticed that I run out disk space in my virtual machine where I install Windows sharepoint services.
I see that the log folder grows very big in size. It is already 2 GB now.
The default log folder is located here :
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\
To avoid it consumes space in C, I change it to different folder which is achieved through:
Sharepoint central administration > Operations > Diagnostic logging.
Then I also change timer job definitions by disabling them (maybe I will enable them once I know more about sharepoint).

Installing Dynamic Ax 2009

After some years working with Axapta 3 and 4, today I tried installing Dynamic Ax 2009.
The first impression with Ax 2009 is that the software contains more options than Ax 4, and the installation guide is more detail.

I download the installer here and the demo data
here. Seems weird because usually all are packed into one installation source (DVD).
Note that partner source login is required to download.

I run the installer and create a new blank database. After installation checklist finished, I restored the demo data (which comes as database backup) and point the AOS to the demo data instead of blank database created during installation.
When I started the AOS service I got this error in the event viewer :

The version of the stored procedures in this database is different than that expected by the Application Object Server (AOS). You must set up a new instance of the AOS that points to this database to update the version of the stored procedures


Seems that the demo data is created using AOS of earlier version from the latest download. Looking at the SQL Server profiler, I found that the table SQLSYSTEMVARIABLES is accessed during service start. Comparing two databases (one created during installation and one from demo data), contents of this table are different, and the one from installer is newer.
So I run this statement into the demo data database :

delete from sqlsystemvariables;
insert into sqlsystemvariables select * from DynamicAx5Blank.dbo.sqlsystemvariables;

Then restart AOS and it works.

The backup set holds a backup of a database other than the existing database

This error message appear when I tried to restore an SQL 2K SP4 db into SQL 2005, using SQL Server Management Studio.
Although I have specified overwrite existing database, the error message still appear.
So I run transact-sql statement instead :

restore filelistonly
from disk = 'D:\SQL Backup\sourceDB.bak'
GO
--This will show the logical file name needed in the operation below
restore database targetDB
from disk = 'D:\SQL Backup\sourceDB.bak'
WITH MOVE 'sourceDB_Data' TO 'D:\SQLDATA\targetDB_Data.MDF',
MOVE 'sourceDB_Log' TO 'D:\SQLDATA\targetDB_Log.ldf',
REPLACE,STATS
GO
-- The option with replace is mandatory as it will overwrite existing database. With stat will show the operation progress