web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Login Problem: A get/change first operation on table 'SY_Users_MSTR'...

(0) ShareShare
ReportReport
Posted on by 5

Suddenly I am having a problem logging into the GP, I get the following error: 

A get/change first operation on table 'SY_Users_MSTR' failed accessing SQL data

More Info: Number of results columns doesnt match table definition.

 

I just got back from vacation and haven't made any changes. This is a hosted system with a separate SQL Server. One odd thing was that initially we (any user) were not able to log into (RDP) into the server. I reset my domain password via their web portal and I was able to get in, but I can't log into the GP Application itself. 

 

Version 12.00.1295 SQL Server 2008R2 10.50.4276

Any Ideas?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Bill Campbell Profile Picture
    12 on at

    Do you know if there was a change to the ODBC connection?

    Do you know what user ID is used for the ODBC connection?

    If the user ID used, has had to change their password, then that is likely the cause of the problem.  

    Check to see what User is connecting and then check on the password.

  • scplimited Profile Picture
    5 on at

    I tried looking at the ODBC settings but wasn't sure how it was supposed to be.

    When i click configure and hit next, "With SQL Server authentication using a login ID and password entered by the user." Is selected, all that is entered is SYSTEM with no password. If I click next with it as is I get a Connection Failed (Login failed for user 'SYSTEM').

    I did point this out to the hosting provider but they didn't really catch on.

    I tried changing it to Windows Integrated authentication but when attempting to login in the GP app I get an error about the connection being trusted and to disable trusted connections?

    Something weird happened with domain authentication though this morning as we couldn't log into the server via RDP, no one could till they reset their password. Now we can't get in.  

    The odd thing now is that the system won't let me change my password (via CTRL-ALT-END), it keeps saying that it isn't complicated (doesn't meet requirements) when I'm pretty sure it was complicated enough and i've used less complicated passwords before. 

  • Bill Campbell Profile Picture
    12 on at

    You might find that you need to reset the user ID and password on the ODBC configuration window.

    Do you have an Administrator there that has the SA ( System Admin) SQL Password?

    If so, that is what we use.  If not, use your GP User ID and password.

    You can not use Window Authentication - it will fail.

  • scplimited Profile Picture
    5 on at

    I entered the SA credentials, it connected and saved, however I still get the same error message when i try to log into GP.

  • Bill Campbell Profile Picture
    12 on at

    What version of GP are you running on your client?

    What version of GP is the HOST running?

    Do you know if there is a chance there was an update done on the system and they did not do the update on your workstation?

  • scplimited Profile Picture
    5 on at

    We are pretty much remote desktop-ing into the host and running it there.  The only thing I can see is 12.00.1295 on the login window.

    It is possible that they could have updated something, but not anything related to GP itself as it's not something they would touch. They would update anything OS or SQL related though.

  • Richard Wheeler Profile Picture
    75,850 Moderator on at

    I would first try going into your DEX.INI file and set SYNCHRONIZE to try and then launch GP. You will be forwarded to GP Utilities and make sure you see the synchronize window pop up for a second. Then launch GP and see if it works. Does GP work on the server?

  • scplimited Profile Picture
    5 on at

    "There was a problem ascertaining product version information. Microsoft Dynamics GP Utilities will now exit. Please check the duinstall.log file for more information."

    duinstall.log contains (small sample):

    Failure encountered ON 7/6/2015 at 4:35:06 PM.  Error:  You are attempting to configure an older version of product 0.  Database 12.0.1745 Code 12.0.1295.

    Failure encountered ON 7/6/2015 at 4:35:06 PM.  Error:  You are attempting to configure an older version of product 346.  Database 12.0.1728 Code 12.0.1289.

    Failure encountered ON 7/6/2015 at 4:35:06 PM.  Error:  You are attempting to configure an older version of product 949.  Database 12.0.1679 Code 12.0.1289.

    and

    Failure encountered ON 7/6/2015 at 4:35:09 PM.  Error:  Product 0 does not support upgrading from version 12.0.1745.

    Failure encountered ON 7/6/2015 at 4:35:09 PM.  Error:  Product 346 does not support upgrading from version 12.0.1728.

    Failure encountered ON 7/6/2015 at 4:35:09 PM.  Error:  Product 949 does not support upgrading from version 12.0.1679.

    Failure encountered ON 7/6/2015 at 4:35:09 PM.  Error:  Product 1042 does not support upgrading from version 12.0.1603.

  • Suggested answer
    Bill Campbell Profile Picture
    12 on at

    Reading this data tells me that the database server (your company databases) and your workstation client code are not on the same version.

    When you were away is it possible that the HOST did any updates and might have forgotten to tell you?

    I can see that the Database version 12.0.1745 and the CODE 12.0.1295 are two different levels - two different Service Packs are at work here.

    Until you get the workstation that has the CODE 12.0.1295 patched with the same Service Pack as on the server, you will continue to encounter this problem.

    Does your HOST partner support your updates on the workstations in your office?

    Let me know.

  • scplimited Profile Picture
    5 on at

    *sighs* I had this in the back of my mind that this might be what the problem, but it's rather mind blowing how that would even happen.

    None of the computers in the Office run GP. We all remote desktop into the hosted GP server and run the client there. The SQL server is a separate machine. 

    However, I installed the R2 12.00.1745 service pack mid last year so we had been running on R2 for quite some time which is why the database reflects that as it should. Somehow the server we all log into got reverted back to RTM 1295... no idea how unless for some reason they reverted to an old snapshot of the VM but I don't know why they would go to one so old or even one at all. I can't think of any other reason how it would have reverted back to RTM unless it's just some glitch. 

    So I guess I need to go through and install12.00.1745 R2 on the server again...?

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans