Manually Uninstalling a DSC

I can't condone manually tweaking the LiveCycle database, so I strongly encourage you to deal with Adobe Support if you ever run into a situation like this.

That being said, on a number of occasions a DSC wouldn't uninstall properly for me and thus I'm faced with the following error when trying to stop/uninstall it from Workbench or by using an Ant script:

2011-11-29 10:41:37,818 ERROR [org.jboss.ejb.plugins.LogInterceptor] RuntimeException in method: public abstract java.lang.Object com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionBMTAdapterLocal.doBMT(com.adobe.idp.dsc.transaction.TransactionCallback) throws com.adobe.idp.dsc.DSCException: java.lang.IllegalStateException: Service: YourCustomService version: 0.0 must be in a running state prior to stopping at com.adobe.idp.dsc.registry.service.impl.ServiceRegistryImpl.stop ServiceRegistryImpl.java:2003)

These are the sql scripts that will allow you to manually fix the state so that it can be uninstalled:

-- Get info about the service in question
select * from adobe.tb_sc_service where id = 'YourCustomService'
-- Chances are it's in a state of 2.
select * from adobe.tb_sc_service_configuration where service_uuid = (select uuid from adobe.tb_sc_service where id = 'YourCustomService')
-- Update the state to 0
update adobe.tb_sc_service_configuration set state = 0 where service_uuid = (select uuid from adobe.tb_sc_service where id = 'YourCustomService')

You should now be able to uninstall the dsc in Workbench.

Custom datatypes in LiveCycle processes

If you're trying to use custom datatypes from your dsc in the LiveCycle executeScript activity in workbench, you may run into the following error:

ERROR [com.adobe.workflow.AWS] Sourced file: inline evaluation of: ``import some.package.SomeClass; SomeClass pdfg = new SomeClass . . . '' : Typed variable declaration : Class: SomeClass not found in namespace : at Line: 2 : in file: inline evaluation of: ``import some.package.SomeClass; SomeClass pdfg = new SomeClass . . . '' : SomeClass

To resolve it, you not only need to have your class in the DataTypes section of your component.xml, but you also need to have that package defined in the Export Packages of your RunTime section of your component.xml.

Connecting with the Gateway

If you're working with Adobe Managed Services and try to connect via Workbench using the Adobe LiveCycle Gateway, there's a chance that port 8443 will be in use and prevent you from connecting.  If that's the case and you're running IIS, you'll have to remove it's binding to 8443.  I should add that many other services could use this port such as Apache, JBoss, etc, but if you're on a Windows 7 box it's a likely culprit.

This can be done by opening Computer Management under Administrative Tools, expanding Services and Applications, clicking on Internet Information Services, clicking on Sites, then inspect which of your sites are binding to 8443 and remove them manually (Bindings under Edit Site when the site is selected).