I have installed SharePoint 2013 Enterprise version we have 3 Server of SharePoint from which 1 is App Server and other 2 is web server. Web server are on load balance. Database is SQL Server 2012 R2

SharePoint is purely used for heavy traffic Internet website. We have enable blob cache on it. Since when I enable blob cache I am getting error in ULS log 

An error occured in the blob cache.  The exception message was 'The system cannot find the file specified. (Exception from HRESULT: 0x80070002)'.

When I go to details and I found below. Now I totally understand that in my SharePoint some page or in master page or in web-part I have given wrong path of css or js due to that I am getting below error.

Which is nice to resolve but I have more that 100 pages on my website. So is there any way that I can find on which page is having such issue so I can directly concentrate to remove that error.

Hope I could put my point over here.

Hi,

In our SharePoint farm, following two user profile sync timer jobs are successfully running but not updating the 'Title' in the hidden user information list.

User Profile to SharePoint Full Synchronization

User Profile to SharePoint Quick Synchronization.

Can someone point me to the right direction? Please note that I don't want to use powershell script shown here to update the 'Title' in the user information list - http://blog.falchionconsulting.com/index.php/2011/12/updating-sharepoint-2010-user-information/.

Thanks,

Manvir

Manvir

I have two separate Sharepoint 2010 farms.  Both were upgraded from 2007.  If I go to a website hosted on farm A and in a document library upload a Word document Test.docx and then do "Edit in Microsoft Word" then everything works fine and I'm able to edit the document.  If I go to a website that's on farm B and do the same, I get the following message:

"The document could not be opened for editing.  A Microsoft Sharepoint Foundation compatible application could not be found to edit the document"

In both cases I used the same Word document, same browser (IE11) and I also verified that both websites are NOT in compatibility view (in IE11).  As a workaround, I can turn on compatibility view for the site on farm B and then that error message disappears.  But I don't understand why for the first website everything works fine but on the second website I have to turn on compatibility view.  The first website is hosted internally within our company so I also made sure that the checkbox "Display intranet sites in compatiblity view" is unchecked just so that I can force both sites to NOT be in compatibility view.  So what else could be causing this difference?  And yes, I do have "Sharepoint Open Documents Class" enabled under Add-Ons.

Thanks

Added more info:

Although both websites are in Sharepoint 2010, website A has the 2010 UI but website B has the 2007 User experience.  So I guess maybe the 2007 user experience is causing the "document could not be opened for editing" message unless the compatibility view is enabled?  This is strange since it's the exact same Word document.

Hello all,

I have a very simple workflow in SPD that looks to a field of a current item, and depending on what is chosen, sends a mail to a specific person.

When the document is uploaded, and the dropdown menu is set to whatever the user wants, and then saves, the workflow starts but no mail is sent. When I open up the item in edit mode and then save it again, the workflow starts and the mail is then sent.

It seems to me that when a document is uploaded and saved, the field is not triggering the mail.  WHen I open it up again, it then reads the field correctly and sends the mail.   Is there a way to get the info from the field on a new save?  The worflow is set to run on save and on change.

Workflow now is When: Current Item:Dropdownfield equals sendmail

then send mail to : users.

Thanks for any tips!

Brennan Best

Hi All,

I have installed OWA 2013 for SharePoint 2013 in a Farm and the same has been connected to the SP Farm. I'm able to access the OWA from all the SharePoint sites in the Farm, but the sites which are added to the Host header in the IIS causing this issue. 

Note: All the sites are Internal and for few of the sites are IIS Host Header Mapped sites.. 

Thanks in advance for your suggestions!

Arun

Arun Prakash

Recently, I've been getting the following exception during a Sharepoint full farm backup:

"A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)"

However, it looks like the final backup status is successful.  Here are some more details as to what is happening:

Backup Start:10:18pm

At 10:54pm the following exception occurs:

"A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)"

And then:

