Quantcast
Channel: XPages and more
Viewing all 628 articles
Browse latest View live
↧

Quick Domino Tip: Error Failed with no Supported Ciphers

February 3, 2020, 6:07 am
$
0
0
On one of our Domino servers that we upgraded to Domino 10.0.1 last weekend we disabled TLS 1.0. After the upgrade to Domino 10 we performed as always an SSL server test (SSL Labs) from which the reference emerged that the overall rating would be downgraded to Grade B from January 2020. Reason for the downgrade was that TLS 1.0 was still supported by the server. The fact that the Domino server still supported TLS 1.0 also emerged in the Protocols section of test results. Enough reason for us to disable TLS 1.0 on the Domino server. Below is a brief description of how we disabled TLS 1.0 on the Domino server and what problem we subsequently encountered. The starting situation before disabling TLS 1.0 is shown below in the test results.
To disable TLS 1.0 on the Domino server, initially added the parameter SSL_DISABLE_TLS_10=1 in the Domino INI (Configuration Settings - NOTES.INI Settings).

After the addition of the above parameter in the Domino INI next restarted the HTTP task on the Domino server.

> tell http quit
31-01-2020 18:10:15 Domino Off-Line Services HTTP extension unloaded.
31-01-2020 18:10:16 XSP Command Manager terminated
31-01-2020 18:10:21 HTTP Server: Shutdown

> load http
31-01-2020 18:11:08 HTTP Server: Using Web Configuration View
31-01-2020 18:11:24 JVM: Java Virtual Machine initialized.
31-01-2020 18:11:24 HTTP Server: Java Virtual Machine loaded
31-01-2020 18:11:25 HTTP Server: DSAPI Domino Off-Line Services HTTP extension Loaded successfully
31-01-2020 18:11:28 HTTP JVM: CLFAD0330I: NSF Based plugins are installed in the OSGi runtime. For more information please consult the log
31-01-2020 18:12:08 XSP Command Manager initialized
31-01-2020 18:12:10 HTTP Server: Started

The results of the new SSL test were correct after the adjustment,  TLS 1.0 was no longer supported in the Protocols section.
In the Log we ran into the following error message after disabling TLS 1.0 on the Domino server.

TLS / SSL connection IPADDRESS (46638) -> IPADDRESS (443) failed with no supported ciphers.

After opening a case at HCL Support, we were informed that the value in SSLCipherSpec is selected automatically in the Server documents or Internet Site documents or Domino 10.0.1 servers. After the upgrade the notes.ini setting on servers is ignored. To resolve the error messages we have carried out the steps below on the Domino server. Initially the template of the server's names.nsf updated to Template version 10 / 10.0.1.

Next we updated the SSL Cipher settings in the server document.
Open the server document and select Ports > Internet Ports > SSL Ciphers > Modify. Through Internet Site documents select Web > Internet sites > Select/open the internet site document > Security Tab > SSL Ciphers > Modify. We disabled all the WEAK Cipher settings.

Finally we restarted  HTTP task. The error messages in the Log were resolved and the SSL test results were correct. After the above changes we have performed the necessary tests in our Domino environment given older applications or devices may not work anymore when all WEAK Cipher settings are disabled on the Domino server. So please test the changes!
For more information see also the HCL Support document: Failed with no supported ciphers.
↧
Search

Comparing Searches - Domino Query Language for Domino Q & A

February 4, 2020, 3:59 am
$
0
0
In the previous blog posts of this series we looked at the DQL Explorer, DQL and DAS and the Desgin Catalog Administration. Before we continue with the following topics in this series, first in this short blog post some attention to the webinar of HCL from last January, Domino Query Language for Domino V11 in Action, and the associated Questions and Answers. In this webinar, extensive attention is paid to DQL in V11, the new additions for DQL in V11 and the future developments regarding DQL. HCL has made the webinar replay available. For those who have missed the webinar, the webinar can be viewed here. Registration is necessary.

For the questions and answers associated with the webinar see the blog post of HCL, Domino Query Language for Domino v11 in Action. Below the content of the webinar.

With V11, Domino Query Language (DQL) completed its consolidation of all means of searching Domino data, using full-text indices. We will discuss and demonstrate this and other vital enhancements in this session. We will also have workshop problems solved in a Collabsphere 2019 session that will show as Lotus script agent code, so DQL can be seen in action. Lastly, the expansive future of DQL will be presented in some detail in the context of programming models and business problems it can be used to address.

See the new power of searching through DQL in Notes applications with the current possibilities that HCL offers and the future possibilities that are further developed by HCL. A must see!




↧
↧

HCL Notes Domino 10.0.1 Fix Pack 4 Available for Download on FlexNet including Release Notes

February 5, 2020, 8:48 am
$
0
0
HCL Notes/Domino 10.0.1 Fix Pack 4 (FP4) was released Feburary 5th, 2020 and is recommended to all customers. If you are running 10.0.1, apply this Fix Pack on top. 10.0.1 Fix Pack 4 is a collection of low-risk, high-impact fixes to help customers safely avoid known issues. HCL strongly recommends that customers running Notes/Domino 10.0.1 apply this Fix Pack since it addresses a small percentage of defects that impact the broadest set of customers. Fix Packs are released periodically between releases to provide a greater level of stability for customer environments. Fix Packs go through a test cycle to find and fix regressions and interoperability issues prior to release. Fix Packs are always cumulative and contain all fixes from previous ones. Fix Packs are language independent and may be applied on any language version of Notes/Domino 10.0.1x.

10.0.1 Fix Pack 4 Fix List descriptions:

Client
SPR# AGUDAY8GCY - Fixed an issue in the Notes client where a blank tab would be shown after reopening tabs from a prior session.
SPR# AYAVBCWEH4 - Fixed a problem in the Notes client where Three Clicks feature warning was incorrectly being displayed when Drag and Drop from an embedded view to a view.
SPR# AYAVBGUN9Q - Fixed a problem in Notes client on Mac 10.15 Catalina where the Create\Save Attachment dialog does not open. Also fixed issue where Ctrl+O to browse crashes.
SPR# AYAVBH9E9W - Fixed a problem in the Notes client where Notes would crash when JAWS 2019 was running.
SPR# CSMHBHWJAY - Fixed a problem in Notes Client on Mac 10.15 Catalina where notes URL links no longer worked.
SPR# GKSIB6JNHU - Fixed a problem in Mac Mojave client where Sametime AV does not work in meeting rooms.
SPR# JVEKAR6GWT -  Fix an issue with the Notes Client where Drag and Drop of an attachment from Notes to Chrome or Firefox browser would result in a 0 length attachment.  Requires notes.ini Disable_opt_drag_drop=1 to be set.
+SPR# KHORBGLRT8 - Fixed a problem where Eclipse Folders created with a common Eclipse class named iFolderLayout for use in custom plugins deployed to users as Notes Widgets do not display after upgrade to Notes V10 or above.  This regression was introduced in 10.0.
+SPR# MAVAB9CQ6B -  Fixed an issue where the action bar background (white) color turns into a gradient color in Notes Client V10.0.1.  This regression was introduced in 10.0.1.
+SPR# MMNDBEKS4Z - Fixed an issue where some Notes client binaries were missing file metadata.  This regression was introduced in 9.0.1 FP10.
SPR# NBFOBGH67T - Fixed an issue where a specific email message will crash the Client.
SPR# NMMMB6NB2Y - Mac Client - Fixed a problem where the version info for Notes shown in Finder window has 10.0.10 instead of 10.0.1.
+SPR# PALTB75LHK - Fixed a problem in the Notes client where Action Hotspots tied to an image generate an Entry not found in Index error.  This regression was introduced in 10.0.
SPR# PBEEBKPEL7 - Fixed an issue where the Client hangs while running a LS agent.
SPR# RCCYB763FT - Fixed a Mac Notes Client crash when attempting to create a new copy of a database with insufficient rights.
+SPR# RMAAB7ZLQX - Fixed a problem in the Notes client with rich text editor where Hebrew text could not be selected within a table using the keyboard shortcuts.  This regression was introduced in 10.0.
+SPR# SSARBG66H7 - Fixed an issue where the connections plugin for Notes broke the Notes UI  This regression was introduced in 10.0.1.
SPR# SSIRAPUBEJ - Fixed an issue where the Notes Client hangs when running when running spell check on Turkish
SPR# SSPLBGE8JT - Mac Client - Fixed an issue where Notes takes a few minutes to get to the login screen and then another few minutess to get to home page when opening on Mojave OS.
SPR# THIOAX8ENG - Fixed an issue where "Expand All Sections" displays the data of hidden sections.
SPR# TSAOB5N559 - Fixed an issue where JVM is updated to include Japanese New Era fix
SPR# WDCABHFPYM - Fixed a problem where the Rest API was showing the incorrect version information.
SPR# YYLI7VYAXX - Fixed a problem in the Notes client where opening some emails would show the message "Notes has detected and repaired one or more corrupted attachments..." when not expected.
SPR# ZNDNBC8H3E - Fixed a Notes client crash on Windows 10 V1809 whenever the user tried to remotely connect to their machine via Remote Desktop Protocol.

Server
SPR# ARUIBC2M67 - Domino - Support Brazil no longer observing DST in 2019/2020
+SPR# ASHEBK9BZF - HTTP Server - Web site rule with content header Content-Disposition for inline not working. This regression was introduced in 10.0.
SPR# BBSZAD7DZV - Fixed an issue where when an admin chose to delete a database and chose the option to delete all other replicas and did not choose the option to leave a redirect, a redirect was being created. Admin had to manually delete the redirect.  This has now been corrected and no redirect will be created.
SPR# BSPRB7EHEX - Fixed a problem with SCR where it was not honoring the notes.ini RTR_INI_DEFAULT_PORT which tells RTR to use a specific port.  SCR will now also use the same port if the INI is set.
+SPR# BSPRBJ3R74 - Fixed a crash in Domino on startup in RestoreSCRState - OSFileGetToken.  This regression was introduced in 10.0.
SPR# CCAYBHFF5H - Fixed a problem where Compact was causing <dbname>.ORIG file to be left behind
+SPR# CSIOBKPHDX - Fixed a problem where the CKEditor stopped working in web app after upgraded to 10.0.  This regression was introduced in 10.0.
SPR# DCKTBGUNLH - Fixed an issue in Domino where reverting an 11.0 server to 10.0.1 where the 11.0 server was DAOS Tier2 enabled and had at least one database with Tier 2 attachments would result in a panic in dbgroup.c - PANIC: ASSERT(MasterDBG->Offlined || FoundOne)
SPR# EPORBGKQSS - Upgraded OpenSSL to 1.1.1a version
SPR# GFALBFRJAP - Fixed a problem with setting the TIKA_JVM_OPTIONS_OVERRIDE ini variable where the first -D parameter gets concatenated to the built in argument.  Workaround was to add the -D parameter twice.
SPR# JDFUBDPAHP - Domino - Fixed a problem where the Domino mail server would crash when processing a particular message.
+SPR# JKEYBEYGPQ - Messages sent to external SMTP systems that returned a failed Delivery Status Notification used to retain the original sent message id in $MessageID.  Now the original sent message id is in the item SMTPSavedMsgID, even for the case fixed in this SPR, where a mime before new mail agent is defined.  This regression was introduced in 10.01
SPR# JMANBHNKQM -  If Cluster Symmetry (Repair) is enabled, when a person was deleted via the Delete Person dialog in the Admin client with the option "Delete mail replicas on all other servers", if the option "Delete user from the Domino Directory immediately" was also selected, Repair would recreate the mail file from a cluster mate after it was deleted.  This is now fixed so that all replicas of the mail file in the cluster are deleted.  A workaround prior to the fix being installed is to not check the "Delete user from the Domino Directory immediately" option.
SPR# JPAIAX9MZX - Fixed a problem in adminp where the Administration Process was incorrectly processing adminp requests multiple times due to a logic error where the timestamp of the last processing request was not being updated.  This has been corrected.  There was no workaround, although any duplicate requests seen could be deleted.
SPR# JUYYBJK4QV - Fixed an issue where there was an HTTP performance issue due to a lock on a semaphore which had been locked by a thread that did not exist.
SPR# KBRNB9JMLA - Fixed a crash in Domino Server if OSInit failed due to incorrect error path.
SPR# KBRNBAEJHL - Added additional debug to Domino Platform Stats to help when failure.
SPR# MOBNBH3JK5 - Fixed a problem with the Full Text Auto Update feature where it was not always indexing all documents.  Workaround was to set  FT_SUPPRESS_AUTO_UPDATING=0 to disable the feature.
SPR# MOBNBJ6Q3E - Domino LDAP - Provided a debug INI to allow disabling of LSCHEMA loading as a way of avoiding a potential crash in LSchemaTerm. Schema loading is not essential if you have not extended the standard LDAP schema.  Set DEBUG_DISABLE_LSCHEMA_LOADING=1.
SPR# MSKABBBJE5 - The INI ARCHIVE_PRESERVE_ADMIN_SERVER=1 can be set on a server that performs archiving to preserve the admin server of the archive db during an archive operation.  Normally, as part of the ACL being copied during archiving of a mail file to an archive db the admin server will be copied as well.  In cases where a copy of the archive is on the same server as the mail file this is not a problem.  But if there is no archive copy on the mail server, then the archive db will have an admin server that is different.  This situation is not common.
SPR# NRBY9GWJ43 - C&S API: The CalUpdateEntry() API call will now convert a non-meeting into a meeting if the update contains ATTENDEES.
SPR# PALTB3GKJB - Fixed an issue where LSX LC agent running on iSeries intermittently crashed when creating a new LCConnection.
SPR# PKURBA6D76 - Repaircleanup - Removed extra output when running repaircleanup task
SPR# PLYSBDFJVD - MIME -  Fixed an issue where the filename parameter for a MIME part in an Internet email is handled incorrectly and corrupted in certain cases.
SPR# PLYSBDWR94 - Fixed an issue with $MIMETrack item note not including CD-MIME conversion operations.
SPR# RDRABGQMWZ - compact -c -ZU no longer allowed on DAOS enabled databases
SPR# SHJRBGBAWV - Fixed an issue where compact -replica -ren_wait # -Restart was not waiting the specified time prior to doing the restart
SPR# SKSWB83KAP - Fixed an issue where unable to retrieve NotesJSONElement from NotesJSONNavigator.
SPR# SOKEB8WRML - Fixed a crash during transaction undo on a database with nifnsf enabled
SPR# SPPPBF7A9W -  Fixed a problem where an agent was not running from the browser, with the error message on console “HTTP JVM: javax.net.ssl.SSLHandshakeException: java.net.SocketException: Software caused connection abort: socket write error”
+SPR# SPPPBJQJJT - Fixed an issue where design docs (and others) were dropped during compact -replica.  This regression was introduced in 10.0.1 FP3.
SPR# YYUNB2M6PH - Fixed a Domino server crash when doing full text search - PANIC: LookupHandle: handle out of range from GetChar__FP10STREAM_CTXP11STREAM_DATA

For the complete Fix List see the Notes/Domino 10.0.1 Fix Pack 4 Release Notice and Fix List.
↧

Quick Domino Tip: WARNING: Server Certificate Issued to ServerName Will Expire

February 7, 2020, 9:44 am
$
0
0
As you may know we have been using the indispensable Ytria Tools for several years now. We use these tools daily in our Domino maintenance. We use the full EZSuite. Yesterday in the consoleEZ the following message: WARNING: Server certificate issued to ServerName by Certifier will expire on 27-04-2020. Contact your Domino administrator. We had not yet encountered this message in the Notes log files. As every Administrator will confirm the certificate referred to in the warning message is the server.id certificate of the relevant server in the warning message. Below is a brief description of how this can be checked and how the certificate can be recertified.

Administrators can check the server.id for any server using the the Administrator Client by selecting Server > Tools > ID Properties > Certificates to check if the certificates for this ID is already expiring. Sometimes Administrators can't see it in the Server > Security > Certificates > Certificate Expiration Tab if the Server Certificate is already expiring. In certain cases Administrators can only see it in the ID file itself.
Another possibility is always the good old Certification Log (certlog.nsf) database. In the View by Expiration Date Administrators should be able to see if the server certificate is expiring.
So there are several options for Administrators to quickly check whether the server.id actually expires on the specified date in the warning message.
Below the steps to re-certify the server.id. To recertify a server ID Administrators must have Author with Create documents access to the ServerModifier role or Editor access to the Domino Directory or at least Author with Create documents access to the Certification Log.

1. Open the Administrator Client
2.Select the Configuration Tab and select Server > All Server Documents.
3. Select the server you are recertifying.
4. Select the Menu Actions > Recertify Selected Servers
5. Select Supply certifier ID and password.

To change to a different certifier ID select Certifier ID, select the new ID, enter the corresponding password and then select OK.

6. Accept the default certificate expiration date (two years from the current date) or enter a different date.
7. Optional: Enter a date in the field Only renew certificates that will expire before if you want to limit which server IDs can be recertified.
8. Optional: Click the check box Inspect each entry before submitting request if you want to view the server ID before finalizing the recertification.

9. Select OK.
10. Select one of the following options:
OK - to submit the recertification.
Skip - if you are recertifying more than one server ID and you want to continue to the next server ID without submitting a recertification for the current server ID.
Cancel Remaining Entries - to cancel this server recertification and recertifications for any other server names you selected and have not yet submitted.
11. Review the processing statistics that appear and then select OK.

Administrators can check the expiration date of the server.id file on one of the  previous mentioned methods after the recertification process.
↧

Enabling Automatic Dead Mail Processing

February 10, 2020, 6:32 am
$
0
0
We currently work in our production environment with a full Domino 10 environment. Both the server and the clients are currently running on Notes Domino 10.0.1 Fix Pack 4. We have also upgraded the Domino Directory to the corresponding 10 Template and have the mail running on the Mail 10 Template.
At this moment we still have to activate a number of new Domino 10 functionalities on the Domino server. For some of you maybe back in time but for us the current reality as we are very careful with new upgrades and functionalities in our production environment. In this blog post a short review of a previous post regarding one of the new Domino Administrator features, Automatic Dead Mail Processing.
Dead mail occurs when the router can't deliver or transfer a message to the intended recipient or a non-delivery report to the sender. Before Domino 10, if administrators wanted to retry sending dead mail, they had to perform this manually in the Administrator Client. Further dead mail stayed in mail.box until an administrator deleted it. Now in Domino 10 administrators can configure the router to automatically retry delivery of dead mail and if unsuccessful delete it from mail.box after a specified number of retry attempts.
Remark: In other to enable automatically dead mail processing on the Domino Mail server it is necessary to upgrade the Domino Directory to the Domino 10 template.

If automatically dead mail processing is enabled on the Domino server and the router detects a dead message in mail.box the following steps will be performed:
  1. If the allowed number of delivery attempts has been reached the router deletes the dead message and processing ends. If the administrator has set allowed delivery attempts to 0, the dead message is deleted without retrying delivery.
  2. The router attempts to deliver the original message to the recipient. If successful processing ends. Note: Step 2 is skipped when the intended recipient is from an external domain outside of your company.
  3. The router attempts to deliver a non-delivery report to the sender. If successful processing ends.
  4. The router waits the specified retry interval then begins with step 1 again.
Enable automatically dead mail processing on the Domino mail server by following the steps below.
1. Open the Domino directory.
2. Select Configuration - Servers - Configurations.
3. Edit the Configurations document associated with the mail server.
4. Select Router/SMTP  - Advanced - Controls.
In the section Undeliverable Mail select Enabled in the field Automatically process dead mail.

