Random tickets are being created daily starting with number 683060 and going to 683103 (we're only at 161). And it's based off inventory. In the columns on the db, the ticket description is the inventory host name, the ticket priority is the IP address, the ticket due date is the device type, the created at column is the IP range that was scanned. It's like any new scan is being registered as a ticket and when I go to open that ticket in the ticket window, it simply loads forever and won't open.

The simple answer isn't restoring as this happens every day. Also, I can't delete them from the db with a "delete from" command because it simply won't work. The command doesn't return an error, but the tickets won't delete.

9 Replies

Here's a screenshot. What is this exactly? When I run a select command for one of those tickets, nothing turns up! It's showing in the db and on the unassigned tickets page, but I can't do anything with it or manipulate it in SQL.

I know how the entire world is against doing anything in the DB, I am as well. But in my situation I had to. Long story short, SW wouldn't start and also hadn't been backing up since March. So I spent about 12 hours reimporting old e-mails and comments and assigning the same previous ticket numbers to what they used to be so that everything could be back to normal. It was really the only way to get our ticket system back to the way it was.

Yes the database was touched, but everything worked fine after that. In fact, even after a network scan, everything still worked fine. This just randomly happens every now and then.

I've been working with an engineer, James Barnett, and actually he's been tremendous help. I have 100% confidence in him, I just wanted to ask here to see if anyone has run into this issue, not that I don't trust him, it just helps to get multiple opinions.

Definitely. But it's weird how "select * from tickets" displays them, but selecting an individual ticket won't. And on the web side, it displays them in unassigned view, (I assume unassigned ticket view is just a specific select command on the ticket table).

Regardless, that doesn't make sense how a select all command will display something, but a select command within that same table won't.