Link to home
Start Free TrialLog in
Avatar of Tercestisi
TercestisiFlag for United States of America

asked on

GP Dynamics 10 Upgrade Company

We have about 15 GP users; a particular user cannot launch a specific company (we have about 12 companies). It states to run GP Utilities first.

If I run GP Utilities, it states a majority of the companies need to be upgraded; this does not happen for other users.

My questions are:

1) What does this company upgrade actually do in GP Utilities?
2) Will this affect anything globally within GP?

This is running from a Terminal Server.
Avatar of Abdulmalek_Hamsho
Abdulmalek_Hamsho
Flag of United Arab Emirates image

The user is not able to run any of the 12 companies?
Avatar of Tercestisi

ASKER

The user is able to run all other but this one.

We have a mixed mode environment; some launch local installs and some via Terminal Services, and some users both depending on where they're located.

What's odd is that this user can go on two separate computers with local installs, and it won't launch, but go on a third with a local install and it will launch; they cannot log into this company via terminal server.
You mean it's related to the logged-in user rather than the GP-client files?
Actually it does seem to be GP-client files based.

I created a test user and this user, on certain workstations, cannot log into this single company either.
But... this test user is able to log into the company via terminal services whereas the original user (which actually is sa) is getting the error about needing to run GP Utilities.
When you update your GP, it upgrades your GP installation on the machine you're running the update from, and then it goes to the GP utilities to update every company.

It seems these is a version mismatch between your GP installation and your Company DB.

Which Service Pack have you recently applied?

- Have you updated all of the companies in GP utilities?
- Have you updated all of the GP -Client installations?

Please ensure doing the above.
We haven't done a SP upgrade in over a year.

We just deployed GP on terminal services a few months back, and I remember the problem then but there was a million and one other issues to take care of that I did not address this. What's odd is that I cannot login to this isngle company within GP with SA via terminal services, but I can using other user credentials. However, we have a local install on the database server of GP, and I cannot login to this company with either SA or any user password. Launching GP on the local terminal server itself, and not via an RDP connection, I can launch this company using SA and other user credentials.
I am getting more involved with GP at this point, so I'm trying to get the house in order; I think the first step will be learning just what upgrading companies in GP Utilities actually does (does it only affect local files) and if so then I assume I can run it with other users still in the system?
GP Utilities can do the following updates:

- Updates the GP DBs
- Updates Forms and Reports dictionaries
- Sychronizes the Account Format (This has nothing to do with your case)
Correct, but what does upgrading a company do?

If 99% of users are fine, but in order for me to login as SA to this specific company on a specific machine or two, and I press OK to upgrade the company files that do not have green check marks by them... what does this actually do and does this affect other users?
Please do me a favore and make sure your GP Client files are in synch with your DB. Copy the GP folder from a 100% working machine to your machine.
ASKER CERTIFIED SOLUTION
Avatar of Victoria Yudin
Victoria Yudin
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
This is the best approach; I don't think copying the dynamics folder is a good idea since this only happens for SA under a terminal session (rdweb app).