5. Dead Mail delivery attempts
Next in the field Dead mail delivery attempts allowed, enter the number of times to allow the router to try to deliver dead mail before deleting it. Default value after enabling is 12. Maximum value for this field is 1000. The count is maintained across router and server restarts. If an Administrator enters the value 0 in this field there is no delivery retry attempt and dead mail is deleted immediately.
6. Time between dead mail delivery attempts
In the field Time between dead mail delivery attempts enter the number of minutes between delivery attempts. The default value after enabling automatically process dead mail  is 360 (6 hours). The minimum value for this field is 15 and maximum value is 1440 (24 hours).
In case there are mail servers in more than one internet domain within a company administrators can specify each internet domain in the field Internal internet domains tseparated by commas. This field should be blank if there is only one internet domain.

The router logs information about whether dead mail is successfully transferred and when dead messages are deleted. The following show stat commands are available for Administrators.

CommandDescription
Show Stat Mail.Dead.RetryCountNumber of dead messages retried since server startup. For example, if message 1 was retried once and message 2 was retried hree times, count is 4. 
Show Stat Mail.Dead.DeletedCountNumber deleted dead messages since server startup. Dead messages are deleted when Dead mail delivery attempts allowed value has been reached or is set to 0. Deletion also occurs in some error cases, such as when server is unable to determine the address to retry.

For monitoring Administrators can changed the DebugRouterDeadMail setting to 3. This setting let administrators view the dead mail processing logging for each attempt. On the Domino console enter: Set config DebugRouterDeadMail=3.
Furthermore there is another setting that affects the processing of Dead Mail messages. In the Configuration document - Router/SMTP - Restrictions and Controls - Transfer Controls there is a setting for the Expired message purge interval. The default value for this setting is 15. So the first attempt for processing the Dead Mail Messages can be delayed up to the value in the field Expired message purge interval in relation to the setting in the field Time between dead mail delivery attempts.
↧
↧

Upcoming HCL Webinars

July 10, 2020, 12:55 am
$
0
0
It has been some time since I wrote a new blog post. But I am back after a long recovery period and will post more blog posts in the coming period. For starters, there are some very interesting HCL webinars in July that should not be missed. This includes the Domino Volt: The New Release and What It Means for You webinar and the HCL Verse 2.0 Launch webinar. You can register for both webinars. For more information about these webinars, see the notes below and the links for registering for the webinars.


HCL Verse 2.0 Launch
Fri, Jul 17, 2020 4:00 PM - 5:00 PM CEST>
Less clutter, less noise, more secure than ever. Powered by Domino, HCL Verse is a proven and trusted enterprise email platform that empowers business users without exposing your organization to security risks. HCL Verse v2.0 helps you better organize your day and seamlessly collaborate with your teams, allowing you to be more efficient and responsive. Join us to learn about the significant capabilities in the Verse v2.0 release.
Registration is open for this webinar.


Domino Volt: The New Release and What It Means for You
Domino Volt makes it easy to develop powerful, secure, and enterprise-grade applications. As promised, Domino Volt is committed to a continuous delivery cycle and the next release is here! 
This is HCL first big release since the launch and we’ve been hard at work implementing your feedback and requests. We have more than 10 new features and enhancements coming your way, including anonymous access, direct access to Domino data, and out-of-the-box directory services. We’ll also cover the latest integration with Z and I Emulator (ZIE). You will learn of a new solution for IBM z and IBM i customers to turn their green screen apps into REST endpoints that Domino Volt can use to build new workflows and apps.
Register for the webinar as we announce the latest capabilities and why your organizations needs Domino Volt today! Can’t make it on July 30? Sign up anyway and we’ll send you the replay after! 

HCL continues unabated and at an incredible pace and brings a lot of new and requested features into the new releases time after time. Awesome! So don't miss the webinars!
↧

Issue Installing Widgets from Widget Catalog in Notes Client

July 10, 2020, 3:23 am
$
0
0
Within our Domino environment we use various Widgets that users can install from the Widget Catalog. However, when installing the new Tabzilla Widget from panangenda, we ran into a problem with users installing the Widget from the Widget Catalog. Users were no longer able to install the widgets in the My Widgets panel in the Notes Client. After various tests, we opened a case for this at HCL. Below is a brief explanation and the response from HCL. 
For the Widgets we use an Update site database. This database contains all Widgets that we ultimately make available to our users. 


The Widgets are created using Configure a Widget from - Features and Pugins on an Update Site.



Next we publish the Widgetsto the Widget Catalog.



Using the My Widgets Panel users can browse the Widget Catalog and add / install new Widget to the Client. When a users adds a Widget to the My Widget Panel the get an error.



We opened a case at HCL Support (CS0128366). It is a know issue and will review the issue in a future major release. Below the response from HCL regarding the issue with installing Widgets.
This is known issue which has been already reported by several valuable customers like you. We have tested this issue and we have reported it to our product development team under special problem report SPR SPR # VRARBLSBLW. However they will review this SPR in future major releases. Please note that addressing this SPR in future major releases entirely depends upon the development team based upon their review and weightage received on SPR. As of now you can track this SPR in the future releases.
As of now we have a work-around for this issue which might help you to resolve this issue. Please open the below KA and scroll down to the bottom of the page, there you can see two points (Note & temporary fix) for this issue, we would suggest you go-through it and follow the same:-
URL:- https://hclpnpsupport.hcltech.com/kb_view.do?sysparm_article=KB0075847

Remark.
The deployment of Widgets using a policy is working correct. So we are using a Desktop Policy in which Widget Categories can be specified. Also the installation of Widgets works correct with Administrator Access or when the Notes Client is started with Run as Administrator. 



More info about deploying widgets in the blog post Deploying IBM Notes Dictionaries in XTAF format using Widgets by Thomas Hampel.
↧

HCL Verse 2.0 Available for Download on FlexNet

July 13, 2020, 12:51 am
$
0
0
HCL has made Verse 2.0 available on FlexNet today. HCL Verse 2.0 brings a number of new functionalities for users and administrators. For detailed information on what's new see the HCL Verse 2.0 documentation. Below is a brief overview of the new functionalities.
Run Verse as a standalone app. Beginning with HCL Verse 2.0, you can install and run Verse as a standalone browser app that is based on progressive web app (PWA) technology.
Use the new calendar event design automatically. The improved calendar event design introduced as a preview feature in HCL Verse® 1.0.x is now enabled automatically in Verse 2.0. Administrators no longer need to enable the new design.
Find messages created within a range of dates. A new search option lets you find messages created within a specific range of dates.
File sent messages to a folder. Before you send a message, you can choose to file it in a folder. The sent message is saved in the folder in addition to appearing in the Sent view.
Manage mail rules from Verse. You can now create, edit, and delete mail rules from HCL Verse.
Pull down your message list to refresh on mobile devices. On a mobile device, you can pull down your message list and release to refresh the content.
Reauthenticate through a browser page after session timeout. If your HCL Verse session times out, as a security best practice you now reauthenticate through a separate browser page.

