After 5 years and 150,000 miles, the Shifter Switch on my 2014/15 Mazda CX-5 began to fail. The symptoms include the accessories failing to turn off even after turning off the ignition. The console displays, “Set Shift Lever to “P”” even though the car is already in Park. The console may also display, “Set Power to OFF.”
I found the solution in TSB NUMBER: 05-004/16 – MULTI-MODEL – IGNITION DOES NOT TURN OFF WHEN PRESSING START / STOP BUTTON
The issue is caused by a worn shifter switch unit. To eliminate the problem, the switch unit material has been redesigned to improve wear resistance. Modified switch units have been established as new service part: KDYO-46-040.
I paid almost $100 US for this part from a dealership, however, I’ve seen the OEM part for half that on Amazon > Genuine OEM Mazda KDY0-46-040 SWITCH
Here is how to replace the unit on a CX-5:
NOTE: This issue can also occur for a Mazda 6 but the access panel is part of the front console instead of the rear console.
Minimum tools required:
Flat-head screwdriver (or similar flat tool) to pry apart plastic parts
Approximate Project Duration:
- Loosen the Rear Console Cover by removing the screw covers and screws on the back of the console (both sides). The screw covers are the round shape shown here.
- Remove the trim around the shifter by gently prying up. (See the area where the green plastic pry tool is inserted.)
- Here is how things look after the trim is placed to the side. Note that I didn’t need to disconnect the plug.
- You may choose to loosen further pieces. The ultimate goal (see step 6) is to get to the two silver screws that hold the switch unit in place. I decided to remove the shifter knob by unscrewing it. I also removed the metal brace (indicated by the thin red line and held in with two FLAT END black screws). Finally, I removed the “Pointy End” screw that was holding the console pieces together.
- Detach (4) four hooks (A) (2 hooks shown below) by gently prying with a flat screwdriver Then, at least pull up to loosen (if not fully removing) the set plate assembly (B).
Example of using screw driver to gently pry one of the hooks:
- Remove the two silver screws (A). Then, while pushing the stopper (B) down, remove the switch unit (C) by pulling it towards the driver’s seat. Be careful to keep track of the Shifter Lock Mechanism (and it’s tiny spring). It also pulls directly off a shaft (indicated by the red circle) towards the driver’s seat . Take careful note of it’s positioning prior to pulling things off so that you know how to properly replace it.
Shifter Lock Mechanism close-up
- Disconnect the switch unit connector and then install the new switch unit in reverse order of removal. NOTE: Use the new screws that came with the new switch unit.
- Re-install other parts in the reverse order of removal.
- Fresh Install of Domino 10.0.1 FP2 on CentOS 7
- Fresh Install of IBM Lotus Notes Traveler 10.0.1.1 Build 201901271808_20
HTTP starts, but only after Traveler fails with various errors including:
- WARNING: Xsp Initialization error – Could not load class or methods
- WARNING: XPages/Traveler/Rest Web Services will not run until this is resolved
- HTTP JVM: java.io.FileNotFoundException: /local/notesdata/domino/workspace/.config/rcpinstall.properties (Permission denied)
- HTTP JVM: java.io.FileNotFoundException: /local/notesdata/domino/workspace/logs/Viewer_Translations.js (No such file or directory)
- HTTP JVM: java.nio.file.NoSuchFileException: /local/notesdata/domino/workspace/logs/error-log-0.html.lck
- HTTP JVM: java.nio.file.NoSuchFileException: /local/notesdata/domino/workspace/logs/trace-log-0.html.lck
- HTTP JVM: at com.ibm.domino.http.bootstrap.BootstrapClassLoader.findClass(BootstrapClassLoader.java:79
Upon inspection of the Owner and Group of /local/notesdata/domino/workspace, it is discovered that root owns the folder instead of notes:
Changing the ownership (recursively) to notes:notes (when that is the account that was used to install Domino) resolves the issue:
Beginning with Domino 10.0.1, SSL cipher options are configurable in the Security tab of Internet Site documents or in the Ports tab of Server documents (depending on if you have or have not enabled Internet Site Documents). All of the supported SSL ciphers are now listed clearly, in order of strength, for easy selection.
In my experience, when “Load Internet configurations from Server\Internet Sites documents” is disabled, the post-upgrade enables NO ciphers by default.
In contrast, ALL (non-weak) ciphers are selected post-upgrade for Internet Site Docs.
If you ARE NOT using Internet Site Docs
To review the current settings, go to the Server doc > Ports > Internet Ports > SSL settings and click the “Modify” button in the “SSL ciphers” field.
If you ARE using Internet Site Docs
To review the current settings, go to the Domino Directory, expand Web, and choose “Internet Sites.” Then open the corresponding Internet Site document and go to the “Security” tab. In the SSL Security section, click the “Modify” button in the “SSL ciphers” field.
When the right ciphers aren’t selected, besides HTTPS pages not rendering in browsers, you will also see something like this on the console or in the log: TLS/SSL connection failed with no supported ciphers
Click this link for IBM’s KB Article about the New SSL cipher configuration for Domino 10.0.1
IBM Notes 10.0 introduces a new look for the tried and true Notes workspace. The trouble is, it is just change for change’s sake. In fact, it reduces the efficiency of using the workspace because it increases the space between tiles (so there are fewer shown on the same size screen).
In short: I hate it.
My Preference: Use the notes.ini setting V10Workspace=0 to revert to the Notes 9 workspace style.
If you are installing or upgrading to Domino 10 on RHEL/CentOS Linux, be sure you have the “bc” package installed. If you don’t you’ll receive the following:
To run this installer you need mandatory packages installed on your 64 bit Linux RedHat.
The installer will exit after this message.
To install bc:
yum install bc
In case you find yourself modifying the Desktop Settings > Preferences > Replication > Default replication schedule, be aware that, even if you don’t set the value (How to apply this setting) for the “Repeat every” field, you will not be able to save the changes if there is not a number in the field.
For instance, if you leave “Repeat every” empty (even though “Don’t set value” is specified), you will receive a save error, “[Field Contains Incorrect Value] Comparison operators must be supplied two values of the same data type.” And then, “Notes Error – field didn’t pass validation formula.” And again, “[Field Contains Incorrect Value] Comparison operators must be supplied two values of the same data type.”
The solution is to enter a number in the “Repeat every” field (even if you don’t plan on making the field effective).
The good news: IBM has released 9.0.1 FP10IF2.
The bad news: the installer hangs at, “Verifying the installation data, this can take several minutes – please, wait…”
I’ve been waiting at that screen for over 12 hours, so I tried again (from scratch) to download a fresh copy from Fix Central. Alas, I arrived at the same result.
Whenever IBM resolves the issue, Admins that install this IF will reportedly reap the following benefits:
||Fixed an issue where LDAP does not properly escape # character in results
||Fixed an HTTP PANIC on LookupHandle
||Fixed a router PANIC on LookupHandle
||Fixed an issue where sending a message from iNotes a second instance of “MIME-Version: 1.0” occurs in MIME header
||Fixed a hang w/ extension mgr search calls
||Fixed a panic at Domino startup if statically enable inline view indexes