Reporting Services, Error 7403 after SQL 2k8 R2 Upgrade
So, I did it. I upgraded the server from SQL Server 2008 to SQL Server 2008 R2. It actually went pretty well. Except for the Reporting Services point. Prior to the SQL 2k8 R2 upgrade I had it working perfectly. I could generate reports with zero problems. Now that I've done the upgrade, I'm getting error 7403 from SMS_SRS_REPORTING_POINT. I left the server alone for the night, came back this morning and my site status is green across the board w/o the Reporting Services role added. This is on a still-in-development server & I have plenty of test clients that still, as of this morning, work just fine on OSD, general software install tasks, etc. Everything server side is still working fine as well, except of course Reporting Services. And yes, I know SQL 2k8 R2 isn't officially supported by SCCM 2k7 yet. Regardless, if there is some sense to be made, some sort of solution or real idea that someone has I would appreciate it. I have done the following: Removed the Reporting Services point. Uninstalled SQL Reporting Services. Rebooted the server. Reinstalled SQL Reporting Services Configured SQL Reporting Services. Note: Configured this using port 80, with a host header instead of IP address. The server as a whole is set to use IPv4 before IPv6. Tested going to http://fqdn-of-the-server/ReportServer and http://fqdn-of-the-server/Reports . This works. It's also how I had it configured prior to the SQL upgrade, only before the upgrade I also had port 443 configured and it too worked just fine. I omitted using 443 this time because a) I'd already tried doing all of this that I'm writing with 443 to no avail and b) Read about (link below) re: SCCM 2k7 R2 with secure reporting. Everything worked before, doesn't now, figured I'd go by the book, so to speak. In the SCCM Console, I re-added the Reporting Services point, gave it a few minutes. After adding the RS point back, in Component Status, SMS_SRS_REPORTING_POINT throws error 7403 - "SMS SRS Web service is not running on SRS Reporting point server…", immediately followed by Message ID 4629 - "SMS Component Status Summarizer detected that the availability of component "SMS_SRS_REPORTING_POINT" on computer "NOTGONNADOIT" has changed to Online." In the SCCM Console, in Reporting -> Reporting Services, I see the server, can right-click on the server and select its properties. At first the Report Folder, Status, Size, and Contains fields all came back as "unavailable". I then went to the "Data Source Settings" tab and put in the server's name & SCCM SQL database name, clicked "Test", worked, set Data Source Authentication to "Windows Integrated Security", hit Apply, hit OK. Re-opened the Reporting Services properties, this time the Report Folder came back with "/ConfigMgr_IS1", Status was "Ok", Size was 0, and Contains was "0 Reports, 0 Folders". Retested by going to http://fqdn-of-the-server/ReportServer and http://fqdn-of-the-server/Reports in Firefox. Still worked. Ran the Copy Reports Wizard, keeping the same settings I had initially set. Most of the reports copied, however there were a good number that didn't. If I retried copying that group, it worked. Still had a few that I had to try a third time. In all cases where copying failed, I saw similar errors. For instance: Creating report 131 of 388 'History - CD-ROM history for a specific computer' Successfully retrieved the report from Wmi. Creating report folder 'Hardware - CD-ROM' on the server. Failed to create the report folder '/ConfigMgr_IS1//Hardware - CD-ROM' Unable to connect to the remote server Object reference not set to an instance of an object. While the Wizard was copying, right after one report failed copying, I went back to the Reporting Services properties, Status was still "Ok", everything else came back with valid data. Eventually I got all the reports copied over. Thus, on the properties of the Reporting Services point, the Size was "30MB (31,752,704 bytes)", and Contains listed "388 Reports, 49 Folders". Again, went to http://fqdn-of-the-server/ReportServer and http://fqdn-of-the-server/Reports . Still worked. Now I could see a folder labeled "ConfigMgr_IS1". I could also go into the folder, bring up a report, and run it successfully. This is all in Firefox 3.6.3, outside the SCCM Console. Oddities: Back in SCCM Console, if I click on "All Reports", at this point I'm never able to retrieve all 388 reports. Sometimes, by the time the query finishes, I can only pull up 3, 10, sometimes even 200-some-odd reports. Likewise if I start clicking on various folders under "Report Folders", I can retrieve most of the reports, though about half way down the list, every folder comes up blank. If I give a few seconds, refreshing the folder returns all the reports present. The behavior is very inconsistent. Sometimes the properties of the Reporting Service point come back as "unavailable" with all previously configurable fields grayed out. Sometimes the properties come back with valid data. At first it looked like the port 443 / grayed out field problem with SCCM 2k7 R2, but that's why I brought up Reporting Services w/o port 443, to negate that possibility. Sometimes I can run a report in SCCM Console, other times it just comes back as "Unable to connect to report server". A co-worker has a server of his own setup, so there's at least two of us trying to get this up and running, he's having the same problems on a box that is configured almost identical to mine. Most notably his is also running SQL 2k8 R2. My server config: OS: Server 2008 R2 SQL: SQL Server 2008 R2 Enterprise File Services, RDS, WDS, and WSUS added as roles. In IIS, SCCM is using its own site (SMSWeb), as is WSUS (WSUS Administration). SCCM is running in Mixed Mode, that never changed. SQL Reporting Services is running in Native mode. As for SQL, it's installed as the Default Instance (MSSQLSERVER) and all Instance & Shared features are installed. Installed at C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER, likewise for the Reporting Services (C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER) and Analysis Services (C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER). I've looked at the following resources, among others: http://blogs.technet.com/b/mwiles/archive/2009/02/18/reporting-services-server-properties-grayed-out.aspx http://support.microsoft.com/kb/957576/en-us http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/e8a1d5ed-5681-46ab-ac40-cf76a36982dc http://technet.microsoft.com/en-us/library/cc161979.aspx http://technet.microsoft.com/en-us/library/cc512026.aspx http://technet.microsoft.com/en-us/library/cc431393.aspx http://social.technet.microsoft.com/forums/en-US/configmgrsetup/thread/c8618325-7420-404a-a38a-d880d9dd99ca/ http://technet.microsoft.com/en-us/library/cc512026.aspx http://social.technet.microsoft.com/Forums/en/configmgrinventory/thread/2a4f9aa6-2bbb-49be-8d3c-7ed364ef9dc4 http://technet.microsoft.com/en-us/library/bb932213.aspx http://blogs.technet.com/b/configmgrteam/archive/2009/05/14/faq-sql-reporting-services-integration-with-system-center-configuration-manager-2007-r2.aspx Logs (changed server name to "notgonnadoit" for security): C:\Program Files (x86)\Microsoft Configuration Manager\Logs\SRSPSetup.log: <06-07-2010 16:51:43> ==================================================================== <06-07-2010 16:51:43> SMSSRSRP Setup Started.... <06-07-2010 16:51:43> Parameters: C:\PROGRA~2\MIE096~1\bin\i386\ROLESE~1.EXE /deinstall /siteserver:NOTGONNADOIT SMSSRSRP <06-07-2010 16:51:43> Deinstalling the SMSSRSRP <06-07-2010 16:51:43> Removing SRS Reporting Point Registry. <06-07-2010 16:51:43> Invoking process "C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe" "C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\SRSSERVER.dll" /unregister <06-07-2010 16:51:43> Unregistered DLL C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\SRSSERVER.dll <06-07-2010 16:51:43> Deinstallation was successful. <06-08-2010 09:09:33> ==================================================================== <06-08-2010 09:09:33> SMSSRSRP Setup Started.... <06-08-2010 09:09:33> Parameters: C:\PROGRA~2\MIE096~1\bin\i386\ROLESE~1.EXE /install /siteserver:NOTGONNADOIT SMSSRSRP <06-08-2010 09:09:33> Installing Pre Reqs for SMSSRSRP <06-08-2010 09:09:33> ======== Installing Pre Reqs for Role SMSSRSRP ======== <06-08-2010 09:09:33> Found 0 Pre Reqs for Role SMSSRSRP <06-08-2010 09:09:33> ======== Completed Installion of Pre Reqs for Role SMSSRSRP ======== <06-08-2010 09:09:33> Installing the SMSSRSRP <06-08-2010 09:09:33> Invoking process "C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe" "C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\SRSSERVER.dll" <06-08-2010 09:09:35> Registered DLL C:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\SRSSERVER.dll <06-08-2010 09:09:35> Installation was successful. C:\Program Files (x86)\Microsoft Configuration Manager\Logs\srsp.log: $$<SMS_SRS_REPORTING_POINT><Mon Jun 07 16:50:03.217 2010 Eastern Daylight Time><thread=880 (0x370)> SMS_EXECUTIVE signalled SMS_SRS_REPORTING_POINT to stop. $$<SMS_SRS_REPORTING_POINT><Mon Jun 07 16:51:37.969 2010 Eastern Daylight Time><thread=7284 (0x1C74)> Shutting Down...~ $$<SMS_SRS_REPORTING_POINT><Mon Jun 07 16:51:37.973 2010 Eastern Daylight Time><thread=880 (0x370)> SMS_EXECUTIVE started SMS_SRS_REPORTING_POINT as thread ID 5964 (0x174C). $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 09:09:38.288 2010 Eastern Daylight Time><thread=7368 (0x1CC8)> This is a SRS Reporting Point Role as SRSRP registry key exists.~ $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 09:09:38.351 2010 Eastern Daylight Time><thread=5964 (0x174C)> ~Waiting for changes for 0 minutes $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 09:09:38.366 2010 Eastern Daylight Time><thread=5964 (0x174C)> Timed Out...~ $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 09:09:38.366 2010 Eastern Daylight Time><thread=5964 (0x174C)> STATMSG: ID=7403 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SRS_REPORTING_POINT" SYS=NOTGONNADOIT SITE=IS1 PID=7268 TID=5964 GMTDATE=Tue Jun 08 13:09:40.098 2010 ISTR0="NOTGONNADOIT" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 09:09:40.098 2010 Eastern Daylight Time><thread=5964 (0x174C)> Failures reported during periodic health check by the SRS Server NOTGONNADOIT. Will retry check in 57 minutes~ $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 09:09:40.098 2010 Eastern Daylight Time><thread=5964 (0x174C)> ~Waiting for changes for 57 minutes $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 09:09:40.113 2010 Eastern Daylight Time><thread=5964 (0x174C)> Timed Out...~ $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 10:06:40.198 2010 Eastern Daylight Time><thread=5964 (0x174C)> STATMSG: ID=7403 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SRS_REPORTING_POINT" SYS=NOTGONNADOIT SITE=IS1 PID=7268 TID=5964 GMTDATE=Tue Jun 08 14:06:40.526 2010 ISTR0="NOTGONNADOIT" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 10:06:40.526 2010 Eastern Daylight Time><thread=5964 (0x174C)> Failures reported during periodic health check by the SRS Server NOTGONNADOIT. Will retry check in 57 minutes~ $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 10:06:40.526 2010 Eastern Daylight Time><thread=5964 (0x174C)> ~Waiting for changes for 57 minutes $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 10:06:40.526 2010 Eastern Daylight Time><thread=5964 (0x174C)> Timed Out...~ $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 11:03:40.586 2010 Eastern Daylight Time><thread=5964 (0x174C)> STATMSG: ID=7403 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SRS_REPORTING_POINT" SYS=NOTGONNADOIT SITE=IS1 PID=7268 TID=5964 GMTDATE=Tue Jun 08 15:03:40.695 2010 ISTR0="NOTGONNADOIT" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 11:03:40.695 2010 Eastern Daylight Time><thread=5964 (0x174C)> Failures reported during periodic health check by the SRS Server NOTGONNADOIT. Will retry check in 57 minutes~ $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 11:03:40.695 2010 Eastern Daylight Time><thread=5964 (0x174C)> ~Waiting for changes for 57 minutes $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 11:03:40.695 2010 Eastern Daylight Time><thread=5964 (0x174C)> Timed Out...~ $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 12:00:40.909 2010 Eastern Daylight Time><thread=5964 (0x174C)> STATMSG: ID=7403 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SRS_REPORTING_POINT" SYS=NOTGONNADOIT SITE=IS1 PID=7268 TID=5964 GMTDATE=Tue Jun 08 16:00:41.018 2010 ISTR0="NOTGONNADOIT" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 12:00:41.033 2010 Eastern Daylight Time><thread=5964 (0x174C)> Failures reported during periodic health check by the SRS Server NOTGONNADOIT. Will retry check in 57 minutes~ $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 12:00:41.033 2010 Eastern Daylight Time><thread=5964 (0x174C)> ~Waiting for changes for 57 minutes $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 12:00:41.033 2010 Eastern Daylight Time><thread=5964 (0x174C)> Timed Out...~ $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 12:57:41.085 2010 Eastern Daylight Time><thread=5964 (0x174C)> STATMSG: ID=7403 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SRS_REPORTING_POINT" SYS=NOTGONNADOIT SITE=IS1 PID=7268 TID=5964 GMTDATE=Tue Jun 08 16:57:41.202 2010 ISTR0="NOTGONNADOIT" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 12:57:41.203 2010 Eastern Daylight Time><thread=5964 (0x174C)> Failures reported during periodic health check by the SRS Server NOTGONNADOIT. Will retry check in 57 minutes~ $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 12:57:41.206 2010 Eastern Daylight Time><thread=5964 (0x174C)> ~Waiting for changes for 57 minutes $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 12:57:41.209 2010 Eastern Daylight Time><thread=5964 (0x174C)> Timed Out...~ $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 13:54:41.449 2010 Eastern Daylight Time><thread=5964 (0x174C)> STATMSG: ID=7403 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SRS_REPORTING_POINT" SYS=NOTGONNADOIT SITE=IS1 PID=7268 TID=5964 GMTDATE=Tue Jun 08 17:54:41.543 2010 ISTR0="NOTGONNADOIT" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 13:54:41.543 2010 Eastern Daylight Time><thread=5964 (0x174C)> Failures reported during periodic health check by the SRS Server NOTGONNADOIT. Will retry check in 57 minutes~ $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 13:54:41.543 2010 Eastern Daylight Time><thread=5964 (0x174C)> ~Waiting for changes for 57 minutes $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 13:54:41.543 2010 Eastern Daylight Time><thread=5964 (0x174C)> Timed Out...~ $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 14:51:41.603 2010 Eastern Daylight Time><thread=5964 (0x174C)> STATMSG: ID=7403 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SRS_REPORTING_POINT" SYS=NOTGONNADOIT SITE=IS1 PID=7268 TID=5964 GMTDATE=Tue Jun 08 18:51:41.696 2010 ISTR0="NOTGONNADOIT" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 14:51:41.696 2010 Eastern Daylight Time><thread=5964 (0x174C)> Failures reported during periodic health check by the SRS Server NOTGONNADOIT. Will retry check in 57 minutes~ $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 14:51:41.696 2010 Eastern Daylight Time><thread=5964 (0x174C)> ~Waiting for changes for 57 minutes $$<SMS_SRS_REPORTING_POINT><Tue Jun 08 14:51:41.712 2010 Eastern Daylight Time><thread=5964 (0x174C)> C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\LogFiles\ReportServerService__06_08_2010_16_02_47.log, upon starting SQL RS: <Header> <Product>Microsoft SQL Server Reporting Services Version 2009.0100.1600.01 ((KJ_RTM).100402-1539 )</Product> <Locale>English (United States)</Locale> <TimeZone>Eastern Daylight Time</TimeZone> <Path>C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\Logfiles\ReportServerService__06_08_2010_16_02_47.log</Path> <SystemName>NOTGONNADOIT</SystemName> <OSName>Microsoft Windows NT 6.1.7600</OSName> <OSVersion>6.1.7600</OSVersion> <ProcessID>7492</ProcessID> <Virtualization>None</Virtualization> </Header> rshost!rshost!f44!06/08/2010-16:02:47:: i INFO: CLR runtime is initialized. rshost!rshost!f44!06/08/2010-16:02:47:: i INFO: Derived memory configuration based on physical memory as 16772032 KB appdomainmanager!DefaultDomain!1574!06/08/2010-16:02:47:: i INFO: Entered managed ServiceMain in DefaultDomain. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing ConnectionType to '0' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: Value '0' of parameter 0 is out of the range [1, 2147483647]. library!DefaultDomain!9a0!06/08/2010-16:02:47:: w WARN: Initializing MaxActiveReqForOneUser to default value of '20' requests(s) because it was incorrectly specified in Configuration file as '0'. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException,Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Threading.ThreadAbortException,System.Web.UI.ViewStateException,System.OutOfMemoryException,System.Web.HttpException,System.IO.IOException,System.IO.FileLoadException,Microsoft.SharePoint.SPException' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing AuthenticationTypes to '4' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing RSWindowsExtendedProtectionLevel to 'Off' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing RSWindowsExtendedProtectionScenario to 'Proxy' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing EnableAuthPersistence to 'True' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing MemorySafetyMargin to '80' percent as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing MemoryThreshold to '90' percent as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing UrlRoot to 'http://notgonnadoitFQDN/ReportServer' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing IsReportManagerEnabled to 'True' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing ReportServerUrl to 'http://notgonnadoitFQDN/ReportServer' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing MaxConnections to '2' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing Timeout to '10' second(s) as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing AppID to '(Default)' as specified in Configuration file. library!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Initializing CacheLevel to 'Default' as specified in Configuration file. resourceutilities!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Reporting Services starting SKU: Enterprise configmanager!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Using report server internal url http://notgonnadoitFQDN/ReportServer. configmanager!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Using report server external url http://notgonnadoitFQDN:80/ReportServer. configmanager!DefaultDomain!9a0!06/08/2010-16:02:47:: i INFO: Using url root http://notgonnadoitFQDN/ReportServer. rshost!rshost!9a0!06/08/2010-16:02:47:: i INFO: Configuring maxPhysicalCpu=8, minLogicalCpu=0 rshost!rshost!9a0!06/08/2010-16:02:47:: i INFO: Logical processor per physical processor 4 rshost!rshost!9a0!06/08/2010-16:02:47:: i INFO: Maximum logical CPU is 8 configmanager!DefaultDomain!9a0!06/08/2010-16:02:48:: i INFO: Using report server internal url http://notgonnadoitFQDN/ReportServer. configmanager!DefaultDomain!9a0!06/08/2010-16:02:48:: i INFO: Using report server external url http://notgonnadoitFQDN:80/ReportServer. configmanager!DefaultDomain!9a0!06/08/2010-16:02:48:: i INFO: Using url root http://notgonnadoitFQDN/ReportServer. appdomainmanager!DefaultDomain!9a0!06/08/2010-16:02:48:: i INFO: Appdomain:2 WindowsService_0 started. resourceutilities!WindowsService_0!9a0!06/08/2010-16:02:48:: i INFO: Reporting Services starting SKU: Enterprise library!WindowsService_0!1d0c!06/08/2010-16:02:48:: i INFO: Catalog SQL Server Edition = Enterprise rshost!rshost!1efc!06/08/2010-16:02:48:: i INFO: Registered url=http://notgonnadoitFQDN:80/ReportServer/, vdir=/ReportServer, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer. rshost!rshost!1efc!06/08/2010-16:02:48:: i INFO: Currently registered url http://notgonnadoitFQDN:80/ReportServer/ on endpoint 2 rshost!rshost!19c0!06/08/2010-16:02:48:: i INFO: Registered url=http://notgonnadoitFQDN:80/Reports/, vdir=/Reports, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportManager. rshost!rshost!19c0!06/08/2010-16:02:48:: i INFO: Currently registered url http://notgonnadoitFQDN:80/Reports/ on endpoint 3 rshost!rshost!e58!06/08/2010-16:02:48:: i INFO: Endpoint 4 is disabled and no url is registered vdir=/ReportServer/ReportBuilder, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\ReportBuilder. resourceutilities!DefaultDomain!9a0!06/08/2010-16:02:48:: i INFO: Maximum memory limit is 2097152Mb rshost!rshost!9a0!06/08/2010-16:02:48:: i INFO: Derived memory configuration based on physical memory as 16772032 KB crypto!WindowsService_0!1d0c!06/08/2010-16:02:48:: i INFO: Initializing crypto as user: NT AUTHORITY\NETWORK SERVICE servicecontroller!DefaultDomain!1680!06/08/2010-16:02:48:: i INFO: Total Physical memory: 17174560768 crypto!WindowsService_0!1d0c!06/08/2010-16:02:48:: i INFO: Exporting public key rpcserver!DefaultDomain!176c!06/08/2010-16:02:48:: i INFO: Process monitoring started. crypto!WindowsService_0!1d0c!06/08/2010-16:02:48:: i INFO: Performing sku validation crypto!WindowsService_0!1d0c!06/08/2010-16:02:48:: i INFO: Importing existing encryption key dbpolling!WindowsService_0!1d0c!06/08/2010-16:02:48:: i INFO: EventPolling polling service started dbpolling!WindowsService_0!1d0c!06/08/2010-16:02:48:: i INFO: NotificationPolling polling service started dbpolling!WindowsService_0!1d0c!06/08/2010-16:02:48:: i INFO: SchedulePolling polling service started dbpolling!WindowsService_0!1d0c!06/08/2010-16:02:48:: i INFO: UpgradePolling polling service started dbpolling!WindowsService_0!fac!06/08/2010-16:02:48:: i INFO: HeartbeatThread(EventPolling): heartbeat thread started. dbpolling!WindowsService_0!14cc!06/08/2010-16:02:48:: i INFO: HeartbeatThread(NotificationPolling): heartbeat thread started. dbpolling!WindowsService_0!1efc!06/08/2010-16:02:48:: i INFO: PollingMaintenance: Polling started resourceutilities!WindowsService_0!1efc!06/08/2010-16:02:48:: i INFO: Maximum memory limit is 2097152Mb rpcserver!DefaultDomain!1d0c!06/08/2010-16:02:48:: i INFO: RPC Server started. servicecontroller!DefaultDomain!1d0c!06/08/2010-16:02:48:: i INFO: RPC Server started. Endpoint name ='ReportingServices$MSRS10_50.MSSQLSERVER' appdomainmanager!WindowsService_0!1d0c!06/08/2010-16:02:48:: i INFO: Appdomain:2 WindowsService_0 initialized. library!DefaultDomain!1574!06/08/2010-16:02:49:: i INFO: Catalog SQL Server Edition = Enterprise Upon Expanding "All Folders" in the SCCM Console, same log: appdomainmanager!DefaultDomain!1afc!06/08/2010-16:07:03:: i INFO: Appdomain:3 ReportServer_MSSQLSERVER_0-1-129205012234697461 started. appdomainmanager!ReportServer_0-1!1afc!06/08/2010-16:07:04:: i INFO: RS authentication mode is 4; effective ASP.NET authentication mode is Windows. vdir=/ReportServer. appdomainmanager!DefaultDomain!1afc!06/08/2010-16:07:04:: i INFO: Appdomain:3 ReportServer_MSSQLSERVER_0-1-129205012234697461 initialized (#1). webserver!ReportServer_0-1!1afc!06/08/2010-16:07:14:: i INFO: Reporting Web Server started resourceutilities!ReportServer_0-1!1afc!06/08/2010-16:07:14:: i INFO: Reporting Services starting SKU: Enterprise resourceutilities!ReportServer_0-1!1afc!06/08/2010-16:07:14:: i INFO: Maximum memory limit is 2097152Mb library!ReportServer_0-1!1afc!06/08/2010-16:07:16:: Call to ListChildrenAction(/, False). library!ReportServer_0-1!1afc!06/08/2010-16:07:16:: i INFO: Catalog SQL Server Edition = Enterprise crypto!ReportServer_0-1!1afc!06/08/2010-16:07:16:: i INFO: Initializing crypto as user: NT AUTHORITY\NETWORK SERVICE crypto!ReportServer_0-1!1afc!06/08/2010-16:07:16:: i INFO: Exporting public key crypto!ReportServer_0-1!1afc!06/08/2010-16:07:16:: i INFO: Performing sku validation crypto!ReportServer_0-1!1afc!06/08/2010-16:07:16:: i INFO: Importing existing encryption key library!ReportServer_0-1!fe4!06/08/2010-16:07:16:: Call to ListChildrenAction(/ConfigMgr_IS1, False). library!ReportServer_0-1!1afc!06/08/2010-16:07:17:: Call to ListChildrenAction(/, False). library!ReportServer_0-1!1afc!06/08/2010-16:07:17:: Call to ListChildrenAction(/ConfigMgr_IS1, False). And soon after that, upon refreshing the view in SCCM Console, same log: library!ReportServer_0-1!3e4!06/08/2010-16:11:35:: Call to GetPropertiesAction(/ConfigMgr_IS1/Asset Intelligence/Hardware 01A - Summary of computers in a specific collection, PathBased). library!ReportServer_0-1!3e4!06/08/2010-16:12:08:: Call to GetPoliciesAction(DATASOURCE). library!ReportServer_0-1!3e4!06/08/2010-16:12:08:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InvalidItemPathException: , Microsoft.ReportingServices.Diagnostics.Utilities.InvalidItemPathException: The path of the item 'DATASOURCE' is not valid. The full path must be less than 260 characters long; other restrictions apply. If the report server is in native mode, the path must start with slash.; Finally, C:\Program Files (x86)\Microsoft Configuration Manager\AdminUI\AdminUILog\SmsAdminUI.log [6][6/8/2010 4:09:39 PM] :Unable to retreive the Server Properties for 'NOTGONNADOIT' [3][6/8/2010 4:09:41 PM] :Creating folder name 'ConfigMgr_IS1', path '/'. [3][6/8/2010 4:09:41 PM] :Unable to connect to the remote server [3][6/8/2010 4:09:58 PM] :Help topic not found in 'HelpTopicLinks.xml' for topic ID: '7e96e251-ed74-4905-87c0-77d082a5fa4d' [8][6/8/2010 4:10:08 PM] :System.Net.WebException\r\nUnable to connect to the remote server\r\n at System.Net.HttpWebRequest.GetResponse() at Microsoft.ConfigurationManagement.AdminConsole.SmsSnapInBase.IsUriAvailable(String uri)\r\nSystem.Net.Sockets.SocketException\r\nAn operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full 207.46.16.233:80\r\n at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)\r\n So, not sure what other logs to supply, I can post any log anyone asks of me, but I'm thoroughly confused at this point, given that everything was made of unicorns & rainbows before the SQL upgrade.. Any help would be greatly appreciated. Thank you in advance!
June 8th, 2010 11:59pm

