I have downloaded sample XPages database http://www.jmackey.net/groupwareinc/johnblog/johnblog.nsf/d6plinks/SurveyToolSample
and deployed it to server. I can open it without problem with my Lotus Notes 8.5.3, but my colleague cannot open it on his Lotus Notes 8.5.2 Standard Configuration.
He gets the following error:
**This Page Cannot Be Displayed**
Internal system error when processing the request for the page ( http://127.0.0.1/xsp/JHGNES!!Major %5CSurvey.nsf/HomePage.xsp?OpenXPage&xspRunningContext=Notes ).
Please retry this request.
Enforced by host JHGMELWEB01
If this condition persists, please contact your corporate network administrator and provide the code shown below.
Notification codes: (1, INTERNAL_ERROR, http://127.0.0.1/xsp/JHGNES!!Major %5CSurvey.nsf/HomePage.xsp?OpenXPage&xspRunningContext=Notes)
I have Recompiled all lotusScript in the database using my 8.5.3 client.
Any ideas what can be the problem?
Recompiling all Lotusscript does not re-compile XPages.
Try doing a clean of the project by opening the database in Domino Designer and then use Project - Clean in the menu. Clean removes all built code and then re-builds the code.
In your 853 Designer, try recompiling the app to support 852 as the minimum release?
Launch the Application Properties in Designer, go to the XPages tab, then under 'Minimum Supported Release' select to compile this application to run on 'Release 8.5.2'.
For the vast majority of cases, apps built or compiles on current releases will work fine on previous releases without needing to do this step. Though in some cases, changes in the new release, like a new property for example, may cause failures in previous releases. This is what I'm guessing what is happening in your case.
Thanks for your quick responses. I have done more testing after I tried suggested solutions and it seems like the problem is not in the database itself but in this colleague's PC configuration, as it works on 5 other PCs running 8.5.2 and 8.5.2FP2.
Actually when you change "Minimum supported Release" on the xpages tab of app properties it prompts you to rebuild all the code.
The problem was in the location settings of that particular machine. After we removed contents of "Proxy configuration" it worked like a charm.
Related
I am using latest okhttp and when using at home it connects just fine. Inside a company it displays dialog box for approval to connect to a server. I do not want the user to see that dialog box just connect silently like it does for me at home. How do I get it to do that? I used httpclient from Apache and it does not do that. I wrote my own code to determine proxy and added that to Apache client code and it does not ask for connection approval.
Thanks for the help,
-Tony
Disable the software firewall that is showing the dialog. The dialog isn't OkHttp; it's just a side effect from OkHttp using your network.
Seems the issue might have nothing to do with firewalls as I expected. I read there were issues with earlier versions of Java and even 8u25. I am using 32-bit 8u45 a security patch release. I installed 32-bit 8u60 EA and it seemed to have fixed the problem. So I am sure 32-bit 8u45 has the issue. Hopefully when 8u60 is released (soon I hope) it will still have the fix. I will check another laptop I have that works to see what version of java it is running.
Regards,
-Tony
Very general question here:
I have Liferay 6.1.1 ga2 set up on my Oracle WebLogic 12c.
It works fine on my local, but when I deploy it onto our development server, I lose all write permissions.
E.g., changing the theme/color scheme, creating web content, pages, and saving changes to most things
I try to import LARs however it is saying it is not permitted
I'm not seeing any errors in the logs, and the control panel messages are even telling me my content was created or change successfully (besides the LARs0, but everything stays the same.
Any reason(s) why my changes aren't showing up? I'll surely give a bounty if I can get pointed in the right direction here
Given your description, I'd recommend checking OS issues, like write access to various folders, like temporary folders etc.. I guess that Liferay has proper permissions to the whole database (it's rare to have incomplete access) and can write to all tables. And you're operating on a portal-wide admin account, right?
Unrelated to LAR import, changes will not show up if you have workflow enabled - then you'd find the changes in the list of tasks that need approval.
As staging has quite an obvious UI in 6.1, I assume you don't have staging activated, otherwise you just need to publish. In order to see new portlets, make sure that the "Edit Controls" checkbox in your dockbar is checked. This has bitten me more than once.
if you're running a cluster, make sure that you have set it up correctly, e.g. that you don't see cached content on your node.
Can you confirm that you can see the options to change on the UI, just that your changes aren't persisted?
Also, please note that Weblogic 12c is not on the "supported Appservers" list for Liferay 6.1, it's there for Liferay 6.2 only (probably due to release date). This doesn't mean that it shouldn't run, just that it's not tested for your version. Further, there's a GA3 release for 6.3 already, so you might want to check if it's a problem that's fixed in GA3.
I am facing a strange error in xpages. Whenever i preview any xpage in internet explorer I get error 500. I've tried this with new nsf, I created only one blank xpage with no elements and tried to preview, I got the same error.
I've also checked the "Display Xpages runtime error page" in xpages tab in Application Properties section but got the same 500 error.
(I am working on my local machine)
Url of my xpage:
http://localhost/test/testdb.nsf/testxpage.xsp
For every preview attempt log.nsf has below entry
04/17/2012 03:24:10 PM HTTP Web Server: Command Not Handled Exception [/test/testdb.nsf/testxpage.xsp] Anonymous
Below is the error on ie.
Error 500
HTTP Web Server: Command Not Handled Exception
Step 1: Go to the application properties and tick "Show standard error page"
Step 2: Make sure that your application is build (default autobuild in project is ON, but you never know)
Step 3: Try project clean
Step 4: Check the errorlog in data/domino/workspace/log
Step 5: Post your code here to have a look
Based on your description most probable reason is security: you have no right to run XPages on the server. Either sign with proper ID or manage to be in "Sign agents or XPages to run on behalf of the invoker:" field of server document (in Security tab).
Anyway, you should always look for the log mentioned by #Simon McLoughlin.
Try looking at the stack trace in C:/domino-Data-Directory/IBM_TECHNICAL_SUPPORT and the most recent xpages_...log file, generally a lot more helpful than the one line errors you get in other places
If you are working on Windows Vista/7 then for starting your Lotus Notes, right click on Lotus Notes icon and click on "Run as administrator". It works this way on my local machine. I guess this is due to UAC (User Account Control).
I guess that it is your Notes client. Then you need to check with your admin.
Some of the time, We do not have a sufficient privilege for data folder. I am also faced this issue.
Check your server port, probably it may 80. So some your application takes port 80 like face book, skype... So quit that process and try :)
Are you using Extension library in the application ?
Then you need to do a double installation, both the designer and the Client installation to be able to preview.
I'm experiencing the same issue with my server, I only did what #stwissel suggested and then restarted my server and it all worked, but in your case your running it locally try restarting you PC and hope it works.
Are you running Quicker? I found this article and thought it might help, http://www.zarazaga.net/web/z.nsf/dx/getting-error-500-on-opening-an-xpage
I am working SDL TRIDION 2011 SP1 version. Suddenly I am unable to see the Trdion site in Internet Information Services(IIS) Manager. Please tell me the procedure how to get it back again.
Remove Tridion Completely (uninstall), then run the installer again.
You won't loose any data (it's all in the database), and you're likely to get your server up and running way faster than trying to fix by hand.
As #bart suggested, your best option to get the web application back (assuming it really has gone), is to run the repair option with the installer. There are a lot of folder specific settings which would be very hard to recreate manually.
I am working on a project where we are using RSA 6.0.1.
I have to run the some set of tasks programmatically. I have open the emx file using UMLModeler.openModel(absoluteModelPath); Then do some editing and save through UMLModeler.getEditingDomain().run( new ResourceSetModifyOperation("Update Operation") {},Monitor); Then I refreshed the project through sourceProject.refreshLocal(IProject.DEPTH_INFINITE,monitor); till now things goes fine and finally when I am closing the model through UMLModeler.closeModel(objUMLModel); It is running this code but not closing the EMX file in the editor.
There is no error , no exception. Can any one please suggest me what can I do to close this emx file.
First, I would upgrade to 7.5.4 as the model concept goes away, in fact the method you are using is deprecated.
From the API documentation:
closeModel(Model model)
Deprecated. Since 7.5, use the closeModelResource(Element) method, instead
Using the newer methods might resolve you problems. Additionally, do you try refreshing the workspace? Either manually by right clicking on the project and selecting refresh or doing it with code.
Finally the most likely issues is that there are multiple 'handles' to the model. Closing yours does not close the editor or project explorer handle. I do not work for IBM so I cannot know this for sure. You could test this by opening it in the project explorer, open it with your code, then close it in the explorer manually, and only then try running your transaction on the model and then closing it. What does the explorer look like when it closes?
Or post more details and maybe I can code my own example. I would try the debugging first and also post this on the IBM developer works site. They are likely going to tell you to upgrade though. :)