For the past week I have attempted to create a staging server for my client's Sharepoint Site. The problem is that it will import 9100-9700 objects and then it will fail and issue me these errors:
Content deployment job 'Remote import job for job with sourceID =
378a003b-941d-46dc-979b-e7e276e60c77' failed.The exception thrown was
'System.UnauthorizedAccessException' : 'Access denied.'
and
Access denied. at
Microsoft.SharePoint.SPGlobal.HandleUnauthorizedAccessException(UnauthorizedAccessException
ex) at Microsoft.SharePoint.Library.SPRequest.PatchUrl(String bstrUrl, String
bstrWebRelFileUrl, String bstrWebRelOldUrl, String bstrWebRelNewUrl, Int32 grf)
at Microsoft.SharePoint.Deployment.ImportObjectManager.FixLinkInFile(String
fileUrl, Guid webId, String oldTargetUrl, String newTargetUrl) at
Microsoft.SharePoint.Deployment.LinkSerializer.SetObjectData(Object obj,
SerializationInfo info, StreamingContext context, ISurrogateSelector selector)
at Microsoft.SharePoint.Deployment.FileSerializer.UpdateLinks(SPFile file,
String linksXml, StreamingContext context, ISurrogateSelector selector) at
Microsoft.SharePoint.Deployment.FileSerializer.UpdateFileAssocData(SPFile file,
SPWeb web, Guid id, String fileUrl, SerializationInfoHelper infoHelper,
SerializationInfoHelper infoHelperListitem, StreamingContext context,
ISurrogateSelector selector, ImportObjectManager objectManager) at
Microsoft.SharePoint.Deployment.FileSerializer.CreateOrUpdateFileAndAssocData(Object
fileOrListItem, SPWeb web, Guid id, String& fileUrl, Boolean fileExistsInDb,
SerializationInfoHelper infoHelper, SerializationInfoHelper infoHelperListitem,
StreamingContext context, ISurrogateSelector selector) at
Microsoft.SharePoint.Deployment.FileSerializer.SetObjectData(Object obj,
SerializationInfo info, StreamingContext context, ISurrogateSelector selector)
at Microsoft.SharePoint.Deployment.XmlFormatter.ParseObject(Type objectType,
Boolean isChildObject) at
Microsoft.SharePoint.Deployment.XmlFormatter.DeserializeObject(Type objectType,
Boolean isChildObject, DeploymentObject envelope) at
Microsoft.SharePoint.Deployment.XmlFormatter.Deserialize(Stream
serializationStream) at
Microsoft.SharePoint.Deployment.ObjectSerializer.Deserialize(Stream
serializationStream) at
Microsoft.SharePoint.Deployment.ImportObjectManager.ProcessObject(XmlReader
xmlReader) at Microsoft.SharePoint.Deployment.SPImport.DeserializeObjects() at
Microsoft.SharePoint.Deployment.SPImport.Run()
I have been all over the web and found nothing for this specific issue. I have tried playing with the features and turning off publishing at the Main Sharepoint Site. I have tried granting access to the Wamrag and the host file folder for that server. I have tried so many different things that I don't even remember. My head is spinning. I got so frustrated that I tried sending Andrew Connell a message to see if he could shed some light on the issue. I'm not even sure I will get a response, but he seems to know a lot about content management. I think I'm at the point where I need to walk away from the problem for a while. This should be a time when I am starting to wind down and kick back. I am on vacation next week in Los Angeles and the last Harry Potter book comes out of this weekend. I even got to level 66 in World of Warcraft and I can now visit the instance I've wanted to see since Burning Crusade came out. In short life is good why stress out about a little Sharepoint issue. The answer will come.
*UPDATE*
I got it to work by excluding this testing like that has every single template Sharepoint can offer including the Fantastic 40. I am assuming there is something in there that angered the import job. I didn't need to copy that directory, so it is not a big deal. I am hoping that this helps someone else who is receiving the same error. Just remember it could be an object in a site that deals with the Fantastic 40. You may need to upload some type of feature or list.
Anyway all is pretty much well aside from this publishing problem. If I try and activate publishing on existing sites for quick deploy to work it doesn't do anything, even with the feature turned on in both the site collection and site. I am not sure why it will not work on the team sites or the workspace sites. I assumed that you activate the feature on the sites and publishing was activated. I am going to look into changing the default.masters in those sites. If anyone else has a better idea I am all ears.
mosslover