Hi, SQL 2008 R2 is not yet supported by ConfigMgr.Bechir Gharbi. MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront (Time Zone : GMT+1)
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2010 12:39am

Hi, SQL 2008 R2 is not yet supported by ConfigMgr. Bechir Gharbi. MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront (Time Zone : GMT+1) I'd really appreciate a response where someone gave some thought to it. Responses like this are the reason why I usually don't take the time to post & just hammer it out myself. Yes, I know, I should have put some sort of disclaimer in my original post.
June 9th, 2010 2:37am

Bechir's answer is valid. SQL 2008 R2 is not listed in the supported configurations: http://technet.microsoft.com/en-us/library/ee344146.aspx.
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2010 9:28am

Bechir's answer is valid. SQL 2008 R2 is not listed in the supported configurations: http://technet.microsoft.com/en-us/library/ee344146.aspx. Again, I'm aware that it's not a supported configuration (yet). Nowhere did I say his answer wasn't valid, per se, but I think the point is being missed here. Every role that I have implemented works except for Reporting Services. That does a lot for the situation as it is. The situation would be vastly different if things were generally broken.
June 9th, 2010 3:12pm

When SQL 2008 R2 become supported there might be a patch or settingt that are required that you don't have set correctly. Unfortunately no one can offer a solution that we don't know what Microsoft will or won't support. Even if you call Microsoft they will tell you that it isn't supported yet. That being said I know some people have it working but I don't know what tweaks and work arounds they did to get it functioning. Is this your test enviroment or your production enviroment?http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2010 3:47pm

