We are migrating to SQL Server 2005 (and also RS shipped with SQL 2005) but
in the middle of the process we have still some servers still not upgraded
(and running SQL Server 2000 and RS2000).
Can we deploy reports to RS servers running SQL Server 2000 using Visual
Studio 2005? It seems we cannot becasue we receive the following error
message. Is any workaround to this or do we need to mantain a copy of both
RS2000 and RS2005 rdl files and deploy each group of them using VS2003 and
VS2005 respectively? This is somewhat repeat the same job twice, and might
lead to mistakes and differences between the same file of each version.
The error messages are in spanish but an approximated translation is
provided (It probably does not match the real error message in native
english).
Thanks a lot.
===================================
No se pudo establecer una conexión al servidor de informes
https://www.mydomain.com/ReportServer. (Diseñador de informes de Microsoft)
A connection to reports server at https://www.mydomain.com/ReportServer
could not be stablished (Microsoft Form Designer)
===================================
Error al intentar conectar con el servidor de informes. Compruebe la
información de conexión y que la versión del servidor de informes sea
compatible. (Microsoft.ReportingServices.Designer)
An error occurred while trying to connect to reports server. Check the
connection information and reports server version be compatable
(Microsoft.ReportingServices.Designer)
--
Ubicación del programa:
en
Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException.ThrowIfEndpointMissing(WebException
e)
en
Microsoft.SqlServer.ReportingServices2005.RSConnection.GetItemType(String
Item)
en
Microsoft.ReportDesigner.Project.ReportServiceClient.GetItemType(String
item)
en Microsoft.ReportDesigner.Project.ReportServiceClient.CheckAuthorized()
en
Microsoft.ReportDesigner.Project.ReportClientManager.GetCredentials(String
url)
en Microsoft.ReportDesigner.Project.ReportProjectDeployer.PrepareDeploy()
===================================
Error de la solicitud con el código de estado HTTP 404: Not Found.
(System.Web.Services)
--
Ubicación del programa:
en
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
message, WebResponse response, Stream responseStream, Boolean asyncCall)
en System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
en
Microsoft.SqlServer.ReportingServices2005.ReportingService2005.GetItemType(String
Item)
en
Microsoft.SqlServer.ReportingServices2005.RSConnection.GetItemType(String
Item)You cannot deploy 2005 reports to RS 2000 server. However, you can deploy RS
2000 reports to a RS 2005 server. One caveat. When I did this I had a few
cases of some minor buggy behavior that went away when I converted to RS
2005. But, you might want to try that out.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"jagb" <jagb@.NOSPAM.com> wrote in message
news:utyRqIwfGHA.2456@.TK2MSFTNGP04.phx.gbl...
> We are migrating to SQL Server 2005 (and also RS shipped with SQL 2005)
> but in the middle of the process we have still some servers still not
> upgraded (and running SQL Server 2000 and RS2000).
> Can we deploy reports to RS servers running SQL Server 2000 using Visual
> Studio 2005? It seems we cannot becasue we receive the following error
> message. Is any workaround to this or do we need to mantain a copy of both
> RS2000 and RS2005 rdl files and deploy each group of them using VS2003 and
> VS2005 respectively? This is somewhat repeat the same job twice, and might
> lead to mistakes and differences between the same file of each version.
> The error messages are in spanish but an approximated translation is
> provided (It probably does not match the real error message in native
> english).
> Thanks a lot.
> ===================================> No se pudo establecer una conexión al servidor de informes
> https://www.mydomain.com/ReportServer. (Diseñador de informes de
> Microsoft)
> A connection to reports server at https://www.mydomain.com/ReportServer
> could not be stablished (Microsoft Form Designer)
> ===================================> Error al intentar conectar con el servidor de informes. Compruebe la
> información de conexión y que la versión del servidor de informes sea
> compatible. (Microsoft.ReportingServices.Designer)
> An error occurred while trying to connect to reports server. Check the
> connection information and reports server version be compatable
> (Microsoft.ReportingServices.Designer)
> --
> Ubicación del programa:
> en
> Microsoft.SqlServer.ReportingServices2005.RSConnection.MissingEndpointException.ThrowIfEndpointMissing(WebException
> e)
> en
> Microsoft.SqlServer.ReportingServices2005.RSConnection.GetItemType(String
> Item)
> en
> Microsoft.ReportDesigner.Project.ReportServiceClient.GetItemType(String
> item)
> en
> Microsoft.ReportDesigner.Project.ReportServiceClient.CheckAuthorized()
> en
> Microsoft.ReportDesigner.Project.ReportClientManager.GetCredentials(String
> url)
> en
> Microsoft.ReportDesigner.Project.ReportProjectDeployer.PrepareDeploy()
> ===================================> Error de la solicitud con el código de estado HTTP 404: Not Found.
> (System.Web.Services)
> --
> Ubicación del programa:
> en
> System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
> message, WebResponse response, Stream responseStream, Boolean asyncCall)
> en System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters)
> en
> Microsoft.SqlServer.ReportingServices2005.ReportingService2005.GetItemType(String
> Item)
> en
> Microsoft.SqlServer.ReportingServices2005.RSConnection.GetItemType(String
> Item)
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment