x Want to participate? Join the group to interact
  • State Verified Answer
  • +2 person also asked this people also asked this
  • Replies 10 replies
  • Subscribers 18 subscribers
  • Views 3711 views
  • Users 0 members are here
Browse Forums
Announcements
105
topics
4
replies
General Discussion
1k
topics
2k
replies
Paul Daly

Sage 200 Upgrade - User must be member of Admins group

SOLVED
Posted By

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

Parents
  • 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?

Reply
  • 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?

Children
  • 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....

*Community Hub is the new name for Sage City