Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
sulatna Absent Member.
Absent Member.
4887 views

VIBE wont start after Upgrade to VIBE4

Hello,

I tried to upgrad our VIBE 3.4 to new Verson 4 how it is explained in documentation.

If I try to start VIBE now I get the following error in catalina.out:

Apr 23, 2015 12:24:08 PM org.apache.catalina.core.StandardService initInternal
SEVERE: Failed to initialize connector [Connector[HTTP/1.1-8443]]
org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-8443]]
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
at org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:821)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
at java.lang.reflect.Method.invoke(Method.java:620)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:280)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:454)
Caused by: java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.initialize(J9VMInternals.java:257)
at javax.crypto.KeyAgreement.getInstance(Unknown Source)
at com.ibm.jsse2.L.h(L.java:53)
at com.ibm.jsse2.L.a(L.java:206)
at com.ibm.jsse2.l$c.a(l$c.java:6)
at com.ibm.jsse2.l.a(l.java:90)
at com.ibm.jsse2.m.a(m.java:2)
at com.ibm.jsse2.m.g(m.java:123)
at com.ibm.jsse2.SSLServerSocketFactoryImpl.getSupportedCipherSuites(SSLServerSocketFactoryImpl.java:11)
at org.apache.tomcat.util.net.jsse.JSSESocketFactory.<clinit>(JSSESocketFactory.java:114)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:235)
at org.apache.tomcat.util.net.jsse.JSSEImplementation.getServerSocketFactory(JSSEImplementation.java:47)
at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:388)
at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:646)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:434)
at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)
at org.apache.catalina.connector.Connector.initInternal(Connector.java:978)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
... 12 more
Caused by: java.lang.SecurityException: Cannot set up certs for trusted CAs
at javax.crypto.b.<clinit>(Unknown Source)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:235)
... 30 more
Caused by: java.lang.SecurityException: Cannot locate policy or framework files!
at javax.crypto.b.c(Unknown Source)
at javax.crypto.b.access$600(Unknown Source)
at javax.crypto.b$0.run(Unknown Source)
at java.security.AccessController.doPrivileged(AccessController.java:341)
... 33 more


Java: 1.7 from IBM ink. JCE
Keystore worked in 3.4 before.

Has anybody an idea how I could solve this problem?

Thanks,

Michael
0 Likes
10 Replies
Knowledge Partner
Knowledge Partner

Re: VIBE wont start after Upgrade to VIBE4

Hi Michael,

What does the appserver.log say?

Cheers,
Willem
0 Likes
sulatna Absent Member.
Absent Member.

Re: VIBE wont start after Upgrade to VIBE4

Hello Willem,

appserver.log:

