My 30 second read and thoughts:
Might be a long shot, but can you verify that they are both patched to the
same versions? Lots of serialization code being executed in that
callstack, most common issue when deserializing is due to differences in the
current code vs that of the sale object you're
No luck. Will see if I can replicate it in our dev environment before worrying.
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Aaron Saikovski
Sent: Monday, 7 November 2011 1:03 PM
To: ozMOSS
Subject: RE: SPS2010 Office Web Apps - Cache error
Also try this:
I'd start by ditching dependencies and security on the export and see if it
will import OK.
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Mike MOSSuMS Stringfellow
Sent: Monday, 7 November 2011 6:10 PM
To: ozmoss@ozmoss.com
Subject: Import error - guidance on
Ok.
Might be time to raise a support case
From: ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] On Behalf Of
Nigel Hertz
Sent: Tuesday, 8 November 2011 7:47 AM
To: ozMOSS
Subject: RE: SPS2010 Office Web Apps - Cache error
No luck. Will see if I can replicate it in our dev
Many thanks for your help Paul and Matthew Definately sounds like we are all
thinking the same way as I've checked those things. Pach level was fine as it's
been moved to the same farm - however missing feature references etc in the
content, as it originally came from 2007 and was then
According to the API,
SPListItemCollection.Itemhttp://msdn.microsoft.com/en-us/library/ms443550%28v=office.12%29.aspx
is supposed to get a list by Name. Is that correct? In my tests it will only
return results when I pass in the Title.
SPSite siteColl = SPContext.Current.Site;
oWeb =
Hi,
Sorry for the delay in replying.
- Yes, both farms are 64-bit.
- Both are in the same domain.
- Yes, path to log files is the same in both.
- Both farms are based on Server 2003 so no UAC
I've also checked regional settings in every area that I can think of and
they are the same
Ok - it looks like this actual 2010 install is FUBAR, as the import works fine
on my dev environment and there are a variety of error in the logs, including
this from nasty from SQL when importing the list: Unknown SQL Exception 206
occurred. Additional error information from SQL Server is
This looks tricky as stsadm - backup/restore is much more robust than
stsadm import.
In most cases when we had issue with export-import -- backup/restore has
worked well.
Can you do one quick test to validate if it's the data in site causing the
issue by creating a new OOTB site collection and
