Follow

How can I repair kaseya?

KB#:  KKB000711

QUESTION

If I have a problem with my kaseya install, such as missing files, what can I do to correct this?

 

ANSWER

There are 4 areas that can cause problems, files, security/configuration settings, database schema, and database data. Depending on where the fault lies, different actions can be taken.

There are 4 levels of recovery, each doing more than the one before. None of these, except level 4 are destructive to your data - they only affect the kaseya files, settings and database schema.

1. In kaseya. system tab -> configure. There is a link at the top end of the page that says "re-apply schema". This will fix any problems in the database, but not alter any files. This runs periodically on kaseya servers as part of the self-maintenance. This is like running chkdsk in windows.
Actions:
- Checks DB schema (tables, indexes, etc) for problems, repairs any found

2. In windows. Start Menu -> kaseya -> re-apply schema. This will wipe all the hotfixes, then check the database for problems.
Actions:
- Checks DB schema (tables, indexes, etc) for problems, repairs any found
- Removes all hotfixes. (Once complete you need to go to the system tab -> configure and click the "Get Latest Hotfix" button

3. Please submit a support ticket and ask support for the installer/update (.exe) to use in this step. This will perform the actions mentioned just above.
Actions:
- Checks DB schema (tables, indexes, etc) for problems, repairs any found
- Removes all hotfixes. (Once complete you need to go to the system tab -> configure and click the "Get Latest Hotfix" button
- Re-applies all file security settings
- Re-applies all IIS configuration settings
- Replaces all kaseya files (but leaves user customizations)

4. Full re-install. This is the last resort. This is comparable to re-installing windows
Actions:
- All data is removed. 

 

APPLIES TO

Kaseya Server - All versions

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.