Do not forget to register for the upcoming webinar HCL Verse 2.0 Launch on Friday, Jul 17, 2020 4:00 PM - 5:00 PM CEST.



Less clutter, less noise, more secure than ever. Powered by Domino, HCL Verse is a proven and trusted enterprise email platform that empowers business users without exposing your organization to security risks. HCL Verse v2.0 helps you better organize your day and seamlessly collaborate with your teams, allowing you to be more efficient and responsive. Join us to learn about the significant capabilities in the Verse v2.0 release.
Registration is open for this webinar.

↧
Search

Controlling Tabs in HCL Notes

July 15, 2020, 2:19 am
$
0
0
As everyone may know, I make extensive use of the MarvelClient and MCUpgrade for our Notes Clients. MarvelClient is an absolute must for every Domino Administrator. It is by far the best option for simple and fast Domino management including the upgrade of the HCL Notes Clients in a simple, fast and stable way without any problems. panagenda has now released a new plugin for the Tabs management in the Notes Client for users. A must have plugin for every HCL Notes user! panagenda Tabzilla improves tabs control in HCL Notes with a simple and free plugin. Below a short description.



Tabzilla is easy to deploy, requiring no clunky administrative tasks - even in a complex environment. Tabzilla takes only a few seconds to learn. Fewer tabs on your desktop speed access to your apps. As mentioned before everyone in your organization can use Tabzilla absolutely free of charge. It is a gift - without the claws, roars or radiation. Amazing! Tabzilla supports Notes Standard (Eclipse-based) clients, including version 8.5 or higher.

Below are some essential links regarding the installation, how to use panagenda Tabzilla and the associated knowledge base where you can find detailed information and the latest news on panagenda Tabzilla.
- Installation panagenda Tabzilla
- How to use panagenda Tabzilla
- Tabzilla Plugin documentation

Make the life of your users easier and deploy the panagenda Tabzilla plugin today! We did with great thanks from our users!

↧
↧

Notes Domino Ytria EZ Suite Version 16.5.5

July 15, 2020, 6:32 am
$
0
0
In recent years we have made intensive use of Ytria EZ Suite in addition to the panagenda MarvelClient. The EZ Suite Tools allows Administrators to manage every aspect of the HCL Notes and Domino environment. It provides deeper insights than either native alternatives or other tools on the market. Administrators can find problems and overall tendencies in properties and settings that would normally go unnoticed because Administrators can truly see all data. Administrators can also perform a wide range of analysis operations on the Domino data thanks to built-in data manipulation tools such as category groupings, sorting and filters. Also Administrators can use mass-editing capabilities, exclusive edit functionality and more to solve any problems they may find on a large scale without losing the big picture. And much, much more. An absolute must have for all Domino Administrators. Ytria has released a new release of EZ Suite.The Ytria EZ Suite 16.5.5 release includes some small improvements and a host of minor fixes. Keep things running smoothly with this new update. Below a summary of what has changed. And stay tuned for a major announcement as Ytria is putting the final touches on version 20!



EZ Suite - All Products
Fixed a bug that caused the command line Notes.ini to be ignored in some products.
Fixed a bug that prevented use of Notes.ini in command line even if automation (-x) is specified.
Improved the process used for ACL presence check (to accommodate the above fixes in aclEZ and scanEZ)
Fixed a bug that was causing a conflict between EZ Suite product panels and Windows taskbar.
Fixed a bug that caused a copied grid to lose its correct ordering.
Fixed – The ‘Restore all hidden entries’ icon was not being greyed out when no hidden entries existed.
Fixed a bug in all grids that, when exporting to Excel, prevented totals from being exported from the values grid.

databaseEZ
Fixed a bug that sometimes displayed dates incorrectly.
Fixed a bug that caused excessive database reloads when User Activity flag is set to ‘On’.
Fixed a bug when loading a large number of databases that could cause a crash due to infinite recursion.

aclEZ
Fixed a bug when checking alternate names extended NAB vs. check presence. This could occur when using products in languages with special characters not recognized by the English alphabet (Japanese, Chinese, etc…)

agentEZ
Fixed – The ‘Edited’ status icon would not appear beside a scheduled agent even after restoring the saved agent properties.
Fixed a bug that caused partial load to take a very long time to process, during which time no user action could be taken.

consoleEZ
Fixed – The Server Tasks were not properly removing hidden rows when refreshed, causing the grid to be overburdened.

scanEZ
Fixed crash when using ‘Export All Attachments…’ with ‘Copy Document links’.
Fixed crash when using ‘Export All Attachments…’ with ‘Copy/Move Documents to Multiple Databases’.
Fixed a bug when using Restore of Soft Deletions from within the Deletions Stub Explorer (as opposed to from the selection tree) that caused extremely long process times.
Fixed a bug when checking alternate names for extended NAB vs check presence. This could occur when using products in languages with special characters not recognized by the English alphabet (Japanese, Chinese, etc…)
Fixed – The Summary Data Size column was not properly populated in the Document Analyzer when using the ‘Sum of Summarized Item Data’.

replicationEZ
Improved the ‘Create new replica’ process. Now includes additional default design elements.
Fixed – When clearing the replication history, clicking on Cancel failed to stop the process.

Automation
Fixed the ModifyItem tag which was preventing the proper handling of user input dialogs.
Improved – added the option to execute an automation file on another EZ Suite product using one instance for each database.

Administrators, update to the latest Ytria EZ Suite release and keep your Notes Domino environment running smoothly as ever.
↧

Installing Notes Widgets Using MarvelClient

July 16, 2020, 4:16 am
$
0
0

Within our organization we use Widgets that users can install from the Widget Catalog. As indicated in my previous blog Issue Installing Widgets from Widget Catalog in Notes Client, there is currently an issue with installing Widgets from the Widget Catalog. Based on this blog post, Florian Vogler pointed out to me that it is also possible to install Widgets using the MarvelClient. In this blog post an example of installing the Tabzilla plugin using the MarvelClient. You must have a MarvelClient license that includes Eclipse plugin install functionality. If not it is an absolute must to have a licensed Marvel Client if you are a Domino Adminstrator.

In our organization we make the Widgets available to all users. For the installation of the Tabzilla plugin from panagenda we use an Update Site database on our Domino server. If no Update Site database is present on the Domino server a new Update Site database will have to be created. Using File - Application - New a new Update Site can easily be created. The Eclipse Update Site template must be used for this. Select the Show advanced templates box to see the Eclipse Update Site template.


Download the Tabzilla plugin from the panagenda site. Next unzip the Tabzilla zip file on a selected directory on the hard drive. After the Tabzilla file is unzipped ad the plugin to the Update Site database, selecting the Import Local Update Site button and browse to the site.xml file in the folder the Tabzilla plugin is unzipped and select OK.


