I am using liferay 6.1.1 with tomcat 7. It boots fine till login page. Once I click on login, it throws the error "ORA-00904: "IMAGEIMPL0_"."TEXT_"invalid identifier.
Has anyone any idea what this is and why this is coming. The entries in DB look fine (Image attached).
The same issue has been reported at : https://community.liferay.com/forums/-/message_boards/message/58226128
DB-screenshot.
If anyone still facing this issue, the problem was that somehow the TEXT_ column was removed from the Image Table. Simply adding the column resolved the issue for me
Related
I'm having a strange issue with my (i admit) very old liferay. Sometime yesterday morning my system broke down and doesn't start up again. I have no idea why it broke down.
Now when I restart my liferay again according to the logfile it starts fine. But when I try to acces the page via browser all I get is inifite loading. No log messages, no exceptions, no timeout, nothing. This all was Liferay 6.0.5 and JBoss 5.
I then downloaded a Liferay 6.0.6 bundle with Tomcat 6 and connected it to my oracle db. Same behavior. Next thing I did was not using an oracle connection so liferay used its built-in memory DB. And voila, startup worked immediatly. reconnecting to oracle results in failure again. I tried this liferay-tomcat bundle with all needed themes and portlets.
Then I undeployed all custom webapps and startet again and suddenly my log showed this message: No theme found for specified theme id <MY_CUSTOM_THEME>. Returning the default theme.
So the request must reach liferay somehow. Sadly the browser still doesn't show anything.
I'm short on ideas so I'm grateful for any help. Btw: I'm planning to relaunch with liferay 6.2 and an other db schema in couple of weeks, so a dirty workaround would totaly be enough for me.
Thinking out of the box: Is it possible to export all data from my database as sql inserts, etc and import them into liferays memory db? I know the memory db is not build for production use, but since it's only a couple of weeks I might give it a shot.
EDIT: I switched back to my jboss 5 and liferay 6.0 setting. I just noticed another strange thing. When I type a non-existent like liferays default community url (not configured in my particular portal instance) I see this message in my log Current URL /de/web/guest/home generates exception: null
. So apparently the illigal requests are recognized but legal requests are not served.
Thanks guys and regards. Sebastian
I am working with a brand new instance of IIS on Windows Server 2012 and I am having trouble getting my CFWheels app to work. The issue it seems to be with ISAPI filters and isapi_redirect.dll because it's trying to find the file in the wrong folder. I tried adding a filter myself which I named jakarta and pointed it to the correct folder of the dll but now I am not getting anything but a blank screen and no error of any sort (before I was getting an error 500)
Anyone with a recommendation of what I need to do!?
I recreated the site under C:\inetpub\wwwroot\ instead of having it on my second HDD and the issue went away.... I would love to know why though so if anyone ever comes across this question please feel free to post
Using sessionAsSigner in SSJS which worked fine until Firefox updated itself to version 28.0
Now get this error: "Error: 'sessionAsSigner' not found"
Still works in Internet Explorer 9.0
Anyone else experienced this and/or know how to resolve it?
I faced this when My xPage/CustomControl and attached ScriptLibrary are signed with different signers.
Resigning the database with server ID and re-building the application fixed the issue.
'sessionAsSigner' works fine now.
I think the browser update was a red herring.
If you get this error every time the code has run then you should ensure all design elements are signed with the same ID. Clean (Project -> Clean) the database if errors continue. I have found that sometimes 2 cleans are needed to resolve this (and other strange xPage issues).
However, I found that even after this has been done a user can still get this error randomly. When the user runs the code a second time it usually runs without error.
I would appreciate anyone's insight into why this could occur randomly.
I've just upgraded from Liferay CE to EE 6.2, and have successfully deployed the WAR on my weblogic 12c appserver. However, I am getting this error while trying to access my portal:
An unexpected system error occurred.
Unable to process template _SERVLET_CONTEXT_/html/themes/classic/templates/portal_normal.vm
I've read that this might be a cache issue, and I've deleted all temporary files and restarted my server but am still getting this error.
Any ideas as to why this occurs?
I've seen it before, but can't remember the exact circumstances. AFAIK it's been a temporary issue and I'm puzzled that restarting the server doesn't help..
However I've found LPS-12683, an issue that is marked as fixed, but maybe you find some circumstances in the description that haven't been fixed. Also this forum entry contains a nice hint to check
You need to import the init.ftl file from your parent theme and fix occurrences of:
stringUtil.equals(x, y)
in
x == y
Im struggling a long time now with the following problem: I generate a very basic (or complex) example portlet with xmlportletfactory. Deploy it to Liferay, add it on a page and try to use it. I can not add a new entry (error message in view) and the server log sais:
ERROR [http-bio-8080-exec-1][PortletBeanLocatorUtil:42] BeanLocator is null for servlet context coursesExample
Environment is:
liferay-portal-6.1.2-ce-ga3
liferay-plugins-sdk-6.1.1
XMLPortletFactory_6.x-v2.2
Tomcat/7.0.40
Postgres 9.2
Java 1.6.0_45
I searched the whole web and find a lot of similiar problems on the liferay forums, but nothing helped me. I posted it also to xmlportletfactory forums http://www.xmlportletfactory.org/forum/-/message_boards/message/145826, but still no answer yet.
What can I do?
In my case, for some reason I changed the project's name, and I started having the same "BeanLocator is null for servlet context..." problem.
A couple of days later, I renamed my eclipse project to the same name I initially used, and everything went back to normal.
Could that be something related to your project's name as well?