pabely ✭✭✭✭✭

It was probably never thought Quick Tickets would be used in this way, you may are going beyond the design of the function, might be worth a support ticket to get verification on whether a Feature Request is required.

I wouldn't think such a thing exists as WHD supports multiple database types so there potentially is different SQL Syntax involved. I suspect this would all be done programmatically rather than via SQL Code.

That would make sense, I have seen this before when the AD/LDAP connection account password becomes outdated or flagged in AD as locked.

You can force WHD to start in DEBUG log Mode using the following: Append <WebHelpDesk>\bin\wrapper\conf\wrapper_template.conf file and add: wrapper.java.additional.20=-DWHDScriptLogLevel=DEBUG **Note**The number (.20) should follow the number in the sequence. Revert to the original wrapper_template.conf afterwards and…

Perhaps you should refer them to this Thwack thread as @"Bugmills" clearly has the same issue so there is at least one other SW case going around. Are you within a similar environment with WHD Installed on a Windows Server and connected to a MS SQL Database Server?

This looks like an Orion/HCO question, I think you have logged into the wrong forum area, this area is to do with the Web Help Desk solution.

Interesting, do let us know how you get on with Support

Looks like your LDAP Client Connection is now invalid. Did you run the migrate.bat script after upgrade?

Probably missing jabsorb.jar from ..\WebHelpDesk\bin\webapps\helpdesk\WEB-INF\lib folder. Support advise you can use a version from a 12.8.3 or 12.8.3+HF3 install if you still have it archived from upgrade to 12.8.5.

Not at a certain point in time because it can only look at the Statuses at runtime of the report. This is where scheduled reports come in where you can get these generated on a regular basis and emailed to you then from this pop into a spreadsheet to see trends. If you have access to something like PowerBI or Excel Power…

I too have seen this but it was intermittent. Sounds like a Debug Log (Healthcheck report) needs to be reviewed by SW Support to better understand the behavior. BTW Which OS and Database do you use for your WHD?

I would ask the Loop1 support team to log a case with SW Support if they have not already.

Does not Setup > Tickets > Options > Client Options > Clients Can Create Tickets Using - untick E-Mail - cover this?

If you can prove you had a perpetual license at one point, SW customer services should be able to give you access.

Easy to miss, you are not the only one who has been caught out with this. Ideally, the installer should have chained this procedure IMHO and make test to see if it is required and just action accordingly. A further Note in the Upgrade Guide rather than just Release Notes would have been helpful.

Did you ever have a perpetual license but did not keep up support?

Did you get as far as running the migrate Tool as discussed in the Release Notes?

Not sure if this is the same thing as that is to do with Inbound rather than your Outbound. I too have tried the OAUTH Outbound method and seen duplicates, I did not have time to investigate so just reversed to the old SMTP.

The syntax on the command line would be: migrate.bat "C:\WebHelpDesk" false changeit

Did you run the migrate.bat as the encrypted details for the O365 connection would be changed?

You say "to solarwinds" but have logged this question within the Web Help Desk Forum, is that correct? WHD only potentially can look at Assets held within Oracle Database tables.

This is to do with your Outbound Mail configuration, I assume you are wanting to use O365 for this?

For Linux I would use the linux keytool command line as shown within the following: documentation.solarwinds.com/.../helpdesksetupcertificates.htm

I would check with support on that one.

Stop It! I almost dropped my coffee mug seeing that!

I missed this first time round as well, would have been nice for Installer to check for this automatically as I'm sure there will be more who fall down on this creating unnecessary support cases.

Likely to be Ticket Status Codes which have been deleted but you have Action Rules which are dependent on Ticket Statuses. I hate the fact that WHD allows you to deleted Status Code, Request Types, Locations etc without any regard to links to Action Rules. SW Really should come up with a script to highlight orphaned Action…

I'm not sure you will get much traction within this area of Thwack, I think you might have a better response within the Orion Platform area rather that the Web Help Desk.

I think the WHD WMI Asset Discovery is only written to interact with details held on the Windows OS. I'm sure it will not be able to interact with anything from OMSA or Dell.

Sounds like one you should log with Support, once you have authorized them, they can look at all layers of visibility control within your Instance. Have you not considered the ESM (Enterprise Service Management) option?