GP client install inconsistency - dictionary errors

[number1rookie]

I installed GP 8.0 from a installation template on 1 XP machine with no problems. I have the ODBC properly setup, and bcp.exe properly installed to satisfy GP Utilities. I am able to log in with different users, no problem.

I did the same thing on two other XP machines and both machines give this Dexterity Runtime error on start-up.

Unable to open dictionary
:CROGRA~1/MID1AC~1/GREATP~1/dictionary name.DIC.

I get this error for the following .dic's:

ADVSECURE.DIC
ADV_FRM.DIC
ADV_RPT.DIC
AREC.DIC
ARECFRM.DIC
ARECRPT.DIC
CFM.DIC
CFMFORM.DIC
CMFRPTS.DIC
EXP1493.DIC
EXP1493F.DIC
EXP1493R.DIC
HR.DIC
HRPFRMS.DIC

Once I click OK on each of these errors the program will start and let me log in, but of course and soon as I try to do something the program gives an error and closes because the dictionaries arent available. I've looked very closely at the client machine that works and the ones that do not. The installation is exactly the same unless I've missed some very small detail. Any help is greatly appreciated. Thank you ahead of time.

 

[jazgeek]

a trick I use is after installing, I copy the directory contents of another "template" machine's great plains directory. That way I'm assured of not having to apply the patches on each machine individually.



-----------
and they wonder why they call it Great Pains!

jaz

 

[number1rookie]

Thank you for replying jaz. Unfortunately, I had already tried that before I posted to no avail. Anybody else have any suggestions? Thanks.

 

[btamulis]

I suggest you look at dynamics.set file which will be in the client machine's Great Plains Folder (under Microsoft Business Solutions). The set file describes where the dictionaries are located to launch application. In you case, you login - the system looks at set file - verifies dictionaries are located where they should be - in your case it doesn't find them and gives you error messages.

I install clients just like Jaz suggests. I install the first client, install all service packs, copy that directory out to the network. Then I go to next machine - install client using CD (this assures registry entries get made) and then - blow away the Great Plains folder created and copy down the updated folder from network. The Great Plains Templates have never worked for me.

When installing off CD - registry entries are made. Your situation still might be a registry problem.

I would probably re-install.

Bron Tamulis

 

[jazgeek]

one thing that may be affecting your installation is user rights. Was GP installed via add remove programs in the administrator profile or was it installed via the user's profile. If by user, did the user have enough rights to do the installation and affect registry settings? Does the user have sufficient rights on the great plains directory etc etc.

Simple way to check this is to grant the user local admin rights and try launching GP and see if you have errors still.



-----------
and they wonder why they call it Great Pains!

jaz

 

[number1rookie]

Thank you both for replying.

BT - I will definately check out the dynamics.set file. This might sound like a dumb question, but what do I use to open the dynamics.set file?

Jaz - I did use the client's user profile to install from the install template, but the client account was already an admin on the local machine.

I did an experiment, I installed a fresh copy of XP Pro w/SP2 and all critical updates on a vacant machine. I then successfully installed GP from the install template. So that makes two successful installs from the template on 2 fresh installs of XP. The machines that were not successful from the template have had MAS200 on them among other various programs and who knows what before I got to them. I'm thinking that these machines have been through something that is conflicting with the GP install. However, I will definately try the install from the CD the way you explained. Maybe that and with making sure the dynamics.set file is in order will help me to be successful. As it stands now, the only successful solution that has worked is a fresh install of XP, but I will definately get to the bottom of it.

Thank you guys for your help, it is greatly appreciated.

 

[VictoriaYudin]

We have seen this A LOT on "non-fresh" installs or imaged installs of Windows (XP as well as other versions.) Some steps that we use to try to mitigate this:

- always install GP as the LOCAL Administrator user (as opposed to domain admin or another user that is a local admin)
- try to turn off as many services as possible prior to install, some that we have seen conflict in the past are Blackberry redirector, anti-virus sw (usually Symantec causes issues), antispyware sw (almost all), I am sure there are a lot of others

To answer your other question, if you right click on dynamics.set and choose Edit (instead of open) it should open in Notepad.

 

[number1rookie]

Thanks so much, I will try these things and let you all know what happens. Thank you again.

 

[number1rookie]

Installing from the CD did the trick. Thank you guys for your advice. I truly appreciate it. Many thanks.