Windows 2003 SCW + Win 2K3 R2 SP2 + Trend ServerProtect

  • Thread starter Thread starter trusty
  • Start date Start date
T

trusty

After configuring a policy in SCW and applying to a DC, the Trend
ServerProtect service fails to start upon boot up. The error info is as
follows:

Source: Service Control Manager
Event ID: 7024
Description: The Trend ServerProtect service terminated with
service-specific error 258 (0x102).

The serive is still set to automatic start but it is not running if you
manually start the service it will start and run normally. Setting the
Recovery options to restart the service has no affect. If you rollback the
SCW policy and reset all changed services back to their original states and
bounce the server, it will start normally. We have followed the Trend
Solution ID 1028537, but this has not fixed the issue. We are using Trend
ServerProtect v5.58 incase that matters. Thanks for any help you can
provide.
 
For anyone who cares, our solution was to migrate to Trend Officescan v8. We
removed the Trend Serverprotect client, rebooted and pushed the Officescan 8
client to the server. After applying the SCW policy to this server, it no
longer was causing issues with Trend AV we now have DCOM errors after
applying the policy, but that's a whole other conversation and help thread.

"trusty" wrote:

> After configuring a policy in SCW and applying to a DC, the Trend
> ServerProtect service fails to start upon boot up. The error info is as
> follows:
>
> Source: Service Control Manager
> Event ID: 7024
> Description: The Trend ServerProtect service terminated with
> service-specific error 258 (0x102).
>
> The serive is still set to automatic start but it is not running if you
> manually start the service it will start and run normally. Setting the
> Recovery options to restart the service has no affect. If you rollback the
> SCW policy and reset all changed services back to their original states and
> bounce the server, it will start normally. We have followed the Trend
> Solution ID 1028537, but this has not fixed the issue. We are using Trend
> ServerProtect v5.58 incase that matters. Thanks for any help you can
> provide.
 
Back
Top