Open regedit
HKLM\Software\Navision\Axapta\3.0
Check value of the key Current (this should be the current config you are
invoking)
Under 3.0 find the key that current is pointing and look for the key
language (could be en-us).
If this does not work then my only suggestion is a clean
Is there another copy of Axapta on the machine?
John T. Lindsay
Micro Sciences Company
_
From: Axapta-Knowledge-Village@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Steven
Sent: Friday, February 17, 2006 6:49 AM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: [Axapta-
Let me understand the setup.
You have a single machine with Axapta and SQL installed (Demo version?) and
running 2 tier?
How is the com connector being used. i.e. IIS, VB, .NET?
John T. Lindsay
Micro Sciences Company
_
From: Axapta-Knowledge-Village@yahoogroups.com
[mailto
One more thing, you must sign on to Axapta via the Client using the same
configuration file before
accessing the com connector. This instantiates the configuration for the com
connector.
Can you send me you configuration file. Use notepad to open it and paste the
contents.
John T. Lindsay
Is the config file local on the machine that the com connector is installed
on?
Confidentiality Notice: This e-mail contains confidential and/or privileged
information and is intended to be read only by the person or authorized
representative of the organization to whom it is addressed. If you
Check the Axapta Configuration and make sure that you are using the correct
configuration file.
The connector needs to have the correct configuration file on the local
machine.
John T. Lindsay
Micro Sciences Company
_
From: Axapta-Knowledge-Village@yahoogroups.com
[mailto:[EMAIL
6 matches
Mail list logo
