Re: SMS 2003 Reporting: http error 500

From: Sai Wong (saiwong_at_online.microsoft.com)
Date: 03/17/04 

Date: Wed, 17 Mar 2004 09:11:22 -0800

Open a dos shell window and
go to your inetpub\wwwroot\SMSComponent directory
and verify that SMSRPH.exe and SMSComponent.dll exist

in the dos window type the following command

SMSRPH.exe /Service

does this command succeed ?
If you get an access denied error then you must give
Administrators "Read & Execute" permissions to this
directory, then try the command again.

Sai

This posting is provided AS IS with no warranties and
confers no rights.

>-----Original Message-----
>Thank you, but still no success!
>
>The site was already in "trusted sites" (IE in W2003
doesn't show any other
>site by default). Changed the security
setting "automatically logon with
>current username and
>password" also for trusted site (this option is only
default for local
>intranet site).
>
>Now, the Windows Logon Screen doesn't appear anymore, I'm
getting the http
>500 error directly.
>
>I did some research and discoverd in the IIS Log (which
is attached to this
>message) a ASP_0177_:_8007007e|Server.CreateObject_Failed
80 error.
>
>According to MS KB 273744, there is a DLL not corrcetly
registred.
>
>Thank you all for more advice in advance!
>Franz
>
>
>"Sai Wong" <saiwong@online.microsoft.com> schrieb im
Newsbeitrag
>news:e3b201c40b88$351b35d0$a501280a@phx.gbl...
>> If you are prompted to enter credentials then I think it
>> is the IE 6 security changes that is the issue.
>>
>> In IE go to "Internet options"
>> Select the Security tab
>> click on the Trusted sites icon
>> press Sites... button
>> add the SMS Report Viewer site as one of your trusted
>> sites (Add the website to the zone)
>> make sure "require server verification" checkbox is
>> UNCHECKED
>> press ok
>>
>> Now press Custom Level... button
>> In the security settings go down to the bottom and make
>> sure "automatically logon with current username and
>> password" is selected
>>
>>
>> Sai
>>
>> This posting is provided AS IS with no warranties and
>> confers no rights.
>>
>>
>>
>> >-----Original Message-----
>> >Hello, unfortunately, it doesn't help:
>> >
>> >- After the SMS 2003 upgrade, reporting never worked,
not
>> one report. Before
>> >the upgrade, SMS 2.0 reporting was not installed on the
>> site. There is not
>> >one report or dashboard that works, so I can't imagine
>> that this is related
>> >to the 5000+ record problem.
>> >
>> >- IE is configured for using a LAN connection, without
>> any proxy server.
>> >
>> >- We put some domain users in the SMS Reporting Local
>> group of the site
>> >server. When we try to open any report, we get the
Logon
>> Dialog from Windows
>> >Authentication, and after entering the correct
password,
>> we instantly get
>> >the http 500 error instead of the report.
>> >
>> >- The reporting installation log and the Reporting
>> application printscreen
>> >is attached to the message before. SMS 2003 runs on
>> Windows Server 2003,
>> >although http 500 error appears when opening a report
in
>> Internet Explorer
>> >locally or from a Windows XP workstation.
>> >
>> >Thank you in advance for more hints!
>> >Franz
>> >
>> >
>> >"Cathy Moya [MS]" <camoya@online.microsoft.com> schrieb
>> im Newsbeitrag
>> >news:uOrMeSsCEHA.2888@TK2MSFTNGP09.phx.gbl...
>> >> How many records are you going to hit? We have this
in
>> the SMS Tech FAQ
>> >> under reporting:
>> >>
>>
>http://www.microsoft.com/technet/prodtechnol/sms/sms2003/t
>> echfaq/tfaq10.mspx
>> >>
>> >> Q. When my web reports contain a column that
has
>> more than 5000
>> >> records I get an IIS error 500 on my IIS 6.0
reporting
>> point. How do I fix
>> >> this? (Added January 21, 2004)
>> >> A. You might need to adjust the
AspBufferingLimit
>> setting. The
>> >> AspBufferingLimit property sets the maximum size of
the
>> ASP buffer. The
>> >> default is approximately 4 MB. To change the default,
>> open
>> >> %WindowsRoot%\System32\InetSrv\MetaBase.xml and
search
>> for
>> >> "AspBufferingLimit". Adjust the setting to allow for
1
>> MB per 1000
>> >records.
>> >> You can make changes to the MetaBase.xml file while
IIS
>> is running only if
>> >> the edit-while-running feature is enabled. Otherwise,
>> you must stop IIS
>> >> before editing the MetaBase.xml file.
>> >>
>> >> For more information about writing changes to
>> MetaBase.xml, see
>> >> "Configuring the Metabase" in the Server
Administration
>> Guide on Microsoft
>> >> TechNet.
>> >>
>> >> Does that help at all?
>> >>
>> >> --
>> >> Cathy Moya, MCT, MCSE, Security +
>> >> Technical Writer, Enterprise Management Content
>> Group
>> >>
>> >> This posting is provided AS IS with no
warranties
>> and confers no
>> >> rights.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> "Franz Schenk" <franz.schenkNOSPAM@fititNO-_SPAM.ch>
>> wrote in message
>> >> news:OfsJFaCCEHA.1604@TK2MSFTNGP11.phx.gbl...
>> >> > We can't access any reports in our SMS 2003 site:
We
>> always get a http
>> >500
>> >> > error.
>> >> >
>> >> > Thanks in advance for any advice how to
troubleshoot
>> this!
>> >> > Franz
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>> >.
>> >
>
>
>
>