Our products coded in Designer are usually structured as:
database1.nsf,
database2-production.nsf,
database3-devel.nsf,
then, all of them use the same template:
database-template-verX.X.ntf
Agents I code, are coded in NTF. After ntf is ready to be moved to NSF files, I usually just do Application > Refresh design. Everything works well. Now here is the thing...
When refreshing design and checking domino.log, usually newly created agents work great on:
database1.nsf,
database3-devel.nsf
However,
- database2-production.nsf doesn't seem to get agents properly. Even If I open NSF file directly in Designer, everything looks good. The agents just don't run. All agents are ENABLED, have proper permissions and are signed. That -production.nsf database just doesnt want to cooperate.
Usually we solve this with restarting domino and even then, sometimes we arent sure if agent will start running as scheduled or not.
Did someone else had similar problems or maybe knows what is wrong? It looks like there's some kind of cache or something..
We have no idea...
Any help would be great!
Thank you in advance!
You can use tell amgr debug * to have the agent manager output detailed information to the console. Unfortunately, if it seems that restarting the server solves the problem temporarily, you may have to collect debug information over a long period of time to see a before and after picture of what's going on -- and even then it might not point you toward the reason.
Check all the design elements property, Prohibit Design refresh or replace to modify should not be checked. Also check your acl for this database.
Related
When I am trying to access a Spotfire dashboard via web player, I am getting the below error message. I was able to access this dashboard earlier without any issues, this issue has popped up recently.
Please advise as what could be the reason for this error?
Below is the screen shot:
Thank you!
this error means that the data source has changed or is not available.
verify that your data source is still working in the Spotfire desktop client. check that the data source is either a linked DB table of some kind and that the information link still works. otherwise ensure any file-based data is embedded in the document.
the error seen on webplayer is pretty high level; it's basically "oh no, something's wrong!" and not very descriptive. if you can share some more including your Spotfire version and relevant logs (don't forget to remove sensitive data) I can probably give you a better answer.
#scsimon/niko - Thanks for your suggestions. I was able to resolve this issue. Cleared cookies and tried to login again. I was able to login to dashboard but one of the pages was not loading. Duplicated page in client and deleted the old one. This resolved the issue.
Greeting, brethren,
So I inherited this app (yes, XPages can be legacy now ;-). It is meant for the Notes client only and one process takes a convoluted route via what I understand is called a Managed Bean (the Code/Java design element).
The database resides on a server.
When editing said bean.java, I meet two issues.
If I test immediately thereafter, I'm greeted with an Error 500 that won't go away unless I close then restart both Notes and Designer
In some cases, changes made to bean.java are not immediately available. So far I haven't been able to characterize those cases. For example, yesterday afternoon I could no anything, nothing would bring a change to the Notes client. (Yes, I cleaned & rebuilt and autobuild is disabled). This morning changes are apparent immediatly (save for the quit/relauch bore).
I've tried to set xsp.application.forcefullrefresh=true in the app's Xsp properties but haven't noticed much effect.
What am I doing wrong ? What could I do to fluidify the modifying of a bean ?
When working in XPiNC, after every change you have to close and restart designer. If I understand things correctly, it's trying to access class files that have been discarded. That's why whenever I've had to develop for XPiNC, my initial testing during development is on a browser, I would recommend this approach.
There are minimal differences in syntax, usually only encountered if manually creating URLs to files etc or using the bad practice "" to specify database location in #DbLookup. Wherever possible, avoid #Formula approaches, their performance is worse than object orientated methods (e.g. view.getAllEntriesByKey())
It's the same for the bean. There are only two ways to speed up picking up updates - use a browser or use XPiNC on a different PC.
When runnning my Coded UI Tests through a VM (deployed via OctoDeploy incase that matters) 2 of my tests will run properly. The other 44 however do not. I am presented with the exception:
Microsoft.VisualStudio.TestTools.UITest.Extension.UITestControlNotAvailableException: The Internet Explorer window is not available.
When looking at the output, it shows that it passes 2 steps, which the second step involves clicking a link. It states that it passes this step, and when I watch it physically, it doesn't look like it does. (I even attempted to take control real quick and click it, but it did nothing).
Has anyone else had these problems?
So looks like I found the answer to this through different means entirely. It was due to the security of the VM and I had to enable Java applets. Sorry for this everyone.
For my company I've created a RSS reader extension for our internal blog. The reason why I've build my own is irrelevant, I know there are many existings extensions. Suffice to say that the blog is completely sealed of from the outside. And let's not forget that it's simply fun to try new things like this :)
The extensions works almost perfectly. It shows a nice popup with the latest 10 posts and it shows a counter if new posts have been added to the blog.
However, since most of my collegaes are webdevelopers like myself, some of them use firefox ( the extension is being ported by an automated script for use in FF ) and have the "clear history on browser close" option enabled. This does however delete the localstorage as well. I know that this setting is the issue and not the porting because my collegae that do not have the option selected don't experience any of these problems.
I use localStorage to remember which posts have been read and which haven't. So for these people the result is that every browser restart the extensions says there are 10 new items regardless of any items they may or may not have read.
I've thought of a way to work around this issue by using a MySQL database through php and ajax. But I'd still need to reliably be able to store a userId or something to personalize the read/unread list.
There must be an easier and better way. I know many extensions with similar functionality that do not have this issue but I've got no idea how and can't find anything about it.
Do any of you have an idea ?
Thanks!
I just tried my own Chrome extension using chrome.storage.sync API.
The storage won't be deleted if you clear all the history and local cache.
I've only built Chrome extensions, not FF ones, but if you have access to the file system, you can store the data in a simple text file. To be honest, I'd blame the developers for clearing their history. ;)
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.