I have few simple Xpages, where i test and learn the newest features in Domino 8.5.3.
Now, after some latest changes somehow i'm not able to delete Documents. The Application asks me for the User Name and password, which i enter and which are correct. However, nothing happens (well, the system thinks few seconds over) and i'm asked for my credentials again... and again.. If i press "cancel" -> i got the expected result -> error 401.
The strange thing as well, if even i give for the "anonymous" the editor rights with the "delete documents" checked, i'm still asked for the credentials...
Well, i think I need now some ideas and tips where can i look after in order to solve the "undeletable documents" problem.
The "Delete" button is made using the Simple Action "Delete Selected Documents".
Update: After looking into the logs (thanks Simon O'Doherty for the hint below!) i found out the following message
28.02.12 19:20: Exception Thrown
com.ibm.xsp.acl.NoAccessSignal: NotesException: Notes error: Document locking is enabled. You must lock the document before deleting.
After removing the setting "Allow Document locking" everything works fine.
The next question, however, and it seems to be intresting, if i want to use this setting - how to make the standart actions (it looks like at least "Delete Selected Documents" has some problems) work properly ?
Or do i have to use SSJS only ?
In the ACL settings. Click Advanced tab. Check that "Maximum Internet name and password access" is at least a level that allows you to edit documents.
May need to restart your browser for that to be registered.
If it is still an issue at that point then the following Debug may give more hints.
Check the XPages logs in the IBM_TECHNICAL_SUPPORT folder of the server.
Check the elements on the page are not being pulled from another location that would require access.
Check for Authors/Readers fields.
The following debug on the server will allow you to see when an ACL call is made, what is asked for and what it got.
Warning This is very verbose debug, so it should only be activated for the test. Also do not paste the results anywhere externally without first sanitizing. (as it would be confidential to you).
DEBUG_THREADID=1
DEBUG_SERVER_ACL=2
I have also seen this behaviour in our application.
The issue is caused by the "Allow document locking" option.
Either you do not need this feature; then just uncheck in the application properties. If you intend to use the feature, you have to lock the document in your code prior to deleting it.
Add a execute script simple action before delete simple action and write the following code
var doc:NotesDocument = currentDocument.getDocument();
doc.lock();
or
dataSource.getDocument().lock();
It might be as easy as:
- check your ACL. Do you have delete rights? Default is off
Related
This new functionality - Link Preview / Verify Links Access / Verify Recipients Access - for MS Outlook desktop app, was ported from Web based app without changes to UI settings to turn off.
I have no idea how to skip it.
The execution of code is stuck on NewEmail.Send until the window receives "Send" or "Send Anyway" msg.
Of course, I was banging my head for 2 weeks trying to find a window by its name, etc...
and when I was in the middle of writing this plea for help one last idea came to my mind.
To comment out following line:
NewEmail.Display
It worked. From all of the sub-ideal solutions, this one is kind of satisfying. You can always put .Display in ErrorHandler. This line is here in first place, because many of macros are being run with task scheduler on VDIs/NPSAs, but some of them are being run by users, so .Display and .Send are always there as a comment or as a code.
I wonder if you have any other ways to manage this change until they will provide registry key or update the UI?
My sccenario is as follows:
I have an excel workbook that does a lot of stuff, like create users and such.
A part of this "create user"-procedure is to edit some info on a website.
BUT this website needs to be launched as another user which has access to it.
I have no problem controlling IE if I launch it normally with the current user. But when I launch IE as another user, I cant take control of it from Excel.
I have done a lot of googling and tried a lot of stuff.
Fx. code from the following sources:
http://www.makeuseof.com/tag/using-vba-to-automate-internet-explorer-sessions-from-an-excel-spreadsheet/
http://www.excely.com/excel-vba/ie-automation.shtml
http://www.mvps.org/emorcillo/en/code/vb6/iedom.shtml
None of which has worked in my scenario.
I found a very good workaround here: https://superuser.com/a/49462
Basically I found out that it's possible to force a loginprompt on pages using Windows Authentication, and then log in as a different user.
That means that the IE process still runs as my user, thus making it possible to take control of the window from Excel.
Can anyone link me to a good Selenium-Grid-Extras guide? I have it installed, and need to customize it. Specifically, I need to update the credentials, and reboot settings. When I go to my link: http://XX.XX.XX.XX:3000/user_auto_logon, I can see the settings, but I don't know how to change them. Also, when I open my selenium_grid_extras_config.json I don't see a section that has any of this information to update. Also, even if I did find a section in the selenium_grid_extras_config.json, how would I update the password for the existing username... I'm sure it's not going to be displayed in plain text. Thanks in advance!
From Shawn McCarthy. This solved my problem:
If you want, you can just delete the selenium_grid_extras_config.json file, and rerun the jar file and it will go through the FirstTimeRunConfig again.
You should be able to pass in the username and password to the endpoint as well, http://XX.XX.XX.XX:3000/user_auto_logon?username=YOUR_USER&password=YOUR_PASSWORD
You can check out the /api endpoint to see all the possible endpoints, and the accepted parameters (and which ones are required or not). Usually with no parameters, it does a get current status/value.
Thanks Shawn!
If I make an edit to a Trac ticket, but someone beat me to it, this message is displayed:
Ideally, I would read this message and figure out what I can overwrite and what I should not. But, depending on this message to keep users from overwriting what was submitted is not something that we should depend on:
This may sound a little harsh, but you'll see, when you do usability tests, that there are quite a few users who simply do not read words that you put on the screen. If you pop up an error box of any sort, they simply will not read it.
Is there a better way to prevent these overwrites in Trac - e.g., if a ticket has been modified while you were modifying it, you must refresh the page, etc?
Yes, if the server would send the page modified outside and if the javascript running in your browser could merge that into your local changes. But noone has implemented it in the current trac.
I was updating a COM+ application, when an error showed up, saying that it couldn't be changed. Now, whenever I go into properties on one of the components in that application, or the properties for that application, everything is greyed out, not allowing me to change it. Delete is no an option for the application, and if I hit delete on the component, it tells me "Some changes could not be applied due to the following errors:" - "The selected item cannot be changed. The item is currently locked against changes." I can't seem to find anything on google. At one point there was an HRESULT that showed up, I don't remember exactly what it was, but it turned out to be something like COM_ADMIN_E_NOT_CHANGEABLE, which also didn't give me much from google.
Logged on as domain user with admin privileges.
Running windows server 2008 standard.
Do you have the Protection (Disable deletion and/or Disable changes) enabled for the COM+ Application? Check by looking at Properties->Advanced for the Application:
If so then un-check Disable deletion and/or Disable changes and click OK. You should now be able to make changes/delete the application.
Going off what Lucas had said, it will work if you do a .\Administrator, and edit the properties.
The important thing to note here is under the Properties of the COM Object, the Activation tab will be the focus. Try selecting Server Application here. Then under the Security tab, choose Authentication Level to Packet, and impersonation Level to Impersonate.
This should allow you to change anything you want now.
For me, the answer was simple. Login as the local admin. ".\Administrator" then I had no problem bringing up the property pages for the COM+ applications.