Well then the migration seems to have done what it needed to have done, but the first time it was run it seems the entry in the migration was not stored for whatever reason.
A few other migrations happen for Forms in V6 such as moving the JSON files from AppPlugins to AppData.
Check that they have moved as well, if so then you should be OK to update/add the entry in manually. Unless there is anything else in the logs that may indicate why the initial migration may have failed & thus store the entry in the DB.
Sorry to necro the thread. Having exactly the same issue. My concern is that there has never been an entry in the umbracoMigration for forms, what should it look like?
Can I add my own apologies for re-necroing the thread? :)
I've recently been tasked with the maintenance of an Umbraco instance that is experiencing the same issue.
Unfortunately for me the migration would have been done some time ago - by someone that no longer works here.
The site appears to be working as expected but I am concerned that this may adversely affect our ability to upgrade the Umbraco instance in the future.
The 'umbracoConfigurationStatus' version in the web.config file is showing as version 7.12.1.
Querying the [umbracoMigration] table in the Umbraco database shows:
id name version createDate
1 Umbraco 7.5.4 2016-12-06 09:30:48.247
2 Umbraco 7.5.7 2017-01-16 12:10:28.237
3 Umbraco 7.9.2 2018-04-26 10:08:46.280
4 Umbraco 7.12.1 2018-09-06 10:18:04.840
This seems to align with the version information the web.config file.
Enabling log debugging in Log4Net though shows alternate version numbers:
I suspect that this is the reason it keeps trying to run the migration - although I am unsure where the migration tasks are stored.
Did anyone identify the steps required to resolve this? Be it manually updating/adding the entry; updating source of the version information seen in the debugging log; or the removal of the migration task?
I'm experiencing the same issue. I'm currently using umbraco 7.10.6 and I've tried upgrading Umbraco Forms to the latest version supported by 7. However, I'm seeing the same issues in the logs as above. What is the solution for this?
The solution that worked for me was to delete the Macro named "Insert Form with Theme" which had the Alias of "renderUmbracoForm" from within the Umbraco back office.
I then restarted the site and it seems to have re-created that macro, without running into any issues. No more errors logged!
It seems that, even though the macro already existed, it was still trying to Insert that macro into the database at startup and it couldn't do that as it caused a foreign key conflict. So, deleting the Macro and allowing the migration to do what it was trying to do at startup seems to have worked in my situation.
It may also be worthwhile looking into the reason why the migration was actually being triggered in the first place.
In my case, I am using uSync and I had a config file (renderUmbracoForm.config) defined for that macro. So, I guess that's what was triggering the update/migration in my case!
Umbraco forms upgrade migration error
Hello,
I've upgrade Umbraco forms from v4 to v6. Everything is working, but in the logs I always get this message when the website is restarting:
Anyone know what could cause this issue and how to fix it?
Jeroen
Hi Jeroen,
Seems something odd going on with the migration, in theory a migration should only ever run once & not multiple times.
Is there an entry in the Migration table for Forms?
Also what Forms macros do you have in the site?
Thanks,
Warren :)
Hi Warren,
I don't see an entry for Forms in the Migration table. Probably because the migration failed.
I have the following macro's:
Insert Form (Legacy)
Insert Form with Theme
Render Forms Scripts (Legacy)
Jeroen
Well then the migration seems to have done what it needed to have done, but the first time it was run it seems the entry in the migration was not stored for whatever reason.
A few other migrations happen for Forms in V6 such as moving the JSON files from AppPlugins to AppData.
Check that they have moved as well, if so then you should be OK to update/add the entry in manually. Unless there is anything else in the logs that may indicate why the initial migration may have failed & thus store the entry in the DB.
Sorry to necro the thread. Having exactly the same issue. My concern is that there has never been an entry in the umbracoMigration for forms, what should it look like?
Thanks in advance.
Can I add my own apologies for re-necroing the thread? :)
I've recently been tasked with the maintenance of an Umbraco instance that is experiencing the same issue.
Unfortunately for me the migration would have been done some time ago - by someone that no longer works here.
The site appears to be working as expected but I am concerned that this may adversely affect our ability to upgrade the Umbraco instance in the future.
The 'umbracoConfigurationStatus' version in the web.config file is showing as version 7.12.1.
Querying the [umbracoMigration] table in the Umbraco database shows:
This seems to align with the version information the web.config file.
Enabling log debugging in Log4Net though shows alternate version numbers:
I suspect that this is the reason it keeps trying to run the migration - although I am unsure where the migration tasks are stored.
Did anyone identify the steps required to resolve this? Be it manually updating/adding the entry; updating source of the version information seen in the debugging log; or the removal of the migration task?
Hi,
I'm experiencing the same issue. I'm currently using umbraco 7.10.6 and I've tried upgrading Umbraco Forms to the latest version supported by 7. However, I'm seeing the same issues in the logs as above. What is the solution for this?
Gemma
The solution that worked for me was to delete the Macro named "Insert Form with Theme" which had the Alias of "renderUmbracoForm" from within the Umbraco back office.
I then restarted the site and it seems to have re-created that macro, without running into any issues. No more errors logged!
It seems that, even though the macro already existed, it was still trying to Insert that macro into the database at startup and it couldn't do that as it caused a foreign key conflict. So, deleting the Macro and allowing the migration to do what it was trying to do at startup seems to have worked in my situation.
It may also be worthwhile looking into the reason why the migration was actually being triggered in the first place.
In my case, I am using uSync and I had a config file (renderUmbracoForm.config) defined for that macro. So, I guess that's what was triggering the update/migration in my case!
is working on a reply...