015-04-23 14:25:03,680 ERROR [localhost-startStop-1] [org.springframework.web.context.ContextLoader] - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sPropsUtil' defined in ServletContext resource [/WEB-INF/context/applicationContext.xml]: Cannot create inner bean 'org.kablink.teaming.util.encrypt.EncryptedClassPathConfigFiles#862127bd' of type [org.kablink.teaming.util.encrypt.EncryptedClassPathConfigFiles] while setting bean property 'config'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.kablink.teaming.util.encrypt.EncryptedClassPathConfigFiles#862127bd' defined in ServletContext resource [/WEB-INF/context/applicationContext.xml]: Invocation of init method failed; nested exception is org.jasypt.exceptions.EncryptionInitializationException: java.lang.NoClassDefFoundError: javax.crypto.b (initialization failure)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:287)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:122)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1417)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1158)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:296)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:293)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:286)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:615)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479)
at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:410)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:306)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:112)
at org.kablink.teaming.spring.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:55)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4992)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5490)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:672)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1862)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:483)
at java.util.concurrent.FutureTask.run(FutureTask.java:274)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
at java.lang.Thread.run(Thread.java:801)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.kablink.teaming.util.encrypt.EncryptedClassPathConfigFiles#862127bd' defined in ServletContext resource [/WEB-INF/context/applicationContext.xml]: Invocation of init method failed; nested exception is org.jasypt.exceptions.EncryptionInitializationException: java.lang.NoClassDefFoundError: javax.crypto.b (initialization failure)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1512)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:521)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:276)
... 31 more
Caused by: org.jasypt.exceptions.EncryptionInitializationException: java.lang.NoClassDefFoundError: javax.crypto.b (initialization failure)
at org.jasypt.encryption.pbe.StandardPBEByteEncryptor.initialize(StandardPBEByteEncryptor.java:638)
at org.jasypt.encryption.pbe.StandardPBEStringEncryptor.initialize(StandardPBEStringEncryptor.java:532)
at org.jasypt.encryption.pbe.StandardPBEStringEncryptor.encrypt(StandardPBEStringEncryptor.java:585)
at org.kablink.util.encrypt.ExtendedPBEStringEncryptor.encrypt(ExtendedPBEStringEncryptor.java:105)
at org.kablink.teaming.util.encrypt.EncryptedClassPathConfigFiles.afterPropertiesSet(EncryptedClassPathConfigFiles.java:169)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1571)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1509)
... 34 more
Caused by: java.lang.NoClassDefFoundError: javax.crypto.b (initialization failure)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:175)
at javax.crypto.SecretKeyFactory.getInstance(Unknown Source)
at org.jasypt.encryption.pbe.StandardPBEByteEncryptor.initialize(StandardPBEByteEncryptor.java:597)
... 40 more
Caused by: java.lang.SecurityException: Cannot set up certs for trusted CAs
at javax.crypto.b.<clinit>(Unknown Source)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:235)
at javax.crypto.KeyAgreement.getInstance(Unknown Source)
at com.ibm.jsse2.L.h(L.java:53)
at com.ibm.jsse2.L.a(L.java:206)
at com.ibm.jsse2.l$c.a(l$c.java:6)
at com.ibm.jsse2.l.a(l.java:90)
at com.ibm.jsse2.m.a(m.java:2)
at com.ibm.jsse2.m.g(m.java:123)
at com.ibm.jsse2.SSLServerSocketFactoryImpl.getSupportedCipherSuites(SSLServerSocketFactoryImpl.java:11)
at org.apache.tomcat.util.net.jsse.JSSESocketFactory.<clinit>(JSSESocketFactory.java:114)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:235)
at org.apache.tomcat.util.net.jsse.JSSEImplementation.getServerSocketFactory(JSSEImplementation.java:47)
at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:388)
at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:646)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:434)
at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)
at org.apache.catalina.connector.Connector.initInternal(Connector.java:978)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:821)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
at java.lang.reflect.Method.invoke(Method.java:620)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:280)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:454)
Caused by: java.lang.SecurityException: Cannot locate policy or framework files!
at javax.crypto.b.c(Unknown Source)
at javax.crypto.b.access$600(Unknown Source)
at javax.crypto.b$0.run(Unknown Source)
at java.security.AccessController.doPrivileged(AccessController.java:341)
... 33 more
2015-04-23 14:25:03,690 ERROR [localhost-startStop-1] [org.kablink.teaming.web.servlet.listener.ContextListenerPostSpring] - Error during startup
java.lang.NullPointerException
at org.kablink.teaming.util.SpringContextUtil.getBean(SpringContextUtil.java:117)
at org.kablink.teaming.web.servlet.listener.ContextListenerPostSpring.getZoneModule(ContextListenerPostSpring.java:145)
at org.kablink.teaming.web.servlet.listener.ContextListenerPostSpring.initZones(ContextListenerPostSpring.java:137)
at org.kablink.teaming.web.servlet.listener.ContextListenerPostSpring.contextInitialized(ContextListenerPostSpring.java:62)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4992)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5490)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:672)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1862)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:483)
at java.util.concurrent.FutureTask.run(FutureTask.java:274)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1157)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:627)
at java.lang.Thread.run(Thread.java:801)


Michael
0 Likes
Knowledge Partner
Knowledge Partner

Re: VIBE wont start after Upgrade to VIBE4

sulatna;2392014 wrote:
Cannot create inner bean 'org.kablink.teaming.util.encrypt.EncryptedClassPa thConfigFiles#862127bd' of type [org.kablink.teaming.util.encrypt.EncryptedClassPat hConfigFiles] while setting bean property 'config'; nested exception is
.....
Invocation of init method failed; nested exception is org.jasypt.exceptions.EncryptionInitializationExce ption: java.lang.NoClassDefFoundError: javax.crypto.b (initialization failure)


That bit makes me think this is related to the JCE extension that is missing or incorrect. The errors I've seen due to that are different though.

I'm not familiar with IBM Java and the JCE extension. From what I've read it seems to be a less straight forward process to correctly add the JCE extension... but I don't have experience with that (using Oracle Java JDK 1.8 here).

Do you also have some more detail on the hosting server? (which OS, patchlevel, etc).

Cheers,
Willem
0 Likes
foccer Absent Member.
Absent Member.

Re: VIBE wont start after Upgrade to VIBE4

Hi Michael

I had a similar issue, mine was solved using Novell support. Mine was caused by the Vibe installer rewriting the zone encryption keys for my site as if it was new, meaning every action was denied by Vibe's security layer until I was able to input my encryption key from my Vibe 3.4 instance to fix it.

