SQL Server Compatibility With SharePoint Workflows
Dec 7, 2007
I am a beginner with SQL Server and SharePoint. I am trying to migrate
the database to other servers that may be running different
platforms. I know that the other servers have SharePoint so they are
running SQL Server 2005, SQL Server 2003, and Access. Is there a way I
could get data from my system (with SQL Server 2005) to another system
(that may be running 2005, 2003, or Access) without affecting my data
or SharePoint workflow? I want the people running the other servers to
be able to access the same data and see the same workflow I do. Thanks
in advance!
who has workflows created and ordered by CreateTimestamp . i need to count the number of workflows from top to point where there is either a success or failure workflow that occurs at the latest .Â
1.ban 137108351 has success workflow and prior to that workflow it has 2 workflows (exclude success and failure) 2.ban 104917284 has success workflow as latest (it still has failure but not considered because it is occurred earlier to success ) and prior to that workflow it has 2 workflows (exclude success and failure) 3.ban 107500674 has failure workflow and prior to that workflow it has 0 workflows (exclude success and failure)
below provided code for sample data as well
GO /****** Object: Table [Temp].[deleteit] Script Date: 7/31/2015 3:04:55 PM ******/ SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE TABLE [Temp].[deleteit]( [ban] [nvarchar](256) NULL,
I get the following error when I try to navigate to a report/model/data source, stored in a Sharepoint Document Library using a Sharepoint URL based on an Extranet or Intranet zone - but it works OK using the url for the Default zone:
System.Web.Services.Protocols.SoapException: The specified path refers to a SharePoint zone that is not supported. The default zone path must be used. ---> Microsoft.ReportingServices.Diagnostics.Utilities.SecurityZoneNotSupportedException: The specified path refers to a SharePoint zone that is not supported. The default zone path must be used.
Is this a limitation of the SQLRS-WSS3 integration or is there a workaround?
Does anyone know the location of Microsoft.ReportingServices.SharePoint.UI.WebParts.dll after you install the web part? I am wondering if I can inherit from this web part to wrap some other functionality into it. I know that i see it in the GAC buyt can't seem to find it so I can look at the assembly using reflector.
Also, how easy is it to pass in parameters to the Report Viewer?
Since I wasn't getting any replies with answers or suggestions to my initial posting, I figured I would continue to list the problems and solutions I've encountered while trying to setup and utilize SharePoint integration mode, and read data from SharePoint with SSRS reports (developed in VS2005). Hopefully this is helpful to anyone that is also trying to learn all this stuff and figure it out.
(Single server - W2K3R2_SP2 as: DC / SQL2005 Standard / MOSS2007 Enterprise - see the bottom of this posting for the steps I took to set that up)
Note: After I get this to work, I intend to post my experiences for setting up SharePoint Integration with SQL and SP on separate boxes.
1. In the new reporting section under SharePoint application management in the Central Admin Console, the Grant database AND Set Server Defaults work when using the domain admin account, but not when using the SQLSPS service account I used to setup both SQL and SharePoint. Why can't I use the service account? Is the domain admin account now going to be used as a service account for accessing the sharepoint database?
This question remains unanswered as of yet.
2. Reporting Services configuration tool shows Sharepoint integration as red x when I create a new database in integration mode. (the service account SQLSPS and the Server object are members of the group WSS_WPG). If I switch back to native mode (the original reportserver database), the red x goes to a blue exclamation instead. Using Service Credentials or Windows credentials (as either the service account SQLSPS or as domain admin) doesn't change anything.
RESOLVED by using a domain user account for the ReportServer WebApp. Even though everything is installed on the same machine, it seems using the default of NETWORK SERVICE wasn't acceptable. Possibly because SharePoint is configured to allow additional machines in the farm?
3. http://servername:8080/reportserver will display Report Server information as it did before the integration on port 80, but http://servername/reportserver doesn't display anything through SharePoint.
Resolved. I needed to define a repository before I could view it (go figure). When I created a sharepoint site based on a report center template, created a data connection library and report library, and then referenced that by http://servername/sites/myReportCenterSite/myReportLibrary, I was able to see the equivalent of http://servername/reports (which is now disabled due to integration mode).
4. Unable to deploy to new report center sharepoint site I mention above using Visual Studio. I kept getting "A connection could not be made to the report server http://servername/sites/ReportCenter. Server was unable to process request. The request failed with HTTP status 503: Service unavailable (System.Web.Services). In Visual Studio, the project properties were: TargetDataSourceFolder = http://servername/sites/myReportCenterSite/myDataConnectionLibrary, TargetReportFolder = http://servername/sites/myReportCenterSite/myReportLibrary, TargetServerURL = http://servername/sites/myReportCenterSite/
Found these errors in the event logs on the server.
Event Type: Warning Event Source: W3SVC Event ID: 1021 Description: The identity of application pool, 'ReportServer' is invalid. If it remains invalid when the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.
Event Type: Warning Event Source: W3SVC Event ID: 1057 Description: The identity of application pool 'ReportServer' is invalid, so the World Wide Web Publishing Service can not create a worker process to serve the application pool. Therefore, the application pool has been disabled.
Event Type: Error Event Source: W3SVC Event ID: 1059 Description: A failure was encountered while launching the process serving application pool 'ReportServer'. The application pool has been disabled.
RESOLVED the issue by changing the Application Pool used by reporting services from ReportServer to DefaultAppPool and changing the account DefaultAppPool used from NETWORK SERVICE to my service account SQLSPS. I have no idea why ReportServer is invalid, it was set to use the service account SQLSPS the same as DefaultAppPool is. Perhaps the reporting services add-on makes a change to invalidate this?
5. Attempting to read a SharePoint list using a SSRS report. This should be fun.
First, created a new custom list in the ReportCenter SharePoint sites I've been using and called it myCustomList. I added one item with a title of myCustomListItem1. I don't know if I need to do more than that for a simple test of reporting or not yet.
Second, configured new shared data source. Name = myCustomList1DataSource, type=XML, Connection String = http://servername/_vti_bin/lists.asmx (this URL is viewable in IE), Using Windows authenticaion.
Third, in VS2005 on a workstation in the domain, create new report item (report1.rdl). New dataset for report; Name=Report1DataSet, Data Source=myCustomList1DataSource (Shared), Command type = text, Query String = [See Queries and associated errors below]:
Initial query obtained from: Connecting SQL Reporting Services to a SharePoint List (David Wise) http://www.sharepointblogs.com/dwise/archive/2007/11/28/connecting-sql-reporting-services-to-a-sharepoint-list-redux.aspx
Note: Queries when executing the dataset (which errors out) and when executing a query in CAML Viewer for the same information (which does work just fine) both initially return 401.1 and 401.2 errors (as viewed in Fiddler). Since the CAML query works, I have not tracked this down yet.
Parameter; Name => listName, Value => =myCustomList
Was NOT prompted to define the query parameters
- Gets this error: "An error occurred while setting the command text property of the data extension command. The XmlDP query is invalid. (Microsoft.ReportingServices.DataExtensions)."
- Advanced information from the error => 'http' is an unexpected token. The expected token is '"' or '''. Line 2, position 19. (System.Xml)
B. Changed: Placed the namespace URL in quotes (also tried with and without / in namespace after /soap)
Parameter; Name => listName, Value => =myCustomList (also tried Value => myCustomList) (no equal sign)
Clicked "!" to execute, and got prompted to define the query parameters Entered Name => listName, Value => myCustomList
- Gets this error: "failed to execute web request for the specified URL (Microsoft.ReportingServices.DataExtensions)."
- Advanced information: <faultstring>Server did not recognize the value of HTTP Header SOAPAction: http://schemas.microsoft.com/sharepoint/soap/GetListItems/.</faultstring>
C. Try the query string that seems to work for Stramit CAML Viewer to read myCustomList
Also tried <Query xmlns="http://schemas.microsoft.com/sharepoint/soap/"> </Query>
And tried entering no query...
Parameter; Name => listName, Value => =myCustomList (also tried Value => myCustomList) (no equal sign)
Clicked "!" to execute, and got prompted to define the query parameters Entered Name => listName, Value => myCustomList
- Gets this error: "failed to execute web request for the specified URL (Microsoft.ReportingServices.DataExtensions)."
- Advanced information: <soap:Fault><soap:Code><soap:Value>soap:Receiver</soap:Value></soap:Code><soap:Reason><soap:Text xml:lang="en">Server was unable to process request. ---> Data at the root level is invalid. Line 1, position 1.</soap:Text></soap:Reason><soap: Detail /></soap:Fault>
RESOLVED. Went back to the query used in B above, and mysteriously it works now. This could be the "funny things happen" symptom I've been reading about. We'll see if it continues to function.
Here's what I've learned so far on Issue #5:
1. XML is confusing. XmlDP is even more confusing...whatever that is. Apparently it's new to/with Reporting Services in SharePoint integration mode? 2. There is far too little documentation regarding XmlDP and querying SharePoint lists from SQL Reporting Services. 3. According to http://msdn2.microsoft.com/en-us/library/ms159741.aspx: You must use the generic query designer to create the query. The query is not analyzed to identify parameters; therefore you must create parameters through the Parameter tab on the Dataset dialog box.
Tried this query:
<Query> <SoapAction>http://schemas.microsoft.com/sharepoint/soap/GetListItems</SoapAction> <Method Namespace="http://schemas.microsoft.com/sharepoint/soap/" Name="GetListItems" /> <Parameters> <Parameter Name="listName"> <DefaultValue>myCustomReport2</DefaultValue> </Parameter> <OrderBy> <FieldRef name="ows_Date" /> </OrderBy> </Parameters> </Query> I was still prompted for the listName and the list returned with ows_Date still out of order. So maybe that proves this statement is true? <translation: why make it convenient when it's already [somewhat] functional?> 4. When building the dataset, anything I place in the "Query string" box has to be enclosed in <query></query> tags or it errors out. I am trying to understand how to translate the CAML viewer query (which does work but isn't wrapped in query tags) into something that fits between query tags, and it hasn't gone well so far. <translation: To be at one with your reports Grasshopper, you must understand xml> 5. According to http://srv1/sites/ReportCenter/_vti_bin/lists.asmx, "GetListItems" operation is supported <translation: you're getting warmer...> 6. According to the soap output of my site http://srv1/sites/ReportCenter/_vti_bin/lists.asmx?op=GetListItems, I am only allowed to specify the following parameters: listName, viewName, query, viewFields, rowLimit, queryOptions and webID. <translation: that and $3.00 will get you a cup of coffee> 7. According to http://www.sharepointblogs.com/dwise/archive/2007/11/28/connecting-sql-reporting-services-to-a-sharepoint-list-redux.aspx, only listName, viewName and rowLimit parameters are usable(?) (query and queryOptions may not be working properly with SSRS). <translation: that kind of sucks> 8. When this started mysteriously working again, I tested using the "/" at the end of the namespace (wouldn't work without) and the "=" sign in front of the parameter value as defined on the parameter tab of the dataset (turns out to be optional).
As long as I can query SharePoint and get my list information back, I'm going to consider this issue closed and move on to actually using this information in a report. I'm sure that won't work right either, but why stop now?!
6. Ok, now that I can read SharePoint list data with SSRS, I need to try and actually do something with it.
A. Begin by setting up new data to report on
1. Create a new custom list (myCustomList2) and add a test record. This list will simulate the data we intend to submit to SharePoint using InfoPath, so it has a number of custom/created columns in it
2. Modify the working information from #5 above; add a new shared data source (myCustomList2DataSource), tell the dataset to use the new shared data source, change the information set in the parameter tab (Name => listName, Value => =myCustomList2) and test the dataset. Lucky me, it actually returned the record I entered on the first try.
B. Begin to build the report with the dataset returned
1. So, as I'm feeling good that it's actually reading the list in Step A without me threatening to destroy the machine, I look to the left in the Dataset results navigation pane in VS2005 and realize there are NO fields for me to choose to report on. 2. At this point, I have no clue what to do about getting this XML data into a report. Not that I have a large clue about SSRS otherwise, but I have at least been able to build SSRS reports when using a SQL database as the datasource. Fyi, http://msdn2.microsoft.com/en-us/library/ms159741.aspx states: "Reports can use data from XML documents and Web services, or embed XML in the query. There is no built-in support for retrieving XML documents from a SQL Server database.", in case anyone is trying to do that....
RESOLVED. Since the fields were not appearing automatically, I had started to add new fields to the dataset manually (if it doesn't work, beat it with a hammer, right?). I entered half a dozen or so fields, each one with the exact name as displayed in the query results, and then decided it would be fun to hit the refresh fields icon. As soon as I did that, all the fields shown in the query immediately appeared in the dataset and I was able to add them to a report. I don't know if I hit the refresh fields when working in issue #5, so I can't say if they are there now because of that, or because of adding some fields manually first, a combination of the two, or if it's just one of those mystery items I'm reading about with sharepoint reporting.
7. Rows are being returned even though they have NULL values (so far anyway), and most data is returning nicely for the bulk of the columns I created in the list I'm reporting on. Here are the current issues:
A. I have one column in my SharePoint list that is multi-lined text. If the text type is either rich text or enhanced rich text, the value returned in the query is formatted like this: "<div class=ExternalClassyadayada<div>My notes display here". If I set the column to be plain text, this doesn't happen. I will need to figure out how to filter that for my report.
RESOLVED. David Wise had some code listed at http://www.sharepointblogs.com/dwise/archive/2007/11/28/connecting-sql-reporting-services-to-a-sharepoint-list-redux.aspx that addressed this issue somewhat. I modified it to match my circumstances. Disclaimer: I'm not a programmer, so use this at your own risk.
function ExtractMultiLineText(myField as string) as string dim strBegin as string dim strEnd as string dim myBegin as integer dim myEnd as integer dim myTextLength as integer strBegin = "<div>" strEnd = "</div>" if myField = nothing then return "" if myField = "" then return "" myBegin = Instr(myField, strBegin) + Len(strBegin) myEnd = Instr(myField, strEnd) myTextLength = myEnd - myBegin
if myBegin < 1 then return myField return mid(myField, myBegin, myTextLength) end function
B. I have two columns in the SharePoint list that are set as number values with 0 decimal places. When I query those however in SSRS, they return with the number plus like 12 zeroes behind the decimal. Not a major issue, but I'll put it on the list anyway.
RESOLVED. Used the Int() function; =Int(Fields!ows_myProblemNumber)
C. If I go to "/_vti_bin/lists.asmx?op=GetListItems", it appears from the sample soap output that I am allowed to ask GetListItems for is: listName, viewName, query, viewFields, rowLimit, queryOptions and webID. As I mentioned in issue #5, according to http://www.sharepointblogs.com/dwise/archive/2007/11/28/connecting-sql-reporting-services-to-a-sharepoint-list-redux.aspx, only listName, viewName and rowLimit parameters are usable(?) and query and queryOptions may not be working properly with SSRS.
So, if I can't put anything other than this in my query string;
<Query> <Method Namespace="http://schemas.microsoft.com/sharepoint/soap/" Name="GetListItems"/> <SoapAction>http://schemas.microsoft.com/sharepoint/soap/GetListItems</SoapAction> </Query> and I only have a couple parameters to pass on top of that, then it appears to me that my options for filtering the amount of data returned from the SharePoint list is to figure out a way to do it with expressions in the parameters or in the report itself. Am I missing something? Is this really all I get to work with out-of-the-box?
More to come...
================================== Installation steps taken to build the server VM: ==================================
(Using VirtualPC 2007) 1. Build OS (2003R2SP2) and promote to DC
1a. Create domain user service account SQLSPS 2. Prep for SQL
3a. Verify SSRS works 3b. RS config tool shows SP integration as blue exclamation 3c. Use service account SQLSPS for anything requiring Windows credentials 4. Install SQL2005 SP2
4a. Verify SSRS works 4b. RS config tool shows SP integration as blue exclamation 5. Prep for SharePoint
5a. Install .NET 3.0 6. Install MOSS2007 Enterprise and configure
6a. Webapps, SSP and anything else use svc acct SQLSPS 6b. Move Default website to port 8080 and re-activate (SharePoint stopped the site) 6c. Verify SSRS works on 8080 7. Install Reporting Services Add-in 8. Create new RS database in integration mode (with service credentials)
8a. RS config tool shows SP integration as red x 9. SP central admin /application management / manage integration settings
9a. reports server = http://srv1:8080/reportserver (since default port has been moved to 8080) 10. SP central admin /application management/grant database access
10a. using the FQDN, confirm servername and default instance - click OK 10b. Prompted for an account to use to retrieve information; svc acct SQLSPS did not work, domain admin did though 11. SP central admin / application management/set server defaults
11a. Accepted all defaults 12. Verify reportserver answers at http://srv1:8080/reportserver (via reportserver AppPool and DefaultAppPool) 13. Changed the application pool identity for the ReportServer AppPool from Network Service to the domain user service account I used for all SQL and SharePoint configurations (SQLSPS) and rebooted. The red x for sharepoint integration in the RS configuration tool is now a green checkmark.
I am trying to install SQL server 2000 on my laptop which has vista as OS. I am not able to install it , somehow it fails. Can anyone please suggest me how can i accomplish this.
Is SQL Server 7.0 compatible with the Windows 200 operating system? Arethere certain patches or service packs that need to be applied to SQL tomake this compatibility work? Thanks.Larry
Are there any known issues with using RDO with SQL Server 2005?
My company is in the process of updating our SQL Server 7 database to SQL Server 2005. Most of our applications are several years old and written using RDO to access the database. I have since started the daunting task of updating all the applications to ADO, but it's only about a quarter of the way done. We need to update the database ASAP, but we cannot wait until all the applications have been updated to ADO.
While testing the applications (written in VB6) against the new SQL Server 2005 database, I have come across a problem with the RDO queries not returning the correct data. The query returns 4 records. In the SQL7, it properly shows 4 for RowCount and 4 records are present in the recordset (as seen by looping through the recordset using rs.MoveNext). In SQL2005, it properly shows 4 for RowCount, but looping through the recordset shows that the recordset only contains 1 record. The problem seems to be linked to a Left Join in the Query. (see below) Table1 has a column that has a RecID for Table2. In the case where the Table2RecID column in Table1 is 0, the row is just not added to the recordset even though it increments the RowCount.
Code:
SELECT * FROM Table1 As T1 LEFT JOIN Table2 As T2 On T1.Table2RecID = T2.RecID
I converted the query to ADO and it ran fine with no problems. The issue has something to do with SQL Server 2005 and RDO.
We are going to upgrade to windows 2000 in the near future. We currently use sql server 6.5. Can anyone tell me if SQL 6.5 will run on windows 2000? Also will SQL server v7 run on windows 2000 or do I need to upgrade to SQL 2000?
A client just purchased a new notebook, pre-installed with Vista. He says he is having trouble installing SQL Server 2000 (database and client tools). I am not certain (yet) if this is the standard edition or the desktop version.
What, if any, are known compatibility issues between SQL 2000 and Vista?
I have an SQL database that I need to detach from an SQL2005 server and reattach to an SQL 2000 database. I tried to set the Compatibility level from SQL Server 2005 (90) to SQL Server 2000 (80). This did not work
Hi, don't know if anyone can help me but I desperately need to roll a report out which relies on an SQL 7.0 datasource.
Current situation - Reporting Services 2000 up and running on an SQL 2000 box - no problems getting reports to run from the native machine but I cannot get the thing to make a hop to our SQL 7.0 box.
I've created three data sources - OLEDB, Native and ODBC. For the OLEDB and Native I am getting a DATABASEPROPERTYEX error - I assume here that reporting services is polling the SQL 7.0 box with an unsupported method.
For ODBC I CANNOT get the parameters to work - I've read all sorts of stuff about using unnamed parameters, so I've put a ? in the query and I'm getting Invalid parameter number and invalid parameter number errors (I suspect it is getting a bit confused, but then so am I).
So I thought I'd try a linked server, sure enough with a fixed parameter I can get through the linked server no problem, but again I can't work out the syntax/series of events needed to use a parameter with this, I'm starting to suspect it can't be done with an Exec statement.
So - first question - is there any way around the DBPROPERTY EX problem so I can use OLEDB/SQL Client connectivity and secondly please can someone explain what exactly has to go in the parameters box when I press ... on the data source box, 'cos it's doing my head in.
Hi. I am using visual studio 2005 with Sql Server Express Edition. I haven't install sql server 2005 Professional edition on my machine. It works fine. The connection string is:
You can see I haven't hardcoded machine name and there is no absolute path. I have open the website on another machine and it works fine. Now , i have open this project on third machine but it doesn't work and gives the following error:
"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"
I think there is some problem with sql server configuration . Please help me in this regards. I will be very thankful to you.
I want to choose between Windows Vista editions. Please help me I should go for Windows Vista Business or Windows Vista Home Premium as I intend to install SQL Server 2005.
We have the following trace flags present in startup in SQL server 2000:
809 1204 3605 3913
Need to understand if these should be required in SQL Server 2005 + SP2 version. I have run the upgrade advisor tool which indcates that the behaviour of some flags has changed and some other TFs are no longer applicable. Hence, I want to know about the above mentioned TFs.
Hi, When using an Access Project 2002 connected with SQL Server Express in OLE DB it's impossible to work in creation mode. A message explains that this Access version is not compatible with this SQL version. Is there a service pack ?
Hello All, I am in the process of upgrading my current database in SQL Server 2000 to SQL Server 2005. I have finished my analysis using the upgrade advisor and have found a lot of SPs having upgrade related issues. From what I estimate I think it will take around 3-4 weeks to resolve all of those issues. I wanted a quicker way to upgrade my database since we have very little time for the final release. The main reason for upgrade to 2005 was use of new features like Database Mirroring and/or peer to peer replication alongwith the Partitioning features and the new T-SQL enhancements.
The question I wanted to ask was does the compatibility level 80 of SQL Server 2005 supports these new features. From what I have read on the KB article at http://support.microsoft.com/kb/822400 is that mirroring is supported in any compatibility level, but there is no specific mention on the peer to peer thing. Also when I personally tried using the New Partitioning Features of 2005 on the database having compatibility 80, it worked fine. Also other features like SQLCLR and TRY...CATCH works fine. One thing I observed was that new T-SQL statements like PIVOT/UNPIVOT is not supported
It will be nice if someone can give out the entire list of features that will be supported in the compatibility Level 80 and also the list of the ones that are not supported.
Hello everybody, I have question ablout the installing SQL Server 2005 in the windows XP profesional, I always install sql server on my machine with the Windows XP professional edition as usual without any problem but now I have a strange problem, first on the System configuration stepeverything is OK except €œSQL Server Edition Operating System Compatibility (Warning) €œ ,with this message :
- SQL Server Edition Operating System Compatibility (Warning) Messages ·SQL Server Edition Operating System Compatibility
·Some components of this edition of SQL Server are not supported on this operating system. For details, see 'Hardware and Software Requirements for Installing SQL Server 2005' in Microsoft SQL Server Books Online.
Meanwhile the main problem is in the €œ Component to install €? window as I don€™t see these serises of component checkbox enable! Except the €œWorlstation component, books online and development tool €œ,
sql server database services -->disable anlysis services -->disable reporting services -->disable notification services -->disable integration services -->disable Worlstation component, books online and development tool -->enable
And after that I make sure about the serious problem and then I decide to continuing installation with clicking on the enable check box and then I have an instance of SQL Server on my machine but it isn€™t compelete . I tried to solving my problem with unistalling the SQL Server and reinstalling the this software again but this problem still exist, and then I decide to change my window and reinstalling this again , I do that but It is not work out!!
Therfor if it possible for you please help me to solving my problem, thank you very much
I have just upgraded a test server from sql server 2008 sp3 to sql server 2014 inplace upgrade. The compatability level of master database has not upgraded. It was showing 90 and the rest of system databases got updated to 120. Is it fine to update the compatibility level of master database ? Any precautions need to taken??
I installed SQL Server 2005 Developer Edition. When i create a new database (using the "New Database" dialog) i cannot set the new database's compatibility level to "SQL Server 2005(90)" because this option is not in the "dropdown list". the only items shown are: "SQL Server 7.0(70)" and "SQL Server 2000(80)". I set the owner to "sa". How do i get "SQL Server 2005(90)" in my "compatibility level" drop down list? Is this an installation option that i missed? Thanks in advance for any assistance!
Not sure if this gets fixed on a restart, but the Backward Compatibility upgrade/piece failed on service pack 1 install for SQL Server 2005. Here is the log output. Anyone experience this?
05/19/2006 08:58:27.648 ================================================================================ 05/19/2006 08:58:27.648 Hotfix package launched 05/19/2006 09:00:04.368 Attempting to install instance: SQL Server Native Client 05/19/2006 09:00:04.383 Attempting to install target: CLARITY 05/19/2006 09:00:04.383 Attempting to install file: sqlncli.msi 05/19/2006 09:00:04.399 Attempting to install file: \<server>s$917f50731dade382ab1bHotFixSqlncliFilessqlncli.msi 05/19/2006 09:00:04.399 Creating MSI install log file at: C:WINDOWSHotfixRedist9LogsRedist9_Hotfix_KB913090_sqlncli.msi.log 05/19/2006 09:00:04.415 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 05/19/2006 09:00:04.415 Failed to read registry key: Debug 05/19/2006 09:00:51.040 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0. 05/19/2006 09:00:51.118 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 05/19/2006 09:00:51.118 Failed to read registry key: Debug 05/19/2006 09:00:51.118 Pending reboot, successfully installed file: \<server>s$917f50731dade382ab1bHotFixSqlncliFilessqlncli.msi 05/19/2006 09:00:51.134 Successfully installed target: <SERVER> 05/19/2006 09:00:51.134 Successfully installed instance: SQL Server Native Client 05/19/2006 09:00:51.134 05/19/2006 09:00:51.134 Product Status Summary: 05/19/2006 09:00:51.134 Product: SQL Server Native Client 05/19/2006 09:00:51.134 SQL Server Native Client (RTM ) - Reboot Required 05/19/2006 09:00:51.134 05/19/2006 09:00:51.134 Product: Setup Support Files 05/19/2006 09:00:51.134 Setup Support Files (RTM ) - Not Applied 05/19/2006 09:00:51.150 05/19/2006 09:00:51.150 Product: Database Services 05/19/2006 09:00:51.150 Database Services (RTM 1399 ENU) - Not Applied 05/19/2006 09:00:51.150 Reporting Services (RTM 1399 ENU) - Not Applied 05/19/2006 09:00:51.150 05/19/2006 09:00:51.150 Product: Notification Services 05/19/2006 09:00:51.150 Notification Services (RTM 1399 ENU) - Not Applied 05/19/2006 09:00:51.150 05/19/2006 09:00:51.150 Product: Integration Services 05/19/2006 09:00:51.150 Integration Services (RTM 1399 ENU) - Not Applied 05/19/2006 09:00:51.150 05/19/2006 09:00:51.150 Product: Client Components 05/19/2006 09:00:51.165 Client Components (RTM 1399 ENU) - Not Applied 05/19/2006 09:00:51.165 05/19/2006 09:00:51.165 Product: MSXML 6.0 Parser 05/19/2006 09:00:51.165 MSXML 6.0 Parser (RTM ) - Not Applied 05/19/2006 09:00:51.165 05/19/2006 09:00:51.165 Product: SQLXML4 05/19/2006 09:00:51.165 SQLXML4 (RTM ) - Not Applied 05/19/2006 09:00:51.165 05/19/2006 09:00:51.165 Product: Backward Compatibility 05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied 05/19/2006 09:00:51.181 05/19/2006 09:00:51.181 Product: Microsoft SQL Server VSS Writer 05/19/2006 09:00:51.181 Microsoft SQL Server VSS Writer (RTM ) - Not Applied 05/19/2006 09:00:51.181
We have recently migrated quite a databases around 20 from SQL 2000 and 2005 to SQL server 2008R2.
I am using Ola's script for index maintenance for those with compatibility level above 80 as i heard it supports that way.
Hence separated in 2 way job where for those with compatibility level 80, we are running job with below query on each database with 80 as compared
USE ABC GO EXEC sp_MSforeachtable @command1="print '?' DBCC DBREINDEX ('?', ' ', 80)" GO EXEC sp_updatestats GO
I am not sure if this is the only way in for those databases, because we are seeing the database getting because of that somewhere using above query.( seems log file filling very rapidly).
But above is not the case with those databases , with compatibility 90 and above.
I have an intranet environment consists of two servers:
- An application server windows 2003 server with 64-bit server Sharepoint 2007 SP1 (Standard version for search) - A database server windows 2003 server with 64-bit SQL Server 2005 SP2 64-bit (Standard - 9.0.3054)
It happens regularly that the database server crash (frozen black screen) while the application server indexes (crawl) the content of the intranet site based on sharepoint. There is no alert / error in the observer of events, nor in the sql logs.
The crash is uncertain: dice once all goes well, soon after that crash. When i set the parameter search service (service management research), I can define a regulatory impact of the robot to change the number of documents at the same time : "Request 2 documents at the same time, the crash is more rare, "ask 64 documents at a time, the crash is more common.
My Intranet under sharepoint is composed of a collection site with a dozen sub-sites. There are 3 large library of PDF document. All done in the 4 go in terms of volume.
My problem for about 3-4 months. (Maybe more. Before, indexing was not yet in place).
I have a problem when configuring SharePoint and RS on two boxes. (If install everything in one box is fine)
I have SQL SP2 + RS in one server and SharePoint on the other server. I've followed every step in the SQL 2005 Online Book to configure the RS and SharePoint including:
How to: Install the Windows SharePoint Services Object Model on a Report Server Computer. (Done) How to: Configure Service Accounts (Reporting Services Configuration). (Done)
However, I got an error when click "Set server defaults" in SharePoint Central Admin: An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode.
In ReadMe of SQL SP2, see below: http://download.microsoft.com/download/f/d/c/fdcb3a53-0cb1-4e67-a1b6-45b89b3c59cf/readme_rsaddin.htm#_rsshare_known_problems_7
--- 6.4 Service account requirements for Reporting Services
Restrictions on using built-in accounts apply to some deployment topologies of Reporting Services that include a report server running in SharePoint integrated mode. The following combination of factors will result in service account requirements:
The report server is integrated with a SharePoint farm comprising more than one computer.
The report server and SharePoint Central Administration Web site run on separate computers.
In this scenario, if either the Report Server Web service or Windows service runs under a built-in account such as NetworkService, the Grant database access option in SharePoint Central Administration will not work correctly. Consequently, accessing any Reporting Services feature through a SharePoint site will result in the following error:
"An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode. --> Server was unable to process request. --> Client found response content type of 'text/html; charset=utf-8', but expected 'text.xml'."
To avoid this error, choose one of the following approaches:
On the computer that hosts the report server, continue to run the Report Server Web service as NetworkService and add the built-in account, such as NT_AUTHORITYNetworkService to the WSS_WPG Windows group.
Configure the service accounts to run under a domain user account as follows:
Start the Reporting Services Configuration tool and connect to the report server.
Click Windows Service Identity, click Windows Account, type a domain user account, and click Apply.
Click Web Service Identity, for Report Server, click New, type an application pool name, click Windows Account, type a domain user account, and click Apply.
Reset IIS.
Restart the Windows service.
---
I did try it out but still get the error when clicking "Set server defaults" link in SharePoint Central Admin.
Is there something wrong with the two boxes installation???
I created an ASP application using Web Developer Express and SQL Server Express on my workstation. Everything works great. I copied the application and all files to my intranet server which is a 2003 server running Sharepoint. When I attempt to run the application from the server.Access to the ADO.net Managed Provider 'SqlClientFactory' was denied in the data source with ID 'SqlDataSource' because of security settingsIs there something in the web config that I must change or settings on the server that must be changed for the application to run?
I have (2) questions about SQL versions and (1) question about "Standard Log Sizing" for SharePoint directory. I am pretty sure about SQL 2000 versions "Not being Certified".
1) Which versions of MS SQL Server 2000 and 2005 are certified to run on Vista?
2) Which versions of MS SQL Server 2000 and 2005 are certified to run on Internet Explorer 7 (IE7)?
3) What should the "Standard Log Sizing" be for MS SharePoint Server drive be? Or is there an actual standard?