This is in a test environment that will eventually become the production one; unfortunately I don't have the resources to bring up two environments at the same time right now. I could potentially roll everything back if absolutely needed as a last resort. Anything you might remember about what tweaks other people used, even search terms? Guess I could do some more searching myself - if the answer's out there I'm willing to hunt for it.
June 9th, 2010 4:06pm

By using the info contained here: http://blogs.technet.com/b/configurationmgr/archive/2010/06/03/solution-you-may-experience-slow-performance-when-using-bits-and-kerberos-authentication-on-configmgr-2007-distribution-points.aspx I'm now able to get a full listing of the reports in the "All Reports" folder. I'm still having problems copying over all those reports, but I consider it to be a bit of headway. EDIT: Something else I'm noticing, when copying reports over to the Report Server, the ones that fail are consistently later in the process. It doesn't seem to matter the category, it hasn't started failing at the start. In addition to following that advice, I've also made some other edits to the SQL RS configuration, according to this: http://social.msdn.microsoft.com/forums/en-US/sqlreportingservices/thread/530ed56d-7c84-4d13-8998-80a8bf142197/ I followed point 1 in that link. I also added SSL back to the SQL RS config and soon after, in the middle of copying or running a report, if it failed I immediately fired up a web browser, tried going to https://fqdn-of-the-server/Reports, I simply got "ERROR". I looked back at the Reporting Services Configuration Manager, and the SSL version of the Web Service URL (ReportServer) had vanished, leaving only the port 80 URLs displayed. I also looked in my logs, in my System log I had Event ID 15300, Source; HttpEvent, "SSL Certificate Settings deleted for Port: xxx.xxx.xxx.xxx:443." Sure enough, the Web Service URL was still accessible over port 80. Since that point I've left off port 443. Copying reports is still flaky, but I've run a few reports via Reporting Services as it is, even in the SCCM Console. It seems like under little or no load the Reporting Services point works, and SQL Reporting Services works no matter what, but if I do too much then the Reporting Services point fails, yet SQL RS continues to run. I'm still getting SMS_SRS_REPORTING_POINT throwing a 7403 error. So better, but not how it should be.
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2010 10:19pm

