New XAL installation
NHL
I try to make a new installation of XAL. A cilent has a brand new server
with Windows Server 2008 Standard Edistion (64-bit) OS and Microsoft SQL
Server 2008 and will have the latest XAL (3.81) SQL version.
I created a new database and ODBC and installed XAL 3.5 according to the
installations guide. I rename the c_codes.sys to .old and change the name to
the downloaded code file to c_codes.sys.
Problems start with running XalActivator: errors occur when trying to
validate kernels and then trying to rename c_codes.sys to c_codes.old (?)
If I replace the kernels with those for 3.81 XalActivator validates kernels
but error occurs when renaming c_codes.sys.
Slize program does not work in 64-bits environment.
If I try to start the application anyway with Install Microsoft XAL from
Start menu, the error message occurs saying “Too many errors” and the
application shuts down.
According to XAL compatibility sheet XAL is supposed to work with windows
2008 and sql 2008.
Does anyone have an idea what could be wrong and how to work it around?
Henrik Hansen [MSFT]
You should keep in mind that the original Navision XAL 3.5 installer was not
targeted to run on 64-bit Windows platform including UAC.
The database compatibility document states the compatibility of a given
kernel version deployed on an existing or upgraded XAL installation.
If you are not familiar with the XAL program and installation procedures you
might want to get hold of a Partner with XAL knowledge to set up the basics.
The following guide does not claim to be perfect or exhausting, but should
be able to get you up and running.
Remember your customer must have a valid maintenance subscription to be
eligible for using latest XAL kernels and updates.
The original installer default install to %ProgramFiles% folder, which on
Windows Server 2008 would violate basic security policies on that folder as
XAL requires RW access for a low privilege user.
So XAL should be installed to e.g. C:\XAL350.
Once installed upgrade the kernels to XAL 3.8.1.351, which were the last
released kernels for Microsoft XAL.
Kernels can be downloaded from
https://mbs.microsoft.com/partnersource/downloads/hotfixes/MicrosoftXAL381351Kernel .
There is a 64-bit compliant version of slize.exe for download as well.
Instead of using XalActivator, slize the XAL kernels directly using
slize.exe:
1. Download the new kernels, UnZip the files, extract these to the
installation folder and overwrite the existing kernels.
2. Download slize.zip, UnZip the file and place it in the installation
folder (if not already present).
3. Open a DOS-prompt (Command-prompt).
4. Go to your installation folder in the DOS-prompt using the command "cd
[folder name]" for instance cd C:\XAL350
5. Enter the command "slize.exe -c [kernel name] -s [kernel code]" to slize
the kernels one at a time e.g. slize.exe -c dxalw32.exe -s 99999999aaaaaaa,
where 99999999 represents your serial number and aaaaaaa represents the
kernel code for the database platform.
Pay attention to the fact that XAL is a 32-bit program and thus on 64-bit
environments run in an emulated environment WoW (Windows on Windows), which
have separate registry settings.
So the ODBC DSN connection should be set up in using the ODBC Administrator
(odbcad32.exe ) found in C:\Windows\SysWOW64.
Create appropriate Windows user groups for setting permissions on the XAL
installations folder.
Users running in low privilege mode should have RW access to the XAL folder.
To get installation up and running I would suggest opening a file browser in
the installation folder and start the kernels directly from there.
On first start up your cxal.ini should look like:
-zdb=XAL350
-zsrvr=ServerName\InstanceName
-zdsn=XAL350
-cdk
-uSupervisor
-zuXAL_SUPERVISOR
-zpYourPassword
-zjSQLSRVR.XAL
given that your SQL server accepts SQL authentication, XAL_SUPERVISOR has
been granted login and is dbo on XAL350 database and has been set up with
xal_supervisor_psw as password for SQL authentication.
Once XAL is started, has connected to the database successfully and
initialization script SQLSRVR.XAL has run you should go to
General/Adjustment/Development
menu/DBD/Various/SQL/Maintenance/Check/Synchronise with all checks turned
on.
Once synchronized -zjSQLSRVR.XAL must be removed from the cxal.ini file.
Now you can run the XAL script SQL-Login with option PASSWORD to save your
password for your SQL authentication user in the c_direct.sys file (not
clear text, but not strong encryption by today’s standards).
Now –zpYourPassword can be removed from cxal.ini. If your SQL authentication
user actually is XAL_SUPERVISOR, you can delete -zuXAL_SUPERVISOR from
cxal.ini as well, as XAL_SUPERVISOR is the default SQL user provided by XAL.
Remove –uSupervisor from cxal.ini and start creating XAL users and XAL user
groups as needed.
The help file system for the GUI will not work by default on post Windows XP
installations, but can be fixed – please refer to
http://support.microsoft.com/kb/917607
--
Best Regards
Henrik Hansen [MSFT]
Tecnical Program Manager Microsoft Dynamics C5 & Microsoft XAL
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
"NHL" <N...@discussions.microsoft.com> wrote in message
news:773C28B4-FE9C-49F4...@microsoft.com...
rake...@gmail.com
I also am facing some difficulties for XAL application on Window 2008. Kindly let me to whom should be contact if need to get the updated version of Kernel(https://mbs.microsoft.com/partnersource/downloads/hotfixes/MicrosoftXAL381351Kernel)
Awaiting for kind response.
kind regards,
Rakesh