Tag Info

New answers tagged

0

You would normally start and stop SharePoint services using Central Administration, not the Services manager. What happens when you go to CA, Application Management, Manage services, select the server, and stop/start the service there? If you still get an error, use a ULS viewer to examine the ULS for related errors.


0

I'm using dual core E5550 + 8GB RAM to host SharePoint 2013, SQL Server 2014, Visual Studio 2013 (community). However this CPU should be stronger then any that can be found in notebook! Its doable, but slow. Especially accessing SharePoint via browser, takes minutes. Go for 4 physical cores (i5 or better), and think about putting more RAM - must be dual ...


0

If you mean i7-4510U, you'll be fine. It's got 2 cores, but each with 4 threads. 16 GB RAM is more important, and with SSD SP2013 will fly.


0

The SharePoint will run but you will get slowness. Some services, such as search, may not work. In the central administration you will have alerts on performance. But for development will probably meet the needs


1

Do a repair on your office 2010 installation. EDIT More info here. You are running Excel 2010 and Visio 2013. Run the repair on 2010 should fix your Excel issue. However you did not install the bits so that you can open it in Visio 2013 - and they don't co-exist as far as I know, you have to use one or the other. Your alternative is to just download ...


1

​15.0.4641.1001 is for ​August 2014 CU while ​15.0.4667.1000 is for ​November 2014 CU. Check from Here So what i think, you installed the Aug 2014 CU on the Live servers while on staging Server You install the Correct the CU. to fix this, simply download the Nov 2014 CU for SharePoint Server and Install on all servers in farm than Run the Config wizard. ...


0

After a day of pouring over different solutions, we found that the problem wasn't actually with SharePoint, but rather was a problem with our sql server cluster. After upgrading from SP1 to SP3 this error was resolved.


0

I had to view the Upgrade-*.log (not mentioned anywhere afaik) to notice that the process is obviously not executing past a specific content database. I had to detach this problematic content database through Central Admin (no idea why it was problematic). After this, I started getting SPUpdatedConcurrencyException, which can be resolved by running (on every ...


0

It looks like when you deployed the tool it modified your CA web app in some way without being deployed there, by removing the web app without retracting the solution your central admin now expects that assembly to be present for some component. Deploying the solution to the central admin(or somewhere else) will solve the error. Once that is done you can ...



Top 50 recent answers are included