As of June 30, looks like SQL 2k8 R2 is now supported: http://blogs.technet.com/b/configmgrteam/archive/2010/06/30/configuration-manager-support-announcements-for-june-2010.aspx Since my last post, I can still generate reports fairly reliably, though I'm still getting error 7403 from SMS_SRS_REPORTING_POINT every hour or so.
July 2nd, 2010 5:11pm

I'll check my lab tonight for 7403 errors. I installed directly to SQL 2008 R2 and I haven't noticed any. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
Free Windows Admin Tool Kit Click here and download it now
July 2nd, 2010 9:26pm

Hello, I work with SCCM extensively as a consultant and I have run into this issue with two different installs of SCCM that use SQL Server 2008 R2 for the ConfigMgr DB and Reports. One of these two SCCM installs was a fresh build, with no prior versions of SQL having been installed. The other install had a previous version of SQL that was upgraded from SQL Server 2005 SP3 to SQL Server 2008 R2. Both of these SCCM servers are functioning properly and reports can be generated successfully, however, the Message ID 7403 keeps popping up regularly in the logs. I wanted to contribute feedback to help raise awareness. The article referenced above at http://blogs.technet.com/b/configmgrteam/archive/2010/06/30/configuration-manager-support-announcements-for-june-2010.aspx mentions "No software update is required." However, it appears a patch will be needed to clear this error. Thank you! Jesse Garcia
July 6th, 2010 7:06pm

