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

Runtime Error when deploying to branch

mbjoe

We have tried to deploy Sophos using the Enterprise Console to two different branches and when doing so we get the very vague message stating: "A runtime error occurred" with the code 00000062.

All but two of the computers received these errors in the two branches (the other two received different errors).

Has anyone seen this before and if so any suggestions on how we should proceed?

:5854


This thread was automatically locked due to age.
  • 0

    Ensure that you have all the necessary services running on the remote systems and that the account you are using has the approrpiate permissions to install S/W and create a sched task. 

    Also ensure that vbscript.dll is registered on the local systems.

    Check the profile path of the account docs and settings\ACCTNAME\local settings\temp\sophos (Or in the root).....There is a log file created by the installer, just remmeber that the log file is in the profile directory of the account used to install the S/W (Account used with protection wizard if that was used) 

    See what error is in the log file. 

    Cheers

    :5856
  • 0

    I had struggled with this same error on one workstation after a recent deployment.  The workstation was Windows XP Pro w/ SP3.  I had gone through all the basics and have done quite a bit of deployments so I'm pretty familiar with all the tricks on getting a failed deployment to work.  Typically my issues would be registry permissions or services not starting.  However nothing was helping this particular case and the error that you recieved in the EC was exactly as mine.  I did look at the Sophos ES setup log file in my profile folder and saw only one other error in that file.  I can not remember the exact error but it was something about a Bootstrap error and had a 0x8000##### code to it which I can't recall, sorry.  I reset all the security on the computers file system and registry as well as local security policies and still no luck.  I called Sophos support and they walked me through installing the components manually using the MSI files.  I did this but, the updates would not work (no errors, they would just do nothing when I initiated an update)and the Sophos Antivirus Service would crash and never could start up again.  I hung up with Sophos support before noticing this so I didn't t/s further with them on that.  However while I went and did my normal cleanups on the computer I noticed that the Windows\Temp folder was completely empty.  This was very odd to me so I then looked at the environment variables and I found my problem.  For some strange reason, the TEMP and TMP system variables where set to D:\TEMP.  Well, there is no D: drive on this system.  Not even the CD/DVD ROM uses D:.  And even if it did obviously that won't work.  I modified both variables to be the defaults which is C:\WINDOWS\TEMP, rebooted, and BAM, it all started magically working.  I did initiate another push from the EC, but I think it started working even before I did this.  Anyway, hopefully this helps anyone who is having a similiar issue.  Check your environment variables!

    Louis

    :15709