On my server I upgraded VoP to 1.0.5 and Traveler stopped working.
Looking at the console there were no errors but the devices could not connect to the server anymore; opening https://server/traveler gave a 404 error.
In order to test I reverted back to VoP 1.0.4 and Traveler started working again, then I upgraded to VoP 1.0.5 again and Traveler stopped working again.
The solution I found is to install first VoP 1.0.5 and then reinstall Traveler, when I did that everything worked again, now I have VoP 1.0.5 and Traveler both up and running.
I upgraded my databases to ODS 53, and ICAA 1.0.2 stopped working.
When I launch it I get those errors
Solution: I had to upgrade to ICAA 2.0 and then everything worked.
I received this today from IBM
Congratulations! You’re a Domino 10 Ready Partner!
I am pleased to announce that you have met the criteria to be one of the first IBM Business Partner organisations to be awarded “Domino 10 Ready”.
You’ve achieved this either by having employees who have passed the Domino V10 Sales Advisor exam or by being nominated by IBM for your fantastic support for Domino V10.
You can find it on Fix Central. It fixes the following bugs
|Fix introduced in release
||SPR / JIRA Defect Number
|Verse On-Premises 18.104.22.168 Interim Fix 1
||Some contacts or groups may be missing in typeahead search result in delegation setting or delegation panel
||Verse could not open mail databases with DBCS file name
||Domino hotfix 901FP10HF292 is also needed to fix this problem.
||Notes.ini setting ‘VOP_UseNotesIDForDisplay’ does not work
||Verse will not generate mail path for data requests if the entry url of Verse has a prefix
I will speak with the lovely Sharon Bellamy James at ICONUK 2018 which is in Birmingham Sept 13-14.
Our Session will be on troubleshooting IBM Connections
I will speak with my friend and guru Martti Garden at Social Connections 14 which is in Berlin Oct 16-17.
We will show how to install step-by-step IBM Connections Component Pack, i.e. the Pink components.
At DNUG 45 Danielle Baptiste, Director of Offering Management, has given a presentation on the Connections Roadmap. Here are the most important news announced.
In a future Cumulative Refrash will be introduced new UI for Files, Communities and Notifications
Files UI now is this, defaults to My Drive
In the future the UI will be this, defaults to All Files
There will be the possibility of searching for keywords in file names
For Communities the actual UI is this
and the future one is this
Also here there will be the possibility of filtering by keyword
For notifications, the actual UI of the Newsletter is this
And it will change to this
Let’s talk about PINK now.
In a while will ship the new version of Component Pack 22.214.171.124, and the big news is that it will not contain anymore IBM Provate Cloud, also known as Conductor for Containers. This because IPC has grown bigger and bigger and getting rid of it will make the architecture simpler. The downside of this is that now we have to install Kubernetes manually before installing CP 126.96.36.199 .
The next PINK service that will be released is the People service, which is a big enhancement to the actual Profiles. Here are some screenshots of what it will look like
At Engage Barry Rosen from HCL and Drew Birnbaum from IBM gave a session on the future of VoP.
There will be a new release before V10, in the July-August timeframe
Here are the features planned
The there will be a V10 version when Domino 10 ships, these are the planned features
Then there will be a series of continuous releases between V10 and V11. These are the features planned for the first post V10 release. Number 1 is the ability of importing ics files
I have the honor of being selected as speaker for DNUG for three years in a row. This year I will be speaking about troubleshooting Connections.
My session will be June 20 at 14.35
You can see the agenda of the DNUG event here
This happened to me and to a customer. When moving our server to a different machine I forgot to move the credstore.nsf database; while my customer simply did not create it.
In both cases VoP was showing the email correctly but the calendar was empty; as soon as we fixed the issues, moving and creating the db, the calendar started working perfectly.
I have no idea of the relationship between the credential store database and the Verse calendar, but the fact is that without the db the calendar will not work.