Next the URL of the Update Site database is needed for the following steps. Select the menu item Actions - Show URLs. This will show you two URLs.
HTTP URL which can be used to access the Update Site database via HTTP
NRPC URL which can be used to access the Update Site database using the native Notes client protocol
If using the HTTP URL the Domino HTTP task must be active an running on the Domino server.


Once the Tabzilla plugin is in an Update Site database the final step is the installationusing the MarvelClient. As mentioned before you must have a MarvelClient license that includes Eclipse plugin install functionality. Select Eclipse - Eclipse Plugin Install/Uninstall.


The following setup can be used in the action document:
Install type: Expeditor Provisioning
Show progress: unchecked
Check signature: unchecked
Allow restart prompt: unchecked
Enable immediately: checked
Update site: the URL from your Update Site database in the previous step
Which feature(s): A single feature (Update Site Database - Open Plugin - Select Tab Manifest)
Feature ID: com.panagenda.tabzilla.feature
Feature Version: Get feature version from update site
Widget Name: Use name of first installed feature
Certificate: checked
Widget: unchecked


A very powerful and easy way to install Widgets in the Notes Client. As mentioned before, MarvelClient is a must have for all Domino Administrators.

↧

Domino 11.0.1 Agent Manager Problems

July 17, 2020, 2:25 am
$
0
0

Our Domino production environment runs on a Domino 11.0.1 server. In general, the 11.0.1 release is very stable, however we have been experiencing some problems with the Agent Manager in Domino 11.0.1 for several weeks. These issues emerged in the Domino Domain Monitoring application in which the following messages appeared daily, Server task Agent Manager on ServerName is no longer responding [GRAN-5M3AE3]. In the Event Change History in the Domino Domain Monitoring application the AMGR task restores itself. The message Server task Agent Manager on ServerName is no longer responding [GRAN-5M3AE3]. opens and closes itself several times a day. Based on the persistent reports in the Domino Domain Monitoring application, we eventually opened a case at HCL with the priority high.

HCL Support took up the case very quickly and the problem was further analyzed through multiple web meetings including screen sharing and sent console logs including manual generated nsd files. The first cause was found very quickly by HCL in a number of ODBC connections that no longer worked correctly regarding the import of data from external applications. As a result, the Agent Manager completely collapsed and could only be restored by a full restart of the Domino server. However, after modifying the ODBC connections the message Server task Agent Manager on ServerName is no longer responding [GRAN-5M3AE3] continued to appear in the Domino Domain Monitoring database. 

In order to further analyze the Agent Manager, at HCL's request we enabled all the debug parameter regarding the Agents manager on the Domino server using the console command Tell amgr debug *. Tell Amgr Debug displays either the current debug settings for the Agent Manager or let Administrators set new ones. When using this command to set debug values Administrators can use the same flags used by the Debug_AMgr command in the NOTES.INI file. These settings take effect immediately, there is no need to restart the Agent Manager or the server. The Tell Amgr Debug parameters Administrators can use are:

CommandResult
cTo output agent control parameters
eTo output information about Agent Manager events
lTo output loading reports
mTo output agent memory warnings
pTo output agent performance statistics
rTo output agent execution reports
sTo output information about AMGR scheduling
vVerbose mode, outputs more messages regarding agent loading, scheduling and queues
*To output all of the information in the parameters

The probable cause for the problem with the Agent Manager is also further analyzed by HCL, the task is not updating its timestamp because it is either waiting for a resource to become free or it is executing time intensive functionality. For now there is no solution for the messages in the DDM, but the Agents are running on the Domin server again. I will update this blog post if there is more information and a solution to the problem.
I wonder if this problem only occurs with us or if multiple organizations have found the same problem in Domino 11.0.1. 

Much respect for the way in which HCL tackles the problems and how they are systematically analyzed through console logs, nsd files and web meetings including screen sharing for further viewing different settings on the Domino server and in the applications themselves.
To be continued....

↧

HCL Notes SwiftFile

July 22, 2020, 12:27 am
$
0
0

Recently we have extensively tested HCL Notes 11 and HCL Notes 11.0.1 in our test environment prior to upgrading the clients in the production environment. We are impressed by HCL Notes 11, the new functionalities and the new look and feel. In the coming blog post a number of new functionalities that are included within HCL Notes 11 and that we will certainly use or activate for our users. The first new functionality is Swiftfile for HCL Notes. SwiftFile assistant is integrated with HCL Notes in 11.0.1. In previous releases it was provided separately.

SwiftFile is an intelligent assistant for HCL Notes that helps you organize your e-mail into folders.
SwiftFile uses a text classifier to learn your mail-filing habits. SwiftFile uses the model it learns to predict the three folders into which you are most likely to place each incoming message. The predictions are presented to you as three shortcut buttons that allow you to quickly file each message into one of the predicted folders.

Swiftfile must be activated in the Notes Mail preferences. The steps below can be followed.
Start HCL Notes if it is not already running.
  • Open the personal mail database.
  • Select the menu item Actions - More - Preferences.
  • Select the SwiftFile preferences tab.
  • Select Enable SwiftFile.
  • Optional: To enable SwiftFile logging select Enable SwiftFile logging. This will turn on a log of all SwiftFile activity that is useful in diagnosing SwiftFile problems and bug reports.
  • Select OK.

SwiftFile must be activated for each replica in which SwiftFile should be used. In particular, if you are using a local replica of your mail database, you may want to enable SwiftFile for both the local and server copies of your mail database.

Using SwiftFile is easy. Whenever a message is opened, SwiftFile will add three shortcut buttons to the top of the message that represent SwiftFile's best guesses as to where to file the message. If one of these buttons is correct, click on that button and SwiftFile moves the message into the selected folder. If none of SwiftFile suggestions are correct, simply file the message using the regular HCL Notes interface for filing messages.
SwiftFile learns about your mail-filing habits by analyzing your previously-filed documents and by watching over your shoulder as you file new messages. This learning takes place in the background and starts as soon as you enable SwiftFile for the current mail database. SwiftFile's learning algorithm is very quick. For most users, SwiftFile can learn to predict where you would like to file the messages in your Inbox after just a few seconds of training. For some users, SwiftFile may take a few minutes of learning before it can make reasonable predictions. Please give SwiftFile a few minutes if you find that its initial predictions are not useful.


The integration of SwiftFile in the HCL Notes Client is a very welcome functionality for the users and easy to enable or disable.

↧
↧

HCL Notes Three Click Support

