Comments
-
Reproduced in my Lab system as well
-
Be interested to know what they come back with....
-
Is this a Free version that has the reduced functionality from day one but does not expire?
-
I would blame cookies! Left see what SW Dev say,
-
Yes I have had to do similar before in past
-
So this only effects a couple of Techs which have linked Client accounts - any End User Clients which are not Techs reporting the same issue?
-
Do you Sync your Clients with any LDAP/AD?
-
Interesting, those sorts of errors in your log file have been common since 12.8.1 release, do your users get entries within the whd-session.log ? I am more inclined to think this is cookie error rather than CSRF. Do you have a Load Balancer/WAF installed in your infrastructure where a WHD session might hit one Load…
-
How are users logging out, do the do this probably or just close the Tab because it tries to auto-login again? Also were you on HF2 before?
-
Yes, updated about 10 customer sites so far?
-
Reading the Release Notes, I cannot see any issue with Outbound SMTP being addressed, only Inbound. I suspect with MS not enforcing OAUTH on SMTP this has been left until 12.8.4.
-
Support can be contacted via https://customerportal.solarwinds.com/support/submit-a-ticket You will need to be a registered user on their system which may require approval by your account portal admin. If your account admin details is outdated then SW Customer Support should be able to…
-
I believe SW are due to fix this within the upcoming HF3 release.
-
Yes, it sends the Canned Response just by having it linked to a Request type, you do not have to select it on the note.
-
Thanks for the update.
-
Did this ever get resolved so the correct free version is available to download?
-
This looks like the list as shown within Action Rules and I always treat this as the master list. I seem to remember we have asked for Phone_2 as well in the past via a Feature Request but do not remember this ever being action by Dev.
-
Juts tested on my system, runs fine.
-
Then you will need to abandon that test Clone and create a new one from Production.
-
A full restore is preferred and do the upgrade in the way documented in the Installation/Upgrade Guide. You cannot just run the WHD12.7.7 installer now as pg9 has gone, I assume you did a Server snapshot / backup before starting the upgrade process?
-
WHD12.7.7 was the last release using Postgres 9, you need to convert to Postgres 13 as per the upgrade Guide whilst on 12.7.7 using the upgradeDatabase.bat. There are a few pre-requists to this as well, version of Powershell, Visual C++ and Server OS Locale.
-
Interesting that for my customer a restart did not help and SW Support have acknowledged that this is an issue.
-
Have you tried the documented method? documentation.solarwinds.com/.../helpdeskrestorepostgresqlafteranupgrade.htm
-
Which environment OS do you run on, have you moved to a new server recently?
-
Also, have you applied HotFix2 on top of WHD12.8.3?
-
You mean using the download .eml which a Tech Admin sees within Ticket History?
-
The Important part is the "Use Embedded Database", is this ticked like this?
-
What connection details are shown in WHD within Setup > General > Database? A good measure to see what version of PostgreSQL you are using (if hosted on Windows) is to check the Windows Services and see what path the executable is.
-
Another thought, does the issue show across all browser types, Chrome, Edge, Firefox or Safari (if using Mac)?
-
I thought this was fixed within the WHD12.8.3 releases?