Hello, I work with SCCM extensively as a consultant and I have run into this issue with two different installs of SCCM that use SQL Server 2008 R2 for the ConfigMgr DB and Reports. One of these two SCCM installs was a fresh build, with no prior versions of SQL having been installed. The other install had a previous version of SQL that was upgraded from SQL Server 2005 SP3 to SQL Server 2008 R2. Both of these SCCM servers are functioning properly and reports can be generated successfully, however, the Message ID 7403 keeps popping up regularly in the logs. I wanted to contribute feedback to help raise awareness. The article referenced above at http://blogs.technet.com/b/configmgrteam/archive/2010/06/30/configuration-manager-support-announcements-for-june-2010.aspx mentions "No software update is required." However, it appears a patch will be needed to clear this error. Thank you! Jesse Garcia
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2010 7:06pm

Hello, I work with SCCM extensively as a consultant and I have run into this issue with two different installs of SCCM that use SQL Server 2008 R2 for the ConfigMgr DB and Reports. One of these two SCCM installs was a fresh build, with no prior versions of SQL having been installed. The other install had a previous version of SQL that was upgraded from SQL Server 2005 SP3 to SQL Server 2008 R2. Both of these SCCM servers are functioning properly and reports can be generated successfully, however, the Message ID 7403 keeps popping up regularly in the logs. I wanted to contribute feedback to help raise awareness. The article referenced above at http://blogs.technet.com/b/configmgrteam/archive/2010/06/30/configuration-manager-support-announcements-for-june-2010.aspx mentions "No software update is required." However, it appears a patch will be needed to clear this error. Thank you! Jesse Garcia Thank you! Finally, someone else who's seen this. In general, this is the exact same thing I'm seeing. My server (now in production) was an upgrade and a co-worker's was a clean install (mentioned in the original post, but understandably, it's long), both servers are producing 7403 errors while still being able to generate reports.
July 6th, 2010 10:25pm

