Hotfixes fix a certain error and are usually provided as a ZIP file. The ZIP file is unpacked in the i-doit installation directory. Confirm the question whether you want to overwrite files during unpacking (Y key for "yes" or A key for "all"). Here you can find an example:
1 2 3 4
Please use hotfixes exclusively with the specified version. Hotfixes will be included in newer versions so that a renewed installation is not necessary. Should you use an older i-doit version it is essential to make an update to the latest version first.
If a hotfix is required to update an older version, it can be found in the hotfix subchapters here in the Knowledge Base.
As these are hotfixes we recommend installing them only when the adjustments are necessary for a flawless operation of your installation or you are requested by the support team to use them. Please ensure that you made a backup of i-doit before you use any hotfix.
Please inform us about the use of hotfixes should you contact our support team afterwards.
The requirements shown below apply to the current version of i-doit, in this case 26 These requirements are adjusted for each release of i-doit. If the requirements of older versions are needed, the change history of this page can be used.
Declaration of consent
By downloading a hotfix you declare that you have read and understood the above mentioned notes completely.
JDisc import via console stops with error#
Related error message
1 2 3 4 5 6 7 8 9 10 11 12 13
Disconnecting relation in custom category causes sql error#
When you get the following error when disconnecting a relation to a custom category:
It is not possible to retrieve the next online i-doit update via button check while updating i-doit#
When you click on the Check for a new version button then version 27 is not displayed, when available.
Wrong attribute name while reading through API#
When reading category C__CATG__IP hostname is the given attribute.
Status filter for multi value categories in report manager is not working correctly for custom categories#
Using cmdb.category.save to assign a object to a contract only assigns root location#
Description fields yield validation errors on 32bit systems#
When using a 32bit system and saving a global or specific category causes validation error.
Assigning a software via software assignment before assigning a operating system causes version number to disappear#
When assigning a Software before assigning a operating system, the version number of the operating system will disappear.
Changing technical keys to only contain words causes entries to lose the values when filled with API (Number only) AND Changing technical keys to only contain words causes entries to lose the values when filled with API (Dialog+) AND Changing technical key in multi value category causes problems in listview#
API Add-on 1.14.1#
Operating system > Version cannot be referenced via title, if a second operating system has the same version title#
This effects you when you get this API error message:
i-doit system error: The specified version could not be assigned to this application"
Using API after update to i-doit pro 25 displays license error message#
Use this when you receive an error message like: