Error on Startup (after Deploying Liferay)

Its solved - i increased the permgan to 1024m (fix) and its works fine now!
Thread can be deleted :)
Hello together,
i got an running WL 12.1 Server and started to deploy liferay.
My PermganSpace is set to 512 up to needed (just for tests) (/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.19.x86_64/bin/java -Xms512m -Xmx512m -Xss1m )
Short: As result i get this Errortrace:
08:43:26,974 INFO [DialectDetector:80] Determine dialect for Oracle 11
08:43:27,162 INFO [DialectDetector:145] Found dialect org.hibernate.dialect.Oracle10gDialect
Jun 03, 2013 8:43:39 AM net.sf.ehcache.Cache initialise
WARNING: Cache: com.liferay.portal.service.impl.PortletLocalServiceImpl has a maxElementsInMemory of 0. In Ehcache 2.0 this has been changed to mean a store with no capacity limit. Set it to 1 if you want no elements cached in memory
08:44:23,808 ERROR [ContextLoader:227] Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.liferay.portal.scheduler.ClusterSchedulerEngineService' defined in class path resource [META-INF/scheduler-spring.xml]: Cannot resolve reference to bean 'com.liferay.portal.scheduler.SchedulerEngineProxyBean' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.liferay.portal.scheduler.SchedulerEngineProxyBean' defined in class path resource [META-INF/scheduler-spring.xml]: Initialization of bean failed; nested exception is java.lang.OutOfMemoryError: PermGen space
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:630)
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:441)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:983)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:879)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:282)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:204)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:47)
at com.liferay.portal.spring.context.PortalContextLoaderListener.contextInitialized(PortalContextLoaderListener.java:159)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:582)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
at weblogic.servlet.internal.EventsManager.executeContextListener(EventsManager.java:233)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:190)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1730)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2740)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1704)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:781)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:213)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:208)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:70)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:212)
at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:111)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:213)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:208)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:70)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:24)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:192)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:369)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:186)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:94)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.liferay.portal.scheduler.SchedulerEngineProxyBean' defined in class path resource [META-INF/scheduler-spring.xml]: Initialization of bean failed; nested exception is java.lang.OutOfMemoryError: PermGen space
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:527)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:322)
... 60 more
Caused by: java.lang.OutOfMemoryError: PermGen space
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2413)
at java.lang.Class.getConstructor0(Class.java:2723)
at java.lang.Class.getConstructor(Class.java:1676)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:719)
at org.springframework.aop.framework.JdkDynamicAopProxy.getProxy(JdkDynamicAopProxy.java:117)
at org.springframework.aop.framework.ProxyFactory.getProxy(ProxyFactory.java:112)
at org.springframework.aop.framework.autoproxy.AbstractAutoProxyCreator.createProxy(AbstractAutoProxyCreator.java:476)
at org.springframework.aop.framework.autoproxy.AbstractAutoProxyCreator.wrapIfNecessary(AbstractAutoProxyCreator.java:362)
at org.springframework.aop.framework.autoproxy.AbstractAutoProxyCreator.postProcessAfterInitialization(AbstractAutoProxyCreator.java:322)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsAfterInitialization(AbstractAutowireCapableBeanFactory.java:407)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1426)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:519)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:322)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:630)
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:441)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:983)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:879)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
<Jun 3, 2013 8:44:23 AM CEST> <Warning> <HTTP> <BEA-101162> <User defined listener com.liferay.portal.spring.context.PortalContextLoaderListener failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.liferay.portal.scheduler.ClusterSchedulerEngineService' defined in class path resource [META-INF/scheduler-spring.xml]: Cannot resolve reference to bean 'com.liferay.portal.scheduler.SchedulerEngineProxyBean' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.liferay.portal.scheduler.SchedulerEngineProxyBean' defined in class path resource [META-INF/scheduler-spring.xml]: Initialization of bean failed; nested exception is java.lang.OutOfMemoryError: PermGen space.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.liferay.portal.scheduler.ClusterSchedulerEngineService' defined in class path resource [META-INF/scheduler-spring.xml]: Cannot resolve reference to bean 'com.liferay.portal.scheduler.SchedulerEngineProxyBean' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.liferay.portal.scheduler.SchedulerEngineProxyBean' defined in class path resource [META-INF/scheduler-spring.xml]: Initialization of bean failed; nested exception is java.lang.OutOfMemoryError: PermGen space
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:328)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:630)
at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:441)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:983)
Truncated. see log file for complete stacktrace
Caused By: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.liferay.portal.scheduler.SchedulerEngineProxyBean' defined in class path resource [META-INF/scheduler-spring.xml]: Initialization of bean failed; nested exception is java.lang.OutOfMemoryError: PermGen space
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:527)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
Truncated. see log file for complete stacktrace
Caused By: java.lang.OutOfMemoryError: PermGen space
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2413)
at java.lang.Class.getConstructor0(Class.java:2723)
at java.lang.Class.getConstructor(Class.java:1676)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:719)
Truncated. see log file for complete stacktrace
>
<Jun 3, 2013 8:44:23 AM CEST> <Notice> <LoggingService> <BEA-320400> <The log file /opt/oracle/user_projects/domains/1/servers/AdminServer/logs/AdminServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms, such as Windows.>
<Jun 3, 2013 8:44:23 AM CEST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /opt/oracle/user_projects/domains/1/servers/AdminServer/logs/AdminServer.log00001. Log messages will continue to be logged in /opt/oracle/user_projects/domains/1/servers/AdminServer/logs/AdminServer.log.>
<Jun 3, 2013 8:44:27 AM CEST> <Warning> <HTTP> <BEA-101162> <User defined listener com.sun.faces.config.ConfigureListener failed: java.lang.OutOfMemoryError: PermGen space.
java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:791)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
Truncated. see log file for complete stacktrace
>
<Jun 3, 2013 8:45:11 AM CEST> <Warning> <J2EE> <BEA-160181> <An error was encountered and ignored during undeployment. The error was: weblogic.utils.ErrorCollectionException:
There are 2 nested errors:
java.lang.OutOfMemoryError: PermGen space
and
java.lang.OutOfMemoryError: PermGen space
weblogic.utils.ErrorCollectionException:
There are 2 nested errors:
java.lang.OutOfMemoryError: PermGen space
and
java.lang.OutOfMemoryError: PermGen space
at weblogic.application.utils.StateMachineDriver.previousState(StateMachineDriver.java:152)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:43)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)
Truncated. see log file for complete stacktrace
>
<Jun 3, 2013 8:45:23 AM CEST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.OutOfMemoryError: PermGen space
java.lang.OutOfMemoryError: PermGen space
>
Exception in thread "[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'"
Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'"
Can someone help me waht i could do to eliminate the errors?
AT the moment i got no ideas :-/
greets Jens
Edited by: 1008097 on 03.06.2013 02:50

