Jump to content


Search the Community

Showing results for tags 'SQL 2008 R2'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests

Found 2 results

  1. Hello together We have an issue in our LAB, when we try to import any driver into SCCM 2012 RC2 Console. It doesnt matter which driver we try to import, it always fail with following error: "An error occureed while importing the selected driver" I had a look into the SmsAdminUI.log and what I found there, seems a bit strange :[6, PID:5604][03/19/2012 15:34:30] :Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put() at Microsoft.ConfigurationManagement.AdminConsole.DesiredConfigurationManagement.ConsoleDcmConnection.Microsoft.ConfigurationManagement.DesiredConfigurationManagement.IDcmStoreConnection.StoreNewItem(ConfigurationItem item) at Microsoft.ConfigurationManagement.DesiredConfigurationManagement.ConfigurationItem.Persist(Object existingStoreItem) at Microsoft.ConfigurationManagement.AdminConsole.Driver.ImportDriverWizardForm.PutDriverObject(SmsDialogData pageData, IResultObject selectedObject, DriverConfigurationItemInfo driverInfo, List`1 allDriversInfoToRefreshDP, Boolean& hasValidDriver, Boolean& hasErrorDriver, PropertyDataUpdateAction& updateAction)\r\nConfigMgr Error Object:instance of SMS_ExtendedStatus{ CauseInfo = ""; Description = "SQL command failed: if (object_id('tempdb..#sp_setupci_resultstr') IS NOT NULL) drop table #sp_setupci_resultstr;"; ErrorCode = 2168851714; File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\ssputility.cpp"; Line = 2105; ObjectInfo = "Please check SMS Provider log file for details of the SQL errors"; Operation = "PutInstance"; ParameterInfo = ""; ProviderName = "ExtnProv"; SQLMessage = "[24000][0][Microsoft][sql Server Native Client 10.0]Invalid cursor state"; SQLSeverity = 0; SQLStatus = 0; StatusCode = 2147749889;}; We use SCCM 2012 with only a Primary Site and SQL Server 2008 R2 SP 1 CU4. May somebody experienced the same problem? Thank you for your help Best wishes
  2. We’ve been using SCCM 2012 since its release without any major issues, but I noticed today that we’re fast running out of room on the partition we have SQL2008 R2 installed on, and that the culprit was ReportServer_log.ldf. It is currently 145GB and growing, and nothing I have tried has reduced its size. So far I have changed the recovery node to Simple, performed a backup (which I thought was supposed to flush LDF files?), and performed a Shrink (file based) on our ReportServer DB (though I can't find any listing of ReportServer_log.LDF when using MS SQL Server Management Studio, and it reports that our ReportServer DB is only ~45MB). Any SCCM/SQL gurus out there that could offer some insight into how I can reduce its size, AND keep it from getting this large in the future? Is there a way to pull up/modify the LDF file from the Management Studio? Thanks for any input...I'm at a complete loss here!
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.