Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I have two sites that were originally migrated from SPS2003. It worked well in SharePoint 2007 and even on SharePoint 2010, however when we migrated it to SharePoint 2013, the home page throws following errors on the ULS Log.

5/24/2013 09:57:46.62 w3wp.exe (0x0D50) 0x1D24 SharePoint Foundation
Files ak8dj High
UserAgent not available, file operations may not be optimized. at Microsoft.SharePoint.SPFileStreamManager.CreateCobaltStreamContainer(SPFileStreamStore spfs, ILockBytes ilb, Boolean copyOnFirstWrite, Boolean disposeIlb) at Microsoft.SharePoint.SPFileStreamManager.SetInputLockBytes(SPFileInfo& fileInfo, SqlSession session, PrefetchResult prefetchResult)


05/24/2013 09:57:46.62 w3wp.exe (0x0D50) 0x1D24 SharePoint Foundation Cobalt ajoii Medium
Mapping Store error to Cobalt error. [Store Error: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.SharePoint.CoordinatedStreamBuffer.SPCoordinatedStreamBufferFactory.CreateFromDocParams(SqlSession session, Guid guidSiteId, Int32 cbContent, Nullable1 parentId, Guid docId, Nullable1 level, SPChunkedArray`1 rgbContent, Byte[] rgbRbsId, Int64 bsn, Byte partition, Int32 pageSize, Boolean bStartFilling)


05/24/2013 09:57:46.62 w3wp.exe (0x0D50) 0x1D24 SharePoint Foundation Cobalt aintx High Failed in CobaltStream.LockBytes: ErrorException --- Error: Unknown (Win32=0x80004003) --- Error message: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.SharePoint.CoordinatedStreamBuffer.SPCoordinatedStreamBufferFactory.CreateFromDocParams(SqlSession session, Guid guidSiteId, Int32 cbContent, Nullable1 parentId, Guid docId, Nullable1 level, SPChunkedArray`1 rgbContent, Byte[] rgbRbsId, Int64 bsn, Byte partition, Int32 pageSize, Boolean bStartFilling) at


05/24/2013 09:57:46.64 w3wp.exe (0x0D50) 0x1D24 SharePoint Foundation Files ak8dj High UserAgent not available, file operations may not be optimized. at Microsoft.SharePoint.SPFileStreamManager.CreateCobaltStreamContainer(SPFileStreamStore spfs, ILockBytes ilb, Boolean copyOnFirstWrite, Boolean disposeIlb) at Microsoft.SharePoint.SPFileStreamManager.SetInputLockBytes(SPFileInfo& fileInfo, SqlSession session, PrefetchResult prefetchResult) at


05/24/2013 09:57:46.64 w3wp.exe (0x0D50) 0x1D24 SharePoint Foundation Database ab1a9 High Failed to get document content data. System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.SharePoint.CoordinatedStreamBuffer.SPCoordinatedStreamBufferFactory.CreateFromDocParams(SqlSession session, Guid guidSiteId, Int32 cbContent, Nullable1 parentId, Guid docId, Nullable1 level, SPChunkedArray`1 rgbContent, Byte[] rgbRbsId, Int64 bsn, Byte partition, Int32 pageSize, Boolean bStartFilling) at

I could not find any materials related to this on the internet, I am not even sure if it has to do something with SPS2003 compatibility.

Any help pointers?

share|improve this question
1  
Not an answer here, but I'm getting the same error message [see below] on a new SharePoint 2013 install. I thought I had finished configuring Search for the site, but the search boxes still show no results and I'm still getting errors in the logs like the one you have listed here. "UserAgent not available, file operations may not be optimized. at Microsoft.SharePoint.SPFileStreamManager.CreateCobaltStreamContainer" Any advice would be greatly appreciated. –  hcShare Jun 10 '13 at 18:04
    
None of my pages are customized, unfortunately. Sudhir, when you say "Once I reset the page to site definition ...", is that something you do in SharePoint designer? Just curious. Thanks. –  hcShare Jun 10 '13 at 18:33
    
Yes, In my case the pages were changed using SharePoint designer, so I opened the page in SharePoint designer and reset it to Site Definition. Unfortunately the error message is pretty generic and it does not reveals any information. Your scenario might be different. –  Sudhir Kesharwani Jun 10 '13 at 19:19

3 Answers 3

up vote 1 down vote accepted

This error has the most simplest answer. I saw that pages in my SharePoint 2007 environment was customized using SharePoint Designer, Once I reset the page to site definition everything started working (without any errors).

I suspect that when the pages are customized in Designer, the HTML scripts for pages are taken as it is through database migrations, and SharePoint 2013 is not smart enough to render the customized pages based on old definition.

Learning, reset Designer customized pages to site definition in case site throws error after migration. This means that you will have to loose all your customization.

Please feel free to post any better answer, in case you find one...

Weird but true...

share|improve this answer
    
I'm getting the same error only I'm getting it on when I open my custom InfoPath 2010 form with code behind that I have running in my SP2013 farm. The form still opens, no issues posting form to site collection or saving data to lists from within the form, just get a lot of these 1 liner errors when I open and close. Any thoughts? Is this something that I just need to worry about? Would this happen if I upgraded the form to SP2013 format? –  Patrick Oct 4 '13 at 14:34
    
Also, is the above answer the only answer to customized forms created in SharePoint Designer? Has anyone come up with a better way to fix than resetting to site definition? I'd rather not lose any customizations. –  Patrick Oct 4 '13 at 14:36

It's a file ghosting issue in your master page. A file that was uploaded before and ghosted doesn't exist any more. You can revert back to the original master page or go through the master page and webparts to find the offending component. However if you run a SQL profiler you may be able to locate the exact component. Trial and error is often faster in these situations.

share|improve this answer

I saw this error when an InfoPath tried to pull the User information through a User Profile service (GetUserProfilebyName). I followed the steps in this post and was able to resolve the issue.

http://blogs.technet.com/b/rajbugga/archive/2013/08/07/infopath-over-claims-authentication-sharepoint-2010-amp-2013.aspx

Hope this helps.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.