Problems exporting reports to Excel

Hello all

I have a problem with an aplication that developed in .Net to view Crystal 9.0 reports, in my dev PC I can export any report to Excel without a problem, but on my client Pc's, click directly on the Export button, the app show the file location window, select Excel file on type file field and click ok, appear an error, it is in spanish but it is the translation ...

"Error in file c:\pathfile\filename.rpt:
Exportation DLL or format file invalid"

Then appear a new message box:

"Unable to export"

Checking on the web I found tow possible solutions, download the last Hot Fix from seagate site or check and replace the U2F*.dll files located in my user's PC Crystal folder. I tried with both but I'm where I started...

Any idea ?

ThanxDid you have latest service pack of CR?
Refer this for more info
http://www.businessobjects.com/support/default.asp

Problems deploying to a remote Report Server(2005)

I developed a simple report using the AdventureWorks sample database on a XP
Pro with SQL Server 2005 BI tools only (Beta 2). The report runs fine in
preview mode. When I attempt to deploy it to a remote Report Server (June
2005 CTP) I get the following error:
"A connection could not be made to the report server
http://<servername>/reportserver.
Additional information: The version of the report server web service
definition (WSDL) is either not valid or unrecognized. The server is not a
compatible version (Microsoft.reportingServices.Designer)"
Any help/responses is greatly appreciated.
PS: The same report developed and deployed on the Report Server works fine!!
--
Thank you,
AshokThe version of RS with Beta2 is not the same as the June CTP. My guess is
that this version mismatch is causing the problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
news:B2A96F52-5CD0-4A83-A0B3-FFEB5EBF5D21@.microsoft.com...
>I developed a simple report using the AdventureWorks sample database on a
>XP
> Pro with SQL Server 2005 BI tools only (Beta 2). The report runs fine in
> preview mode. When I attempt to deploy it to a remote Report Server (June
> 2005 CTP) I get the following error:
> "A connection could not be made to the report server
> http://<servername>/reportserver.
> Additional information: The version of the report server web service
> definition (WSDL) is either not valid or unrecognized. The server is not
> a
> compatible version (Microsoft.reportingServices.Designer)"
> Any help/responses is greatly appreciated.
> PS: The same report developed and deployed on the Report Server works
> fine!!
> --
> Thank you,
> Ashok|||THanks Bruce. I appreciate your prompt reponse.
I suspected that it would be an incompatibility issue. Would you recommend
that I uninstall the Beta and install the june CTP on the client?
--
Thank you,
Ashok G
"Bruce L-C [MVP]" wrote:
> The version of RS with Beta2 is not the same as the June CTP. My guess is
> that this version mismatch is causing the problem.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
> news:B2A96F52-5CD0-4A83-A0B3-FFEB5EBF5D21@.microsoft.com...
> >I developed a simple report using the AdventureWorks sample database on a
> >XP
> > Pro with SQL Server 2005 BI tools only (Beta 2). The report runs fine in
> > preview mode. When I attempt to deploy it to a remote Report Server (June
> > 2005 CTP) I get the following error:
> >
> > "A connection could not be made to the report server
> > http://<servername>/reportserver.
> >
> > Additional information: The version of the report server web service
> > definition (WSDL) is either not valid or unrecognized. The server is not
> > a
> > compatible version (Microsoft.reportingServices.Designer)"
> >
> > Any help/responses is greatly appreciated.
> >
> > PS: The same report developed and deployed on the Report Server works
> > fine!!
> > --
> > Thank you,
> > Ashok
>
>|||Yes. If you have the report available from RS 2000 then I suggest
uninstalling the beta and install the CTP and then bring over the reports
from RS 2000.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
news:72F122A5-2CD7-4EC1-A776-F8536B016EAB@.microsoft.com...
> THanks Bruce. I appreciate your prompt reponse.
> I suspected that it would be an incompatibility issue. Would you
> recommend
> that I uninstall the Beta and install the june CTP on the client?
> --
> Thank you,
> Ashok G
>
> "Bruce L-C [MVP]" wrote:
>> The version of RS with Beta2 is not the same as the June CTP. My guess is
>> that this version mismatch is causing the problem.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
>> news:B2A96F52-5CD0-4A83-A0B3-FFEB5EBF5D21@.microsoft.com...
>> >I developed a simple report using the AdventureWorks sample database on
>> >a
>> >XP
>> > Pro with SQL Server 2005 BI tools only (Beta 2). The report runs fine
>> > in
>> > preview mode. When I attempt to deploy it to a remote Report Server
>> > (June
>> > 2005 CTP) I get the following error:
>> >
>> > "A connection could not be made to the report server
>> > http://<servername>/reportserver.
>> >
>> > Additional information: The version of the report server web service
>> > definition (WSDL) is either not valid or unrecognized. The server is
>> > not
>> > a
>> > compatible version (Microsoft.reportingServices.Designer)"
>> >
>> > Any help/responses is greatly appreciated.
>> >
>> > PS: The same report developed and deployed on the Report Server works
>> > fine!!
>> > --
>> > Thank you,
>> > Ashok
>>|||I moved to another RS 2005 server that has CTP June and it worked! I was
able to publish and execute the report.
Thanks once again.
--
Thank you,
Ashok G
"Bruce L-C [MVP]" wrote:
> Yes. If you have the report available from RS 2000 then I suggest
> uninstalling the beta and install the CTP and then bring over the reports
> from RS 2000.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
> news:72F122A5-2CD7-4EC1-A776-F8536B016EAB@.microsoft.com...
> > THanks Bruce. I appreciate your prompt reponse.
> > I suspected that it would be an incompatibility issue. Would you
> > recommend
> > that I uninstall the Beta and install the june CTP on the client?
> >
> > --
> > Thank you,
> > Ashok G
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> The version of RS with Beta2 is not the same as the June CTP. My guess is
> >> that this version mismatch is causing the problem.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Ashok G" <ashokg@.discussions.microsoft.com> wrote in message
> >> news:B2A96F52-5CD0-4A83-A0B3-FFEB5EBF5D21@.microsoft.com...
> >> >I developed a simple report using the AdventureWorks sample database on
> >> >a
> >> >XP
> >> > Pro with SQL Server 2005 BI tools only (Beta 2). The report runs fine
> >> > in
> >> > preview mode. When I attempt to deploy it to a remote Report Server
> >> > (June
> >> > 2005 CTP) I get the following error:
> >> >
> >> > "A connection could not be made to the report server
> >> > http://<servername>/reportserver.
> >> >
> >> > Additional information: The version of the report server web service
> >> > definition (WSDL) is either not valid or unrecognized. The server is
> >> > not
> >> > a
> >> > compatible version (Microsoft.reportingServices.Designer)"
> >> >
> >> > Any help/responses is greatly appreciated.
> >> >
> >> > PS: The same report developed and deployed on the Report Server works
> >> > fine!!
> >> > --
> >> > Thank you,
> >> > Ashok
> >>
> >>
> >>
>
>

