Thank you for your post. I'm sincerely sorry to hear of the trouble. The stored procedure you are referring to is created or updated dynamically each time you add a custom field to tabs within InstantKB. This is the stored procedure that manages the INSERT and UPDATE of custom field data.
I mention this as you won't find a stored procedure called ikb_sp_InsertArticleCustomFieldValues_1 within any of our installation scripts. You should however still see this stored procedure when you connect to your upgraded InstantKB database. We don't delete or alter those procedures during any upgrade.
Do you know if the SQL account has changed that your using to connect to your updated database? If so it could be the ikb_sp_InsertArticleCustomFieldValues_1 stored procedures owner is set to the previous account so you can't access this with the new account.
The "_1" at the end of the stored procedure name refers to the TabID that the custom fields belong to within InstantKB. In this case your Knowledgebase Tab. By default this tab has the TabID of 1 within the InstantKB_Tabs table. If the TabID has changed (this should not change with our upgrade scripts) this could cause problems.
If you connect to your database via SQL Server Management Studio does the object owner change for this stored procedure. I've highlighted the object owner below...
I hope something here helps point you in the right direction.
Don't hesitate to respond if these suggestions don't help resolve the issues and I'll certainly assist further,
firstname.lastname@example.orgBlog | Community