Read previous posts about same problem (SIGSEGV.)
/bto/sys/oracle/product/10.2.0/lib/libocijdbc10.soAnd that is JNI.

Similar Messages

Error in XCM after deploying the customized SCA

Hi All,
we are getting error in XCM after deploying the customized SCA in the server for UCES.
Below is the error message when trying to access the XCM ./bdisu/admin/xcm/init.do
link ./bd/admin/xcm/init.do is working fine..
ISA Framework: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: Internal error while parsing JSP page [/usr/sap/EPT/JC04/j2ee/cluster/server0/apps/sap.com/isucesear/servlet_jsp/bdisu/root/admin/xcm/MainConfig.jsp].
Details: No details available

Hi,
Did you find any solution for this? We face the same problem and we are looking for a good solution.
Kind Regards
Daniel Jadeholt

HTTP Error 403 - Forbidden after deployed to Oracle Application Server

I hit HTTP Error 403 - Forbidden every time after I deployed my war file to my Oracle Application Server.
Any help?
Ming Man

Thanks, I got it works here:
Re: HTTP Error 403 - Forbidden
Ming Man

Error in startup after fresh install

I have Final Cut Express and accidentally deleted LiveType. I put in the disk to reinstall and after it installed, I checked to see if it works right but there's some error when I open it. How can I fix this?
Screenshot of error message - http://img229.imageshack.us/img229/8432/picture1xk4.png
P.S. When I try to click something from the menu bar such as file then "About LiveType" it shows this error message http://img300.imageshack.us/img300/2951/picture1rs5.png
Message was edited by: moheh

If it helps, the serial number that LiveType is asking for is the same serial as the one that your FCE installation asked for.
Should that not work, go to Macintosh HD > Library > Receipts and delete all instances of the installation packages that you find there containing the words "LiveType" there should be four of them.
Then reinstall LiveType.

Error restarting services after deploying a RPD.