"SQL command failed and needs to be restarted. The command will be re-started a total of three times before throwing an exception"

"Retrying to connect to SQL"

Backup End: 2:06am

When I look in the backup log file, at the end it says:

"[4/30/2015 2:06:49 AM] Finished with 22 warnings.
[4/30/2015 2:06:49 AM] Finished with 0 errors.
[4/30/2015 2:06:49 AM] Backup completed successfully."

Does that mean the backup was successful?  It seems so but my full farm backup done on 4/18/2015 was 147GB (and contained 804 files) and last night's full farm backup was 109GB (and contained 732 files).  I looked at the content database size between these two backups and they were pretty much the same so I'm not sure why the more recent backup would be that much smaller.

Is there any way to prevent this "The specified network name is no longer available" error?  When I searched for it, many times it said that it might be caused by Symantec antivirus and how it handles shared network folders but I talked to our IT guy and he said that we have the latest version of Symantec and this issue does not happen with it.

I'm pretty sure we used to be able to complete the full backup with no errors.

thanks,

Hello SharePointers,

I'm migrating a SharePoint 2003 farm to SharePoint 2013 using the attach - upgrade content database method. The migration process to 2007 was fine, no errors here. But the process to 2010 came with some errors. After completing the upgrade in 2010, when opening the portal, the following message was displayed

Could not load type'Microsoft.SharePoint.WebControls.HomePage from assembly Microsoft.SharePoint.Portal

I removed it, and them, another surprise

Unknown server tag 'SPSWC:CategoryNavigationWebPart'.

Then i figured two problems here.

First: The tag 'SPSWC:CategoryNavigationWebPart'were found inside every default.aspx (welcomepage of every subsite). Removing it implies in remove the navigation menu, and the tag is inserted within default.aspx. Not the page layout, neighter the masterpage. (the portal has about 430 subsites. It is a lot of pages to edit / tags to remove )

Second: The tag in this context is the navigation tag. Removing it implies to remove the portal navigation (Maybe  recreating the masterpage and a new page layout would insert the navigation again)

How do I completely upgrade my 2003 to 2013 ? Do I need to remove it manually (programatically) ? 

I wish to bring down a SharePoint farm1 and create a new site collection in an existing farm2 and connect the new site collection in farm2 to the content db in farm1.

Is this possible and how should I do it?

An upgrade is required from a SharePoint 2007 Farm with an existing disaster recovery (DR) site to a newSharePoint 2013 Farm with a DR site. 

Currently, the production environment has a web server (Win Server 2003 R2 Standard), application server (Win Server 2003 R2 Enterprise) and a SQL 2005 standard  ( Win Server 2003 R2 Enterprise) 

The DR site has a web server (Win Server 2003 R2 Standard), application server (Win Server 2003 R2 Enterprise) and a SQL 2005 standard  (Win Server 2003 R2 Enterprise) as well. 

So just to clarify if these are the right steps to execute the upgrade.  

1. Build a SharePoint 2010 Farm ( 2 Servers - 1 web app + SQL) and perform a database attach upgrade to 2010 from the 2007

2. Build a Full SharePoint 2013 ( 2 Web Front Servers + 1 Application Server and SQL) and perform a database attach upgrade from 2010 to 2013. 

3. Build an identical farm of the SharePoint 2013 Farm as the DR site 

4. Create a Network Load Balance between the SharePoint Environment with the DR or Hot site by using network load balancing. 

5. Configure the SharePoint SQL to sync with the DR SQL by using log shipping from the Primary SQL Server to Secondary SQL Server 

In summary does most of the work in the upgrade is smoothly migrating the SQL databases from 2007 to 2010 and then finally 2013 and if this goes well everything should be fine? I know its complex but is this the general idea behind the upgrade? 

These articles helped but I'm still uncertain if these are all the right steps involve from experiences. 

http://blogs.msdn.com/b/sambetts/archive/2013/10/11/hot-standby-disaster-recovery-sharepoint-farms-basic-setup-amp-failover-high-availability-sharepoint.aspx 

