Report builder error after applying sql server 2008R2 SP3 when click on report builder gives error like 'Application validation did not succeed. Unable to continue.

Hi All,
I applied SQL server 2008 R2 SP3 recently but report builder doesn't work since then
When click on report builder gives error like 'Application validation did not succeed. Unable to continue.
and when I try to see details the error summary like following:
+File, Microsfot.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
this is urgent.
Please reply me asap.
thanks a lot in advance.
Regards,
Nik
Regards, Naman

Hi nikp11,
According to your description, you recently updated SQL Server 2008 R2 to SP3, Report Builder doesn’t work since then the error occurs: "Application validation did not succeed. Unable to continue".
This is an known issue in SSRS 2008 R2 SP3 that Microsoft has published an article addressing this issue. It is not planning to release a fix for this issue. But we could implement one of the following workarounds:
Install and run Report Builder 3.0 of SQL Server 2008 R2 RTM.
Install and run Report Builder of SQL Server 2014.
Uninstall Service Pack 3 then uninstall Service Pack 2 and then reinstall Service Pack 3.
Reference:
Report Builder of SQL Server 2008 R2 Service Pack 3 does not launch
Thank you for your understanding.
Best Regards,
Wendy Fu

Similar Messages

  • Re SQL Server 2008R2 SP3 installation on Windows 8 64 bit

    Hi,
    I am trying to install SQL Server 2008R2 SP3 on Windows 8 64 bit but I am getting stuck while selecting features.
    Error: There are no SQL Server instances or shared features that can be updated on this computer.
    Let me know how this can be resolved.
    Thanks,
    Ar

    Are you running right setup file depending on whether your machine (or Express instance) is x86 or x64?
    ENU\SQLServer2008R2SP3-KB2979597-x64-ENU.exe
    ENU\SQLServer2008R2SP3-KB2979597-x86-ENU.exe
    Please reverify current version of the server - just to make sure it was not patched.
    SELECT
      SERVERPROPERTY('productversion') as 'Product Version',
      SERVERPROPERTY('productlevel') as 'Service Pack',
      SERVERPROPERTY('edition') as 'Edition',
      SERVERPROPERTY('instancename') as 'Instance',

  • Error while installing SQL Server 2005 SP3

    I have installed SQL Server 2005 Standand Edition (32-bit) on a standalone server machine running
    Windows Server 2003 R2 Standard 64-bit with Service Pack 2. After installing SQL Server, when I tried installing the Service Pack 3 (as per application requirement) through local administrator account, I am repeatedly getting below error in
    "C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_SqlSupport.msi.log"
    SECUREREPAIR: SecureRepair Failed. Error code: 4ec4E6A3388
    MSI (s) (F8:40) [16:49:33:515]:
    Error 1260. Windows cannot open this program because it has been prevented by a software restriction policy.
    I have checked rights on the folders and also got the anti-virus (symantec) services stopped on the server. Still no success, can anyone help.

    I have installed SQL Server 2005 Standand Edition (32-bit) on a standalone server machine running
    Windows Server 2003 R2 Standard 64-bit with Service Pack 2. After installing SQL Server, when I tried installing the Service Pack 3 (as per application requirement) through local administrator account, I am repeatedly getting below error in
    "C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_SqlSupport.msi.log"
    SECUREREPAIR: SecureRepair Failed. Error code: 4ec4E6A3388
    MSI (s) (F8:40) [16:49:33:515]:
    Error 1260. Windows cannot open this program because it has been prevented by a software restriction policy.
    I have checked rights on the folders and also got the anti-virus (symantec) services stopped on the server. Still no success, can anyone help.
    Just to add: Have already referred
    http://support.microsoft.com/kb/918357

  • After Installing SQL Server 2012 Service Pack the RDL reports do not work

    I installed SQL Server 2012 Service Pack on backEnd sharepoint and also on BI Server that host Reporting Service.(Before installation everything was working properly)
    After this installation the RDL reports do not open and I receive this error message.
    The permissions granted to user 'domain\username' are insufficient for performing this operation. (rsAccessDenied)
    I also receive the same error message on changing DataSource, Parameters and subscription.
    I should mention that, I am using Reporting Services in the Integration Mode. I want to open and modify RDL reports from SharePoint and inside the SharePoint Document Library.

    Hi Hedayat,
    Thanks for posting your issue,
    To solve this problem you have to grant your SQL Reporting Service Application Pool
    Account (whatever is running your SQL Service Application, see Central Admin -> Manage Service Application -> SQL Server Reporting Services)
    Full Control to the web application that report is being deployed to in your particular case.
    Or you could just use the powershell command below:
    $webApp = Get-SPWebApplication –Identity http://yoursharepointapp 
    $webApp.GrantAccessToProcessIdentity(“domain\SSRSAccount”) 
    Also, check out below mentioned URLs for more details and fixes of this issue
    http://paulliebrand.com/2013/09/25/ssrs-and-permissions-granted-to-user-are-insufficient-for-performing-this-operation/
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/4ea477ec-ea12-4a3e-bc33-2fcf9d52b84e/error-rsaccessdenied-nt-authoritynetwork-service-are-insufficient?forum=sqlreportingservices
    I hope this is helpful to you, mark it as Helpful.
    If this works, Please mark it as Answered.
    Regards,
    Dharmendra Singh (MCPD-EA | MCTS)
    Blog : http://sharepoint-community.net/profile/DharmendraSingh

  • Install sql server 2008 r2 in windows xp service pack3 gives error

    After Installing Support Files, a pop up occurs stating that Microsoft SQL Server 2008 R2 installation has encountered an error.
    Error Signature: EventType : sql100msi P1 : 10.50.1600.1 P2 : 10.50.1600.1
    P3 : sqlncli.msi P4 : 0x2d2816fe P5 : 0x1603 P6 : install_sqlncli can anyone help me

    Hello people. I am having much problem trying to get the SQL installed on my computer.
    I just added half of error log:
    === Verbose logging started: 5/1/2014  13:27:12  Build type: SHIP UNICODE 4.05.6001.00  Calling process: f:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x86\setup100.exe
    ===
    MSI (c) (94:CC) [13:27:12:770]: Resetting cached policy values
    MSI (c) (94:CC) [13:27:12:770]: Machine policy value 'Debug' is 0
    MSI (c) (94:CC) [13:27:12:770]: ******* RunEngine:
               ******* Product: f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi
               ******* Action: 
               ******* CommandLine: **********
    MSI (c) (94:CC) [13:27:12:770]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (94:CC) [13:27:12:770]: Grabbed execution mutex.
    MSI (c) (94:CC) [13:27:12:770]: Cloaking enabled.
    MSI (c) (94:CC) [13:27:12:770]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (94:CC) [13:27:12:770]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (2C:A0) [13:27:12:833]: Running installation inside multi-package transaction f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi
    MSI (s) (2C:A0) [13:27:12:833]: Grabbed execution mutex.
    MSI (s) (2C:6C) [13:27:12:848]: Resetting cached policy values
    MSI (s) (2C:6C) [13:27:12:848]: Machine policy value 'Debug' is 0
    MSI (s) (2C:6C) [13:27:12:848]: ******* RunEngine:
               ******* Product: f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi
               ******* Action: 
               ******* CommandLine: **********
    MSI (s) (2C:6C) [13:27:12:848]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (2C:6C) [13:27:13:379]: File will have security applied from OpCode.
    MSI (s) (2C:6C) [13:27:13:629]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi' against software restriction policy
    MSI (s) (2C:6C) [13:27:13:645]: SOFTWARE RESTRICTION POLICY: f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi has a digital signature
    MSI (s) (2C:6C) [13:27:13:942]: SOFTWARE RESTRICTION POLICY: f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi is permitted to run at the 'unrestricted' authorization level.
    MSI (s) (2C:6C) [13:27:13:942]: End dialog not enabled
    MSI (s) (2C:6C) [13:27:13:942]: Original package ==> f:\41ab42c0be4c457100b4\1033_ENU_LP\x86\setup\x86\sqlncli.msi
    MSI (s) (2C:6C) [13:27:13:942]: Package we're running from ==> f:\WINDOWS\Installer\250ed1.msi
    MSI (s) (2C:6C) [13:27:13:958]: APPCOMPAT: looking for appcompat database entry with ProductCode '{4AB6A079-178B-4144-B21F-4D1AE71666A2}'.
    MSI (s) (2C:6C) [13:27:13:958]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (2C:6C) [13:27:13:973]: MSCOREE not loaded loading copy from system32
    MSI (s) (2C:6C) [13:27:13:989]: Machine policy value 'TransformsSecure' is 0
    MSI (s) (2C:6C) [13:27:13:989]: User policy value 'TransformsAtSource' is 0
    MSI (s) (2C:6C) [13:27:13:989]: Machine policy value 'DisablePatch' is 0
    MSI (s) (2C:6C) [13:27:13:989]: Machine policy value 'AllowLockdownPatch' is 0
    MSI (s) (2C:6C) [13:27:13:989]: Machine policy value 'DisableLUAPatching' is 0
    MSI (s) (2C:6C) [13:27:13:989]: Machine policy value 'DisableFlyWeightPatching' is 0
    MSI (s) (2C:6C) [13:27:13:989]: APPCOMPAT: looking for appcompat database entry with ProductCode '{4AB6A079-178B-4144-B21F-4D1AE71666A2}'.
    MSI (s) (2C:6C) [13:27:13:989]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (2C:6C) [13:27:14:004]: Transforms are not secure.
    MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'F:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140501_131426\sqlncli_Cpu32_1.log'.
    MSI (s) (2C:6C) [13:27:14:004]: Command Line: ADDLOCAL=SQL_SNAC_CORE,SQL_SNAC_SDK INSTALLSQLSHAREDDIR_32=F:\Program Files\Microsoft SQL Server\ IACCEPTSQLNCLILICENSETERMS=YES REBOOT=ReallySuppress MEDIAPACKAGEPATH=\1033_ENU_LP\x86\setup\x86\ EXTERNALMSICONTROL=1
    CURRENTDIRECTORY=f:\41ab42c0be4c457100b4 CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=3988 
    MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{79872AB7-3F02-4F99-BDA4-03BBC4644342}'.
    MSI (s) (2C:6C) [13:27:14:004]: Product Code passed to Engine.Initialize:           ''
    MSI (s) (2C:6C) [13:27:14:004]: Product Code from property table before transforms: '{4AB6A079-178B-4144-B21F-4D1AE71666A2}'
    MSI (s) (2C:6C) [13:27:14:004]: Product Code from property table after transforms:  '{4AB6A079-178B-4144-B21F-4D1AE71666A2}'
    MSI (s) (2C:6C) [13:27:14:004]: Product not registered: beginning first-time install
    MSI (s) (2C:6C) [13:27:14:004]: Product {4AB6A079-178B-4144-B21F-4D1AE71666A2} is not managed.
    MSI (s) (2C:6C) [13:27:14:004]: MSI_LUA: Credential prompt functionality not available on this operating system
    MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
    MSI (s) (2C:6C) [13:27:14:004]: Entering CMsiConfigurationManager::SetLastUsedSource.
    MSI (s) (2C:6C) [13:27:14:004]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (2C:6C) [13:27:14:004]: Adding new sources is allowed.
    MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
    MSI (s) (2C:6C) [13:27:14:004]: Package name extracted from package path: 'sqlncli.msi'
    MSI (s) (2C:6C) [13:27:14:004]: Package to be registered: 'sqlncli.msi'
    MSI (s) (2C:6C) [13:27:14:004]: Note: 1: 2262 2: AdminProperties 3: -2147287038 
    MSI (s) (2C:6C) [13:27:14:004]: Machine policy value 'DisableMsi' is 0
    MSI (s) (2C:6C) [13:27:14:004]: Machine policy value 'AlwaysInstallElevated' is 0
    MSI (s) (2C:6C) [13:27:14:004]: User policy value 'AlwaysInstallElevated' is 0
    MSI (s) (2C:6C) [13:27:14:004]: Product installation will be elevated because user is admin and product is being installed per-machine.
    MSI (s) (2C:6C) [13:27:14:004]: Running product '{4AB6A079-178B-4144-B21F-4D1AE71666A2}' with elevated privileges: Product is assigned.
    MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding ADDLOCAL property. Its value is 'SQL_SNAC_CORE,SQL_SNAC_SDK'.
    MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding INSTALLSQLSHAREDDIR_32 property. Its value is 'F:\Program Files\Microsoft SQL Server\'.
    MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding IACCEPTSQLNCLILICENSETERMS property. Its value is 'YES'.
    MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding REBOOT property. Its value is 'ReallySuppress'.
    MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding MEDIAPACKAGEPATH property. Its value is '\1033_ENU_LP\x86\setup\x86\'.
    MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding EXTERNALMSICONTROL property. Its value is '1'.
    MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'f:\41ab42c0be4c457100b4'.
    MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
    MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is '1'.
    MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '3988'.
    MSI (s) (2C:6C) [13:27:14:004]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
    MSI (s) (2C:6C) [13:27:14:004]: DisableAutomaticApplicationShutdown system policy is ignored on this version of Windows.
    MSI (s) (2C:6C) [13:27:14:004]: TRANSFORMS property is now: 
    MSI (s) (2C:6C) [13:27:14:004]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '300'.
    MSI (s) (2C:6C) [13:27:14:004]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Application Data
    MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Favorites
    MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\NetHood
    MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\My Documents
    MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\PrintHood
    MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Recent
    MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\SendTo
    MSI (s) (2C:6C) [13:27:14:020]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Templates
    MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Application Data
    MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Local Settings\Application Data
    MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\My Documents\My Pictures
    MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Start Menu\Programs\Administrative Tools
    MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Start Menu\Programs\Startup
    MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Start Menu\Programs
    MSI (s) (2C:6C) [13:27:14:036]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Start Menu
    MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Desktop
    MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Start Menu\Programs\Administrative Tools
    MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Start Menu\Programs\Startup
    MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Start Menu\Programs
    MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Start Menu
    MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\Rashmi\Desktop
    MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\Documents and Settings\All Users\Templates
    MSI (s) (2C:6C) [13:27:14:051]: SHELL32::SHGetFolderPath returned: F:\WINDOWS\Fonts
    MSI (s) (2C:6C) [13:27:14:051]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16 

  • RDL Reports are not working after installing SQL Server 2012 Service Pack 2 in the SharePoint integration Mode

    I am using Reporting Service Integration mode with SharePoint. SSRS is installed on separated machine of SharePoint stacks in Integration Mode. Everything was working properly and I could create/edit/modify RDL reports(parameters, Datasource, Subscription)
    inside SharePoint and Document Libraries.
    But after installing SQL Server 2012 Service Pack 2, on opening RDL reports inside SharePoint I receive this error message. 
    The permissions granted to user 'i:0#.f|membership|username' are insufficient for performing this operation. ---> Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user 'i:0#.f|membership|username' are insufficient for performing this operation
    I should mention that SSRS is installed in the SharePoint integration Mode and there is no SSRS management console.

    Hi Hedayat-Abedijoo,
    According to your description, you are using Reporting Services in SharePoint Integrated mode, and everything worked fine before you install SQL Server 2012 Service Pack 2. After the package is installed, when you open RDL reports, the error occurred: The
    permissions granted to user 'i:0#.f|membership|username' are insufficient for performing this operation.
    According to my search, there may be two reasons for the problem:
    This is caused when the application pool account that runs the SharePoint Web application you are on in IIS and the application pool account that SharePoint believes is running the site differ. This happens if the application pool account is changed directly
    in IIS instead of through SharePoint (using the approved method).
    This error can be caused when Kerberos authentication has been set up correctly and delegation in a double hop scenario will succeed, but Reporting Services integration has been set up for Trusted Account rather than Windows Authentication. This causes
    SharePoint to continue to impersonate the logged-on user when contacting Reporting Services; when Reporting Services compares the application pool account to the user account making the request, they are not equal.
    In this case, we can solve the problem by changing the application pool account in IIS back to the previous account and set AuthenticationTypes to RSWindowsNTLM only. For detail information, please refer to 8.3 “The permissions granted to user 'Domain\User'
    are insufficient for performing this operation” in the document:http://msdn.microsoft.com/en-us/library/ee384252(SQL.100).aspx
    If you have any questions, please feel free to let me know.
    Thanks,
    Wendy Fu

  • Report Builder 1.0 for SQL Server Reporting Services 2008 R2

    We are trying to implement Ad-Hoc Reporting using SSRS 2008 R2.
    First of all, it is very unhelpful that all SSRS books are for either 2008 or 2012, even though SSRS has major changes in 2008 R2 compared to 2008.
    Our instructional materials indicate that we should build Report Models to abstract out our databases into terms familiar to our business users.
    The problem we are having is the difference in functionality between Report Builder 1.0 and Report Builder 3.0. Report Builder 3.0 is touted as having the modern, ribbon based interface that is supposed to make end-users feel more comfortable.  However,
    all the documentation says that end users are supposed to use Report Builder 1.0 for Ad-Hoc Reporting.  And, it seems, that the reports generated by Report Builder 1.0 are not round-trip compatible with all the other reporting tools for SSRS 2008 R2.
    The documentation we have illustrates that Report Builder 1.0 is nice for Ad-Hoc reporting, because is based on connecting directly to Report Models, and the end users can directly drag-and-drop entities and fields into their reports.
    When we try working with Report Builder 3.0, it seems we must first connect to the Report Model as a Data Source and then build a Dataset query on the Report Model.  Only then are some entity attributes available to be dropped into the report. 
    If the user decides another source column is needed, they have to go back, edit the query, save the query, and then drag the column from the Dataset to the report.  This does not seem end user friendly at all!
    We are also concerned that if we train our users on the seemingly soon-to-be-obsolete Report Builder 1.0, and get them used to having direct Report Model access, that at some point we will have to move them to the Dataset-interrupted approach of Report Builder
    2+.  Highlighting this perception of impending obsolescence of Report Builder 1.0 is that in our shop that is starting with SSRS 2008 R2, we cannot figure out how to get a copy of Report Builder 1.0 in the first place.
    We just don't see our end users being savvy enough to handle the steps involved with creating Datasets on top of Report Model Data Sources.  So we would have to build the Datasets for them.  But in that case, what point is there in creating any
    Report Models in the first place if DBAs are the ones to make Datasets?
    As such, it is hard to envision a forward-looking SSRS implementation that has the end user ease-of-use Ad-Hoc reporting that the SSRS 2008 documentation presents.
    What is it that Microsoft actually wants/expects SSRS implementers to do?
    Dan Jameson
    Manager SQL Server DBA
    CureSearch for Children's Cancer
    http://www.CureSearch.org

    Hi Dan,
    Report Builder 1.0
    Simple template-based reports
    Requires report model
    Supports only SQL Server, Oracle, and Analysis Services as data sources
    Supports RDL 2005
    Bundled in SSRS
    Report Builder 2.0 or later
    Full-featured reports as the BIDS Report Designer
    Doesn't require (but supports) report models
    Supports any data source
    Supports RDL 2008
    Available as a separate web download
    In your scenario, you want to use Report Builder 1.0 in SQL Server Reporting Services 2008 R2, I am afraid this cannot achieve. Report Builder 1.0 is available in the box in either SQL 2005 or SQL 2008. It is not available as a separate client apps and is
    only available as a click once application.
    Report Builder 1.0
    Report Builder 3.0
    Thank you for your understanding.
    Regards,
    Charlie Liao
    If you have any feedback on our support, please click
    here.
    Charlie Liao
    TechNet Community Support

  • Reporting with Report Builder 3.0 and SQL Server 2008 R2

    Hi everyone
    I'm trying really hard to find books about Report Builder 3.0 or SQL Server 2008 R2
    I found the following books on the "learn" site, sadly they do not cover Report Builder 3.0 or SQL Server 2008 R2 since there all too old.
    Microsoft® SQL Server® 2008 Analysis Services Step by Step
    Microsoft® SQL Server® 2008 MDX Step by Step
    Microsoft® SQL Server® 2008 Reporting Services Step by Step
    What are good books (like the ones above) for the newest system?

    Hello wishmasterIN,
    Thank you to post your question on TechNet forum.
    Based on my experience, the books are always delayed to the new technology, since the author need time to summarize and analyze the new features in the new product or technology, write it down and publish it. If you want to have a quick learning about the
    new technology, MSDN library is a good place. It can be a cookbook for you. It contains some detail steps for tools, such as Report Builder or BIDS. It also contains many new features introduction. It is always very useful for you to understand the new features.
    In addition, it is based on web and many links make you can jump to the other technical point freely. The most important is all of these is free and all the information will be updated if the new feature is released.
    In short, if you want to learn the latest technology about Microsoft product, MSDN is a good choice. I hope my introduction is helpful to you.
    Regards,
    Edward
    Edward Zhu
    TechNet Community Support

  • Error Accessing Report in SharePoint Integrated Mode (SQL Server 2008 with SharePoint 2007)

    I have installed reporting services with SharePoint Integration Mode, however, whenever I access the report, below error occurs:
    Report Server has encountered a SharePoint error. (rsSharePointError)
    Exception occurred. (Exception from HRESULT: 0x80020009 (DISP_E_EXCEPTION))
    Exception occurred. (Exception from HRESULT: 0x80020009 (DISP_E_EXCEPTION)
    Checking through the Log Files, there is more detailed error message, but not sure what cause the error:
    library!ReportServer_0-2!4064!11/01/2010-15:00:39:: Call to GetPermissionsAction(http://[servername]/sites/Reporting/Reports/TestReport.rdl).
    library!ReportServer_0-2!4170!11/01/2010-15:00:39:: Call to ListParentsAction(http://[servername]/sites/Reporting/Reports/TestReport.rdl).
    library!ReportServer_0-2!4170!11/01/2010-15:00:40:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: Report Server has encountered a SharePoint error., ;
     Info: Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: Report Server has encountered a SharePoint error. ---> Microsoft.SharePoint.SPException: Exception occurred. (Exception from HRESULT: 0x80020009 (DISP_E_EXCEPTION)) --->
    System.Runtime.InteropServices.COMException (0x80020009): Exception occurred. (Exception from HRESULT: 0x80020009 (DISP_E_EXCEPTION))
       at Microsoft.SharePoint.Library.SPRequestInternalClass.GetFileAsByteArray(String bstrUrl, String bstrWebRelativeUrl, Boolean bHonorLevel, Byte iLevel, OpenBinaryFlags grfob)
       at Microsoft.SharePoint.Library.SPRequest.GetFileAsByteArray(String bstrUrl, String bstrWebRelativeUrl, Boolean bHonorLevel, Byte iLevel, OpenBinaryFlags grfob)
       --- End of inner exception stack trace ---
       at Microsoft.SharePoint.Library.SPRequest.GetFileAsByteArray(String bstrUrl, String bstrWebRelativeUrl, Boolean bHonorLevel, Byte iLevel, OpenBinaryFlags grfob)
       at Microsoft.SharePoint.SPFile.GetFileContent(SPOpenBinaryOptions openOptions)
       at Microsoft.SharePoint.SPFile.OpenBinary(SPOpenBinaryOptions openOptions)
       at Microsoft.SharePoint.SPFile.OpenBinary()
       at Microsoft.ReportingServices.SharePoint.Server.SharePointServiceHelper.SyncToRSCatalog(String path, Boolean createOnly)
       --- End of inner exception stack trace ---
    library!ReportServer_0-2!4064!11/01/2010-15:00:40:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: Report Server has encountered a SharePoint error., ;
     Info: Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: Report Server has encountered a SharePoint error. ---> Microsoft.SharePoint.SPException: Exception occurred. (Exception from HRESULT: 0x80020009 (DISP_E_EXCEPTION)) --->
    System.Runtime.InteropServices.COMException (0x80020009): Exception occurred. (Exception from HRESULT: 0x80020009 (DISP_E_EXCEPTION))
       at Microsoft.SharePoint.Library.SPRequestInternalClass.GetFileAsByteArray(String bstrUrl, String bstrWebRelativeUrl, Boolean bHonorLevel, Byte iLevel, OpenBinaryFlags grfob)
       at Microsoft.SharePoint.Library.SPRequest.GetFileAsByteArray(String bstrUrl, String bstrWebRelativeUrl, Boolean bHonorLevel, Byte iLevel, OpenBinaryFlags grfob)
       --- End of inner exception stack trace ---
       at Microsoft.SharePoint.Library.SPRequest.GetFileAsByteArray(String bstrUrl, String bstrWebRelativeUrl, Boolean bHonorLevel, Byte iLevel, OpenBinaryFlags grfob)
       at Microsoft.SharePoint.SPFile.GetFileContent(SPOpenBinaryOptions openOptions)
       at Microsoft.SharePoint.SPFile.OpenBinary(SPOpenBinaryOptions openOptions)
       at Microsoft.SharePoint.SPFile.OpenBinary()
       at Microsoft.ReportingServices.SharePoint.Server.SharePointServiceHelper.SyncToRSCatalog(String path, Boolean createOnly)
       --- End of inner exception stack trace ---
    Any idea on how to resolve the issue?

    Hi Jin Chen,
    Thank you for your response. I have disabled all the Symantec End Point Protection Service, but problem persists..
    Further, I have checked through the ULS Log in SharePoint, there is more error reported there:
    11/03/2010 15:19:48.44 ReportingServicesService.exe (0x3510)  
    0x4064
    Windows SharePoint Services   Database                      
    6f8g Unexpected
    Unexpected query execution failure, error code 282. Additional error information from SQL Server is included below. "The 'proc_GetTpWebMetaDataAndListMetaData' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be
    returned instead." Query text (if available): "{?=call proc_GetTpWebMetaDataAndListMetaData(?,'F77D6A37-F8D2-492C-911C-923C8A135DEB',?,NULL,1,?,?,6187)}"
    11/03/2010 15:19:51.46 ReportingServicesService.exe (0x3510)  
    0x4064
    Windows SharePoint Services   General                      
    8e2s Medium  
    Unknown SPRequest error occurred. More information: 0x80020009
    11/03/2010 15:19:51.69 ReportingServicesService.exe (0x3510)  
    0x1EEC
    Windows SharePoint Services   General                      
    8e2s Medium  
    Unknown SPRequest error occurred. More information: 0x80020009
    Do you have any idea based on the error above?

  • Which .exe file I should choose to apply SP2 for SQL Server 2008r2 Enterprise Edition 64Bit

    Hi All,
    Which .exe file I should choose to apply SP2 for SQL Server 2008r2 Enterprise Edition 64Bit.
    And what is the difference between below .exe files. 
    SQLServer2008R2SP2-KB2630458-x64-ENU.exe
    SQLServer2008R2SP2-KB2630458-IA64-ENU.exe
    Grateful to your time and support. Regards, Shiva

    Good day
    Shiva Shakthi,
    I have change the type of the thread to a question, as this is a question :-)
    please chose the right type next time. If you have a question then use a question thread (this is the default), and that will let you mark the answers that you get.
    Have a nice day :-)
    [Personal Site] [Blog] [Facebook]

  • SQL Server 2008R2 SP2 Query optimizer memory leak ?

    It looks like we are facing a SQL Server 2008R2 queery optimizer memory leak.
    We have below version of SQL Server
    Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)
     Jun 28 2012 08:36:30
     Copyright (c) Microsoft Corporation
     Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
    The instance is set MAximum memory tro 20 GB.
    After executing a huge query (2277 kB generated by IBM SPSS Clementine) with tons of CASE and a lot of AND/OR statements in the WHERE and CASE statements and muliple subqueries the server stops responding on Out of memory in the internal pool
    and the query optimizer has allocated all the memory.
    From Management Data Warehouse we can find that the query was executed at
    7.11.2014 22:40:57
    Then at 1:22:48 we recieve FAIL_PACE_ALLOCATION 1
    2014-11-08 01:22:48.70 spid75       Failed allocate pages: FAIL_PAGE_ALLOCATION 1
    And then tons of below errors
    2014-11-08 01:24:02.22 spid87      There is insufficient system memory in resource pool 'internal' to run this query.
    2014-11-08 01:24:02.22 Server      Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
    2014-11-08 01:24:02.22 Server      Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
    2014-11-08 01:24:02.30 Server      Error: 17312, Severity: 16, State: 1.
    2014-11-08 01:24:02.30 Server      SQL Server is terminating a system or background task Fulltext Host Controller Timer Task due to errors in starting up the task (setup state 1).
    2014-11-08 01:24:02.22 spid74      Error: 701, Severity: 17, State: 123.
    2014-11-08 01:24:02.22 spid74      There is insufficient system memory in resource pool 'internal' to run this query.
    2014-11-08 01:24:13.22 Server      Error: 17312, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
    2014-11-08 01:24:13.22 spid87      Error: 701, Severity: 17, State: 123.
    2014-11-08 01:24:13.22 spid87      There is insufficient system memory in resource pool 'internal' to run this query.
    2014-11-08 01:24:13.22 spid63      Error: 701, Severity: 17, State: 130.
    2014-11-08 01:24:13.22 spid63      There is insufficient system memory in resource pool 'internal' to run this query.
    2014-11-08 01:24:13.22 spid57      Error: 701, Severity: 17, State: 123.
    2014-11-08 01:24:13.22 spid57      There is insufficient system memory in resource pool 'internal' to run this query.
    2014-11-08 01:24:13.22 Server      Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
    2014-11-08 01:24:18.26 Server      Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
    2014-11-08 01:24:24.43 spid81      Error: 701, Severity: 17, State: 123.
    2014-11-08 01:24:24.43 spid81      There is insufficient system memory in resource pool 'internal' to run this query.
    2014-11-08 01:24:18.25 Server      Error: 18052, Severity: -1, State: 0. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
    2014-11-08 01:24:18.25 Server      BRKR TASK: Operating system error Exception 0x1 encountered.
    2014-11-08 01:24:30.11 Server      Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
    2014-11-08 01:24:30.11 Server      Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
    2014-11-08 01:24:35.18 spid57      Error: 701, Severity: 17, State: 131.
    2014-11-08 01:24:35.18 spid57      There is insufficient system memory in resource pool 'internal' to run this query.
    2014-11-08 01:24:35.18 spid71      Error: 701, Severity: 17, State: 193.
    2014-11-08 01:24:35.18 spid71      There is insufficient system memory in resource pool 'internal' to run this query.
    2014-11-08 01:24:35.18 Server      Error: 17312, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
    2014-11-08 01:24:35.41 Server      Error: 17312, Severity: 16, State: 1.
    2014-11-08 01:24:35.41 Server      SQL Server is terminating a system or background task SSB Task due to errors in starting up the task (setup state 1).
    2014-11-08 01:24:35.71 Server      Error: 17053, Severity: 16, State: 1.
    2014-11-08 01:24:35.71 Server      BRKR TASK: Operating system error Exception 0x1 encountered.
    2014-11-08 01:24:35.71 spid73      Error: 701, Severity: 17, State: 123.
    2014-11-08 01:24:35.71 spid73      There is insufficient system memory in resource pool 'internal' to run this query.
    2014-11-08 01:24:46.30 Server      Error: 17312, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
    2014-11-08 01:24:51.31 Server      Error: 17053, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
    2014-11-08 01:24:51.31 Server      Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
    2014-11-08 01:24:51.31 Logon       Error: 18052, Severity: -1, State: 0. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
    Last error message is half an hour after the inital Out of memory at 2014-11-08 01:52:54.03. Then the Instance is completely shut down
    From the memory information in the error log we can see that all the memory is consumed by the QUERY_OPTIMIZER
    Buffer Pool                                   Value
    Committed                                   2621440
    Target                                      2621440
    Database                                     130726
    Dirty                                          3682
    In IO                                            
    0
    Latched                                          
    1
    Free                                           
    346
    Stolen                                      2490368
    Reserved                                          0
    Visible                                     2621440
    Stolen Potential                                  0
    Limiting Factor                                  17
    Last OOM Factor                                   0
    Last OS Error                                     0
    Page Life Expectancy                             28
    2014-11-08 01:22:48.90 spid75     
    Process/System Counts                         Value
    Available Physical Memory                29361627136
    Available Virtual Memory                 8691842715648
    Available Paging File                    51593969664
    Working Set                               628932608
    Percent of Committed Memory in WS               100
    Page Faults                                48955000
    System physical memory high                       1
    System physical memory low                        0
    Process physical memory low                       1
    Process virtual memory low                        0
    MEMORYCLERK_SQLOPTIMIZER (node 1)                KB
    VM Reserved                                       0
    VM Committed                                      0
    Locked Pages Allocated                            0
    SM Reserved                                       0
    SM Committed                                      0
    SinglePage Allocator                       19419712
    MultiPage Allocator                             128
    Memory Manager                                   KB
    VM Reserved                               100960236
    VM Committed                                 277664
    Locked Pages Allocated                     21483904
    Reserved Memory                                1024
    Reserved Memory In Use                            0
    On the other side MDW reports that the MEMORYCLERK_SQLOPTIMIZER increases since the execution of the query up to the point of OUTOF MEMORY, but the Average value is 54.7 MB during that period as can be seen on attached graph.
    We have encountered this issue already two times (every time the critical query is executed).

    Hi,
    This does seems to me kind of memory Leak and actually it is from SQL Optimizer which leaked memory from buffer pool so much that it did not had any memory to be allocated for new page.
    MEMORYCLERK_SQLOPTIMIZER (node 1)                KB
    VM Reserved                                       0
    VM Committed                                      0
    Locked Pages Allocated                            0
    SM Reserved                                       0
    SM Committed                                      0
    SinglePage Allocator                       19419712
    MultiPage Allocator                             128
    Can you post complete DBCC MEMORYSTATUS output which was generated in errorlog. Is this the only message in errorlog or there are some more messages before and after it.
    select (SUM(single_pages_kb)*1024)/8192 as total_stolen_pages, type
    from sys.dm_os_memory_clerks
    group by typeorder by total_stolen_pages desc
    and
    select sum(pages_allocated_count * page_size_in_bytes)/1024,type from sys.dm_os_memory_objects
    group by type
    If you can post the output of above two queries with dbcc memorystaus output on some shared drive and share location with us here. I would try to find out what is leaking memory.
    You can very well apply SQL Server 2008 r2 SP3 and see if this issue subsides but I am not sure whether this is fixed or actually it is a bug.
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • Windows Server 2008R2 running Remote Desktop Services reports printer process does not exist when installing PDF printer

     Windows Server 2008R2 running Remote Desktop Services reports printer process does not exist when installing PDF printer, And when Installing network printers from the domain controller it reports it cannot connect to printer.  I can ping all
    network devices. I can connect to the internet.
    On boot I get a netlogon 5719 error followed by service control manager errors 7023,7001 and a group policy error 1129.
    Clients can connect to the remote application and RDP operates to connect to the server internally and externally.
    The domain controller is another server 2008r2 box. I have scoured the internet but have not found any solutions that work yet.

    Hi,
    After referring to your post, it can be identified that the issue which you are facing is mostly due to some network issue in your environment. Please recheck your network connection issue between computer and domain controller. 
    Can you able to ping with IP address and also with fully qualified name of a domain controller in the users' and computers' domain. If it fails states that name resolution issue with computer and domain controller. Are you using MS DHCP Relay agent then there’s
    available Hotfix for the particular Event ID. Please go through this KB 2459530 to fix the error event ID.
    As per the net logon error 5719 which you are facing states that the client component of Netlogon was unable to locate a DC for the domain it was trying to perform an operation against. Below is one of the reason. If this is being logged on a DC and the event
    refers to the DC's own domain, something might be preventing the client component of Netlogon from starting a network session (to itself or to another DC in the domain). The following event 7001 & 7023 states start & stop operation service. Please
    go through beneath article for more details.
    1.  Event ID 5719 is logged when you start a computer
    2.  Netlogon 5719 and the Disappearing Domain [Controller]
    3.  Event ID 1129 — Microsoft-Windows-GroupPolicy
    Hope it helps!
    Regards.

  • SETUP ERROR WHILE INSTALLING SQL SERVER 2008 R2

    Hi ,
    I'm coming across the following error while installing Microsoft SQL Server 2008R2
    SQL Server Setup has encountered the following error:
    The required MSI package 'D:\SQL Sever 2008 R2 Developer Edition\x86\setup\sql_engine_core_shared_msi\sql_engine_core_shared.msi' doesn't exist.
    Error code 0x84B20001.
    I tried reinstalling the same. But results the same.
    Please suggest. :)

    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
    rerun SQL Server Setup.
      Exit code (Decimal):           -2068709375
      Exit facility code:            1202
      Exit error code:               1
      Exit message:                  The required MSI package 'D:\softwares\SQL Sever 2008 R2 Developer Edition\x86\setup\sql_engine_core_shared_msi\sql_engine_core_shared.msi'
    doesn't exist.
      Start time:                    2013-12-31 20:47:50
      End time:                      2013-12-31 20:55:44
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131231_204629\Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.1600.1%26EvtType%3d0xD2FD83B3%400xC2B0B50B%401202%401
    Machine Properties:
      Machine name:                  SAMPLE-PC
      Machine processor count:       2
      OS version:                    Windows 7
      OS service pack:              
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x86
      Process architecture:          32 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2005                                                         
    Tools                                    1033                
    Express Edition      9.2.3042        No       
      Sql Server 2005                                                         
    ToolsClient                              1033                
    Express Edition      9.2.3042        No       
      Sql Server 2005                                                         
    ToolsClient\Connectivity                 1033                 Express Edition     
    9.2.3042        No       
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services                
    1033                 Express Edition      10.1.2531.0     No       
      Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication                  
    1033                 Express Edition      10.1.2531.0     No       
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         D:\softwares\SQL Sever 2008 R2 Developer Edition\x86\setup\
      Installation edition:          DEVELOPER
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 TEST
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Config
      ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  TEST
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            SAMPLE-PC\SAMPLE
      ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131231_204629\ConfigurationFile.ini
      CUSOURCE:                     
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,SSMS,ADV_SSMS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
      FTSVCPASSWORD:                 *****
      HELP:                          False
      IACCEPTSQLSERVERLICENSETERMS:  False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    TEST
      INSTANCENAME:                  TEST
      ISSVCACCOUNT:                  TEST
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                    
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  SAMPLE-PC\TEST
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 TEST
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           SAMPLE-PC\SAMPLE
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    0
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131231_204629\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       SQL Server Replication
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Analysis Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Reporting Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Integration Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Connectivity
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools SDK
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Client Tools Backwards Compatibility
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Business Intelligence Development Studio
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131231_204629\SystemConfigurationCheck_Report.htm
    Exception summary:
    The following is an exception stack listing the exceptions in outermost to innermost order
    Inner exceptions are being indented
    Exception type: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInvalidOperationException
        Message:
            The required MSI package 'D:\softwares\SQL Sever 2008 R2 Developer Edition\x86\setup\sql_engine_core_shared_msi\sql_engine_core_shared.msi' doesn't exist.
        Data:
          ChainerInvalidOperationExceptionData = InstallPackage
          DisableWatson = true
        Stack:
            at Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia, InstallAction pkgAction)
            at Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
            at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)

  • Unknown SQL Exception 208 occurred. Additional error information from SQL Server is included below.Invalid object name 'Webs'.

    SP 2013 Server + Dec 2013 CU. Upgrading from SharePoint 2010.
    We have a web application that is distributed over 7-8 content databases from SharePoint 2010. All but one database are upgradable. However, one database gives:
    Invalid object name 'Webs'.
    while running Test-SPContentDatabase or Mount-SPContentDatabase.
    EventViewer has the following reporting 5586 event Id:
    Unknown SQL Exception 208 occurred. Additional error information from SQL Server is included below.Invalid object name 'Webs'.
    After searching a bit, these links do not help:
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/fd020a41-51e6-4a89-9d16-38bff9201241/invalid-object-name-webs?forum=sharepointadmin
    we are trying PowerShell only.
    http://blog.thefullcircle.com/2013/06/mount-spcontentdatabase-and-test-spcontentdatabase-fail-with-either-invalid-object-name-sites-or-webs/
    In our case, these are content databases. This is validated from Central Admin.
    http://sharepointjotter.blogspot.com/2012/08/sharepoint-2010-exception-invalid.html
    Our's is SharePoint 2013
    http://zimmergren.net/technical/findbestcontentdatabaseforsitecreation-problem-after-upgrading-to-sharepoint-2013-solution
    Does not seem like the same exact problem.
    Any additional input?
    Thanks, Soumya | MCITP, SharePoint 2010

    Hi,
    “All but one database are upgradable. However, one database gives:
    Invalid object name 'Webs'.”
    Did the sentence you mean only one database not upgrade to SharePoint 2013 and given the error?
    One or more of the following might be the cause:
    Insufficient SQL Server database permissions
    SQL Server database is full
    Incorrect MDAC version
    SQL Server database not found
    Incorrect version of SQL Server
    SQL Server collation is not supported
    Database is read-only
    To resolve the issue, you can refer to the following article which contains the causes and resolutions.
    http://technet.microsoft.com/en-us/library/ee513056(v=office.14).aspx
    Thanks,
    Jason
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Jason Guo
    TechNet Community Support

  • Will Cumulative Update 12 for SQL Server 2008R2 SP2 fix: Warning: Unable to Verify TimeStamp for Path\ProgramName?

    Hello,
    I had a server crash recently and our outsource hosting tech support suggested applying Cumulative Upade 12 for SQL server 2008R2 SP2 to fix the issue.  The exception from our dump file "Warning: Unable to Verify TimeStamp for Path\ProgramName"
    is not in the list of hotfixes for this CU.  Do you know if this will fix this issue?  The CU warns not to apply the CU if your issue id not addressed by the CU.  Here is a portion of the dump file with the relevant error:
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (7e8.2ab4): Unknown exception - code 000042ac (first/second chance not available)
    ntdll!NtWaitForSingleObject+0xa:
    00000000`777412fa c3              ret
    0:240> .sympath srv*c:\Websymbols*http://msdl.microsoft.com/download/symbols;
    Symbol search path is: srv*c:\Websymbols*http://msdl.microsoft.com/download/symbols
    Expanded Symbol search path is: srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
    0:240> .reload /f
    .Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sqlservr.exe
    ..........Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlos.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sqlos.dll
    ...............Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\opends60.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for opends60.dll
    .......Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\BatchParser.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for BatchParser.dll
    ....Unable to load image C:\Program Files\Microsoft SQL Server\100\Shared\instapi10.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for instapi10.dll
    *** ERROR: Module load completed but symbols could not be loaded for instapi10.dll
    ..Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\sqlevn70.rll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sqlevn70.rll
    *** ERROR: Module load completed but symbols could not be loaded for sqlevn70.rll
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    .................Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\ftimport.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ftimport.dll
    .Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\msfte.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for msfte.dll
    *** ERROR: Module load completed but symbols could not be loaded for msfte.dll
    ...........Unable to load image C:\Windows\System32\sqlncli10.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sqlncli10.dll
    ...Unable to load image C:\Windows\System32\1033\SQLNCLIR10.RLL, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SQLNCLIR10.RLL
    *** ERROR: Module load completed but symbols could not be loaded for SQLNCLIR10.RLL
    ..Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\xpsqlbot.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for xpsqlbot.dll
    .Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\XPStar.DLL, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for XPStar.DLL
    .Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlscm.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sqlscm.dll
    ...*** ERROR: Module load completed but symbols could not be loaded for odbcint.dll
    ...Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\XPStar.RLL, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for XPStar.RLL
    Thank you,
    Steve -

    The error message appears to be related to a debug session and not come from the actual crash.
    So all I know is that you hade a server crash. I don't even know exactly what that means. Did Windows bite the dust? Or was it only SQL Server?
    Assuming the latter, I would expect the SQL Server errorlog to have some information (and that would be ERRORLOG.1 or earlier, since the server have been restarted), but if SQL Server died the output may be incomplete.
    There may be also dump files, but as I rarely look into these, I am not sure how to interpret them. But I am quite confident that "Unable to verify TimeStamp..." is not the reason SQL Server went down.
    I would suggest the following course:
    *  If the server is not critical, do nothing. As long as it has onlyl happened once, it has only happened once.
    *  If the server is critical, open a case with Microsoft if you are not able to figure out the reason yourself. The key here is "Unknown exception - code 000042ac".
    *  If it happens again, you should absolutely open a case. An important thing here is whether the stack dump is identical or something different. If the stack dumps are identical, you may have hit a bug in SQL Server or the OS, and applying CUs or OS
    fixes could help if it is a known issue. If the stack dump is something else, you have ghosts in the machine - that is, bad hardware.
    Erland Sommarskog, SQL Server MVP, [email protected]

Maybe you are looking for