Hi all,
I have recently performed OBIEE installation and, when a repository is deployed and all services restarted comes an error like this one and BI Server status is down:
Operation Failed: start; OracleInstance: instance1; Component: coreapplication_obis1; msg 0 of 1 processes started.
OBIEE version is 11.1.1.6 and the unique RPD that works is the sample one, any others fail during the restart process.
I have been thinking that maybe it was a logging error but I am not sure due to the last actions I performed, which have been those:
- Create a new user in the Console
- Create a new repository and give the username created before and its password.
Can you help me please?
Regards,
Borja M.

Think this may be the wrong place to be posting the question about BI

Error on console after deployment

I use asadmin to deploy ejb applications. When it is successful, I can see my ejb on console. But there is a warning asking me to apply changed. So I click on "Apply Changes" button, then I get error as below. I did not remember beta version of son one 7 gave me such warning.
>>>>>>>>>>>>>>>>>>>>>>>>>>
ConfigChange of type Add/Delete or Set for applications and modules should be handled immediately in MBean

The issue is that deployment rollback sometimes does not cleanup "changes cache" maintained in config layer. In any case, the solution is to retry "Apply Changes" or reconfig. The error won't show up the next time. The bug 4737808 is slated for MU1.

Error at startup after uninstalling Webassist, attached message

I was having problems COMPLETELY uninstalling WebAssist 3rd party extensions and may have deleted a vital file. After this message, I get another saying the java script error occurred. I click on OK, and continue and there doesn't seem to be a problem, but the error message is getting on my nerves. I'm sure i deleted WA_processor thinking it a WebAssist file. Can I download this file again?

Try adding an empty folder/sub-directory called WA_Processor to the Floaters folder/sub-directory and restart Dreamweaver.
If that does not work, close Dreamweaver, rename the Configuration folder to Configuration-backup or similar and restart Dreamweaver.

Receive error "bobj undefined" after deploying Web app to Win 2008 server

Developed Asp 2 app in a Windows 2003 server environment with VS 2005 and an upgraded full version of Crystal Reports 2008.
Installed full version of Crystal Reports 2008 on Windows server 2008.
Copied Web app over to Windows 2008 server.
App comes up fine until I attempt to display a report where I receive the bobj undefined error.
Searched the forums and found that the majority of the problems are caused by the Aspnet_Client folder not being copied to c:\inetpub\wwwroot folder.
The folder already exists and is populated. Just to be sure I copied the aspnet_client folder from the development environment over to Windows 2008. Still get error.
Installed vs2005 on Windows 2008 and applied all the necessary patches. Opened the Web app project and ran within VS 2005. Get same error "bobj undefined".
Checked versions in Web.config for app as well as assembly entries in c:\windows\assemblies, c:\Windows\Microsoft .NET\Framework\v2.0.50727\ASP.NETClientFiles and all reflect the correct version 12.

Well it appears that the problem is fixed. The issue was tha aspnet_client folder was indeed copied to c:\inetpub\wwwroot folder but the folder did not show up under the default Web site as a virtual directory in the IIS Service Manager.
I created the virtual directory aspnet_client and pointed it to c:\inetpub\wwwroot\aspnet_client folder and now my reports render without error.
I will try deploying the app to another VMWare Windows 2008 server and see if this will work. I don't want to have VS 2005 installed on the production system so I need to be sure that I only require the installation of the full version of Crystal Reports 2008. I am assuming the Crystal Reports runtime will also be installed.
Installed full version of Crystal Reports 2008.
Created virtual directory aspnet_client
Copied ASP app over
Reports now work.
It appears that the Crystal Reports 2008 install can't create the virual directory aspnet_client on IIS7.
Regards
Paul

Kernel error on startup after trying to backup with Time Machine

Hi there,
So last night I was using time machine to back up my macbook hard drive to my external hard drive. As this was happening, my machine was slowing down and such which I attributed it to having a couple of programs running at the same time as backing up. A little bit into this, I got the spinning pinwheel that would not stop or go away so I decided to let it go all night because maybe it would go away as usual. This morning it was still spinning so I shut down the computer. I didn't know if Time machine had finished or not. I tried restarting it an I got a kernel error. I tried to reset the PRAM and the NVRAM but I still got Kernel errors. I would try to do an archive and install of Leopard, but I left my disc in my dorm and I won't be able to get to it until next month. I do however have my Tiger start up disc that came with the MacBook when I first got it. Now I was thinking of doing an archive and install downgrade to Tiger just until I could reinstall Leopard next month. I don't know if that would be a good idea or not. I just want to make sure my data is ok by hopefully reinstalling Tiger to copy my data to my external HD. Is there a way to do this and not mess anything up? I don't think it's my hard drive because I already replaced it once to a non-Apple hard drive. Is there anything I haven't tried yet or should try again to try and get things going again?
Thanks so much.

