Tuesday, March 20, 2012
Can't access Report Manager on another computer
Windows XP Pro boxes that are part of the same Windows workgroup. I
need to deploy reports from one box to the other, but I can't see the
Report Manager on the opposing machine, even though I can see it
locally on the respective machine.
I know we're talking beta here, but I need to give a coworker a way to
have access to all our reports on his laptop. Since Reporting
Services for SQL 2000 requires a server, the only way he and I can
have the reports locally on Win XP Pro is via Reporting Services 2005.
Any idea how I can get access to his Report Manager? When I go to
Report Manager on my machine, I go to
"http://MyComputerName/Reports$2005", which works fine. When I'm on
his machine and go to Report Manager, I go to
"http://HisComputerName/Reports$2005" and that works fine. When I try
the same path from my computer, I get a "page not found" error.
I am a local administrator on his machine and have full directory
access (e.g. //ComputerName/C$). I checked the IIS permissions for
his Reports$2005 virtual directory and the Directory Security
authentication method is set to Integrated Windows authentication. I
tried Anonymous access, but that didn't help. Any ideas?I figured it out. Service Pack 2 for Win XP Pro was installed on the
remote machine, so the firewall was preventing me from getting to the
Report Server. I simply disabled the firewall temporarily so I could
deploy my reports. I didn't know how to configure the firewall to
allow me to access the computer, so I found that disabling the
firewall was the best method.
Anyway, that solved my problem.
steve.pantazis@.gmail.com (Steve Pantazis) wrote in message news:<437b6286.0409250937.485cb6ac@.posting.google.com>...
> I have Reporting Services for SQL Server 2005 (beta 2) installed on 2
> Windows XP Pro boxes that are part of the same Windows workgroup. I
> need to deploy reports from one box to the other, but I can't see the
> Report Manager on the opposing machine, even though I can see it
> locally on the respective machine.
> I know we're talking beta here, but I need to give a coworker a way to
> have access to all our reports on his laptop. Since Reporting
> Services for SQL 2000 requires a server, the only way he and I can
> have the reports locally on Win XP Pro is via Reporting Services 2005.
> Any idea how I can get access to his Report Manager? When I go to
> Report Manager on my machine, I go to
> "http://MyComputerName/Reports$2005", which works fine. When I'm on
> his machine and go to Report Manager, I go to
> "http://HisComputerName/Reports$2005" and that works fine. When I try
> the same path from my computer, I get a "page not found" error.
> I am a local administrator on his machine and have full directory
> access (e.g. //ComputerName/C$). I checked the IIS permissions for
> his Reports$2005 virtual directory and the Directory Security
> authentication method is set to Integrated Windows authentication. I
> tried Anonymous access, but that didn't help. Any ideas?sql
Sunday, February 19, 2012
cannot set permission in SQL Server DBE for a database
None of the checked boxes has been accepted. I set up "user or roles" to "public." Then a long list of "permissions" appear with two options: "permit" or "deny." The error message is "Grant Failed for database *****"
Additional Information: "Cannot grant, deny or revoke the connect database permission to roles and application roles." Big surprise!!! The whole form is designed to grant permissions to "roles."
Any ideas?
Thanks.the error message is correct - one can not grant, revoke or deny CONNECT DATABASE to roles or approles, because a role or approle is not a primary principal, i.e. can not connect to a database. Only a user, who is a primary principal can connect to a databse.
Hoewever, the UI should gray out those boxes, otherwise it becomes a usability problem, how you correctly noted above.
cannot set permission in SQL Server DBE for a database
None of the checked boxes has been accepted. I set up "user or roles" to "public." Then a long list of "permissions" appear with two options: "permit" or "deny." The error message is "Grant Failed for database *****"
Additional Information: "Cannot grant, deny or revoke the connect database permission to roles and application roles." Big surprise!!! The whole form is designed to grant permissions to "roles."
Any ideas?
Thanks.the error message is correct - one can not grant, revoke or deny CONNECT DATABASE to roles or approles, because a role or approle is not a primary principal, i.e. can not connect to a database. Only a user, who is a primary principal can connect to a databse.
Hoewever, the UI should gray out those boxes, otherwise it becomes a usability problem, how you correctly noted above.
Thursday, February 16, 2012
Cannot select "Server Database Engine" when installing SQL Server Sep 2005 CTP
check boxes on the Components to Install page of the Microsoft SQL Server Installation Wizard to select component groups for your SQL Server installation, they are all disabled, except "Workstation Components, Development Tools, and SQL Server Books Online".
I tried installing and after it finishes, there are no SQL instances.... What am I doing wrong? Please help. Thank you.
1. What is your operating systems. SQL Server 2005 Enterprise needs server operating systems such as W2K SP4, W2K3 EE SP1, LH Server.
2. What is the instance name you select? If you have already installed SQL Engine with instance name "SQLEngine" and now you restart setup with the same instance name "SQLEngine", then SQL Engine cannot be selected as it is already installed with under the specified instance name. You can only choose other components, which has not been installed under the specified instance name or other shared common components.
Note, "SQLEngine" is a fabricated instance name.
Cannot select "Server Database Engine" when installing SQL Server Sep 2005 CTP
check boxes on the Components to Install page of the Microsoft SQL Server Installation Wizard to select component groups for your SQL Server installation, they are all disabled, except "Workstation Components, Development Tools, and SQL Server Books Online".
I tried installing and after it finishes, there are no SQL instances.... What am I doing wrong? Please help. Thank you.
1. What is your operating systems. SQL Server 2005 Enterprise needs server operating systems such as W2K SP4, W2K3 EE SP1, LH Server.
2. What is the instance name you select? If you have already installed SQL Engine with instance name "SQLEngine" and now you restart setup with the same instance name "SQLEngine", then SQL Engine cannot be selected as it is already installed with under the specified instance name. You can only choose other components, which has not been installed under the specified instance name or other shared common components.
Note, "SQLEngine" is a fabricated instance name.