https://technet.microsoft.com/en-us/library/cc262483.aspx 

https://technet.microsoft.com/library/ff607663(v=office.14) 

Is there anything else I should keep in mind and review. 

Please advise. 

Thanks, 

In our sites the designers coded all URLs as FQDN  (e.g. http://servername/sites/mysite1....). This includes URLs in webparts too. We now want to transfer the site to a new SharePoint box, of a different name, and power down the original box.  We ran a test and, sure enough, the FQDN URLs hardcoded in the copied webparts point back to the original box. This means when the old box is eventually powered down the new one won't work. My question is this: should our Designer have used relative URLs (e.g.  ../sites/mysite1) everywhere instead of referencing the server name?

TIA,

edm2

Hi using http://get-spscripts.com/2011/08/diagnose-missingwebpart-and.html to remove some Missing Dependencies.

I have a webpart being reference 58 times in the db. The wsp is currently deployed. Used the Run-SQLQuery output to track down the site, path, and aspx page. When I performed a ?contents=1 I'm not seeing any ErrorWebParts.

I've recently refreshed the Missing Server Side Dependencies, same results.

Are the odds greater that there is something wrong with analyzer, or do I need to delete all versions of the page? I'd rather avoid that if there's a better solution. Any other suggestions?

Thanks,

Scott

Hey People,

In our SharePoint 2010 based Intranet, we have a site collection (with it's own content DB) that is used for workflow processing (SP Workflows, forms, tasks and passing messages to/from BizTalk).

We go through about 3000 workflows a month and at any one time there's about 400 workflows in progress.

We've got some information management policies in place on some of the librarys/lists to keep the number of items down (~5000), but the primary workflow lists I manually delete older items (one day we'll come up with a suitable archive process).

This means the recyclebin generally has a few thousand items in it at any one time.

This has been running for just over three years now and I'm finding that I'm having to manually empty the recyclebin and run a DB maint (index re-org and statistics update), every so often, to keep the site performant.

Even though there's only about 20,000 items total in the site and the content DB is about 3Gig, I've noticed that there are 750,000+ items in the AllUserData, AllDocs, NameValuePair_Latin1_General_CI_AS and StorageMetrics tables.

I'm sure this is part of the performance problem, as it just never seems to be purging old records from these tables.  And hence, if the indexes aren't up to scratch, performance plumets.

Does anyone have any advice around this?

We're not using versions.  It just seems that old, probably deleted, content isn't being purged out of these tables.

Thanks
Craig

Hi there,

All my reports are throwing below error in a sharepoint site configured with Access services. Does anyone have a clue what's causing it?

An error has occurred during report processing. (rsProcessingAborted)
 Query execution failed for dataset 'Default'. (rsErrorExecutingCommand)
 The SharePoint list query is not valid: Data at the root level is invalid. Line 1, position 1. (rsSPDataProviderError)

Thanks

Manvir

Hi,

We have a sharepoint site in uk, we set the regional settings on the site to English(United Kingdom). On the master page for the html tag 'lang' attribute is <%$Resources:wss,language_value%> which is picking up from resource file and is shown as en-Us. What can be done to make it show en-gb. What is the recommended approach?

Hi,

after deploying SharePoint CU April 2014 "copy & paste" doesn't work for rich-text fields. The only way for getting text into rich-text fields is using the icons in the edit window. In environments before CU April "copy & paste" works fine.

Does somebody know the reason and (much more important) does somebody know how to get back the short cut?

Regards, Jens

How can I move our Sharepoint list to a different site collection (within the same web application)?

In Central Admin I can see Granular Backup->Export site or list, export then list.  Would that work?  If so, how do I then restore it to the new site collection?

I want to move it with content and permissions if possible but content only would be fine too as the permissions can be easily recreated.

thanks,

I have a number of items that are reporting in the Health Analyzer regarding missing features. I need to remove these before I do an upgrade to SP2. The problem is I am not sure why they are showing as missing when all these features are actively being used on the site. I have used the following resource to remove these features http://get-spscripts.com/2011/06/removing-features-from-content-database.html however when doing so all it does it deactivate it on the site that has the feature. Does anyone have any insight on how to go about getting rid of these?

Thanks

Kim

We have several SP 2010 sites.  When we first put the first of them up we had a little trouble with the User Profile Synchronization service but managed to get it working.  In the subsequent installations all was good.  Recently all of the UPA services stopped.  Both Filefront identity manager services show disabled and stopped.  Trying to start the UPS service in the configuration manager doesn't work on any of them.

I double checked everything stated here for permissions and whatnot..

http://blogs.msdn.com/b/russmax/archive/2010/03/20/sharepoint-2010-provisioning-user-profile-synchronization.aspx

All of our local and AD domain permissions are present.  When we try to fire up the UPA this exception is logged.

The configuration database was queried for a non-existent object with the id 213b3181-bc35-4b42-8aa4-a4c1c0455ed3. Most commonly, this is caused by removing an SPFeatureDefinition without writing upgrade code to remove references to the feature from each site.

Updating SPPersistedObject UserProfileApplication Name=User Profile Service Application. Version: 749423 Ensure: False, HashCode: 3276456, Id: f5cbf5a6-5113-4afd-952b-c73e35d69932, Stack:  
 at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()   
 at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.Update()   
 at Microsoft.Office.Server.Administration.UserProfileApplication.Update()   
 at Microsoft.Office.Server.Administration.UserProfileApplication.ResetILMFlags()   
 at Microsoft.Office.Server.Administration.ProfileSynchronizationSetupJob.Execute(SPJobState state)   
 at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)   
 at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)