This means that your NAS does not support the required encryption. Update your NAS to the latest firmware or ditch it and buy a Time Capsule (they are the most reliable when using TM).

Excel macro error after deploying in Weblogic

Halo,
I have written excel macros and it is working fine.
but if the same file if i try to open from hyperlink after deploying in Weblogic server , I get the error
"error occured initializing the VBA libraries.
If Microsoft Visual Basic for Applications (VBA) was not installed, or was set to Install on first use,
(advertised, or set to install on demand) you may receive this error message.
Depending on the mode of installation used and the rights of the user to change current settings,
it is possible to install VBA through Control Panel, Add/Remove Programs, Microsoft Office, Add or Remove
features. If Visual Basic for Applications is not listed as an installable feature of Office, the administrator
of your system may have disabled it so it is impossible for you to install it. If VBA is not installed,
it is impossible to run VBA applications/projects on this computer. "
1. Even though Excel VBA application is installed in my machine , why am i getting this error.??
2. I would like to know is there any way to open the excel file even though if the excel software is not installed in client machine??
Appreciate your help.
Thanks.

Hi,
I do not see any reason for this to not work.
Is there any difference between the preferences for RX and RXI. Please go to "edit" -> "Preferences" -> "Security(Enhanced)" and uncheck "Enable protected mode at startup".
Are you able to open any pdf from command line with the same command:
"C:\Program Files (x86)\Adobe\Reader 11.0\Reader\AcroRd32.exe" <<PDF_FILE>>
Thanks,
Amish.

Error after deploying the application in PI java system

Hi all,
I have created a test web dynpro java application and deployed in PI7.1 java engine. Using the JCO's maintained i hav connected to ECC7.1 system and created a model to call a bapi. After deploying and running the application, I got the following error. Please let me know the solution
Regards
Sagar
    500   Internal Server Error SAP NetWeaver Application Server/Java AS
The initial exception that caused the request to fail, was:
java.lang.NullPointerException
    at com.sap.conn.jco.rt.DefaultDestinationManager.checkProperties(DefaultDestinationManager.java:405)
    at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:142)
    at com.sap.conn.jco.rt.DefaultDestinationManager.searchDestination(DefaultDestinationManager.java:292)
    at com.sap.conn.jco.rt.DefaultDestinationManager.getDestinationInstance(DefaultDestinationManager.java:90)
    at com.sap.conn.jco.JCoDestinationManager.getDestination(JCoDestinationManager.java:61)
    ... 82 more
