Friday, March 23, 2012
Reporting Services on Windows 2003 Domain Controller FAILING
controllers. I never get past the screen that installs the "Microsoft
SQL Server Reporting Services Setup Support Files". When I click
"Next" the screen dissapears and a event log is created that states:
Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 3/10/2005
Time: 12:30:20 PM
User: N/A
Computer: <<COMPUTERNAME>>
Description:
Faulting application setup.exe, version 0.0.0.0, faulting module
sqlspars.dll, version 2000.80.743.0, fault address 0x00059cf8.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
When I look at the install log, the program dies on the following
function:
<Func Name='PerformDetections'>
0
That is the end of the log. Nothing follows. I am worried that a
GROUP POLICY is preventing me from continuing. Any ideas on what to
check? I have installed the RS on a 2003 test server that was not a
domain controller.
TIA,
Doug CrabtreeNevermind, found the answer:
http://support.microsoft.com/default.aspx?scid=kb;en-us;840219
Didn't seem to relate until we had another problem with authentication on
one of our databases. This solved it on both DCs.
Doug
>I have tried several times to install RS on two of our domain
> controllers. I never get past the screen that installs the "Microsoft
> SQL Server Reporting Services Setup Support Files". When I click
> "Next" the screen dissapears and a event log is created that states:
> Event Type: Error
> Event Source: Application Error
> Event Category: (100)
> Event ID: 1000
> Date: 3/10/2005
> Time: 12:30:20 PM
> User: N/A
> Computer: <<COMPUTERNAME>>
> Description:
> Faulting application setup.exe, version 0.0.0.0, faulting module
> sqlspars.dll, version 2000.80.743.0, fault address 0x00059cf8.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> When I look at the install log, the program dies on the following
> function:
> <Func Name='PerformDetections'>
> 0
> That is the end of the log. Nothing follows. I am worried that a
> GROUP POLICY is preventing me from continuing. Any ideas on what to
> check? I have installed the RS on a 2003 test server that was not a
> domain controller.
> TIA,
> Doug Crabtree
>sql
Tuesday, March 20, 2012
Reporting Services installation question.
I have installed Developer edition Sql Server and Reporting Services 2005 on my Windows XP machine (peer-to-peer network not domain). If I try to access the Report Manager home page (http://localhost:8080/reports), a login dialog appears but my own login is denied access, even though I am a member of the computer administrators group.
If I change the access of the reports virtual directory to permit anonymous access then I can get to the Report manager home page, but of course there is then no site settings tab.
In the Rpting Svcs Configuration, the following are maked completed: Server status, Report Server Virtual Directory, Report Manager Virtual Directory, Windows Service Identity (set to LocalSytem), Web service identity (set to ASPNET account), Database Setup & Initiatialization.
Where did I go wrong?
Hello Bill,
Can you make sure that the Windows Authentication boxes are checked on Default Web Site/Reports/ReportServer within IIS? Also, you'll need to make sure that the DefaultAppPool (or the application pool you are using) is the same account that is listed in your Web Service Identity.
Jarret
|||Thanks for taking the time to answer. Definitely using Windows Authentication. As I am using IIS 5.1, is DefaultAppPool even relevant? I also did some more research on my problem. I can access Report manager home page (with Site settings tab visible!) if I run IE under the built-in administrator account. My account (which as I said is a member of the computer admin group) however gets a HTTP 401.3 error, meaning my account is not on the ACL for this folder (right?) I am however using simple file sharing--so do I have to turn off SFS and institute ACL everywhere?
|||I am experiencing the same issues. On server machine when i login in via Remote Desktop as my domain account, http://localhost/reports/ pulls up the report manager page and i can set security because my domain account has been added to the machines builtin\Administrators group. From the "Home" section i click "properties" then "New Role Assignment" and add my domain user account with all roles. Next on my personal desktop I try to pull up http://<servername>/Reports and the user/pass box comes up. Typing in the user/pass three times pulls up the 403.1 forbidden.
I have created my own apppool called "reportapppool" and it runs under the same account as the asp.net service account used when cofiguring reports services. What am i missing?
Reporting Services installation question.
I have installed Developer edition Sql Server and Reporting Services 2005 on my Windows XP machine (peer-to-peer network not domain). If I try to access the Report Manager home page (http://localhost:8080/reports), a login dialog appears but my own login is denied access, even though I am a member of the computer administrators group.
If I change the access of the reports virtual directory to permit anonymous access then I can get to the Report manager home page, but of course there is then no site settings tab.
In the Rpting Svcs Configuration, the following are maked completed: Server status, Report Server Virtual Directory, Report Manager Virtual Directory, Windows Service Identity (set to LocalSytem), Web service identity (set to ASPNET account), Database Setup & Initiatialization.
Where did I go wrong?
Hello Bill,
Can you make sure that the Windows Authentication boxes are checked on Default Web Site/Reports/ReportServer within IIS? Also, you'll need to make sure that the DefaultAppPool (or the application pool you are using) is the same account that is listed in your Web Service Identity.
Jarret
|||Thanks for taking the time to answer. Definitely using Windows Authentication. As I am using IIS 5.1, is DefaultAppPool even relevant? I also did some more research on my problem. I can access Report manager home page (with Site settings tab visible!) if I run IE under the built-in administrator account. My account (which as I said is a member of the computer admin group) however gets a HTTP 401.3 error, meaning my account is not on the ACL for this folder (right?) I am however using simple file sharing--so do I have to turn off SFS and institute ACL everywhere?
|||I am experiencing the same issues. On server machine when i login in via Remote Desktop as my domain account, http://localhost/reports/ pulls up the report manager page and i can set security because my domain account has been added to the machines builtin\Administrators group. From the "Home" section i click "properties" then "New Role Assignment" and add my domain user account with all roles. Next on my personal desktop I try to pull up http://<servername>/Reports and the user/pass box comes up. Typing in the user/pass three times pulls up the 403.1 forbidden.
I have created my own apppool called "reportapppool" and it runs under the same account as the asp.net service account used when cofiguring reports services. What am i missing?