I have created the backup file a few times which is frustrating bit.
To be more clear, I have a successful upgrade to 2013.
I am now however doing a site collection backup/restore to change the URL from
/sites/sitename to sitename.domain.com.au
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-bou
Where are you restoring from and to, Chris?
Do you have another site backups you can use to see if the problem is
specific to this backup? InvalidData sounds like there might be an issue
with the backup file.
On 4 March 2013 12:11, Matthew Cosier wrote:
> I’m assuming you’re trying to restore
I'm assuming you're trying to restore a 2010 backup into 2013?
Why don't the sites exist after you mount/perform the upgrade of the content
dbs? Are you using classic or claims auth on the web app(s)?
Did you perform a Test-SPContentDatabase before you did the Mount? Was
there anything in th
Hi Guys,
Today I followed a process I had working on Friday that is.
1. Upgrade content db from 2010 to 2013
2. Upgrade s/c experience
3. Perform a backup of the s/c
4. Create a new content database
5. Restore using Restore-SPSite (Restore-SPSite -Identity
"htt
I'm following the white paper now and just got stumped on creating a new
Group in the term store. There was no arrow or New Group link available.
[image: Inline images 1]
Adding myself to the Term Store Administrators group resolved this most
unusual security requirement. :)
On 1 March 2013 23:
Great are the mysteries of SharePoint. :)
On 1 March 2013 15:04, Dylan Tusler
wrote:
> Well, after we had this issue for a few days, I went through and
> inspected all our Scopes rules (didn't change anything, mind you) and
> suddenly everything was working again.
>
>
>
> No idea what happened