See full exception chain for details.
Failed to process request. Please contact your system administrator.
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; GTB6.3)
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Java Applets enabled
Accessibility mode disabled
Rendering engine: Lightspeed
Inline CSS: enabled
Validate by rendering: enabled
Server
Web Dynpro Runtime vendor: 'sap.com', name: 'tc/wd/webdynpro', location: 'SAP AG', counter: '7.1100.20081021173332.0000', change number: '28470', codeline: NW711_00_REL
J2EE Engine 7.11.3710.27866.20080910102732
System ID (SID) PID
Server Node ID |1698650|16986|Server 00 00_16986|sappidev01.xtium.com/10.255.30.89|SERVER|RUNNING
Java VM SAP Java 64-Bit Server VM, version:5.1.027, vendor: SAP AG
Operating system Windows 2003, version: 5.2, architecture: amd64
Application
Java EE Application (deployable object) demo.sap.com/pegatest
Web Dynpro Application Pegatestappli
Request URI /webdynpro/dispatcher/demo.sap.com/pegatest/Pegatestappli
Version vendor: 'demo.sap.com', name: 'pegatest', location: 'localDevelopment', counter: '20100112141118', change number: 'null'
Session & Other
Session Locale en_US
Session Timezone Pacific Standard Time
Time of Failure Tue Jan 12 00:39:45 PST 2010 (Java Time: 1263285585307)
Session User ClientUser(id=USER.R3_DATASOURCE.J2EE_ADMIN, name=J2EE_ADMIN)
Client Session Id bxuvisJvMVwF2Jn5_M0-ODXALydDRLAhJgFa6xkA_SAP
Client Window Id 09190ac2ff5611dea2480050568315be
Application Session Id 09190ac3ff5611dea70e0050568315be
Web Dynpro Code Generation Infos
demo.sap.com/pegatest
Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session ApplicationSession(id=09190ac3ff5611dea70e0050568315be, name=com.sap.demo.pegatest.pegatestappli.Pegatestappli). The causing exception is nested. RID=09190ac0ff5611deb9b80050568315be
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:680)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:239)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:258)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:457)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.tc.webdynpro.progmodel.context.DictionaryException: InvocationTargetException
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getDataType(DictionaryHandler.java:192)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:434)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:978)
at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:294)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:950)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:954)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:69)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:205)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:552)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1296)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoPreprocessing(AbstractExecutionContextDispatcher.java:146)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppPreprocessing.doService(DispatchHandlerForAppPreprocessing.java:35)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoPreprocessing(ExecutionContextDispatcher.java:100)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:74)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:571)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:602)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:252)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:677)
... 48 more
Caused by: com.sap.dictionary.runtime.DdException: InvocationTargetException
at com.sap.dictionary.runtime.ProviderFactory4J7.getProvider(ProviderFactory4J7.java:36)
at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:96)
at com.sap.dictionary.runtime.DdDictionaryPool.makeDictionary(DdDictionaryPool.java:75)
at com.sap.dictionary.runtime.DdDictionaryPool.makeDictionary(DdDictionaryPool.java:63)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:224)
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler._getScalarType(DictionaryHandler.java:462)
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getDataType(DictionaryHandler.java:171)
... 67 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at com.sap.dictionary.runtime.ProviderFactory4J7.getProvider(ProviderFactory4J7.java:21)
... 73 more
Caused by: com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination DEV_ECC6_220_METADATA does not exist
at com.sap.mdi.jco7.Factory.makeException(Factory.java:41)
at com.sap.mdi.jco7.Destination.<init>(Destination.java:35)
at com.sap.mdi.jco7.Destination.make(Destination.java:21)
at com.sap.mdi.jco7.Factory.getDestination(Factory.java:28)
at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:115)
... 78 more
Caused by: com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination DEV_ECC6_220_METADATA does not exist
at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:163)
at com.sap.conn.jco.rt.DefaultDestinationManager.searchDestination(DefaultDestinationManager.java:292)
at com.sap.conn.jco.rt.DefaultDestinationManager.getDestinationInstance(DefaultDestinationManager.java:90)
at com.sap.conn.jco.JCoDestinationManager.getDestination(JCoDestinationManager.java:61)
at com.sap.mdi.jco7.Destination.<init>(Destination.java:32)
... 81 more
Caused by: java.lang.NullPointerException
at com.sap.conn.jco.rt.DefaultDestinationManager.checkProperties(DefaultDestinationManager.java:405)
at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:142)
... 85 more

yes, you are getting Cross Origin Problem .So, you need to disable the web security for chrome.
Go to properties of chrome , and add this after path of chrome.
--disable-web-security
After this restart the chrome.
Please follow the below link for reference.
windows - Is it possible to run Chrome with and without web security at the same time? - Super User
Regards
Sridevi

Error executing the Query after deploying and executing the application in WLS 6.1 SP3

Hi,
We are trying to run a application by deploying a war file on Web Logic Server
6.1 SP3. After deploying and at the time of execution of the application, the
server console displays this error message
java.sql.SQLException: ORA-00600: internal error code, arguments: [ttcgcshnd-1],
[0], [], [], [], [], [], []
While debugging thru the application we found that this error comes at the time
of execution of the query thru the Statement.executeQuery method of java.sql.Statement
class.
This same application when deployed on Web Logic Server 8.1 runs perfectly, without
any hitches.
Please, provide me the solution to this asap.

