I had worked on an agent for 2 days and was testing.
I enambled security on the agent.
Set the default acess for who can view and run this agent. When I tried to save, I received some mumbo jumbo error message, I could not save the agent. And on top of that, the agent was deleted.
A lotuscript agent.
The 8.5.1 eclipse designer and client is an Amateurish IBM product and has simply too many issues to be on the market.
I would expect this from Microsoft and appears that IBM is joining the club.
Subject: Solved
Error message:Agent Script Content Save Aborted.
Reason:
a 0 (zero) noteid would have been passed into IPC_ACTION_STATE_SAVE_CONTENTS in LSEDTIPC.dll.
Save could not be completed.
On further reflection I decided to check whether or not removing myself from the role before making the change to the security setting would allow me to make the change and save.
I added me (the designer) back to the role, opened designer to the agent section and lo and behold there were my deleted agents.
Both the original and the copy that I made when I started my modifications.
The agent was not deleted, only hidden. changing the property to only allow members of the group to view and run the agent apparently hides the agent even in designer.
And even though I was being told my the error message most emphatically that the agent could not be saved, it apparently was saved. And the saving of the agent with the property change hide the agent from me because I was no longer a member of the role.
Adding my name back to the role allowed me to see the agent in designer.
IBM should be more professional and provide better error messages.
This event took me most of the afternoon to trouble shoot and resolve.
Come on IBM, you can do better.
Subject: Great thanks!
I’ll do up an SPR tomorrow for it and tech note. Cheers.
Subject: created SPR SODY85FFBT
And tech note submitted.
Subject: Help us help you.
Hi,
Can you print more details? Like the exact error message or exact steps to reproduce the issue?
Subject: Some 40 character java exception message
Now that the agent has been deleted, most likely not.
My question and complaint is why can’t IBM handle these errors better. How about a more professional message one that informs a user on what to do.
The result of this issue was my agent was deleted from the database!
And just now while trying to open a mail file from the administrator, i had to simply force notes to close because the opening of this mail file was more than notes could handle.
Completely unresponsive!
Subject: Can you remember anything at all?
Even part of the message? Did the client crash and then the agent was gone? Or was it just a pop up message then the agent was gone?
If it was a pop up message, can you remember anything at all about it?
If it was a client crash then an NSD would of been generated in the IBM_TECHNICAL_SUPPORT folder. Can help in diagnosing the issue here.
Also do you know the exact version of Notes Designer you were using? Is it installed on top of another client previously?
Subject: is it possible…
…that you removed the rights for yourself to see the agent? Perhaps it is not deleted, but you can’t see it?If you could describe the security changes you have made it might help us to give you additional suggestions.
Not knowing what you changed and who you gave access to, I have two suggestions:
(1) ask someone who has the rights of a full administrator to look at the database, see if the agent is stil there and undo the changes you have made to security.
(2) You can try a tool like Notespeek that would allow you to see the database and look at design elements (agent has an icon of a lightbulb) and see if you see your agent. You can’t make changes through this tool, but you can see if the agent is still there to verify my theory
Subject: In 8.5.2 this seems to be causing design element corruption
I ran across this little ‘feature’ today. I created a new role in my template and tried to restrict the agent access to the new role when I got the error message, presumably because I didn’t have the role myself. This caused the agent to disappear from the design element list. I assumed it had deleted itself so I recreated it, but got the same problem and the agent disappeared again. Not only that, but an agent I hadn’t even been editing also disappeared. When I refreshed the design of the live database from the template, I found that there were several copies of the agent now in the live database.
I used NotesPeek to see what was going on in the template and sure enough, there were several copies of the agent in there which I couldn’t see using Designer. I tried using GetDocumentByID with the note IDs that NotesPeek showed me to get a handle on the rogue agents to delete but it couldn’t get a handle on the notes that way. I also tried using a NotesNoteCollection and although it found the agent notes, using GetDocumentByID with the note id from the collection wouldn’t return a note object for me to remove.
I tried using fixup and compact but this didn’t make a difference. In the end, I found that either creating a copy of the database gave me a version without the corrupted agent notes, or overwriting my replica of the template with one from elsewhere also worked. Unfortunately I was never able to get the original agent back, but luckily in my case it was only a couple of lines of code referring to a function in a ScriptLibrary so not much was lost. I could have been in a very bad way if all of my code had been in the agent rather than the script library.
I tested this in a separate database using the following steps:
Create a new role in the ACL
Create a new agent.
Give the agent a name and save it
Confirm the agent is in the design list
Go to the agent Security properties, uncheck ‘All readers and above’ for ‘Default access for viewing and running this agent’ and check the role created in step 1
Click save
Enjoy the exciting error message which appears
Close your agent and confirm that it is now missing from the agent list
Use NotesPeek to see that the agent does exist but is invisible in Designer
IBM have technote about this (https://www-304.ibm.com/support/docview.wss?uid=swg21431216) but it doesn’t apply to 8.5.2 and claims only to be an unhelpful error message, it doesn’t mention the corruption problems. I’ve submitted feedback on the technote but have no other way of reporting how the bug differs in 8.5.2
For reference, the full text of the error message is:
Save could not be completed.
Reason:
A zero note ID would have been passed into IPC_ACTION_STATE_SAVE_CONTENTS in LSEDTIPC.DLL. Agent script content save aborted
Emily
EDIT: I can confirm that if you already have the role BEFORE you open the database for editing, you don’t get the error message, the agent saves successfully and nothing gets corrupted
Subject: Upd
Hello, I must add that if transferred to the production database they become visible in actions menu and can scare users(of course if agent starts via action menu selection).And for me the role in the ACL were created long time ago before I changed security access to this role(Notes 8.5.2)