View Complete Post
I'm running Server 2008 (64bit) with 8Gig of RAM and 4 processors. We haven't had more than four people in Sharepoint at the same time and performance has been extremely poor (had moments where things run ok but it usually doesn't last for more than
a few minutes). We're not even doing anything advanced. Just a very small document repository with basic searching.
When I log into the server I can see several w3wp.exe processes running and will spike up to 100% of the CPU. Memory will be around 100-800 Mb for each process.
Any ideas on how to speed up SharePoint 2010 performance? Our SharePoint 2003 box runs MUCH faster and has 100+ users and over 3000 documents???
Office 2010 and SharePoint 2010 include a new set of components called Application Services. These put a rich set of tools in a developer's bag for Office automation. We'll show you how to use Office OpenXML, Word Automation Services and SharePoint to build a simple application that merges separate status reports into a single document.
Manvir Singh, Ankush Bhatia
MSDN Magazine July 2010
Microsoft Office SharePoint Server (MOSS) 2007 provides great portal and search features and much more, and Ted Pattison puts them to good use here.
MSDN Magazine August 2006
The solution covered here includes a custom SharePoint Web service that accepts SQL Server-generated report files and, through the WSS object model, stores the file in the appropriate library for enhanced collaboration possibilities.
MSDN Magazine March 2006
The knowledge worker is greatly empowered if she is able to access information across the enterprise from a central access point. With the SharePoint Portal Server 2001 Search Service you can catalogue information stored in Exchange public folders, on the Web, in the file system, and even in Lotus Notes databases. This article discusses the use of ActiveX Data Objects and the Web-based Distributed Authoring and Versioning protocol for creating search solutions based on SharePoint Portal Server 2001.
MSDN Magazine April 2002
Most large organizations have mounds of disjointed information in a variety of formats spread out across an enterprise. To make the most efficient use of that information, it must be readily accessible, easy to identify, and simple to navigate. SharePoint Portal Server 2001 unifies information by allowing members of any organization to create, share, and publish documents from a single access point. This article covers the services in SPS that can help an organization improve workflow and information management.
MSDN Magazine September 2001
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified).
Remote connections are connected, I am not 100% on the Instance name, (how would I go about checking this?)
Also I cannot access the link to SharedServices1 - Open Shared Services Admin site (not clickable), guess it's permissions but I seem to have full site permissions, I think I need SSP-Admin to make more edits to the Search, maybe this is related :s
Both Search Servers are runnig, I have tried everything I can think of to fix this and allow the Search Centre to work.
I am running Sharepoint 2007 on SQL Server 2008.
We have installed Reporting Services 2008 integrated with MOSS with SQL Server 2008 on a 64 bit platform.
The environment has worked fine in test (but the servers are not hardend).
With the production environment, any attempt to export from a report into another format (eg excel, tiff etc) results in an unexpected error within SharePoint requiring closing the browser and reopening.
There are no details behind the error. We can also find no traces of the error within any of the logs (SharePoint, Reporting Services, Windows event log etc)
When the report is opened directly from Reporting Services (ie
http://servername:8080/reportserver) the report exports fine. Similarly, if the report is opened directly from Report Builder 2, or through opening Report Builder 2 from SharePoint there is no issue. This issue
only happens when the report is invoked directly through SharePoint.
We can only assume that this issue has something to do with server hardening/UAC as we have
I have a serious problem that cannot be solved by googling around the keywords below: sharepoint, moss 2007, reporting service, ssrs 2008, rendering, internal server error, ....
The error is;
"An error occurred during client rendering. The remote server returned an error: (500) Internal Server Error. "
Everything is O.K.;
* When I render the report from the REPORTSERVER (http://localhost/ReportServer) * When the reports are scheduled to be sent by the reporting service (planned via MOSS 2007)ÃÂ
But if I open (render) the RDL file from the sharepoint REPORTS LIBRARY interface, all of the reports fail with that internal error message above.ÃÂ
It is weird also that parametrized reports are displayed without errors although the parameters are queried from a sql dataset. But I got the error when rendering the report after I've chosen a parameterÃÂ and order "apply/report"...
Possible causes how I met that error may be;
After I have installed (then uninstalled) AJAX extensions After I have re-configured IIS Web Service Extensions list items
Possible solution alternatives I've found;
I've found a solution on MSDN replying a similar issue with an ideal cause of the error but an evreka answer but no sol
our sharepoint server needs to be restarted twice a day now - always around 9.30am and 14.30pm. this has only started in the last 2 weeks. its working along fine then all of a sudden it goes to a dead page.
i have spent the last week trying to identify what it is. i have set the logging to verbose and put plenty of the messages in there into google but can not see anything relevant. the event viewer shows nothing.
i have sp2 installed but no cumalitve updates. i am wary of installing these at the mo and wreaking the whole thing. if noone has any suggestions ill install them. ill list soem details about the problem below.
it doesnt happen on weekends so it must have something to do with users using the system so im thinking something to do with the database (SQL Server 2000). NB users dont use our sp2007 on weekends.
if i restart iis, the layout of the page comes back but some of the webparts are dead so that doesnt work.
if i resart sql server, that doesnt work either.
there is plenty of room on drives and the task manager is at 20-30% when i check it when the site is down.
only a server resart seems to work.
there are just so many messages in the sp logs that i cant identify what it could be. is there any other loggi
Had a Sharepoint farm I inherited that was running on ____ hardware in a ____ setup- raid controller failed, and the rack was setup so that I have to down 15 servers that might not come back up, just to get at the server... Complete, unrecoverable failure.
This server was a member of our Sharepoint 2007 farm, and had Reporting Services on it. There are a lot of little pieces that are still referenced in the Central Configuration. I removed the server forcibly, and need to know next steps, specifically:
1. I tried to move Reporting Services to another server, but I get an error in the Grant Database privileges that I cannot connect to the Report Server's WMI Provider. I created a SPN on a DC, forced a replication a few hours ago, and still no luck. Any
2. How do I fix all the little things that reference that server? Anytime Sharepoint initiates a web page to Central Administration, it tries to use that server address.
I think the failed server was running SQL 2008 or SQL 2008 R2, and the server I am moving this to is SQL 2005 SP2. I have installed the correct Reporting Services for Sharepoint. Have I missed something?
Time is of the essence because management relies on Reporting Services and I am under a great deal of pressure to fix this. I appreciate any help I can get.