July 22, 2020, 3:48 am
$
0
0
In my previous blog post, HCL Notes SwiftFile, I started by briefly describing some new functionalities in HCL Notes 11. Some of these functionalities need to be specifically enabled through settings in the preferences or by adding new parameters in the notes.ini file. A new level of security in HCL Notes 11 can be added using the new Three Click Support functionality. This functionality must be enabled through a notes.ini setting. Below is a brief description of this functionality.
Three click support adds a level of security when a user opens an attachment within an email. The Open-Save-View dialog box still appears after a user double clicks an attachment. When three click support is enabled the user will then be prompted to confirm the action they have chosen in a second message box.
To enable three click support administrators need to add EnableThreeClicks = 1 to the notes.ini settings. The new parameter can be included in a Desktop Policy for all users or can be added to the notes.ini files of all users via the MarvelClient. Below is a brief explanation of both methods.

To add the new notes.ini parameter using a Desktop Policy the steps below can be followed.
  • Open the Domino Directory.
  • Select Configuration - Policies - Settings.
  • Select the Desktop Policy document.
  • Select the Tab Custom Settings.
  • Select the Action Button Edit List.
  • Add the new notes.ini parameter.
  • Select the Action Button Add/Modify Value.
  • Select OK to save the new settings.
The new notes.ini parameter will be added to all notes.ini files in this way.
The MarvelClient can also be used to add the new notes.ini parameter. The procedure is very simple using the steps below.
Open the MarvelClient Config database.
Select the Menu Option Mavelclient - All Actions.
Select Objects - A5 *ini & Variables
Add the new ini parameter as shown below in the Actions document.
It is advisable to enable this new functionality using the new notes.ini parameter for an extra layer of security for the attachments. In the following blog posts more new settings and functionalities for HCL Notes 11.
↧

HCL Notes Changes to Attachment Viewing and Importing

July 23, 2020, 12:38 am
$
0
0
HCL Notes 11 in a very stable and modern Notes Client. As mentioned before HCL added a number of new functionalities and a number of changes in this version. In this new short blog series about the new functionalities and changes in HCL Notes 11 in this blog post a short overview about the changes for viewing and importing attachments in Notes 11. See also the previous bog posts in this series HCL Notes SwiftFile and HCL Notes Three Click Support. 
For viewing and importing attachments the underlying software that Notes uses to import and view attachments has changed in 11.0.1. When viewing an attachment in 11.0.1 the attachment is shown in an external browser rather than within Notes. The following table compares the types of attachments that can be viewed in Notes 11.0.1 compared to earlier releases. 

Table 1. Types of attachments that can be viewed in Notes 11.0.1
The following table compares the type of attachments that can be imported in Notes 11.0.1 compared to earlier releases.

Table 2. Types of attachments that can be imported in Notes 11.0.1
In the next blog post more about the new features and changes in HCL Notes 11.
↧
Search

Upcoming HCL Webinars

July 23, 2020, 1:48 am
$
0
0
Again there are some very interesting HCL webinars in July and August that should not be missed. This includes the Domino Volt: The New Release and What It Means for You webinar, the HCL Domino: Next Generation Monitoring webinar and the HCL Connections Getting Projects Done on Time with Connections and Kudos Activities Plus webinar. You can register for these webinars. For more information about these webinars see the notes below and the links for registering for the webinars. If you want to stay informed of the latest developments register today even though you may be on summer vacation, the link for the replay will be sent to you.
Domino Volt: The New Release and What It Means for You
Domino Volt makes it easy to develop powerful, secure, and enterprise-grade applications. As promised, Domino Volt is committed to a continuous delivery cycle and the next release is here! 
This is HCL first big release since the launch and we’ve been hard at work implementing your feedback and requests. We have more than 10 new features and enhancements coming your way, including anonymous access, direct access to Domino data, and out-of-the-box directory services. We’ll also cover the latest integration with Z and I Emulator (ZIE). You will learn of a new solution for IBM z and IBM i customers to turn their green screen apps into REST endpoints that Domino Volt can use to build new workflows and apps.
Register for the webinar as HCL announces the latest capabilities and why your organizations needs Domino Volt today! Can’t make it on July 30? Sign up anyway and we’ll send you the replay after! 
HCL Domino: Next Generation Monitoring
In this webinar, HCL has teamed up with CYONE to share how Domino administration and business application monitoring can be automated with an onPrem monitoring solution.
Monitoring allows organizations to predict problems in advance and fix them before they impact your business or even automate a problem resolution. We provide over 700 metrics out-of-the box to ensure that your Domino environment is always in its best shape. Servers are monitored 24/7 and verified when statistics are in range of good values, and if not, you will be notified with a proposed solution from our built-in knowledge base. Deployed professional monitoring can save on average 30-60 minutes of an administrators time per server per day.  
Registration is open for this webinar.
Getting Projects Done on Time with Connections and Kudos Activities Plus
Project coordination is an integral component of employee collaboration for aligning resources, tools and knowledge to achieve common goals. HCL Connections v6.5 delivers Kudos Activities Plus with an advanced toolset to make managing tasks easier. Join our webinar to learn how Connections and Kudos Activities Plus can help you achieve on-time delivery for your projects.
Registration is open for this webinar.

HCL continues unabated and at an incredible pace and brings a lot of new and requested features into the new releases time after time. Awesome! So don't miss the webinars!
↧

Unable to read rollover values from view.Vault 'CN= XX/OU= XXX/O=XXXX'. User '/ID Vault

September 14, 2020, 12:32 am
$
0
0

Recently we have had a number of messages on our Domino server of which the cause could not be traced. One of these messages was the message Unable to read rollover values from view.Vault 'CN = XX / OU = XXX / O = XXXX'. User '/ ID Vault. The message is continuously displayed in the Domino Domain Monitoring database. It concerns a failure in the security access. In the DDM there is no additional explanation or help available for this event. Based on this, I opened a case at HCL.

The HCL product development team has confirmed that Domino is working as currently designed. It is not a critical message, just informative that the user is not currently in the process of key rollover. Based on my case, HCL has created SPR # NBALBTCK4V and corresponding AHA request: Unable to read rollover values from view.Vault 'CN = XX / OU = XXX / O = XXXX'. User '/ ID Vault. 

The customer sees errors 'Unable to read rollover values from view. Vault 'CN=XX/OU=XXX/O=XXXX'. User '/ID' being logged into the DDM.nsf throughout the day, for several users.During Vault sync, the Domino server checks if the user is in the middle of key rollover and looks for these items on the user Vault entry. 'ActiveKeyWidth', 'ActiveKeyCreated', 'PublicKeyHash', 'KeyGenState', 'LastCertReq', 'AliasHash'. If the code does not find them then it logs a message that the rollover values were not read. It is not a critical message - just informative that the user is not currently in the process of key rollover. Domino is working as currently designed. However, we would request to limit the trace message, as Customer sees these message getting logged throughout the day & suspect there is a problem.

Please vote for the AHA request.


↧
↧

Delete Notes Users Using AdminP With New INI Settings

September 16, 2020, 4:35 am
$
0
0

