It has been 5 years or more since I worked in that environment. Pervasive has not been supported for at leat that long. Here is a KB I found to help out.
Dan
Location Translation - Comprehensive Checklist for Dynamics
View products that this article applies to.
--------------------------------------------------------------------------------
Confidential Article
(The information in this article is provided to you in accordance with your Confidentiality Agreement)
--------------------------------------------------------------------------------
Article ID : 856159
Last Review : N/A
Revision : 1.5
TechKnowledge Content
The information in this document applies to:
- Great Plains Standard on Pervasive.SQL
- Great Plains Standard on c-tree
Issue
I am receiving the Location Translation error message during the launch of Dynamics. What can I do to resolve this?
Resolution
Here is a list of the most common causes of this error - includes tips for using different Location Translations, existing installations, and new installations of Dynamics:
1. My system has worked fine in the past, now I am receiving this error from all workstations. In this case, the SY02100 and/or SY03600 files may be damaged.
a. Replace these files from your most recent working backup.
b. The SY02100 is the pathnames file. This file only changes when a company is added or removed.
c. The SY03600 is the location translation master table. It will not change until a workstation is added that is pathed to the data files differently than your other workstations.
2. My system has worked fine in the past, now all workstations receive this error. I have replaced the SY02100 and SY03600 with the same results.
a. A location translation message will also appear if the SY05100 or SY01700 files are missing or damaged.
b. The SY05100 is the Modules Id Master table and should be located at the root of your Dynamics data directory, at the same level as the SY02100 and SY03600 files.
c. The SY01700 is the Error Messages Master table, located in the System folder of the data directory. Both of these files can be copied off of the corresponding version's CD to attempt to cure this problem.
Note - Unmark the Read Only option after copying a file from the Dynamics CD. The SY05100 is involved in some Service Packs. You may need to get the file from the download if the Service Pack has been applied in the system. Refer to the Readme file in each Service Pack to determine if this is an issue for your installation.
3. I am receiving the Location Translation window, but it is entirely blank.
a. You should at least be able to see the default Location Translation Id of 'Windows'. If the window is blank, you are having a connectivity issue. In most cases, launching Dynamics instead of Dynamics Utilities will produce a numbered error message you can use to further troubleshoot the problem.
b. If you are prompted to launch Dynamics Utilities each time you try to launch Dynamics, you need to edit a line in the dex.ini file located in each Dynamics client directory. Change SYNCHRONIZE = from TRUE to FALSE and you will be able to launch Dynamics.
Note - Keep in mind that if this is a newly installed client, you must go thru Dynamics Utilities to synchronize this client before trying to log in to Dynamics. Change SYNCHRONIZE = back to TRUE and launch Dynamics Utilities if you get to the login screen after resolving the Location Translation problem.
4. When I launch, I do see the default Location Translation Id of 'Windows', and I have tried steps 1 through 3 above.
a. In this scenario, we need to check the pathnames file to see if we have pathing to the companies. To do this look for the ADD or LOCATIONS button.
b. Depending on the Dynamics version you are on, you will get these options in different sequences. If you see an ADD button, click it. The subsequent window will have the LOCATIONS button.
c. This button opens a path preview window, which opens your SY02100 file. In here, you should see pathing statements which include references to any company you have installed.
For example: :F:Dynamics/Two_Inc/Finance.
d. If all you see are 4 generic statements, you are not pathed to the correct directory from this workstation.
e. To check this, look at the pathname= line in the dex.ini file of the clients Dynamics folder.
f. This should be pointing to the data folder where your SY02100 file is located.
g. If you are unsure of what the path should read, you can blank out what pathname= and workstation= in the dex.ini. The workstation= line stores which Location Translation Id this workstation is using to access the data.
Note - The workstation2= line has nothing to do with Location Translation. Do not change this line.
h. Once you have blanked out the pathname= and workstation= lines, launch Dynamics.
i. You will be prompted to enter the location of your pathnames file. This is the SY02100 file in the root of your data folder. Use the yellow folder button to open a browser and browse to this location.
j. Once you see your correct pathnames file, choose Save. Do not highlight the SY02100 itself when browsing. Click OK to the subsequent window and you should now see your correct Location Translation information.
k. Should you find you were pathed to an incorrect directory, check that location to see if an SY02100 and SY03600 file were created there. If so, rename them. Verify you can still launch successfully before deleting these extra files.
5. I am creating a new company and get prompted for a Location Translation.
a. In this scenario, you have one of two problems.
1. You have mixed pathing in your pathnames file. To check this, go to Setup | System | Location Translation, then choose the Locations button. This will open your SY02100 in a path preview window. All of these pathing statements should be similar, meaning that they should all be UNC type pathing or all begin with the same mapped drive letter. If you have a mixture of pathing statements, you will most likely be unable to create a company. Recreating your pathnames file is your best option here. Refer to Techknowledge for steps to recreate the pathnames file.
2. You are attempting to create this company from a workstation not pathed to the data as written in the pathname file.
a. When you create a company, Dynamics will write these path statements based on the pathname= line of your dex.ini file. If this line is different from how your pathname file is written, you will not be able to create the company and are actually creating the mixed pathing problem.
b. For example, looking in the path preview window, I see all of my pathing statements begin with :J:. My pathname= line in the dex.ini of this workstation has UNC pathing. In order to get this to work, you will either need to find a workstation whose pathname= line sees the data thru a J: drive mapping, or reconfigure this workstation to find the data thru the J: drive mapping.
c. One unique situation is when the data has been moved and the pathname file was originally written with UNC pathing. In this scenario, all pathing statements are written beginning with the name of the old data server. Since you are now on a server with a new name, it is impossible to be at a workstation with a correct UNC path.
For example, the pathname file reads //Server1/apps/dynamics/.... The data is now on //Server2/, meaning that all workstations using UNC pathing must see the data as //Server2/apps/dynamics/.... In this situation, your only recourse is to recreate the SY02100 file with pathing referring to the new server name.
6. I know I need to create a Location Translation, but am unsure of what it should be.
a. Here is the easiest way to determine a Location Translation.
b. Look at the pathname= line of the dex.ini and write this down.
c. In our example, we will say pathname=G:\Apps\Dynamics. This is the To: portion of your location translation.
d. Next, bring up the path preview window, either thru the LOCATIONS button in the Location Translation entry window or thru Dynamics in Setup | System | Location Translation | LOCATIONS.
e. Write down the first line of this file. In most cases, it will be to the Finance folder of the Two_Inc company. In our example, let's say it reads :Q:Dynamics/Two_Inc/Finance. This is our From: portion of our Location Translation.
f. Keep in mind that you should never have duplicate Location Translation Id's. Make sure that when adding a new id, it is different than all other id's.
g. In our example, we will call our id 'Herman'. The id name is totally arbitrary, meaning it can be anything, as long as it isn't a duplicate.
h. Compare the two statements. When they are exactly the same, you can cancel what is written in each at that point and to the right.
i. In our example, both statements come to a point where they refer to the Dynamics directory. In each, we can drop Dynamics and everything to the right.
j. This leaves us with our Location Translation of 'Herman' translate From :Q: ( we drop Dynamics and everything to the right) translate To :G:Apps/ (again we drop Dynamics and everything to the right).
k. When drive letters are used, remember you always put colons around the letter and there is no slash between the second colon and directory name. You also need a trailing forward slash (/) at the end. Always use forward slashes in your Location Translation Id.
l. The end result for the example is: FROM :Q: TO :G:Apps/
This article was TechKnowledge Document ID: 25179
