Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 14 replies
  • Subscribers 1 subscriber
  • Views 22289 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

New setup - cant deploy to users - installation could not be started

dalboy

Hi guys

OK i have installed

Enterprise Console 5 on a server 2008 machine.

I had problems with the database at first and it wouldnt load the interface.  Followed steps online and after lots of messing around I managed to load the console succesfully.

I have managed to protect the server it is already on OK

However, this is a new domain with new antivirus - I can see the 1st workstation i have setup when I do a scan via active directory.  But when I try to protect the computer after a while I get:

Installation could not be started 0x0000002e

Ive done the usual google searches and cant get it to work.

The workstation I am trying to protect is windows 7 64bit.

I have tried to follow the below:

http://www.sophos.com/en-us/support/knowledgebase/111180.aspx

I think I have done it correctly 

Firewall rules and services seem to be correct.

Are there any tests I can do to see what I have missed?

when i do protect computer the administrator password is accepted but then at the end i get the error

Can it be to do with a problem connecting to the database still? If i right click the problem computer in sophos to view computer details i get the error "cannot open database sophos51.  Login failed for user sophosm (which is what the account is in active directory)

Any help appreciated, I did try to follow the setup steps but what they dont seem to match with what I have on screen

thanks!

:27283


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

    Hello dalboy,

    if you can't reset the server ('cause it's not virtual or you don't have an appropriate snapshot) you can remove all components using Programs and Features (start with the AutoUpdate endpoint component), postpone any reboot requests until the last component has been removed. Note that the SQL instance will be kept as well as the databases themselves (so you might want to drop these).

    After reboot run the installer. Might seem tedious but carefully note the steps you've taken (and any problems met) as this information might be adjuvant if you encounter an error(which will hopefully not be the case).

    Christian

    :27325
Reply
  • 0

    Hello dalboy,

    if you can't reset the server ('cause it's not virtual or you don't have an appropriate snapshot) you can remove all components using Programs and Features (start with the AutoUpdate endpoint component), postpone any reboot requests until the last component has been removed. Note that the SQL instance will be kept as well as the databases themselves (so you might want to drop these).

    After reboot run the installer. Might seem tedious but carefully note the steps you've taken (and any problems met) as this information might be adjuvant if you encounter an error(which will hopefully not be the case).

    Christian

    :27325
Children
No Data