jholzhey_bu · Technical Administrator, Bruin Support Services · ✭✭✭✭✭

What's the Perl update? Can that be done manually? I can't go back to HF1.

Truth!

This is our CURRENT ParseExcel.pm file. Clean install of HF2 (+ HF3).

We're getting both 400 and 401, depending on how it feels at that particular time. Still in far fewer numbers than before the upgrade, and it often starts working again without me doing anything. However, we did have to reauth yesterday a few times for different mailboxes (we have 6), but it's no longer something we have…

Never mind. We just got some auth errors. Enabled debug logging and will capture overnight and into tomorrow.

I don't know about you guys, but the support rep I got has been awesome! Her name is Danica Jison. I gave her the update on our status, and she's keeping our ticket open until Friday just in case.

HF3 is only to fix the mistake in HF2 regarding MSSQL dbase connections, from what I understand.

That's a good point to add. We're using 365 as well.

Finally got HF2 (and HF3) installed, and we're basically back to normal. A very small number of auth errors yesterday, but NONE since before 4PM yesterday until now (10 AM).

Not sure what they're looking for, but they're not going to find anything. For testing, they've had us move back to a 2-application/API setup on our test env, which has yet to have any problems. Hoping to finish that up today and see what happens. If nothing breaks, I'll do the same for prod, and I guess install HF2 at the…

Maybe they mean adding it to the disabled algorithms list? But this is only for dbase connections, as far as I knew. Otherwise, I guess you'd have to disable on your server? ..\WebHelpDesk\bin\jre\conf\security\java.security jdk.tls.disabledAlgorithms=SSLv3, TLSv1, TLSv1.1, RC4, DES, MD5withRSA, \ DH keySize < 1024, EC…

Update from Support (Tue 4/15/2025 7:02 PM CDT): "I want to update you that I am still investigating this issue with our internal team. I will provide an update again tomorrow."

I got the same response a few weeks ago. We also do not use the "Accepted Domains" function. Completely blank. Regardless, they're admitting it's a bug in the 365/OAuth coding. They need to get it fixed before Fall because Simple Auth (SMTP Auth) is going bye-bye.

Our ticket for this issue has been open since 31 Mar 2025. Our ticket for duplicate ticket emails has been open since 03 Mar 2025. For both issues, we've been told they're known issues that their dev team is working on. However, they continue to trouble-shoot and ask for more uploads. If you want, tell them it's the same…

Reports for historical data, Advanced Search (query) for real time. And queries can be used for dashboards, reports cannot. Once you run the query, use the droppy-down thing next to "New Ticket" to export the data in TSV format. What's REALLY cool is that the column set you're using at the time determines the columns in…

Exactly what we've been doing to compensate for 2 weeks now? And we have 6 mailboxes. I'm seriously questioning my decision to support multiple mailboxes. It's great when it works, but then reauth time comes around every 90 days (per Microsoft) and it's a hassle. Multiply that by multiple times a day (and night).

I thought 12.8.3 HF3 was bad. 12.8.5 has been a nightmare for us.

Yeah, and we had that working in 12.8.4. And now support is telling us that BOTH of our problems, this and the duplicate emails issue, are things others have reported and are being handled by the devs.

Yeah, that's all good. SW support responded with a bunch of questions and asked if I ran migrate.bat. Well, no, that's never been required. So trying to find out what that does and respond back.

Did you happen to delete a tech group? If you delete any tech groups, this will happen until you restart WHD. At least that's what I've always had to deal with. I have tons of empty tech groups that I keep planning to delete after hours or during at upgrade, then forget. Just like I did yesterday.

Support suggested I check our AD/LDAP connections. I couldn't at all understand why it would matter, but...the password for each connection was out of date. We updated the password for every connection, and we are now able to accept and create clients/tickets from unrecognized email addresses!! I still don't quite…

I have a ticket open on this now.

No, I've never run that after an upgrade. What's that do? Also, we can create tickets via email from an existing client. It's the unrecognized 3rd party email accounts we're having trouble with. So not in Active Directory to begin with. And no problems that I've seen with the nightly sync.

I just submitted a support ticket. This is getting out of control.

The amount of messages I'm getting about this today, I think this started just this weekend. We moved to outbound OAuth about 3 weeks ago. No idea what going on.

That post is 4 months old. This issue, just as for you, seems to have begun for us after switching to OAuth for outbound. However, I only became aware of it today. Hence my visit to the forums today. This and our missing "deleted after being processed" messages.

I fully agree, though isn't Portecle a .bat script (i.e., Windows only)? That looks like Linux to me.

Ticket submitted.

Concerning this part specifically: "...upgrades the cryptographic algorithms between WHD and a database." What were the updates to those algorithms? Due to our legacy database cluster, I still have to re-enable TLS 1.0/1.1 within '..\WebHelpDesk\bin\jre\conf\security\java.security' to even be able to connect to our…