New answers tagged

1

From your command, it is not the content database backup rather a site collection backup. For a site collection backup and restore both source and destination farm should be on same level. As your source is lower version(4763) then destination (4861)in that case you do Content database backup and restore backup the content database in sql server restore ...


1

This usually occur when This content database has a schema version which is not supported in this farm To solve this issue, you should match the Configuration database version of destination farm to be the same as the source farm before you take a backup of content database from source farm by following the mentioned at This content database has a ...


0

Restore-SPSite does not work across patch levels. You will need to bring the source up to the same version. Note: this issue does not occur with the database attach method (Mount-SPContentDatabase) unless the mismatch is too great. Edit: There is no possible way to rollback. It'll require a complete reinstall.


1

Looks like issue with Drive space on the DB Server. Make Sure Drive where you storing the MDF & LDF files should have of plenty of free space. Also make sure tempDB is not full. You can run XP_Fixeddrives in SQL Management studio against the DB server, it will tell you how much free space on each drive.


0

Felt my way around this, I found that context.Load(file) , context.ExecuteQuery(), was needed to actually load the file, and then I need to proceed into putting it in a stream which I later turned into a byte array which I was able to convert into base 64. public static void GetImage(ClientContext context, string uri) { try { var files = ...



Top 50 recent answers are included