Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 5 subscribers
  • Views 5972 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

User/name incorrect when accessing to Safeguard.

PeterRL

Hi all,


Weird issue happening on a new installation of the safeguard 7.01. over a new Server 2012 R2 using SQL express 2012.


After creating some group policies and installing some safeguard clients, for some reason, and making some tests with success, suddently when trying to access to the Safeguard managment console is not possible since the system states that the username/password are incorret. No change was made so this cannot be. 

Also when selecting the option to sync on the Safeguard client, returns the message that that the server cannot be contacted.

All services are up and running (even the SQL ones). Eventviewer does show any problems. I´m completely lost over here. Can someone bring some light please?



This thread was automatically locked due to age.
Parents
  • FormerMember
    0 FormerMember

    Hi Peter,

    If this occurred after creating those Group Policies are you sure they aren't to blame?

    The Certificate Store Password (that you enter for the MSO) is unique to the Windows profile, make sure you're accessing the Management Centre from the Windows profile it was installed under, and not via Remote Desktop either.

    If the server can't be contacted try running an invoke test on the server. Go to IIS > Click on the SGNSRV site > Browse on Port 80 > CheckConnection > Invoke > Does the WebService string come back as OK and does DBAuth report back fine?

    If you start getting issues here check IIS > Application Pool > SGNSRV-Pool. If that has stopped please start the service.
    Under that same SGNSRV-Pool can you check the Identity please, just make sure the user is a domain admin (typically it'll be called SGNSQL)
    Can you now go into SQL Server Management Studio and check the permissions for the user that's been set in Identity of SGNSRV-Pool.
    Please make sure they have permissions to access the SafeGuard database with db_datareader and db_datawriter permissions.
    Make sure the above account is member of the IIS_WPG Windows security group.

    If the above doesn't resolve the issue please follow through the guide below:
     
    Article ID: 109662
    Title: Analyzing client-server communication issues in SafeGuard Enterprise
Reply
  • FormerMember
    0 FormerMember

    Hi Peter,

    If this occurred after creating those Group Policies are you sure they aren't to blame?

    The Certificate Store Password (that you enter for the MSO) is unique to the Windows profile, make sure you're accessing the Management Centre from the Windows profile it was installed under, and not via Remote Desktop either.

    If the server can't be contacted try running an invoke test on the server. Go to IIS > Click on the SGNSRV site > Browse on Port 80 > CheckConnection > Invoke > Does the WebService string come back as OK and does DBAuth report back fine?

    If you start getting issues here check IIS > Application Pool > SGNSRV-Pool. If that has stopped please start the service.
    Under that same SGNSRV-Pool can you check the Identity please, just make sure the user is a domain admin (typically it'll be called SGNSQL)
    Can you now go into SQL Server Management Studio and check the permissions for the user that's been set in Identity of SGNSRV-Pool.
    Please make sure they have permissions to access the SafeGuard database with db_datareader and db_datawriter permissions.
    Make sure the above account is member of the IIS_WPG Windows security group.

    If the above doesn't resolve the issue please follow through the guide below:
     
    Article ID: 109662
    Title: Analyzing client-server communication issues in SafeGuard Enterprise
Children
  • 0 in reply to FormerMember

    Hi Toby,


    fortunatelly, i was able to reinstall (we were at the the first stage of the deployment). Reinstalling has "solve it". I did not made additional testing  However, this is a great article - i will keep if for future reference.


    However,:

    "If the server can't be contacted try running an invoke test on the server. Go to IIS > Click on the SGNSRV site > Browse on Port 80 > CheckConnection > Invoke > Does the WebService string come back as OK and does DBAuth report back fine?"

    The invoke test was successfull. However the server keep telling me that the password was incorrect.

Unfiltered HTML