KIM Registration Not Working

Jim Piller asked on May 9, 2022 16:35

I have a site that was built in Kentico 12 and I need to upgrade it to 13. I had it registered in KIM 13, however I was troubleshooting and unregistered it thinking it would help w/ my issue. I cannot get the site to re-register and KIM keeps telling me the folder doesn't have a Kentico Xperience installation even though I know it does. How can I get this site to register so that I can use the KIM utility to upgrade the site?

Correct Answer

Brenden Kehren answered on May 9, 2022 20:07

The KIM is looking specifically for the file WebApp.sln or WebSite.sln AND there to be a /LIB and /CMS directory in root of where you're registering the website. Also, when registering the site, you don't need to go inside the /CMS directory, just the parent of that directory.

1 votesVote for this answer Unmark Correct answer

Recent Answers


Brenden Kehren answered on May 9, 2022 17:06

You should be able to use the KIM for v12 without any issue to run your upgrade.

Have you changed the name of the solution file from the original file name to another file name? Have you modified the folder structure at all where the solution file and the rest of the site are housed? These are 2 common issues we run into.

0 votesVote for this answer Mark as a Correct answer

Jim Piller answered on May 9, 2022 19:53

I haven't changed the project structure or solution name in quite some time - not since the first few commits and we've been working on this project for over 3 years. I just don't understand why it doesn't see the Xperience instance...I've got to be missing something pretty simple.

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on May 9, 2022 20:12

You could also manually add the record in the C:\ProgramData\KIM\kim.xml file. Your entry would look something like this:

  <item>
    <guid>6eb50de2-df37-4743-b5e2-72e71463522b</guid>
    <url>http://localhost</url>
    <name>K12 Site</name>
    <version>12.0</version>
    <path>C:\Websites\kentico12</path>
    <created>2022-04-07T12:14:49</created>
    <hotfix>29</hotfix>
    <showlist>0</showlist>
    <netversion>0</netversion>
  </item>

You'd need to make sure the hotfix is what your current site is at. Again, keep in mind, the KIM for v12 or v13 will work. It's smart enough to manage that because all of the KIMs use the same file just operate off the version node.

1 votesVote for this answer Mark as a Correct answer

Jim Piller answered on May 9, 2022 20:43

I deleted the project folder and re-pulled it from Github and somehow that worked. I was able to register it just now. Not sure what changed, but it's working now. Thanks for the quick reply!

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.