I work with SCCM extensively as a consultant and I have run into this issue with two different installs of SCCM that use SQL Server 2008 R2 for the ConfigMgr DB and Reports. One of these two SCCM installs was a fresh build, with no prior versions of SQL having been installed. The other install had a previous version of SQL that was upgraded from SQL Server 2005 SP3 to SQL Server 2008 R2. I am just amazed that you've done two SCCM installs/upgrades on SQL 2008 R2 since it became supported last week. Of course as a consultant you'd never do an unsupported install right? ;-) Seriously, someone needs to open a CSS case on this to see if there's a hotfix forthcoming. I have a SCCM lab on SQL 2008 R2 now but I haven't looked for this particular issue. I will look for it tonight though. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2010 11:16pm

Has anyone seen this error when running SQL 2008 SP1?
July 7th, 2010 9:20pm

Hi all, We are also seeing this error. Has anyone opened a case to see if a hot fix is forth coming. all reports are working as of right now but I am afraid that leaving the site like this will cuse other admins missiung an actual issue. If anyone has heard anything please let us know. I'm working on opening a case, if I am able to (should know in the next 2 days), I will re-post any info I gain from it.
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2010 9:21pm

Has anyone seen this error when running SQL 2008 SP1? It's possible; error <del>7403</del> 7404 was seen the most from perhaps SCCM SP1 and earlier - there was a hotfix for it prior to SCCM SP2 and the hotfix was included in SP2, but it applied to SQL Server 2008 SP1 and earlier. This thread is regarding SQL Server 2008 R2 specifically. Edit : Actually that was for error 7404 (http://support.microsoft.com/kb/957576/en-us ). Still - everything mentioned here is really about SQL 2k8 R2.
July 7th, 2010 9:35pm

