If you notice that your Adam X.X.0.0 Service is not starting or is starting
and stopping immediately, then there are typically only a few problems that can
cause this. This blog entry describes the ones we've encountered so far in support.
Error 1
Could not start the Adam 4.4.0.0 Service service on Local Computer.
The application has failed to start because the application configuration is incorrect.
Reinstalling this application may fix the problem.- The Adam.Core.server.exe.config file does not have a correct XML-structure.
The simplest way to detect this is by adding an .xml-extension to this file and
by opening this XML-file then in Internet Explorer. Many XML-related errors would
be reported there.
Error 2
The Adam 4.4.0.0 Service on Local Computer started and then stopped. Some services
stop automatically if they have no work to do, for example, the Performance Logs
and Alerts service.
The Adam service is attempting to use a TCP/IP-port which is already in use. Either
stop the other application that is using the TCP/IP-port (on a development laptop,
this could be applications like Outlook or Skype because they sometimes use random
ports). Or configure the Adam Service to use a different TCP/IP-port. Do this by
adding a port-attribute to the Adam.Core.Server-element of Adam.Core.Server.exe.config:
| XML |
1
2
3
|
<configuration>
<Adam.Core.Server port="1835">
...
|
- The Adam.Core.Server.exe.config contains invalid values for certain configuration
elements. For example, the following error could cause this problem:
| XML |
1
2
3
|
<configuration>
<Adam.Core.Server port="wrongvalue">
...
|
To fix this problem, make sure that all configuration properties have correct values.
- The Adam installation is corrupt. Double click on the MSI-file used to perform
the Adam installation and choose Repair.
- The Adam.Core.server.exe.config file contains bindings that point to an
incorrect Adam version. We strongly encourage you to remove all bindings from this
file as they are never necessary. These bindings could look like this:
| XML |
1
2
3
4
5
6
7
8
9
10
11
|
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<qualifyAssembly partialName="Adam.Web" fullName="Adam.Web, Version=4.3.0.0, Culture=neutral, PublicKeyToken=63f11f167f68d05b" />
<qualifyAssembly partialName="Adam.Web.Core" fullName="Adam.Web.Core, Version=4.3.0.0, Culture=neutral, PublicKeyToken=63f11f167f68d05b" />
<qualifyAssembly partialName="Adam.Web.StudioControls" fullName="Adam.Web.StudioControls, Version=4.3.0.0, Culture=neutral, PublicKeyToken=63f11f167f68d05b" />
<qualifyAssembly partialName="Adam.Core" fullName="Adam.Core, Version=4.3.0.0, Culture=neutral, PublicKeyToken=63f11f167f68d05b" />
<qualifyAssembly partialName="Adam.Tools" fullName="Adam.Tools, Version=4.3.0.0, Culture=neutral, PublicKeyToken=63f11f167f68d05b" />
</assemblyBinding>
</runtime>
...
|
To fix this, simply remove the entire assemblyBinding-tag.
Error 3
Could not start the Adam 4.4.0.0 Service service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely
fashion.- The Adam Server service needs to have an internet connection to verify its Authenticode
Signatures. Either make sure that this server can access the Internet or add the
following entry to the configuration file:
| XML |
1
2
3
4
5
6
7
8
9
|
<configuration>
<runtime>
<!-- This element has been added to ensure that the Adam Server service is able to start
on server without an internet connection. Without this line, Windows would attempt
to contact Verisign to verify the Authenticode Signature which would eventually time
out and prevent the server from starting. -->
<generatePublisherEvidence enabled="false" />
</runtime>
</configuration>
|
- The Adam installation is corrupt. Double click on the MSI-file used to perform
the Adam installation and choose Repair.