Can't Find ConfigEdit

I installed the ConfigEdit XML editor mentioned in Kirk Haselden's great Integration Services book. But I can't use it unless I can find it! It's nowhere to be found in the Start menu or BIDS or right-click menus or inside projects. The book assumes you know where to go to open the editor. I'll be the first to eat crow if it's somehwere obvious. ConfigEdit installs to %ProgramFiles%\SSIS\Package Configurations Editor. I wouldn't call that obvious.|||

jaegd wrote:

ConfigEdit installs to %ProgramFiles%\SSIS\Package Configurations Editor. I wouldn't call that obvious.

The setup executable prompted me for the location to save it to... So, yes, it is obvious.

Did you guys run (do you have) SetupConfigEdit.msi dated 12/27/2005?|||

Thanks jaegd, got it!

Phil, the date of my SetupConfigEdit.msi is 12/27/2005, but I don't recall getting a prompt. It's possible I was surrounded by distractions at the time or I may have installed it and didn't have time to try it right away. In any case, it would have been helpful to mention the default location in the book. Oops, I'm supposed to be eating crow...

|||

Sorry folks... :(

What can I say. It wasn't like, my day job or something...

Hopefully, you get some facility from the utility!

K

|||

Kirk, if you wrote merely the best SSIS book out there (IMHO) in your spare time then I'm even more amazed. I'll be one of the first in line (or online) if you ever do a 2nd Edition. That's because I use this book a lot and would always want the latest version--something I can't say for most of the tech manuals on my shelf.

ConfigEdit is just what the doctor ordered when using XML package configurations. Without it I'd be stuck using a text editor right now. Yuk. It would be nice to have such a utility built in to SSIS...

Cant enter user&password for Integration Services

I'm about to start using Integration Services in Mgmt Studio 2005.

But, when I try to register a server for Integration Services,
the option for choosing between Windows authentication and SQL Server
authentication is greyed out, and it's set to Windows.
My domain user is automatically filled in, but greyed out. I can't enter
my password since this field is also greyed out.
Is this some installation problem? (Connection to a Database Engine works fine.)SSIS doesn't support sql auth (at least not from SSMS). there is only windows auth.

SSAS is the same way.|||My next problem is that I can't make my domain account connect
without making it a member of the server's local Administrators group.

I read this article:

http://msdn2.microsoft.com/en-us/library/aa337083.aspx

which describes how to fix this. I gave my users all kind of rights
for the MsDtsServer component and restarted the Integration Services service on the server, but it doesn't help. What can be missing?|||I had to add my user to the Distributed DCOM Users group, and
the Users group had to get full access to the MsDtsServer component.
Now it works.

Can''t deploy "unsafe assembly", permission problem(?)

Hello,

I think I have some kind of permission problem. But first things first:

I have code which I would like to run in SQL Server (CLR Integration). First thing is that my code uses third-party-dll. I have to deploy my code as unsafe because of

"

CREATE ASSEMBLY failed because method "add_FunctionAdd" on type "USP.Express.Pro.FunctionsCollection" in safe assembly "USP.Express.Pro.2.0" has a synchronized attribute. Explicit synchronization is not allowed in safe assemblies.

"

Of course I can not create "asymmetric key" for third-party-dll (Or can I?).

So, I tried to use trustworthy DB. But I get all the time error Msg 10327: "Assembly is not authorised for PERMISSION_SET=UNSAFE"

I am using Windows Login to log on Sql Server. Login is granted "Unsafe assembly" and DB has trustworthy setting "on".

Login has server roles "sysadmin" and "securityadmin".

Login is mapped with DB User who has same name ( DOMAIN\UserName ) and has default schema "dbo".

Login has DB memberships "db_owner" and "db_securityadmin".

DB user owns schemas "db_owner" and "db_securityadmin".

Am I missing something?

Interesting thing is that I can do deployment (as unsafe assembly) in master-database. But not in the other databases.

Questions are:

- Is there other way to authorise third-party-dll than using trustworthy?

- Why deployment can be done in master-database?

And finally:

- Why deployment can not be done in other database?

So when you are deploying an assembly with the UNSAFE permission set (or EXTERNAL_ACCESS) and are using the TRUSTWORTHY settings (i.e. not assymetric keys etc), the login of the owner of the database has to have the relevant permissions. In your case UNSAFE ASSEMBLY.

Niels
|||

Hello Niels,

" login of the owner of the database has to have the relevant permissions. In your case UNSAFE ASSEMBLY."

As far as I know, permission _should_ be OK.

I checked following:

1. database -> properties (the database I want unsafe assembly to be created): owner is <DOMAIN\username>.

2. corresponding database user -> properties: Login name is same.

I have done "Grant UNSAFE ASSEMBLY to <DOMAIN\username>;" and "ALTER DATABASE <database> SET trustworthy on". Both are executed without errors.

<DOMAIN\username> is the Login name of owner of <database> and <database> is the db I want my assembly to be created.

Is there something still missing?

What I should check next?

- Jorma

|||Hmm, what is the exact error message you are getting? Is this database a new database, or is it restored from (perhaps) SQL 2000? What happens if you were to create a new database (with DOMAIN\username as owner), setting the database to TRUSTWORTHY and deply the assembly?

Niels
|||

Hello again,

Error message is:

Msg 10327, Level 14, State 1, Line 1

CREATE ASSEMBLY for assembly 'MillCC' failed because assembly 'USP.Express.Pro.2.0' is not authorized for PERMISSION_SET = UNSAFE.

"USP.Express.Pro.2.0" is the third-party-dll my code is using. Previously message were same but assembly named in the message was my code... Interesting.

I created new database as you suggested. And assembly was created without errors. Why in the world I didn't try this before... So, problem is somehow related with the database I am using.

The database is restored from SQL Server 2005 Express Edition.

Is there something I should know when using restored database and CLR?

|||Ah, it is restored. Try this for me please:
1. Run ALTER AUTHORIZATION against the database and change it to [Domain\username] (I know that you said that was the owner, but do it once again, please.
2. Run ALTER DATABASE and reset TRUSTWORTHY to on
3. Try and deploy

Niels
|||

I tried

Alter authorization on DATABASE::<database> to <[DOMAIN\username]>

but there came out following error:

Msg 15110, Level 16, State 1, Line 1

The proposed new database owner is already a user or aliased in the database.

Should I remove something before running ALTER AUTHORIZATION? I am quite confused about the permissions at this stage |||OK, drop the user in the database, which is the user for the login [Domain\username], then run the ALTER AUTHORIZATION again.

Alternatively, you can create a SQL login (just a login) and make that login the owner of the database and assign the login the necessary permissions.

Niels
|||

OK,

first I tried to drop my user but there came out errors because user owns schemas etc.

I was impatient to test this, so I created new login and made login owner of the database. After givin permissions to the login I was able to create assembly.

In other words, now it is working! Thank you very much Niels!

Can you explain to me what was wrong with the "original" owner? I quess there happens "something" when database is restored...

Can''t deploy "unsafe assembly", permission problem(?)

Hello,

I think I have some kind of permission problem. But first things first:

I have code which I would like to run in SQL Server (CLR Integration). First thing is that my code uses third-party-dll. I have to deploy my code as unsafe because of

"

CREATE ASSEMBLY failed because method "add_FunctionAdd" on type "USP.Express.Pro.FunctionsCollection" in safe assembly "USP.Express.Pro.2.0" has a synchronized attribute. Explicit synchronization is not allowed in safe assemblies.

"

Of course I can not create "asymmetric key" for third-party-dll (Or can I?).

So, I tried to use trustworthy DB. But I get all the time error Msg 10327: "Assembly is not authorised for PERMISSION_SET=UNSAFE"

I am using Windows Login to log on Sql Server. Login is granted "Unsafe assembly" and DB has trustworthy setting "on".

Login has server roles "sysadmin" and "securityadmin".

Login is mapped with DB User who has same name ( DOMAIN\UserName ) and has default schema "dbo".

Login has DB memberships "db_owner" and "db_securityadmin".

DB user owns schemas "db_owner" and "db_securityadmin".

Am I missing something?

Interesting thing is that I can do deployment (as unsafe assembly) in master-database. But not in the other databases.

Questions are:

- Is there other way to authorise third-party-dll than using trustworthy?

- Why deployment can be done in master-database?

And finally:

- Why deployment can not be done in other database?

So when you are deploying an assembly with the UNSAFE permission set (or EXTERNAL_ACCESS) and are using the TRUSTWORTHY settings (i.e. not assymetric keys etc), the login of the owner of the database has to have the relevant permissions. In your case UNSAFE ASSEMBLY.

Niels
|||

Hello Niels,

" login of the owner of the database has to have the relevant permissions. In your case UNSAFE ASSEMBLY."

As far as I know, permission _should_ be OK.

I checked following:

1. database -> properties (the database I want unsafe assembly to be created): owner is <DOMAIN\username>.

2. corresponding database user -> properties: Login name is same.

I have done "Grant UNSAFE ASSEMBLY to <DOMAIN\username>;" and "ALTER DATABASE <database> SET trustworthy on". Both are executed without errors.

<DOMAIN\username> is the Login name of owner of <database> and <database> is the db I want my assembly to be created.

Is there something still missing?

What I should check next?

- Jorma

|||Hmm, what is the exact error message you are getting? Is this database a new database, or is it restored from (perhaps) SQL 2000? What happens if you were to create a new database (with DOMAIN\username as owner), setting the database to TRUSTWORTHY and deply the assembly?

Niels
|||

Hello again,

Error message is:

Msg 10327, Level 14, State 1, Line 1

CREATE ASSEMBLY for assembly 'MillCC' failed because assembly 'USP.Express.Pro.2.0' is not authorized for PERMISSION_SET = UNSAFE.

"USP.Express.Pro.2.0" is the third-party-dll my code is using. Previously message were same but assembly named in the message was my code... Interesting.

I created new database as you suggested. And assembly was created without errors. Why in the world I didn't try this before... So, problem is somehow related with the database I am using.

The database is restored from SQL Server 2005 Express Edition.

Is there something I should know when using restored database and CLR?

|||Ah, it is restored. Try this for me please:
1. Run ALTER AUTHORIZATION against the database and change it to [Domain\username] (I know that you said that was the owner, but do it once again, please.
2. Run ALTER DATABASE and reset TRUSTWORTHY to on
3. Try and deploy

Niels
|||

I tried

Alter authorization on DATABASE::<database> to <[DOMAIN\username]>

but there came out following error:

Msg 15110, Level 16, State 1, Line 1

The proposed new database owner is already a user or aliased in the database.

Should I remove something before running ALTER AUTHORIZATION? I am quite confused about the permissions at this stage |||OK, drop the user in the database, which is the user for the login [Domain\username], then run the ALTER AUTHORIZATION again.

Alternatively, you can create a SQL login (just a login) and make that login the owner of the database and assign the login the necessary permissions.

Niels
|||

OK,

first I tried to drop my user but there came out errors because user owns schemas etc.

I was impatient to test this, so I created new login and made login owner of the database. After givin permissions to the login I was able to create assembly.

In other words, now it is working! Thank you very much Niels!

Can you explain to me what was wrong with the "original" owner? I quess there happens "something" when database is restored...

Can't connect to Report Server via Management Studio

Hi,

I have a local installation of SQL Server 2005 (Developer Edition) on XP Professional SP2, with Reporting Services, Integration Services, and Analysis Server installed.

I can connect to Integration Services and Analysis Server via the SQL Server Management Studio, but not to the Report Server. I can access and use the Report Server installation via http://localhost/Reports and http://localhost/ReportServer, and everything checks out on the Reporting Services Configuration tool, so the server appears to be working fine.

I've uninstalled/re-formatted/reinstalled the services (with all default options, and services running as "Local Service"), but always end up with the following error when connecting to Report Server via Management Studio:

The request failed with HTTP status 503: Service Unavailable. (Microsoft.SqlServer.Management.UI.RSClient)

Program Location:
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at Microsoft.SqlServer.Management.UI.RSClient.RSClientConnection.CreateConnection(String connectionString)
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.CreateConnectionObject()
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
Any hints would be appreciated...

Thanks,
/vijayan

There are two server addresses you can use in the SSMS connection dialog:

http://servername/reportserver

or

servername/instance

The second uses WMI to enumerate the instance so you either need to be an administrator or in the DCOM users group on the server machine.|||Thanks for your reply; I tried the 'http://' address, and that fails with exactly the same error. Also, I am an administrator.

Indeed, I can't connect to RS installations on other servers either, while other users are able to. They also connect successfully to my RS instance via SSMS... so it appears to be something completely on my client that I need to fix.

Run out of ideas to try...

/v|||This is a bit of a stretch, but you can try www.sysinternals.com filemon utility and look for access denied or buffer overflow messages when connecting. If you can narrow it down to a file permissions problem it may be easier to troubleshoot.
Also try using your machine name or IP address to connect rather than localhost.|||

You don't have any other version of the .NET Framework on the client machine, do you? Maybe uninstalling the SQL tools and the .NET framework and the reinstalling might help. I've never seen this before.

|||

Vijayan

Did you manage to solve this problem? I am getting the same error message (HTTP Status 503) when connecting to Report Server from Management Studio. Any advice would be appreciated.

Thanks

Brad

|||Vijayan -

I am also having the same problem. and I have no idea on how to trouble shoot it? Can you let us know if you made any progress on the resolution of the issue?

Jim|||

I am also having the same problem. Tried everything, no solution yet. My server is having two SQL Server instances SQL 2000 and 2005, will this be a problem. It doesn't connect to IIS.

Roshan.

|||

Can you open IIS manager in MMC and tell me what the settings are for the reportserver virtual directory?

I firstly, can you provide the directory to which the reportserver virtual directory is pointing

Secondly, what are the script mappings for the virtual directory? You can get to this from the properties page for the V-dir and then clicking the 'configuration' button.

Lastly, if there is an ASP.Net tab, what is the value set to?

If there isn't a reportserer virtual directory, is there one called reportserver$InstanceName?

If there is no virtual directory starting with report server, can you open the reporting services configuration tool from the start menu and create one on the report server virtual directory tab?

Thanks!

-Lukasz

|||

Hi Lukasz,

Following are the information requested.

ReportServer virtual directory is pointing to :

C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer

Mappings:

Application extensions: There are no entries

Wildcard application maps:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll

Options:

Enable session state : Ticked

Enable buffering : Ticked

Default ASP Language : VBScript

There is no ASP.Net tab.

Best Regards,

Roshan.

|||

Do you know if you installed .Net Framework v2 before you had IIS installed? If you did or if the following registry key is not present, you'll need to register ASP.NET.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\2.0.50727.0

If it does not exist, run the command:

aspnet_regiis.exe -i

from the folder:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\

You may want to run it regardless just to ensure ASP.NET is registered correctly on your computer. Note this does have consequences for encryption keys for the ASP.NET account (and consequently the RS 2000). Before running the command back up your symmetric key for the RS2K server using:

rskeymgmt.exe

-Lukasz

|||

Hi Lukas,

Thanks for the reply.

I tried with registering ASP.NET again, but still it's not connecting to Report Server using SQL Mgmt Studio. Also it's not connecting to Report Manager using Internet explorer too. I have created a report server project and deployed a sample report to IIS, it's working and I can view it from the browser.

Thanks,

Roshan.

|||

So if you open the report server virtual directory in IE you can browse the report server namespace and execute the report, but if you try to view the report using report manager, it doesn't work?

That is really unusual.

When you say you deploy the report to IIS - did you use the Deploy feature of Report Designer?

-Lukasz

|||Has anyone found an answer to this issue? I am having the same problem.|||

Can you provide more info on exactly how you reproduce the problem?

Can you provide answers to my post above?

-Lukasz

Can't connect to Report Server via Management Studio

Hi,

I have a local installation of SQL Server 2005 (Developer Edition) on XP Professional SP2, with Reporting Services, Integration Services, and Analysis Server installed.

I can connect to Integration Services and Analysis Server via the SQL Server Management Studio, but not to the Report Server. I can access and use the Report Server installation via http://localhost/Reports and http://localhost/ReportServer, and everything checks out on the Reporting Services Configuration tool, so the server appears to be working fine.

I've uninstalled/re-formatted/reinstalled the services (with all default options, and services running as "Local Service"), but always end up with the following error when connecting to Report Server via Management Studio:

The request failed with HTTP status 503: Service Unavailable. (Microsoft.SqlServer.Management.UI.RSClient)

Program Location:
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at Microsoft.SqlServer.Management.UI.RSClient.RSClientConnection.CreateConnection(String connectionString)
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.CreateConnectionObject()
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
Any hints would be appreciated...

Thanks,
/vijayan

There are two server addresses you can use in the SSMS connection dialog:

http://servername/reportserver

or

servername/instance

The second uses WMI to enumerate the instance so you either need to be an administrator or in the DCOM users group on the server machine.|||Thanks for your reply; I tried the 'http://' address, and that fails with exactly the same error. Also, I am an administrator.

Indeed, I can't connect to RS installations on other servers either, while other users are able to. They also connect successfully to my RS instance via SSMS... so it appears to be something completely on my client that I need to fix.

Run out of ideas to try...

/v|||This is a bit of a stretch, but you can try www.sysinternals.com filemon utility and look for access denied or buffer overflow messages when connecting. If you can narrow it down to a file permissions problem it may be easier to troubleshoot.
Also try using your machine name or IP address to connect rather than localhost.|||

You don't have any other version of the .NET Framework on the client machine, do you? Maybe uninstalling the SQL tools and the .NET framework and the reinstalling might help. I've never seen this before.

|||

Vijayan

Did you manage to solve this problem? I am getting the same error message (HTTP Status 503) when connecting to Report Server from Management Studio. Any advice would be appreciated.

Thanks

Brad

|||Vijayan -

I am also having the same problem. and I have no idea on how to trouble shoot it? Can you let us know if you made any progress on the resolution of the issue?

Jim|||

I am also having the same problem. Tried everything, no solution yet. My server is having two SQL Server instances SQL 2000 and 2005, will this be a problem. It doesn't connect to IIS.

Roshan.

|||

Can you open IIS manager in MMC and tell me what the settings are for the reportserver virtual directory?

I firstly, can you provide the directory to which the reportserver virtual directory is pointing

Secondly, what are the script mappings for the virtual directory? You can get to this from the properties page for the V-dir and then clicking the 'configuration' button.

Lastly, if there is an ASP.Net tab, what is the value set to?

If there isn't a reportserer virtual directory, is there one called reportserver$InstanceName?

If there is no virtual directory starting with report server, can you open the reporting services configuration tool from the start menu and create one on the report server virtual directory tab?

Thanks!

-Lukasz

|||

Hi Lukasz,

Following are the information requested.

ReportServer virtual directory is pointing to :

C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer

Mappings:

Application extensions: There are no entries

Wildcard application maps:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll

Options:

Enable session state : Ticked

Enable buffering : Ticked

Default ASP Language : VBScript

There is no ASP.Net tab.

Best Regards,

Roshan.

|||

Do you know if you installed .Net Framework v2 before you had IIS installed? If you did or if the following registry key is not present, you'll need to register ASP.NET.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\2.0.50727.0

If it does not exist, run the command:

aspnet_regiis.exe -i

from the folder:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\

You may want to run it regardless just to ensure ASP.NET is registered correctly on your computer. Note this does have consequences for encryption keys for the ASP.NET account (and consequently the RS 2000). Before running the command back up your symmetric key for the RS2K server using:

rskeymgmt.exe

-Lukasz

|||

Hi Lukas,

Thanks for the reply.

I tried with registering ASP.NET again, but still it's not connecting to Report Server using SQL Mgmt Studio. Also it's not connecting to Report Manager using Internet explorer too. I have created a report server project and deployed a sample report to IIS, it's working and I can view it from the browser.

Thanks,

Roshan.

|||

So if you open the report server virtual directory in IE you can browse the report server namespace and execute the report, but if you try to view the report using report manager, it doesn't work?

That is really unusual.

When you say you deploy the report to IIS - did you use the Deploy feature of Report Designer?

-Lukasz

|||Has anyone found an answer to this issue? I am having the same problem.|||

Can you provide more info on exactly how you reproduce the problem?

Can you provide answers to my post above?

-Lukasz

Can't connect to Report Server via Management Studio

Hi,

I have a local installation of SQL Server 2005 (Developer Edition) on XP Professional SP2, with Reporting Services, Integration Services, and Analysis Server installed.

I can connect to Integration Services and Analysis Server via the SQL Server Management Studio, but not to the Report Server. I can access and use the Report Server installation via http://localhost/Reports and http://localhost/ReportServer, and everything checks out on the Reporting Services Configuration tool, so the server appears to be working fine.

I've uninstalled/re-formatted/reinstalled the services (with all default options, and services running as "Local Service"), but always end up with the following error when connecting to Report Server via Management Studio:

The request failed with HTTP status 503: Service Unavailable. (Microsoft.SqlServer.Management.UI.RSClient)

Program Location:
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at Microsoft.SqlServer.Management.UI.RSClient.RSClientConnection.CreateConnection(String connectionString)
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.CreateConnectionObject()
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
Any hints would be appreciated...

Thanks,
/vijayan

There are two server addresses you can use in the SSMS connection dialog:

http://servername/reportserver

or

servername/instance

The second uses WMI to enumerate the instance so you either need to be an administrator or in the DCOM users group on the server machine.|||Thanks for your reply; I tried the 'http://' address, and that fails with exactly the same error. Also, I am an administrator.

Indeed, I can't connect to RS installations on other servers either, while other users are able to. They also connect successfully to my RS instance via SSMS... so it appears to be something completely on my client that I need to fix.

Run out of ideas to try...

/v|||This is a bit of a stretch, but you can try www.sysinternals.com filemon utility and look for access denied or buffer overflow messages when connecting. If you can narrow it down to a file permissions problem it may be easier to troubleshoot.
Also try using your machine name or IP address to connect rather than localhost.

|||

You don't have any other version of the .NET Framework on the client machine, do you? Maybe uninstalling the SQL tools and the .NET framework and the reinstalling might help. I've never seen this before.

|||

Vijayan

Did you manage to solve this problem? I am getting the same error message (HTTP Status 503) when connecting to Report Server from Management Studio. Any advice would be appreciated.

Thanks

Brad

|||Vijayan -

I am also having the same problem. and I have no idea on how to trouble shoot it? Can you let us know if you made any progress on the resolution of the issue?

Jim|||

I am also having the same problem. Tried everything, no solution yet. My server is having two SQL Server instances SQL 2000 and 2005, will this be a problem. It doesn't connect to IIS.

Roshan.

|||

Can you open IIS manager in MMC and tell me what the settings are for the reportserver virtual directory?

I firstly, can you provide the directory to which the reportserver virtual directory is pointing

Secondly, what are the script mappings for the virtual directory? You can get to this from the properties page for the V-dir and then clicking the 'configuration' button.

Lastly, if there is an ASP.Net tab, what is the value set to?

If there isn't a reportserer virtual directory, is there one called reportserver$InstanceName?

If there is no virtual directory starting with report server, can you open the reporting services configuration tool from the start menu and create one on the report server virtual directory tab?

Thanks!

-Lukasz

|||

Hi Lukasz,

Following are the information requested.

ReportServer virtual directory is pointing to :

C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer

Mappings:

Application extensions: There are no entries

Wildcard application maps:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll

Options:

Enable session state : Ticked

Enable buffering : Ticked

Default ASP Language : VBScript

There is no ASP.Net tab.

Best Regards,

Roshan.

|||

Do you know if you installed .Net Framework v2 before you had IIS installed? If you did or if the following registry key is not present, you'll need to register ASP.NET.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\2.0.50727.0

If it does not exist, run the command:

aspnet_regiis.exe -i

from the folder:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\

You may want to run it regardless just to ensure ASP.NET is registered correctly on your computer. Note this does have consequences for encryption keys for the ASP.NET account (and consequently the RS 2000). Before running the command back up your symmetric key for the RS2K server using:

rskeymgmt.exe

-Lukasz

|||

Hi Lukas,

Thanks for the reply.

I tried with registering ASP.NET again, but still it's not connecting to Report Server using SQL Mgmt Studio. Also it's not connecting to Report Manager using Internet explorer too. I have created a report server project and deployed a sample report to IIS, it's working and I can view it from the browser.

Thanks,

Roshan.

|||

So if you open the report server virtual directory in IE you can browse the report server namespace and execute the report, but if you try to view the report using report manager, it doesn't work?

That is really unusual.

When you say you deploy the report to IIS - did you use the Deploy feature of Report Designer?

-Lukasz

|||Has anyone found an answer to this issue? I am having the same problem.|||

Can you provide more info on exactly how you reproduce the problem?

Can you provide answers to my post above?

-Lukasz

Can't connect to Report Server via Management Studio

Hi,

I have a local installation of SQL Server 2005 (Developer Edition) on XP Professional SP2, with Reporting Services, Integration Services, and Analysis Server installed.

I can connect to Integration Services and Analysis Server via the SQL Server Management Studio, but not to the Report Server. I can access and use the Report Server installation via http://localhost/Reports and http://localhost/ReportServer, and everything checks out on the Reporting Services Configuration tool, so the server appears to be working fine.

I've uninstalled/re-formatted/reinstalled the services (with all default options, and services running as "Local Service"), but always end up with the following error when connecting to Report Server via Management Studio:

The request failed with HTTP status 503: Service Unavailable. (Microsoft.SqlServer.Management.UI.RSClient)

Program Location:
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at Microsoft.SqlServer.Management.UI.RSClient.RSClientConnection.CreateConnection(String connectionString)
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.CreateConnectionObject()
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
Any hints would be appreciated...

Thanks,
/vijayan

There are two server addresses you can use in the SSMS connection dialog:

http://servername/reportserver

or

servername/instance

The second uses WMI to enumerate the instance so you either need to be an administrator or in the DCOM users group on the server machine.|||Thanks for your reply; I tried the 'http://' address, and that fails with exactly the same error. Also, I am an administrator.

Indeed, I can't connect to RS installations on other servers either, while other users are able to. They also connect successfully to my RS instance via SSMS... so it appears to be something completely on my client that I need to fix.

Run out of ideas to try...

/v|||This is a bit of a stretch, but you can try www.sysinternals.com filemon utility and look for access denied or buffer overflow messages when connecting. If you can narrow it down to a file permissions problem it may be easier to troubleshoot.
Also try using your machine name or IP address to connect rather than localhost.

|||

You don't have any other version of the .NET Framework on the client machine, do you? Maybe uninstalling the SQL tools and the .NET framework and the reinstalling might help. I've never seen this before.

|||

Vijayan

Did you manage to solve this problem? I am getting the same error message (HTTP Status 503) when connecting to Report Server from Management Studio. Any advice would be appreciated.

Thanks

Brad

|||Vijayan -

I am also having the same problem. and I have no idea on how to trouble shoot it? Can you let us know if you made any progress on the resolution of the issue?

Jim|||

I am also having the same problem. Tried everything, no solution yet. My server is having two SQL Server instances SQL 2000 and 2005, will this be a problem. It doesn't connect to IIS.

Roshan.

|||

Can you open IIS manager in MMC and tell me what the settings are for the reportserver virtual directory?

I firstly, can you provide the directory to which the reportserver virtual directory is pointing

Secondly, what are the script mappings for the virtual directory? You can get to this from the properties page for the V-dir and then clicking the 'configuration' button.

Lastly, if there is an ASP.Net tab, what is the value set to?

If there isn't a reportserer virtual directory, is there one called reportserver$InstanceName?

If there is no virtual directory starting with report server, can you open the reporting services configuration tool from the start menu and create one on the report server virtual directory tab?

Thanks!

-Lukasz

|||

Hi Lukasz,

Following are the information requested.

ReportServer virtual directory is pointing to :

C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer

Mappings:

Application extensions: There are no entries

Wildcard application maps:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll

Options:

Enable session state : Ticked

Enable buffering : Ticked

Default ASP Language : VBScript

There is no ASP.Net tab.

Best Regards,

Roshan.

|||

Do you know if you installed .Net Framework v2 before you had IIS installed? If you did or if the following registry key is not present, you'll need to register ASP.NET.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\2.0.50727.0

If it does not exist, run the command:

aspnet_regiis.exe -i

from the folder:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\

You may want to run it regardless just to ensure ASP.NET is registered correctly on your computer. Note this does have consequences for encryption keys for the ASP.NET account (and consequently the RS 2000). Before running the command back up your symmetric key for the RS2K server using:

rskeymgmt.exe

-Lukasz

|||

Hi Lukas,

Thanks for the reply.

I tried with registering ASP.NET again, but still it's not connecting to Report Server using SQL Mgmt Studio. Also it's not connecting to Report Manager using Internet explorer too. I have created a report server project and deployed a sample report to IIS, it's working and I can view it from the browser.

Thanks,

Roshan.

|||

So if you open the report server virtual directory in IE you can browse the report server namespace and execute the report, but if you try to view the report using report manager, it doesn't work?

That is really unusual.

When you say you deploy the report to IIS - did you use the Deploy feature of Report Designer?

-Lukasz

|||Has anyone found an answer to this issue? I am having the same problem.|||

Can you provide more info on exactly how you reproduce the problem?

Can you provide answers to my post above?

-Lukasz

Can't connect to Report Server via Management Studio

Hi,

I have a local installation of SQL Server 2005 (Developer Edition) on XP Professional SP2, with Reporting Services, Integration Services, and Analysis Server installed.

I can connect to Integration Services and Analysis Server via the SQL Server Management Studio, but not to the Report Server. I can access and use the Report Server installation via http://localhost/Reports and http://localhost/ReportServer, and everything checks out on the Reporting Services Configuration tool, so the server appears to be working fine.

I've uninstalled/re-formatted/reinstalled the services (with all default options, and services running as "Local Service"), but always end up with the following error when connecting to Report Server via Management Studio:

The request failed with HTTP status 503: Service Unavailable. (Microsoft.SqlServer.Management.UI.RSClient)

Program Location:
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at Microsoft.SqlServer.Management.UI.RSClient.RSClientConnection.CreateConnection(String connectionString)
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.CreateConnectionObject()
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
Any hints would be appreciated...

Thanks,
/vijayan

There are two server addresses you can use in the SSMS connection dialog:

http://servername/reportserver

or

servername/instance

The second uses WMI to enumerate the instance so you either need to be an administrator or in the DCOM users group on the server machine.|||Thanks for your reply; I tried the 'http://' address, and that fails with exactly the same error. Also, I am an administrator.

Indeed, I can't connect to RS installations on other servers either, while other users are able to. They also connect successfully to my RS instance via SSMS... so it appears to be something completely on my client that I need to fix.

Run out of ideas to try...

/v|||This is a bit of a stretch, but you can try www.sysinternals.com filemon utility and look for access denied or buffer overflow messages when connecting. If you can narrow it down to a file permissions problem it may be easier to troubleshoot.
Also try using your machine name or IP address to connect rather than localhost.

|||

You don't have any other version of the .NET Framework on the client machine, do you? Maybe uninstalling the SQL tools and the .NET framework and the reinstalling might help. I've never seen this before.

|||

Vijayan

Did you manage to solve this problem? I am getting the same error message (HTTP Status 503) when connecting to Report Server from Management Studio. Any advice would be appreciated.

Thanks

Brad

|||Vijayan -

I am also having the same problem. and I have no idea on how to trouble shoot it? Can you let us know if you made any progress on the resolution of the issue?

Jim|||

I am also having the same problem. Tried everything, no solution yet. My server is having two SQL Server instances SQL 2000 and 2005, will this be a problem. It doesn't connect to IIS.

Roshan.

|||

Can you open IIS manager in MMC and tell me what the settings are for the reportserver virtual directory?

I firstly, can you provide the directory to which the reportserver virtual directory is pointing

Secondly, what are the script mappings for the virtual directory? You can get to this from the properties page for the V-dir and then clicking the 'configuration' button.

Lastly, if there is an ASP.Net tab, what is the value set to?

If there isn't a reportserer virtual directory, is there one called reportserver$InstanceName?

If there is no virtual directory starting with report server, can you open the reporting services configuration tool from the start menu and create one on the report server virtual directory tab?

Thanks!

-Lukasz

|||

Hi Lukasz,

Following are the information requested.

ReportServer virtual directory is pointing to :

C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer

Mappings:

Application extensions: There are no entries

Wildcard application maps:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll

Options:

Enable session state : Ticked

Enable buffering : Ticked

Default ASP Language : VBScript

There is no ASP.Net tab.

Best Regards,

Roshan.

|||

Do you know if you installed .Net Framework v2 before you had IIS installed? If you did or if the following registry key is not present, you'll need to register ASP.NET.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\2.0.50727.0

If it does not exist, run the command:

aspnet_regiis.exe -i

from the folder:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\

You may want to run it regardless just to ensure ASP.NET is registered correctly on your computer. Note this does have consequences for encryption keys for the ASP.NET account (and consequently the RS 2000). Before running the command back up your symmetric key for the RS2K server using:

rskeymgmt.exe

-Lukasz

|||

Hi Lukas,

Thanks for the reply.

I tried with registering ASP.NET again, but still it's not connecting to Report Server using SQL Mgmt Studio. Also it's not connecting to Report Manager using Internet explorer too. I have created a report server project and deployed a sample report to IIS, it's working and I can view it from the browser.

Thanks,

Roshan.

|||

So if you open the report server virtual directory in IE you can browse the report server namespace and execute the report, but if you try to view the report using report manager, it doesn't work?

That is really unusual.

When you say you deploy the report to IIS - did you use the Deploy feature of Report Designer?

-Lukasz

|||Has anyone found an answer to this issue? I am having the same problem.|||

Can you provide more info on exactly how you reproduce the problem?

Can you provide answers to my post above?

-Lukasz

Can't connect to Report Server via Management Studio

Hi,

I have a local installation of SQL Server 2005 (Developer Edition) on XP Professional SP2, with Reporting Services, Integration Services, and Analysis Server installed.

I can connect to Integration Services and Analysis Server via the SQL Server Management Studio, but not to the Report Server. I can access and use the Report Server installation via http://localhost/Reports and http://localhost/ReportServer, and everything checks out on the Reporting Services Configuration tool, so the server appears to be working fine.

I've uninstalled/re-formatted/reinstalled the services (with all default options, and services running as "Local Service"), but always end up with the following error when connecting to Report Server via Management Studio:

The request failed with HTTP status 503: Service Unavailable. (Microsoft.SqlServer.Management.UI.RSClient)

Program Location:
at Microsoft.SqlServer.ReportingServices2005.RSConnection.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.RSConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.RSConnection.ValidateConnection()
at Microsoft.SqlServer.Management.UI.RSClient.RSClientConnection.CreateConnection(String connectionString)
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.CreateConnectionObject()
at Microsoft.SqlServer.Management.UI.RSClient.RSConnectionInfo.RSTypeImpl.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.RSType.GetConnectionObject(UIConnectionInfo ci)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
Any hints would be appreciated...

Thanks,
/vijayan

There are two server addresses you can use in the SSMS connection dialog:

http://servername/reportserver

or

servername/instance

The second uses WMI to enumerate the instance so you either need to be an administrator or in the DCOM users group on the server machine.|||Thanks for your reply; I tried the 'http://' address, and that fails with exactly the same error. Also, I am an administrator.

Indeed, I can't connect to RS installations on other servers either, while other users are able to. They also connect successfully to my RS instance via SSMS... so it appears to be something completely on my client that I need to fix.

Run out of ideas to try...

/v|||This is a bit of a stretch, but you can try www.sysinternals.com filemon utility and look for access denied or buffer overflow messages when connecting. If you can narrow it down to a file permissions problem it may be easier to troubleshoot.
Also try using your machine name or IP address to connect rather than localhost.|||

You don't have any other version of the .NET Framework on the client machine, do you? Maybe uninstalling the SQL tools and the .NET framework and the reinstalling might help. I've never seen this before.

|||

Vijayan

Did you manage to solve this problem? I am getting the same error message (HTTP Status 503) when connecting to Report Server from Management Studio. Any advice would be appreciated.

Thanks

Brad

|||Vijayan -

I am also having the same problem. and I have no idea on how to trouble shoot it? Can you let us know if you made any progress on the resolution of the issue?

Jim|||

I am also having the same problem. Tried everything, no solution yet. My server is having two SQL Server instances SQL 2000 and 2005, will this be a problem. It doesn't connect to IIS.

Roshan.

|||

Can you open IIS manager in MMC and tell me what the settings are for the reportserver virtual directory?

I firstly, can you provide the directory to which the reportserver virtual directory is pointing

Secondly, what are the script mappings for the virtual directory? You can get to this from the properties page for the V-dir and then clicking the 'configuration' button.

Lastly, if there is an ASP.Net tab, what is the value set to?

If there isn't a reportserer virtual directory, is there one called reportserver$InstanceName?

If there is no virtual directory starting with report server, can you open the reporting services configuration tool from the start menu and create one on the report server virtual directory tab?

Thanks!

-Lukasz

|||

Hi Lukasz,

Following are the information requested.

ReportServer virtual directory is pointing to :

C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer

Mappings:

Application extensions: There are no entries

Wildcard application maps:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll

Options:

Enable session state : Ticked

Enable buffering : Ticked

Default ASP Language : VBScript

There is no ASP.Net tab.

Best Regards,

Roshan.

|||

Do you know if you installed .Net Framework v2 before you had IIS installed? If you did or if the following registry key is not present, you'll need to register ASP.NET.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\2.0.50727.0

If it does not exist, run the command:

aspnet_regiis.exe -i

from the folder:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\

You may want to run it regardless just to ensure ASP.NET is registered correctly on your computer. Note this does have consequences for encryption keys for the ASP.NET account (and consequently the RS 2000). Before running the command back up your symmetric key for the RS2K server using:

rskeymgmt.exe

-Lukasz

|||

Hi Lukas,

Thanks for the reply.

I tried with registering ASP.NET again, but still it's not connecting to Report Server using SQL Mgmt Studio. Also it's not connecting to Report Manager using Internet explorer too. I have created a report server project and deployed a sample report to IIS, it's working and I can view it from the browser.

Thanks,

Roshan.

|||

So if you open the report server virtual directory in IE you can browse the report server namespace and execute the report, but if you try to view the report using report manager, it doesn't work?

That is really unusual.

When you say you deploy the report to IIS - did you use the Deploy feature of Report Designer?

-Lukasz

|||Has anyone found an answer to this issue? I am having the same problem.|||

Can you provide more info on exactly how you reproduce the problem?

Can you provide answers to my post above?

-Lukasz