I work with SCCM extensively as a consultant and I have run into this issue with two different installs of SCCM that use SQL Server 2008 R2 for the ConfigMgr DB and Reports. One of these two SCCM installs was a fresh build, with no prior versions of SQL having been installed. The other install had a previous version of SQL that was upgraded from SQL Server 2005 SP3 to SQL Server 2008 R2. I am just amazed that you've done two SCCM installs/upgrades on SQL 2008 R2 since it became supported last week. Of course as a consultant you'd never do an unsupported install right? ;-) Seriously, someone needs to open a CSS case on this to see if there's a hotfix forthcoming. I have a SCCM lab on SQL 2008 R2 now but I haven't looked for this particular issue. I will look for it tonight though. John Marcum | http://myitforum.com/cs2/blogs/jmarcum | Hi John, Both installs were in test labs. I wouldn't do this in a customer's environment without letting them know up front they could have an issue that would need to be fixed by a hotfix down the road. I actually did a customer install today of SCCM and used SQL 2008 (non-R2). Thanks, Jesse
Free Windows Admin Tool Kit Click here and download it now
July 8th, 2010 6:31am

I work with SCCM extensively as a consultant and I have run into this issue with two different installs of SCCM that use SQL Server 2008 R2 for the ConfigMgr DB and Reports. One of these two SCCM installs was a fresh build, with no prior versions of SQL having been installed. The other install had a previous version of SQL that was upgraded from SQL Server 2005 SP3 to SQL Server 2008 R2. I am just amazed that you've done two SCCM installs/upgrades on SQL 2008 R2 since it became supported last week. Of course as a consultant you'd never do an unsupported install right? ;-) Seriously, someone needs to open a CSS case on this to see if there's a hotfix forthcoming. I have a SCCM lab on SQL 2008 R2 now but I haven't looked for this particular issue. I will look for it tonight though. John Marcum | http://myitforum.com/cs2/blogs/jmarcum | Hi John, Both installs were in test labs. I wouldn't do this in a customer's environment without letting them know up front they could have an issue that would need to be fixed by a hotfix down the road. I actually did a customer install today of SCCM and used SQL 2008 (non-R2). Thanks, Jesse
July 8th, 2010 6:31am

I've had this error in my environment ever since I did my original ConfigMgr install. I originally had SRS installed on a SQL 2008 database with ConfigMgr SP1. I installed the hotfix mentioned above and that fixed the 7404 errors I was getting, but I still get the 7403 errors (once an hour no less). I have since upgraded ConfigMgr to SP2, and the SRS database to 2008 R2. I am still getting the 7403 and it's driving me nuts! Anyone finds a hotfix to get rid of those errors I'll be more than happy to test it our for ya!
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2010 8:58pm

Hi, the error 7403 can appears not only with SQL 2008 R2 but also with SQL 2005/2008 http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/5d97eb7e-e811-4c7b-a057-a22821cb21d4 Take a look at this thread http://social.technet.microsoft.com/Forums/en-US/configmgrinventory/thread/2a4f9aa6-2bbb-49be-8d3c-7ed364ef9dc4 , I know this solution has resolved the issue (SQL 2005) for Marco08 and maybe it helps you also Microsoft MVP - SCCM
July 14th, 2010 9:54pm

Same here, ConfigMgr SP2 R3 running on 2008 R2 pointing at a SQL2008 R2 cluster, all patched and up to date. It all works great, reports copied over fine, can view reports fine but yeah every hour or so - Error 7403:SMS SRS web service is not running on SRS Reporting point server XXXXX Apart from the error message everything seems to be working OK. Has anyone opened a call for this yet?
Free Windows Admin Tool Kit Click here and download it now
July 26th, 2010 5:05pm

Hi, A little info, see the Sherry's reponse here http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/c230c65f-ecad-424b-b6a2-bf5763e2900b
July 30th, 2010 10:07pm

Hi, Now the CU4 for SQL Server 2008 R2 fix the error 7403 http://support.microsoft.com/kb/2345451/en-us
Free Windows Admin Tool Kit Click here and download it now
October 21st, 2010 12:22am

Bechir, Thanks for posting the link to that, sure enough, that fixed the 7403 error. The other errors shown in the logs were part of a multi-layered problem. Another admin (not on my server) had put a GPO in place that altered DCOM permissions to enable event forwarding, but with the way the GPO was implemented, it didn't allow other accounts to properly launch/activate processes as they should have been allowed to. Clearing off that GPO increased server performance by a very noticeable amount (among other things). Reporting Services is still being flaky, but with every other problem resolved it's become much easier to determine the source of this last remaining issue. Thanks again.
November 2nd, 2010 10:42am

Hi all sorry to tag ont othe end of this but a customer of mine is seeing this issue we are looking at putting the CU4 for SQL Server 2008 R2 to try and fix the error 7403 http://support.microsoft.com/kb/2345451/en-us but which patch / hotfix contained in the role up is the actual one that fixes the issue? does any one have any idea ?? thanks for your help
Free Windows Admin Tool Kit Click here and download it now
June 14th, 2011 5:10am

I think it is this one SQLServer2008R2_RTM_CU4_2345451_10_50_1746_x64http://www.enhansoft.com/
June 14th, 2011 6:06am

hi thanks for your reply, that is the full update package from kb 2345451 (http://support.microsoft.com/kb/2345451/en-us ) , what i would like to know out of the hotfixes that are included in that update package which one of those individual hotfixes contained in the role up is the one that fixed the problem
Free Windows Admin Tool Kit Click here and download it now
June 14th, 2011 6:14am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics