• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 375
  • Last Modified:

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.
0
Tercestisi
Asked:
Tercestisi
  • 7
  • 5
1 Solution
 
Abdulmalek_HamshoCommented:
The user is not able to run any of the 12 companies?
0
 
TercestisiAuthor Commented:
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.
0
 
Abdulmalek_HamshoCommented:
You mean it's related to the logged-in user rather than the GP-client files?
0
Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

 
TercestisiAuthor Commented:
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.
0
 
TercestisiAuthor Commented:
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.
0
 
Abdulmalek_HamshoCommented:
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.
0
 
TercestisiAuthor Commented:
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.
0
 
TercestisiAuthor Commented:
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?
0
 
Abdulmalek_HamshoCommented:
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)
0
 
TercestisiAuthor Commented:
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?
0
 
Abdulmalek_HamshoCommented:
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.
0
 
Victoria YudinCommented:
Do not actually do the upgrade in Utilities - this updates the data on your SQL Server, not local files.  While there may be others, the most common reasons for this message are:
- You have products installed/updated on the client that are not installed/updated on the server.
- You have a version mismatch between your data (on the SQL Server) and the GP application you are launching.
- You are launching an incorrect version of the GP application or are pointing to the wrong SQL instance.
- There is a permissions issue of some sort.  (This would most likely be Windows permissions, not GP.)

These are probably in order that I have seen them occur.  Again, you do not want to actually perform an update if everything else besides this is working correctly.  And you definitely do not want to do anything like this while other users are in GP and without a full backup.

Unless this issue is not time sensitive at all, you may want to consider talking to your GP partner or GP Support to get this sorted out properly and quickly.  
0
 
TercestisiAuthor Commented:
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).
0

Featured Post

Microsoft Certification Exam 74-409

VeeamĀ® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now