The problem I am about to describe has been going on since we upgraded from 8.5.2 to 8.5.3.
We have a simple required reading program that routes documents to be read and has a button that allows folks to indicate that they read it. On occasion, these readings are connect to our training records database to record that someone read some training material. That training database is an Oracle system and is updated by an Oracle procedure that is called (using LotusScript) when they press the button that they have read the document.
I have a development computer as well as a test computer. The test computer is usually loaded with our company standard load that has been tested on all of the various types of computers we purchase. Anyway, last year I upgraded my development computer to 8.5.3 while leaving my test computer on 8.5.2 (have since upgrade it as well).
After I upgraded my dev computer to 8.5.3, I noticed that whenever I received an error from the Notes application that there was an issue with the Oracle Procedure call, my Notes session would crash when I tried to open that email or preview it in the preview pane. I tried opening it in the web client and had no problems. I tried opening it with my test computer (running 8.5.2) and experienced no problems. We have been short handed here for some time, so the priority was not very high on solving this problem. However, now the problem has spread. Presently, whenever a new document is created and routed, it may or may not cause the person's Notes Session to crash when they try to open the document.
I don't profess to know the inner workings of Notes and what the differences between 8.5.2 and 8.5.3 could be that might cause this. Has anyone seen this?
Thanks,
MJ
Software crashes (and other software defects) with Lotus Notes should be reported to IBM by opening a PMR on this site:
http://www.ibm.com/software/lotus/support
Well, I don't know, if it is the same problem as happend in out application BUT:
We figured out, that using PNG images will crach the notes client (and the domino server). This bug happend in some versions of domino (and notes).
http://www-01.ibm.com/support/docview.wss?uid=swg1LO48673
Related
Last week I tried to update my Notes client installation from 9.0.1 FP9 to FP10 IF 3. For technical reasons I had to roll back which proved to be quite difficult, and I ended up completely uninstalling Notes and doing a fresh installation of 9.0.1 (standard) then FP9 IF 2.
Everything's fine (and much more responsive than before, too) with one serious exception:
Within the client help popup window for Notes client and Domino Designer help is hardly usable now; obviously there's no CSS style or whatever applied to the nav page / frame:
As you can see in the screenshot styling of the main window part (green frame) is fine. But everything that is releated to navigation (red frames) appears to be raw html. Javascript calls are apparently working but it's really hard to navigate the "chapters". Same applies to Designer help, of course.
Here's what I tried to solve that riddle:
uninstalled and re-installed full client 3 times; sometimes I ran the
installation as local Admin other times I didn't (no difference)
just installed plain Notes 9.0.1 from scratch then tested Client help before updating to FP9IF2 (no difference)
restored the entire [Notes-Programm]\framework directory from a
backup I took when Notes help still was working as expected (no difference)
copied over the entire \Notes\ folder from a different PC where popup help is still working fine (no difference)
Problem with that is: being a Developer I need to have a functioning help window in my Domino Designer. The navigator as it is right now however is plain useless. And designer_help.nsf isn't of help at all when it comes to Java, LotusScript etc. objects and classes.
One of my co-workers has the same phenomenon while another one hasn't.
Question: did anyone else experience something like that? Where you able to solve it? How?
This seems to be related to an issue with the embedded browser windows that Domino Designer uses to open the Help website.
Try to open following link in a modern browser (such as Chrome or Firefox) and the navigation should be fine.
http://localhost:50970/help/index.jsp?topic=%2Fcom.ibm.notes.help.doc%2Ffram_getting_started_c.html
Bookmark it and use it when you need it.
Try using the IBM Nice tool to see if it can fix your issue
https://www-01.ibm.com/support/docview.wss?uid=swg21459714
Meanwhile I restored my entire Windows system partition from a backup created just before all that began (lucky me that I have both regular local backups plus a separate system partition). And that finally helped resolve the problem.
Meanwhile I'm 99% sure that this is due to a rather new registry and/or firewall setting not yet known to IBM's NICE tool.
I am facing issue (Error:500 Unexpected run time error ) in some cases when xpages based application is opened in Note 9.0.1 client. This issue is not reproduce because when you restart your client it automatically resolve the problem and its not come very often.
Initially we were using Server 8.5.3 but we have upgraded server to 9.0.1 FP4HF71. We have not observed this issue on 8.5.X clients.
Can anybody tell why this issue sometime occur on some machine and automatically issue is fixed when machine re-starts .
Anybody else facing same issue or not? Possible solution?
It works well other than xpages apps.
Thanks,
Qaiser
Is this while you're developing? If you make a change in Domino Designer and want to see the change in XPiNC, you need to close Notes and re-open. It's to do with how the applications are loaded and how the XPages runtime differs in XPiNC vs server. (My guess is that the XPiNC XPages runtime uses the .class files for the application loaded in memory, but building the application recreates those - it has to - so the files are no longer available for the XPiNC runtime.)
There's no way round it and my recommendation (and what I've used for XPiNC development on other projects) is develop and test in Firefox, then do a final review in XPiNC when complete. Troubleshooting in Firefox is significantly easier than XPiNC, even with Firebug Lite plugin, so it will be an easier development experience.
The biggest single different with XPiNC look and feel / processing is if #DbLookup and #DbColumn are coded with "" as the first parameter, which works on browser but is bad practice. Following best practice of using #DbName() as the first parameter will yield consistent results on XPiNC and browser.
It won't occur for non-XPages applications, because they are the only applications using the XPages runtime built into the Notes Client for XPiNC.
Try changing the port under Preferences -> Domino Designer -> Web Preview Port to 8080 or something along those lines. Maybe port 80 is already in use.
In developing Xpages applications I have noticed that the applications will intermittently and apparently randomly freeze. It happens when I am changing code and previewing quite a bit in XPiNC, which I might be able to understand. But at times it happens when I am just editing a document.
For example, I just updated a RT field in a document using CKEditor, and the app froze about 12 or 15 times. I will no longer be able to move the cursor or move scroll bars up or down. I am able to switch to a different tab (like my email) but if I try to switch back to the Xpages app, I will still see the email application.
I have checked the "IBM Technical Support" Folder for the Xpages log and the console log, with nothing there, and I have checked the Help ==> Support Trace and Log, nothing there either.
We are running Revision 20131022.1138 (Release 9.0.1) on the server, and I am running the same on my client and designer.
An application we're developing for a customer is running more or less fine on our internal development servers (V 8.5.3 with UP1 and FP5 as well as a secondary V 9). Our development is done using V 9 designer clients.
Yesterday we pushed a test version onto the customer's server (V 8.5.3 FP5 / UP1). The result rendered by their server however is completely different from what we get from our servers. It turns out that only custom style sheets are rendered while everything that usually should be coming from the server's webstandard theme is completely missing: no xsp.css, xsp_ie.css and the likes. Thus the pages are completely unusable: tabbed panels are rendered as standard elements, rich text editors are completely broken, just to name a few things.
We had the local admins check the server file system: webstandard theme appears to be there, and accessible to everyone.
Has anyone ever come across something like that? In 4 years of developing Xpages I've never seen something like that, at the moment I'm completely clueless in what to try next.
I really hope that this is just a minor flaw easy to be resolved.
Lothar
Have you checked the installation? I have seen servers that were upgraded the wrong way by copying the data directory, then upgrading and then moving back the data old directory, thus overwriting some important files or even loosing important files and directories...
This is hilarious: for security reasons the customer's admins deleted all files from the server's file system that they thought weren't needed. For some reasons they left the themes but removed all resources like css and js files (including all dojo dirs). No, I won't tell any names.
Lesson learned: never just assume a customer's setup to be fully functional until this fact is properly proved ;)
Sometimes the style sheet disappears when naviguating on our WSS 3.0 sites (white background on the site, no colors, no formatting, etc.). This has mainly happened with IE6 (corporate browser for the majority of our computers). The fixes were :
clean up temporary internet files
if it still doesn't work, upgrade to IE 7
However, this time, the upgrade to IE 7 hasn't worked, the style sheet isn't applied. When we clean up temporary internet files, things go back to normal, but after a while the css disappears again.
Here are a few ideas on what you could try:
Fiddler should be able to tell you if there is a network problem.
Check the HTML for anything unusual. Is it malformed in any way? Can you save a copy and run it through an online validator (although this is limited in use as SharePoint's default markup isn't compliant).
If some users are having the issues but others aren't, check their permissions on the server.
You could also try using the SharePoint "Log in as another user" feature to see if the problem can be reproduced on your machine when logged in as them. You may also want to try running Internet Explorer as that user.
Check the Event Viewer on both client and server for anything unusual.
Check the IIS logs on the server for any errors.
Check the SharePoint ULS logs on the server in the "12 Hive" for errors that might be related to this problem.
Try running Process Monitor on the client and reproduce the problem. Search for keywords such as FAIL or ERROR to see if anything appears. Make a note of the time the problem occurs and see if the Process Monitor logs give any additional information.
Is there some javascript that's involved as well? Could it be a virus scanner that is set way to strict? As you pointed out in one of the comments, the CSS isn't even being requested (at IIS log level, which is as basic as you get, not even in SHarePoint yet), so it HAS to be something on the client PC.