Posts tagged "failed"

LiveCycle ES2: Unexpected exception. Failed to create directory: \\<cluster>\GDS

Issue

If you have configured the WebSphere node agents to start as Windows services instead of using the batch files in your cluster you may experience the following behaviour:

  • in AdminUI > Services > Applications and Services > Application Management, you may receive an ALC-DSC-033-000 error
  • in AdminUI > Services > Applications and Services > Service Management, you will see many services marked Inactive, and you cannot stop/start them

You will also notice the following errors in the SystemOut.log on the individual cluster nodes when starting the servers:

E com.adobe.idp.dsc.registry.service.impl.ServiceStoreImpl createServiceConfigurationFromBOI
    COULD NOT PROCESS SERVICE: Process Management (system)/Queue Sharing VERSION: 1.0 MARKING AS INACTIVE
E com.adobe.idp.dsc.registry.service.impl.ServiceStoreImpl createServiceConfigurationFromBOI TRAS0014I:
    The following exception was logged java.lang.ClassNotFoundException: server.startup : 1Class name
    com.adobe.idp.workflow.dsc.descriptor.WorkflowDSCDescriptor from package com.adobe.idp.workflow.dsc.descriptor not found.
....
W com.adobe.idp.dsc.registry.service.impl.ServiceRegistryImpl getHeadActiveConfiguration
    Head active ServiceConfiguration for service: Process Management (system)/Queue Sharing version: 1.0 is not active as expected.
    The service was probably Marked INACTIVE due to an error loading the service.  Please look at the logs to see if this service was Marked INACTIVE.
...

The SystemOut.log will also contain the following error:

E com.adobe.idp.DocumentFileBackend getTimeSkewDelta DOCS001: Unexpected exception. Failed to create directory: \\es2cluster\GDS.
E com.adobe.idp.Document passivate DOCS001: Unexpected exception. While re-passivating a document for inline data resizing..
E com.adobe.idp.Document passivate TRAS0014I: The following exception was logged com.adobe.idp.DocumentError:
Failed to create directory: \\es2cluster\GDS
    at com.adobe.idp.DocumentFileBackend.getTimeSkewDelta(DocumentFileBackend.java:113)
    at com.adobe.idp.DocumentFileBackend.<init>(DocumentFileBackend.java:86)
    at com.adobe.idp.Document.getGlobalBackend(Document.java:3153)
    at com.adobe.idp.Document.writeToGlobalBackend(Document.java:2977)
    at com.adobe.idp.Document.doInputStream(Document.java:1698)
    at com.adobe.idp.Document.passivateInitData(Document.java:1457)
    at com.adobe.idp.Document.passivate(Document.java:1235)
    at com.adobe.idp.Document.passivateGlobally(Document.java:1205)
    at com.adobe.idp.dsc.management.impl.ArchiveStoreImpl.createNewArchive(ArchiveStoreImpl.java:636)
    at com.adobe.idp.dsc.management.impl.ArchiveStoreImpl._getArchive(ArchiveStoreImpl.java:438)

Reason

The Windows services that you have created do not have the correct privileges for accessing the LiveCycle GDS directory which is required for the proper operation of the LiveCycle server.

Solution

Open the Services view from the Control Panel in Windows.
Select the WAS NodeAgent service and goto properties > LogOn > Log on as > This account.
Browse for an Administrator account with sufficient privileges to access the GDS share.
Restart the NodeAgent.
Then restart the cluster from the WAS ND admin console.

Additional Information

To create the nodeagent as a Windows service instead of using the batch files:

1. Change to the \bin directory where WebSphere is installed, for example:

C:\Program Files\IBM\WebSphere\AppServer\bin

2. Run the following command:

wasservice -add ctgNode01_nodeagent
          -servername nodeagent
          -profilePath “C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01″
          -wasHome “C:\Program Files\IBM\WebSphere\AppServer”
          -logFile “C:\Program Files\IBM\WebSphere\AppServer\profiles\ctgAppSrv01\logs\nodeagent\startNode.log”
          -logRoot “C:\Program Files\IBM\WebSphere\AppServer\ctgAppSrv01\logs\nodeagent”
          -restart true
          -startType automatic

You can do this for each cluster node.  Now when you restart Windows, the nodeagent on each cluster node will start automatically.

reference: (1911394)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 9.0/10 (1 vote cast)

LiveCycle ES: ALC-TTN-011-031: Bootstrapping failed for platform component [DocumentServiceContainer] | clustered environments

Issue

 If you are attempting a clustered installation of LiveCycle ES, you may experience errors during the bootstrapping phase of LiveCycle Configuration Manager (LCM) with the following exception in the LCM log:

[5/25/11 8:09:12:768 EDT] 0000003f DSCBootstrapp E com.adobe.livecycle.bootstrap.bootstrappers.AbstractBoostrapper log ALC-TTN-011-031: 
Bootstrapping failed for platform component [DocumentServiceContainer]. The wrapped exception's message reads: See nested exception; nested exception is: 
java.lang.Exception: java.lang.NoClassDefFoundError: com.adobe.livecycle.cache.adapter.GemfireCacheAdapter (initialization failure)

[5/25/11 8:09:12:768 EDT] 0000003f DSCBootstrapp E com.adobe.livecycle.bootstrap.bootstrappers.AbstractBoostrapper log TRAS0014I: 
The following exception was logged com.adobe.livecycle.bootstrap.BootstrapException: ALC-TTN-011-031: 
Bootstrapping failed for platform component [DocumentServiceContainer]. The wrapped exception's message reads: See nested exception; nested exception is: 
java.lang.Exception: java.lang.NoClassDefFoundError: com.adobe.livecycle.cache.adapter.GemfireCacheAdapter (initialization failure)
 at com.adobe.livecycle.bootstrap.bootstrappers.DSCBootstrapper.bootstrap(DSCBootstrapper.java:73)
 at com.adobe.livecycle.bootstrap.framework.ManualBootstrapInvoker.invoke(ManualBootstrapInvoker.java:78)
 at com.adobe.livecycle.bootstrap.framework.BootstrapServlet.doGet(BootstrapServlet.java:156)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)

LCM may also display error message dialogs such as the following:

Reason

In a clustered environment, the cluster caching must be configured correctly and working before the database initialization can complete successfully.

Solution

The cluster caching should be configured using one of the options below, depending on whether you are using UDP or TCP caching:
A) UDP caching uses the following Java argument to set a port number: -Dadobe.cache.multicast-port=<port number>
The multicast port must be unique to the LiveCycle ES cluster (that is, the port must not be used by any other cluster on the same network). It is recommended that you configure the same <port number> on all nodes in the LiveCycle ES cluster.

B) TCP caching uses the following Java argument: -Dadobe.cache.cluster-locators=<IPaddress>[<port number>],<IPaddress><port number>]
Configure, as a comma-separated list, the locators for all nodes of the cluster. The value for <IPaddress> is the IP address of the computer running the locator, and the value for <portnumber> is any unused port between 1 and 65535 (the port must not be used by any other cluster on the same network). It is recommended that you configure the same <port number> for all locators.

Troubleshooting

Here are some further troubleshooting tips for LCM errors related to the DB initialization step:

  • ensure the DB privileges for the DB user match what is specified in the installation documentation
  • ensure sure the user that is starting the application server has R/W access to the GDS and LC TEMP directories (Bootstrap will fail if the permissions are incorrect)
  • it may be necessary to drop the DB and re-create it if there was an error the first time
  • if using WebSphere, test the DB connection from the WAS admin console
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 9.0/10 (1 vote cast)