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

Error installing SEC 4.7 on 2008 R2

Hey Everyone-

  I am setting up a new domain and have a couple new Windows 2008 R2 servers.  I have a dedicated SQL 2008 R2 server as well.  I ran the installation for the SEC DB on the SQL server and that went fine.  Ive moved on to the SEC Server (different system) and try to install the Management Console and Server there.  When I run through the install it eventually errors out after entering the Update Manager user credentials.  The error states "Server not found. Verify that the specified server exists".  Thats it..nothing the windows logs either.  Im not sure which server it means...the local system, DC or SQL server.  Also not sure if the update manager user creds are causing it either.  Ive tried multiple accounts and types during the installation and nothing seems to work.

  I have TCP/IP enabled on the SQL server and its listening fine.  The DCs seem okay...I can browse the directory with other applications.  I turned off the firewalls on all of the related servers and it still errors out.  I also tried enabling Network Discovery on all of the server as stated in Sophos KB Article 64869 but that has not helped either.

  Id appreciate any help anybody can throw my way.  I have a ticket open with Sophos, but no resolution yet.

Thanks!

:12325


This thread was automatically locked due to age.
Parents
  • After more testing, I found out that if I enter a current user information for the update manager user that it went though.  But, it failed with another error.  I dug into it more and found that I have some servers with duplicate SIDs.  These are all newly installed systems so its not a big deal to wipe them out and re-deploy.  Ill be able to see if that took care of my problem later today, hopefully.

    :12361
Reply
  • After more testing, I found out that if I enter a current user information for the update manager user that it went though.  But, it failed with another error.  I dug into it more and found that I have some servers with duplicate SIDs.  These are all newly installed systems so its not a big deal to wipe them out and re-deploy.  Ill be able to see if that took care of my problem later today, hopefully.

    :12361
Children
No Data