Problems connectiong to a remote DB

Hello

I developed a vb.net win app which interacts with a sqlserver 2005 express DB.

When the DB is located in my local computer everything works just fine.

I'm trying to connect to a remote DB (mdf file that located on a remote server) but without any success.

I assume that a connectionstring change is needed, however I can't find what change to perform (I tried to insert the server IP address to the connectionstring but it didn't work either).

the app connectionstring looks like that:

connectionString

="Data Source=.\SQLExpress;AttachDbFilename=C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\DBName.mdf;Integrated Security=True;User Instance=False" providerName="System.Data.SqlClient" />

Hope someone can help me find the solution.

Since your question concerns a Windows Forms application, and not ASP.NET, you should ask it on theMSDN Forums.|||Try looking atwww.connectionstrings.com...|||Hi yarit, post the connection failure error message would help to solve the issue. You can also take a look at this post:
http://forums.asp.net/thread/1289341.aspx|||

Hello

Firstly thanks for all of your replies.

Now, I've succeeded to connect my app to a remote DBbut only in my company's network, the DB is located on a different machine in the company's network and I can connect to it using this connection string:

connectionString

="Data Source=Inner network IP address \ SQLEXPRESS;Database=DBName;Uid=xxx;Pwd=yyy;"providerName="System.Data.SqlClient">

However I have no success connecting it to an outerIP address, although the machine is connected to the internet via a router and has an outerIP address.

I'll justindicate that my GUI is supposed to be accessed via the internet (a web app) so I must be able to connecteventually via an outer IP address.

Does anybody know if I need to change some config or if it is a pure network problem.

|||

Hello

Firstly thanks for all of your replies.

Now, I've succeeded to connect my app to a remote DBbut only in my company's network, the DB is located on a different machine in the company's network and I can connect to it using this connection string:

connectionString

="Data Source=Inner network IP address \ SQLEXPRESS;Database=DBName;Uid=xxx;Pwd=yyy;"providerName="System.Data.SqlClient">

However I have no success connecting it to an outerIP address, although the machine is connected to the internet via a router and has an outerIP address.

I'll justindicate that my GUI is supposed to be accessed via the internet (a web app) so I must be able to connecteventually via an outer IP address.

Does anybody know if I need to change some config or if it is a pure network problem.

|||Hi yairt, first of all you have to make sure on teh SQL box no firewall is blocking TCP/IP communication to the SQL Express service from Internet. You can use telnet to check this, please refer to the post I mentioned in my previous post.|||

hi Iori jay

thanks for your reply.

The problem was solved (or better said was by-passed), apparently it has nothing to do with SQLSERVER or connection strings.

We connected the server to the internet via ADSL line (`and not through a router that probably concealed its address) and everything worked just fine.

Problems connecting thru firewall

I have developed an application that handles data from a SQL server runnig inside my main domain.

When i connect with the SQL server from the inside i have no problems at all.

However we opened up the application (smart client application) for some beta testers and i bumped into some problems. i changed the connectionstring to use the IP for the server. I also tried a registered dns name, but i got the following

The aspnetdb i use for authentication is refusing to run the stored procedures and i get the famous disconnected due to the remote server does not accept remote calls, or something like that.

If i disable the Authentication in the application and just run the application with the same connectionstring IP or DNS, parts of the application works. Some of the stored procedures get executed , and the others does not get executed.

I have looked at the owner of the items but they all have the same owner and exec rights. I have checked my C# code and they are all using the patterns to execute the calls the same way.

Does anyone have any idea whats going on here ?

I also confirmed that the correct SQL ports has been opened in the PIX.
I ran home and tried to connect the sql server managment studio from home and i got access , the application still behaves like before

how about using a sql server mixed mode for authentication.|||

Hi

The SQL server is set to mixed mode security and i'm using a SQL login i created with dbo schema.

|||

is the server configured to accept local and remote connection

in the surface configuration

start>programs> sqlserver2005>

configuration tools>surface area configuration>

configuration for service and connection>datbase engine

>remote connection> check local and remote connection

|||

Thanks for your answer

I found the problem last night. In the solution someone had added a SQL report that had a hardcoded connectionstring. The try catch found the connection issue and then skipped parts of the load of the application.

Once i removed the conn string everything is working fine...