Delete extension 172 and recreate it. See if the problem still happens after you recreate.

For some reason it sounds like the system didnt fully create the extension.