Share via

Should errors in a database upgrade to sharepoint 2016 mean that the system wont work ?

Greg Booth 1,536 Reputation points
2023-03-22T15:28:00.3066667+00:00

We are upgrading to Sharepoint 2016 ( from sharepoint 2013) using the database attach method.

We are using Mount-SPContentDatabase to upgrade the content database.

The log file from this generates a number of errors. A large number of these reference missing features., missing weparts, missing setup files etc. The official advice for these appears to be install the solution/customisation that contained the missing object. However in our case we dont have these solutions for sharepoint 2016 and cannot re-install them ( and dont want to, partly for licensing reasons) .

So the upgrade log contains multiple errors.

We do not plan to use the pages that refer to missing objects ( or will delete them at a later date).

The upgrade log file has an INFO message near the end that says

"Upgrade session failed. 21 errors and 123 warnings encountered"

Is it safe to ignore the message saying that the upgrade has "failed" and use the Sharepoint 2016 system ?

Microsoft 365 and Office | SharePoint Server | For business
0 comments No comments

Answer accepted by question author

DarW!n 155 Reputation points
2023-03-22T15:43:55.26+00:00

Was this answer helpful?


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.