Yesterday, Vladislavs Tatarincevs published a great blog post on preventing the removal of users who left company from Reader and Authors fields and NAMES fields when using the AdminP process. For many Administrators, this was the main reason for not using the AdminP process when removing Notes Users. The blog post refers to two new Domino INI settings that can be added in the configuration document in the Domino Directory. This includes the ADMINP_DISABLE_NAMEITEM_DELETE = 1 and the ADMINP_DISABLE_READAUTH_DELETE = 1 setting. I added these settings in our test environment and then restarted the AdminP tasks on the Domino server. Finally, based on the new settings, a users removed from the Administrator Client.

Initially added the new Domino INI settings in the configuration document in the Domino Directory (Domino Directory - Configurations - Servers - Configurations - Edit Configuration - NOTES.INI settings).


Next restarted the AdminP task on the Domino server (tell adminp restart). Finally deleted a user in the Administrator Client.


After deleting the users in the Domino Directory, the actions below are created in the Administration Request application. See also the HCL Technote'Delete Person in Domino Directory'.
Finally all AdminP tasks performed on the server.
> Tell Adminp Process All
16-09-2020 12:51:25 Admin Process: Checking for all requests to perform
09/16/2020 12:51:33 PM USERNAME does not appear in the unread lists of the databases on SERVERNAME.
09/16/2020 12:51:33 PM Admin Process: USERNAME does not appear in design elements of any databases designating SERVERNAME as their Administration Server


The Delete in Readers/Authors fields is created in the Administration Request application but is no longer executed by the new INI settings. In several Notes applications checked whether the deleted user still exists in the Reader and Authors fields as well as in the NAMES fields. The user has NOT been removed from these fields based on the new settings.
Please test it for yourself in a test-environment before put it in production.
Finally a solution for an old problem when removing users via AdminP!
Thanks HCL for a solution to a centuries-long problem. Very happy Administator!

For more information see the HCL Technote What does the Domino Servers notes.ini parameters "ADMINP_DISABLE_NAMEITEM_DELETE = 1" and "ADMINP_DISABLE_READAUTH_DELETE = 1" contribute in the Adminp deletion process?

↧

Enable Notes AutoSave using MarvelClient

September 17, 2020, 5:03 am
$
0
0
Autosave is one of the many nice features in Notes. Autosave can create a copy of recent work done in Notes. If your computer crashes by any reason this feature will save a copy of your latest work. With the help of that copy you can easily recover your data. AutoSave allows you to save your documents automatically after a fixed interval of time. This time interval can be set by a desktop policy setting or a MarvelClient INI & Variables action document. The most current version of the document is saved to an Autosave database in your Notes data folder. If you by mistake close the Notes application improperly or somehow the Notes client crashes your data will always be saved. Autosave provides safety and security by data encryption. Within our organization, we have for the most part abandoned policies and use MarvelClient for these settings, including the NOTES.INI settings in addition to other settings.

To enable AutoSave using MarvelClient follow the steps below.
1. Open the MarvelClient Config applicatie
2. Select MarvelClient - All Actions
3. Form the Menu select Objects - A5. ini & Variables
4. Enter the INI settings in the action document as shown below.
5. Save and Close the Action Document.

After the restart of the Notes Client the new INI settings are activated in the Notes Client by the action document in the MarvelClient.
With the new settings users can recover autosaved documents immediately upon startup. At startup after a crash or power loss, and after a user logged, the user will be prompted to recover their unsaved work with the message "You have x unsaved document (s). Do you want to recover these documents now?"
If the user selects Yes the Recover Unsaved Documents dialog box appears that lists the documents that can be recovered.
From the Recover Unsaved Documents dialog box the user has the following options:
Recover - recover the selected document
Recover All - recovers all documents without prompting for each one
Remove - removes the selected document from the Autosave database
Remove All - removes all documents from the local database
Alternatively users can select No at the recovery prompt and recover the autosaved documents later by selecting File - Autosave - Recover Autosaved Documents. 
The Recover Unsaved Documents dialog box appears and you can recover or delete documents as described previously.
Once a document has been recovered from the AutoSave database, it is automatically removed from that database. 
This helps keep the Autosave database from becoming too big.
Occasionally users may be in the middle of editing a document and need to save the document immediately. Users now have the option of saving the current document to the AutoSave database by selecting File - AutoSave - Autosave Now. 

Remark: For Autosave to work in Notes applications Developers should enable the Form property Allow Autosave. Make sure to test the forms in their applications with Autosave to ensure that Autosave works properly with the application! For more information about Autosave see Autosaving Notes documents.
↧

Notes ID Vault Problem

September 18, 2020, 6:32 am
$
0
0

We are currently rolling out the latest Notes 11.01 Clients including Fix Pack 1 using the MarvelClient MCUpgrade. Next week a new blog series will be launched on how to perform a super fast, flawless upgrade of the Notes Clients with MCUpgrade. The best solution on the market. However, after the upgrade to Domino and Notes 11.0.1 Fix Pack 1, a strange problem has arisen in the ID Vault application. 
The Notes ID vault is an optional, server-based application that stores protected copies of Notes user IDs. An ID vault allows administrators and users to easily manage Notes user IDs, reducing user downtime and help desk costs. Users are assigned to an ID vault through policy configuration. Copies of user IDs are uploaded automatically to a vault after the policy takes effect.
Below is a brief description of the problem we are currently seeing in the ID Vault application.  

Basically, the ID Vault works as follows. A user ID can be uploaded to a vault only if two conditions are met. First, the parent certifier of the user ID must issue a Vault Trust Certificate. Second, the user's effective policy must have a Security Settings document that specifies the vault name. The Vault Trust Certificate certifies that the parent certifier trusts the vault. When a user changes the ID on a Notes client, for example changes the password or adds an Internet certificate, the change needs to be pushed to the ID copy in the vault. When a change is made to an ID copy in a vault, for example the password is reset, the change needs to be pushed to the Notes client.

For most of our users this works correct. However, in certain cases, something goes wrong when synchronizing the IDs located in the Notes Client with the Vault copy. We see with multiple users that one or more tildes (~) are placed before the name in the ID Vault application (Field IDOwner). This results in the following error message in the Domino Domain Monitoring application.
ID failed to authenticate in vault 'O = ID Vault'. 'USERNAME / XX / XXX' (IP address XXX) made request. Error: Entry not found in index.

We opened a case with HCL Support who has been reviewing the issue for the past week. Unfortunately up to this point no cause has been found for the problem and there is no solution yet. Is anyone familiar with the problem? Any help is welcome. We alredy performed an updall -X -R on the Vault applicatie and performed a fixup, compact and updall on the Domino Directory (names.nsf). For more information see also the HCL Technote How an ID Vault Works.
↧
Viewing all 628 articles
Browse latest View live
Search