Updating SPPersistedObject ProfileSynchronizationSetupJob Name=ProfileSynchronizationSetupJob. Version: 749435 Ensure: False, HashCode: 8255333, Id: 7b73978a-04c5-4b03-b999-3403ab537514, Stack:  
 at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()   
 at Microsoft.SharePoint.Administration.SPJobDefinition.Update()   
 at Microsoft.Office.Server.Administration.ProfileSynchronizationSetupJob.Execute(SPJobState state)   
 at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)   
 at Microsoft.SharePoint.Administration.SPTimerJobInvoke.Invoke(TimerJobExecuteData& data, Int32& result)

The Execute method of job definition Microsoft.Office.Server.Administration.ProfileSynchronizationSetupJob (ID 7b73978a-04c5-4b03-b999-3403ab537514) threw an exception. More information is included below.  An update conflict has occurred, and you must re-try this action. The object UserProfileApplication Name=User Profile Service Application was updated by IBTS\wap2010adm, in the OWSTIMER (8128) process, on machine SIAMAT.  View the tracing log for more information about the conflict.

Exception stack trace:  
 at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure)   
 at Microsoft.SharePoint.Administration.SPConfigurationDatabase.Microsoft.SharePoint.Administration.ISPPersistedStoreProvider.PutObject(SPPersistedObject persistedObject, Boolean ensure)   
 at Microsoft.SharePoint.Administration.SPPersistedObject.BaseUpdate()   
 at Microsoft.SharePoint.Administration.SPIisWebServiceApplication.Update()   
 at Microsoft.Office.Server.Administration.UserProfileApplication.Update()   
 at Microsoft.Office.Server.Administration.UserProfileApplication.ResetILMFlags()   
 at Microsoft.Office.Server.Administration.ProfileSynchronizationSetupJob.Execute(SPJobState state)   
 at Microsoft.SharePoint.Administration.SPTimerJobInvokeInternal.Invoke(SPJobDefinition jd, Guid targetInstanceId, Boolean isTimerService, Int32& result)

I'm thinking something is wrong with the database?  But I'm at a loss..