Link to home
Create AccountLog in
Avatar of tegenius
tegeniusFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Poor Peformance on Sharepoint Foundation 2010 & SQL Server

I'm having slow performance problems with my sharepoint 2010 server and I don't know where to start troubleshooting them.

Access time is very slow getting onto sharepoint whilst browsing around documents is considerably quicker at times. Accessing any of the central administration is incredibly slow also and when executing powershell commands to add a solution I get this TCP provider error and then upon retrying it works. What could be causing this?

User generated image
UPDATE: I occasionally get errors saying it cannot connect to the configuration database and also Error: Exception from HRESULT: 0x80131904
Avatar of Arnold Layne
Arnold Layne
Flag of United States of America image

Are you in a very high use situation where SharePoint, SQL and Search are all on the same machine? This will effect performance, but by how much depends upon the usage.
Avatar of tegenius

ASKER

Search doesn't work so that's another issue entirely.

SQL is on a remote server. Sharepoint is a fresh install with only a couple of sites on there for early development and testing.
OK, go into SharePoint Central Admin/monitoring/review health problems and solutions and see if it's telling you anything. If you see anything in there, all bets are off until you fix all the problems.
Nothing apart from disk space as it says it won't be able to dump a snapshot. Surely that wouldn't cause it to be extremely slow though?
health.JPG
ASKER CERTIFIED SOLUTION
Avatar of Arnold Layne
Arnold Layne
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Got a ton of application errors with that transport-level error :-(

User generated image
Intermittently getting:

Error executing SQL command: 'dbo.read_calc_result'. Error: Error connecting to database!A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
IP Conflict... DOH! - After enabling and disabling various protocols I troubleshooted TCP/IP.
Thanks for the points. I don't mean appear lazy by just posting links, but this covered it all, so rather than pick through each possibility, why not let you see them all for yourself? Glad it worked out.