This post is to start discussions on v9.6.x issues. If believe you've discovered a defect, be sure to log the issue with Support and work with them to confirm the issue is a defect. If you have experienced an issue with v9.6.x and have figured out a solution, please share here.
Issue list so far:
Issue: Outbound email from CSM are not marking themselves as readCherwell Support Ticket(s): 347731Status: Pending Investigation
Issue: Installing CSM on a drive letter other than C, results in "Cherwell Service Host" to not start and CherwellMQS to not be installedCherwell Support Ticket(s): 346944 (DR44937 w/Fix ETA in 9.7)Status: Confirmed by support. Per my (Kelson) notes, in partnering with support, there may be a workaround which may be problematic for some resulting in more challenging workaround/installation.
Issue: Embedded forms within embedded forms no longer works in Portal and Web ClientCherwell Support Ticket(s): 348752 (DR16526 w/Fix ETA 9.6.2)Status: Confirmed by support, functionality no longer works. The unintended functionality has been present for over 5 years and now is no longer available. No documentation provided by Cherwell of the removal of this functionality.Workaround/Recommendation: Support recommends re-designing all forms that utilize this capability. There is also a idea posted that needs additional up-votes from interested users to allow this capability for all of CSM (https://cherwell.ideascale.com/a/dtd/Allow-nesting-of-embedded-forms/309465-44235). I encourage anyone who is impacted by this "fix" to reach out to any and all contacts to escalate this issue with Cherwell Corporate. If this capability was a defect that needed to be patched, where is the support documentation to suggest this capability no longer exists and that this is an intended patch. A capability that existed for over 5 years no longer works.
Issue: Automation processes aren't triggeringCherwell Support Ticket(s): Unknown - Information provided by Graham Moore and Jay BetancourtStatus: Unknown
Issue: Scheduler timeouts ("Scheduled Item exceeded allowed run length")Cherwell Support Ticket(s): DR44932 w/ETA Fix for 9.6.2Status: Still investigating. At minimum it appears to affect LDAP imports and a workaround exists to increase the timeout period from 20 to 180.
Issue: Unable to resize font or headers in grid on dashboardCherwell Support Ticket(s): Unknown - Reported by Stepuluk and MartSinimaaStatus: Unknown
Issue: Specifics will not loadCherwell Support Ticket(s): Unknown - Reported by ajonesStatus: Unknown
Issue: ASP.NET Runtime errors when accessing web componentsCherwell Support Ticket(s): 346945Status: Solution - Uninstall and reinstall 9.6 Browser/portal apps
Issue: User unable to see new "Design buttons"Cherwell Support Ticket(s): DR 44918Status: Reported by MartSinimaa. not sure the description of how to reproduce or to determine if this affects others. Unsure of when this was introduced, but didn't exist in 9.5.2
We have a potential issue with attempting to start the "Cherwell Service Host" It appears as though either that service or the micro-services require the default OOTB Cherwell Admin username and password even if we set it to use windows authentication. Support ticket 346944 has been submitted and we are awaiting response.
Issue: ASP.NET Runtime Errors When Accessing Web ComponentsImpact: Cherwell Client, Cherwell Portal and Cherwell API (all web components) are generating runtime errors "You appear to be using an older version of Cherwell Service Management. Please contact your administrator."Ticket Number: 346945Status: Opened a ticket with support and resolved by uninstalling/reinstalling 9.6 Browser/Portal Apps.Forum URL: https://www.cherwell.com/community/f/database/11654/upgrading-from-9-5-3-to-9-6
I have two open support tickets right now:
1) Installing the Cherwell Server onto Windows 10 doesn't appear to install the services correctly (can't open the Server Manager at all / no services installed in Windows)
2) In our hosted environment, services are up and running but the Scheduler isn't working (jobs are not triggering) & when you run a manual 'Test' it times out.
I'd be curious if #2 above is related to the same thing we're seeing. Have you removed the CSDAdmin account or have you changed the default password for that account?
I mentioned it to the support agent I was speaking to as I had read your post earlier - it's been escalated now though. Since our environment is hosted they do configure new passwords for the default accounts, although it appears the services are actually started and working. There was another issue which I don't have full details of yet, but they weren't able to turn on logging for the services either. Sounds to me like something has gone a bit off track with the services in general.