(imported comment written by gsmith91)
Hello,
I am having a similar issue with the service not starting but replacing the ActionSite.afxm file did not resolve my issue. Here is the details of the error below. Anyone have other ideas of what could cause this issue?
System Event Log:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 9/3/2009
Time: 6:22:38 PM
User: N/A
Computer: 17POS38
Description:
The BES Client service terminated with service-specific error 24.
Application Event Log (remote):
Event Type: Error
Event Source: BESClient
Event Category: None
Event ID: 24
Date: 9/3/2009
Time: 6:22:38 PM
User: NT AUTHORITY\SYSTEM
Computer: 17POS38
Description:
The description for Event ID ( 24 ) in Source ( BESClient ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Failed loading action site.
Today’s error log:
September 3, 2009
At 15:03:13 -0400 -
Starting client version 7.2.4.60
At 15:03:14 -0400 -
FIPS mode disabled by default.
At 15:03:18 -0400 -
Client shutdown (Failed loading action site)
At 15:24:11 -0400 -
Starting client version 7.2.4.60
At 15:24:12 -0400 -
FIPS mode disabled by default.
At 15:24:14 -0400 -
Client shutdown (Failed loading action site)
At 15:46:02 -0400 -
Starting client version 7.2.4.60
At 15:46:03 -0400 -
FIPS mode disabled by default.
At 15:46:04 -0400 -
Client shutdown (Failed loading action site)
At 19:20:25 -0400 -
Starting client version 7.2.4.60
At 19:20:26 -0400 -
FIPS mode disabled by default.
At 19:20:27 -0400 -
Client shutdown (Failed loading action site)
At 19:22:36 -0400 -
Starting client version 7.2.4.60
At 19:22:37 -0400 -
FIPS mode disabled by default.
At 19:22:38 -0400 -
Client shutdown (Failed loading action site)
Thanks!!