Sage 200 Upgrade - User must be member of Admins group

SOLVED

Evening Folks

( you might be able to help me on this one hopefully)

Bit of an oddball one haven't come across it before, running a Sage 200 upgrade and at the point of entering the credentials for the Sage Service accounts I'm getting the message below: 

The strange thing is the account definitely exists in the Sage200Admins group because the existing install still works..

I've even gone to the stage of creating new service accounts and it still doesn't work.

But, the account I use to access the server is also a member of that Sage200Admins Group and if I enter those account details it accepts them Thinking

Anyone any ideas?

Thanks,
Paul

  • 0

    Nothing specific I can think of Paul.  The times I had that error relate to it happening all of the time due to the Pre-Windows 2000 name not matching.  There isnt 2 Sage200Admin groups is there? Like Sage200Admins and Sage200Admin or something?  Is the user in both the Users and Admins group, which is why the current system works?

  • 0 in reply to GaryButler

    cheers Gary

    No there is only the 1 group, its only a small version jump too.
    The site is currently on Sage 200c Spring 2019 (v12.00.0031) and I'm simply bringing them up to latest 2020R2 release (v12.00.00.41) so no a big jump so service account setup would be same.


    I carrying out the upgrade as the databases are going onto SQL 2019 where support was only introduced for recently.


    So this is very strange altogether,
    I'm holding off performing a full uninstall and reinstall in case I can't get it working with the Service accounts again....

  • 0

    Hi,

    There is a tool somewhere on the sage downloads called ADBrowser that looks at active directory, and can highlight an issue if the DC's are unavailable or misconfigured.  This can typically happen when a dc has been retired but not removed from Active Directory properly.

  • 0 in reply to Toby

    Thats the one Toby, i couldn't remember the name of it 
    I had to use it years ago when the Windows Auth was introduced when multiple domains were in play on a site.

    i'll give it a go

    cheers

  • 0

    Thanks & Toby

    Have been through everything and ruled everything out and still no joy

    - No duplicate or dormant domains on the DC
    - The DC is not set as read-only
    - The AdBrowser returned a clean report no errors and no issues with configuration
    - No Duplicate Sage Groups
    - Sage200Services account is only in the Sage200Admins group

    Confused confused.com

    I have my own admin account that is used on the server and is also a member of the Sage200Admins and I can get by the above screen with that account but can't really be used

    Cheers
    Paul

  • 0 in reply to Paul Daly

    If you create a new user does it work?

  • 0 in reply to GaryButler

    No, I had a new user called "Sage200Services2" added into Sage200Admins group and it still wasn't able to get passed that authentication screen

  • 0 in reply to Paul Daly

    Did you ever get to the bottom of this, 

    I can't seem to find a solution on this and it is happening on multiple installs, weirdly it doesn't happen all the time, This may be a red herring but if you use ADBrowser and look at the member of attribute is it empty, i seem to be running across users i have created with this attribute being empty.

    I am in the process of testing it and it thats the case i will let ya know

  • +1
    verified answer

    Good morning. We're reviewing posts that have not been marked as answered. Apologies for the delay in updating this one.

    The message received during installation usually means that it hasn't been possible to determine whether the Windows user entered as the Sage 200 services account is part of the Sage 200 Admins group, despite you visibly being able to see it is in Active Directory.

    The cause is normally down to the Windows permissions of those service accounts where they don't have sufficient rights to interrogate Active Directory. However there could other possibilities where, for example, using the ADBrowser utility previously discussed need to be used.
     
    With regards to this type of message, as Business Partners, you can contact the Sage 200 support team and we have an 'Installation Helper' tool we can use to assist you with finding the potential cause of the problem.

    Many thanks.

    Chris

  • 0 in reply to Chris Chapman

    Half the issue here is that no one can tell us exactly what checks are being done with the installer.

    One fix I have come up with that works 90% of the time is switching the users primary group to be the sage admins group.


    Would be nice to know how the look up is being done by the installer as I have had the issue where AD Browser sees the users and correctly reports the group but the sage installer refuses to continue as it reports the user not being in the correct group (which it is).

    when we contact sage support we would get a response of "put user in the correct group" and then when pressing for how this installer lookup is done or what logic it uses we get a revert to you need to setup a supported environment.

    I seem to think the fact the memberof attribute in Active Directory is a computed back-link attribute could be causing some issues but I can't be sure.

    We deploy to pretty standard setups and we run into this issues intermittently but it's really frustrating to fix

    Just my two cents