Look for sometime around November. No exact date.
Eric
"Dominic Tulley" <[email protected]> wrote in message
news:[email protected]..
Thanks Eric,
you know what I'm going to ask next right?
Any ideas when SP4 comes out?
Cheers,
-Dominic
"Eric Gross" <[email protected]> wrote in message
news:[email protected]..
The next version of Apache that we will support will be 2.0.42/2.0.43
and
the module for that will be included in the next Service Pack for6.1(SP4)
and 7.0(SP2).
The problem with Apache 2 is that when a new release comes out a newmodule
needs to be compiled. Most of the time. For 2.0.42/2.0.43 this is notthe
case.
Regards,
Eric
"Dominic Tulley" <[email protected]> wrote in
message
news:3da3f246$[email protected]..
I'm trying to set this up (initially just apache in front of a single
WLS
server but ultimately I want to put it in front of a cluster).
I've installed Apache 2.0.40.
I've copied the mod_wl_20.so file into the apache modules folder.
I've edited the httpd.conf file and added the line:
LoadModule weblogic_module modules/mod_wl_20.so
When I run apache -t to check the configuration I get the following:
C:\Program Files\Apache Group\Apache2\bin>apache -t
Syntax error on line 173 of C:/Program Files/Apache
Group/Apache2/conf/httpd.conf:
Cannot load C:/Program Files/Apache Group/Apache2/modules/mod_wl_20.sointo
server: The specified procedure could not be found.
So what's going on here?
Looking at previous postings it sounds like there's an issue with
versions
of apache after 2.0.39 but I can't find a download for that version.Also,
it sounded like the issues were for WLS 7, not 6.1. Can this work
with
2.0.40 or am I wasting my time?
If I get the mod_wl_20.so from dev2dev I get the "incompatible plugin"
message that has been mentioned in this group already.
Any suggestions appreciated,
-Dominic

Error after Deploying a new Entity Service

After deploying an entity service and testing it via the testtool the following error occured. Do you have an idea about the reason for this strange behaviour?
Thanks in advance.
ERROR. Exception thrown in method create. The transaction is marked for rollback.: javax/jdo/InstanceCallbacks -
Loader Info -
ClassLoader name: [siemens.com/sm3kshtlog] Parent loader name: [Frame ClassLoader] References: common:service:http;service:servlet_jsp service:ejb common:service:iiop;service:naming;service:p4;service:ts service:jmsconnector library:jsse library:servlet common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl library:ejb20 library:j2eeca library:jms library:opensql common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore interface:resourcecontext_api interface:webservices interface:cross interface:ejbserialization sap.com/cafcore library:cafmetamodellib library:cafruntimeapilib sap.com/cafruntimeear Resources: C:\usr\sap\P7D\JC00\j2ee\cluster\server0\apps\siemens.com\sm3kshtlog\EJBContainer\clientjars\clientsiemens.comsm3kshtlogejbmodule.jar C:\usr\sap\P7D\JC00\j2ee\cluster\server0\apps\siemens.com\sm3kshtlog\EJBContainer\applicationjars\siemens.comsm3kshtlogejbmodule.jar C:\usr\sap\P7D\JC00\j2ee\cluster\server0\apps\siemens.com\sm3kshtlog\src.zip Loading model: {parent,references,local} -
The error occurred while trying to load "com.siemens.sm3k.shtlog.besrv.sigdatsource.SigDatSourceJDO".:

Hi Samir,
you could be right...
it could be, that our metadata are inconsistent, because we had before problems with the automatic code generation.
What should we do, if we have such a inconsistency of our ejbmodule, dictionary and metadata model?
is there a way to repair the project?
Undeploy and Redeploy doesn't have an effect on this.
We cannot start again, because we put in 10days of development?
Thanks for any help.
Greetings Jens

After deploy into weblogic server while running the application-404 Error

Hi All,
Created an ADF application and Deployed this application to Weblogic server.
I am getting the below error After deploy into weblogic server while running the application
I am able to run this application well in JDeveloper using the IntegratedWebLogicServer.
The Application is successfully deployed to the Web Logic server.
While creating the domain, I have extended the Oracle JRF classes.
Error
Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
JDeveloper Version : 11.1.1.3.0
Weblogic Version : 10.3.3.0
Thanks
Satish

On the Deployments look for the Testing tab.. you will see your test link to check your deployment ..
Some times.. for some reasons( which i dontKnow :( it doesnt identify with m/c name.. repalce it with IP address..and give a try.. if its on local /c u can try 127.0.0.1 /(or local host too)

"Application not found" error after deploying

Hi,
I am getting error as "Application not found" after deploying.
When I depoly the project am getting Finished Deployment message in the Deploy Output View followed by a popup message "Application not found".
Please help me in solving this error.
Regards,
Rajesh A

HI,
Enabled application is much different than started application.
When you deploy an application then by default it is in enables state.
under general tab you can see whether application is started or not?
and in reference tab you can see. all the referred application and components. and there you'll know which components is giving problem to your application
so check these tabs and let me know

Error on Startup (after Deploying Liferay)

Similar Messages

Maybe you are looking for