To see if you have the same problem as me -
on your Vibe 3.4 instance (or backup files): look at /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/classes/config/ssf.properties, copy the value for kablink.encryption.key
on Vibe 4: look at /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/classes/config/ssf-ext.properties, and for values kablink.encryption.key and kablink.encryption.key.initial, they should both match your previous Vibe 3.4 key (mine didn't)
(and you might also possibly need to edit /var/opt/novell/teaming/conf/sec.properties in the same way)

I had to edit both of these and re-run the installer for my site to work. I'm not sure if you need to re-run the installer though, try restarting teaming before doing that bit.

hope that helps you


Aaron.

sulatna;2391886 wrote:
Hello,

I tried to upgrad our VIBE 3.4 to new Verson 4 how it is explained in documentation.

If I try to start VIBE now I get the following error in catalina.out:

Apr 23, 2015 12:24:08 PM org.apache.catalina.core.StandardService initInternal
SEVERE: Failed to initialize connector [Connector[HTTP/1.1-8443]]
org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-8443]]
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
at org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:821)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
at org.apache.catalina.startup.Catalina.load(Catalina.java:638)
at org.apache.catalina.startup.Catalina.load(Catalina.java:663)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56)
at java.lang.reflect.Method.invoke(Method.java:620)
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:280)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:454)
Caused by: java.lang.ExceptionInInitializerError
at java.lang.J9VMInternals.initialize(J9VMInternals.java:257)
at javax.crypto.KeyAgreement.getInstance(Unknown Source)
at com.ibm.jsse2.L.h(L.java:53)
at com.ibm.jsse2.L.a(L.java:206)
at com.ibm.jsse2.l$c.a(l$c.java:6)
at com.ibm.jsse2.l.a(l.java:90)
at com.ibm.jsse2.m.a(m.java:2)
at com.ibm.jsse2.m.g(m.java:123)
at com.ibm.jsse2.SSLServerSocketFactoryImpl.getSupportedCipherSuites(SSLServerSocketFactoryImpl.java:11)
at org.apache.tomcat.util.net.jsse.JSSESocketFactory.<clinit>(JSSESocketFactory.java:114)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:235)
at org.apache.tomcat.util.net.jsse.JSSEImplementation.getServerSocketFactory(JSSEImplementation.java:47)
at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:388)
at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:646)
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:434)
at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)
at org.apache.catalina.connector.Connector.initInternal(Connector.java:978)
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
... 12 more
Caused by: java.lang.SecurityException: Cannot set up certs for trusted CAs
at javax.crypto.b.<clinit>(Unknown Source)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:235)
... 30 more
Caused by: java.lang.SecurityException: Cannot locate policy or framework files!
at javax.crypto.b.c(Unknown Source)
at javax.crypto.b.access$600(Unknown Source)
at javax.crypto.b$0.run(Unknown Source)
at java.security.AccessController.doPrivileged(AccessController.java:341)
... 33 more


Java: 1.7 from IBM ink. JCE
Keystore worked in 3.4 before.

Has anybody an idea how I could solve this problem?

Thanks,

Michael

0 Likes
sulatna Absent Member.
Absent Member.

Re: VIBE wont start after Upgrade to VIBE4

Hello Aaron,

thanks for your reply.

Looked in all files you wrote - keys are correct like in vibe3.4.

Michael
0 Likes
sulatna Absent Member.
Absent Member.

Re: VIBE wont start after Upgrade to VIBE4

Hello Willem,

JCE is installed like described in documentation.

I also tried to change JAVA to oracle (with jce) - but I get always the same error.

More details on hosting server: SLES11sp3 - x64 - patched via update channel.

To exclude a keystore-problem I created a new one (like described in VIBE - administration guide) - but this also doesn't solve my problem.


Also I started a SR at novell.


Michael
0 Likes
Knowledge Partner
Knowledge Partner

Re: VIBE wont start after Upgrade to VIBE4

sulatna;2392443 wrote:
Hello Willem,

JCE is installed like described in documentation.

I also tried to change JAVA to oracle (with jce) - but I get always the same error.

More details on hosting server: SLES11sp3 - x64 - patched via update channel.

To exclude a keystore-problem I created a new one (like described in VIBE - administration guide) - but this also doesn't solve my problem.


Also I started a SR at novell.


Hi Michael,

Hopefully the SR will quickly find the source of the issue.

Let us know how you go.

Cheers,
Willem
0 Likes
ksiddiqui Absent Member.
Absent Member.

Re: VIBE wont start after Upgrade to VIBE4

Was this an upgrade on the same server or did you migrate from a 3.4 server to a 4.0 server?

Note: migration is only supported between 4.0 to another 4.0 server; 3.4 to 4.0 will not work.
0 Likes
sulatna Absent Member.
Absent Member.

Re: VIBE wont start after Upgrade to VIBE4

It was an update from 34 to 40 on the same server - no migration.


SR could solve my problem:

Because I wanted to use IBM java there was an entry "algorithm=IbmX509" in server.xml at 443-connector also after I changed to oracle java and made a reconfiguration.

I had to change to oracle java first and then make update to Vibe4 and delete this wrong entry in server.xml.

Problem solved for me - VIBE4 is running.


Michael
0 Likes
Rimser1 Absent Member.
Absent Member.

Re: VIBE wont start after Upgrade to VIBE4

Aaron, that was a great hint. Helped me a lot!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.