/build/static/layout/Breadcrumb_cap_w.png

KACE Product Support Question


How to troubleshoot Opps Something went Wrong with the K1000.

01/24/2017 1848 views

When clicking on a device from the inventory to view it's information, we receive a error page saying oops something went wrong. The error is the following.

PHP Error: Uncaught ADODB_Exception in /kbox/kboxwww/include/KTicket.class.php on line 4686: mysqli error: [1033: Incorrect information in file: './ORG1/HD_TICKET.frm'] in EXECUTE("select HD_TICKET.ID, CONCAT('TICK:', case when LENGTH(HD_TICKET.ID) < 4
then LPAD(HD_TICKET.ID, 4, '0')
else HD_TICKET.ID end) as TICKET_NUMBER,
case NAME
when 'Opened' then 'Opened'
when 'Closed' then 'Closed'
when 'Need More Info' then 'Need More Info'
when 'New' then 'New'
else NAME
end as STATUS,
TITLE
from HD_TICKET, HD_STATUS
where MACHINE_ID = 586 and HD_STATUS_ID = HD_STATUS.ID 
order by ID DESC limit 10")

everything else within the K1000 is working fine. Has anyone see this before?

K1000 Version: 6.4.120822

Agent Version: 6.4.522

3 Comments   [ + ] Show comments

Comments

  • Hi James,

    It looks like you have a service request opened for this. I would let tech support take a look at this and they should be able to assist you with resolving the issue.
  • We are getting this error, too. Was it an easy resolution?
  • Once the service request was opened, a quest engineer was able to resolve the issue. Our K1000 was down while the engineer was making the corrections. I think the total down time was a hour or two,

Be the first to answer this question

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