Showing posts with label correctly. Show all posts
Showing posts with label correctly. Show all posts

Tuesday, March 20, 2012

Can't export report to CSV,XMl correctly, sql 2005 reporting service

Hi all,

I am developing reports using sql2005 report service. I can export reports in excel and pdf format, but can't export to csv and xml correctly.

The exported csv and xml files only contain some thing like the textbox,..., but no report content are there.

Anybody can help? thanks in advance.

BTW, all reports are matrix, is martrix can cause some issues?

Hi,

For most items on your report, you can define how it needs to be rendered to XML. For example the xml output for an item in a matrix can be set as follow:

select the item in the matrix|||

Thanks, Greert.

Your reply is really helpful. Now I know how to export report in xml format. But, how about CSV? I still can't export report to csv.

Thanks again

|||

Hi,

The same goes for CSV. For example if you set the Output of a column to No, you will see that the column is not included in the CSV file.

Greetz,

Geert

Geert Verhoeven
Consultant @. Ausy Belgium

My Personal Blog

|||Hi Geert,

Thanks a lot.

When I set th output of a column to yes, it works. Before, the the output of column was set to Auto.

Thursday, March 8, 2012

Can't debug SP from Query Analizer with SP3a

Hi,
I am able to debug them correctly from VS.NET 2003, but trying from Query
Analizer gives me this error:
Server: Msg 229, Level 14, State 5, Procedure sp_sdidebug, Line 1
[Microsoft][ODBC SQL Server Driver][SQL Server]EXECUTE permission denied on
object 'sp_sdidebug', database 'master', owner 'dbo'.
Any ideas?
Thanks in advance,
Juan Dent, M.Sc.
The first thing to do is to make sure that the account you are using can
execute the stored procedure indicated in the error message:
GRANT EXECUTE ON sp_sdidebug TO <your user account goes here>
Keith
"Juan Dent" <juan5@.dev.com> wrote in message
news:058F454E-48E0-4194-BBA2-21A953BF2B53@.microsoft.com...
> Hi,
> I am able to debug them correctly from VS.NET 2003, but trying from Query
> Analizer gives me this error:
> Server: Msg 229, Level 14, State 5, Procedure sp_sdidebug, Line 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]EXECUTE permission denied
on
> object 'sp_sdidebug', database 'master', owner 'dbo'.
> Any ideas?
> --
> Thanks in advance,
> Juan Dent, M.Sc.
|||Yes I have done this, to no avail.
"Keith Kratochvil" wrote:

> The first thing to do is to make sure that the account you are using can
> execute the stored procedure indicated in the error message:
> GRANT EXECUTE ON sp_sdidebug TO <your user account goes here>
> --
> Keith
>
> "Juan Dent" <juan5@.dev.com> wrote in message
> news:058F454E-48E0-4194-BBA2-21A953BF2B53@.microsoft.com...
> on
>

Thursday, February 16, 2012

Can't Connect to SQL 2005 Express Edition via Server Manangment Studio

I have installed SQL 2005 Express Edition on a Windows 2003 Web Edition server. Everything installed correctly, no errors to be found. I also have:

Local & Remote Connections using TCP/IP only turne don

SQL Browser is running as well.

I have tried connecting with the most recent CTP of Microsoft SQL Server Management Studio Express 9.00.1399.00

When trying to connect using the SA account I recieve:

'An error has occured while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (Provider: Named Pipes Provider, error 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

After that failed I tried creating a connection locally on the server using ODBC Manager with no luck as well.

Microsoft SQL Native Client Version 09.00.1399

Running connectivity tests...

Attempting connection
[Microsoft][SQL Native Client]TCP Provider: No connection could be made because the target machine actively refused it.

[Microsoft][SQL Native Client]Login timeout expired
[Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

TESTS FAILED!

Any help would be appreciated.


Try this.

Start > All Programs > Microsoft SQL Server 2005 > Configuration tools > SQL Server Surface Area Configuration

Then click Surface Area Configuration for Services and Connection. Select your instance of sql server (by default MSSQLSERVER). Then expand Database Engine and click on remote connections. On the right side select Local and remote connections > Using both TCO/IP and named pipes.

|||

I'm having the same issue, i've tried all of the above. My server has 9 active IP addresses, and I've tried connecting to the one which I use to remote in to the server. Is this the correct approach?

Also, in the SQL Server Configuration Manager, I've set that IP address to 'Active' and 'Enabled' with no luck. Same error as the gentleman above.

Any other suggestions?

Thank you,

Bret

|||I still can't get it to work. I've even tried the old remove and reinstall approach. This is very aggravating as I've tried everything under the sun that I can think of.|||

Got it working:

Under Protocols for SQLEXPRESS and tcp/ip and the ip addresses tab

Tcp dynamic ports – set to blank

Disabled other ips except the loopback

At the bottom, set dynamic ports to blank and the tcp port to 1433

Stopped and restarted the sql server.

Can't Connect to SQL 2005 Express Edition via Server Manangment Studio

I have installed SQL 2005 Express Edition on a Windows 2003 Web Edition server. Everything installed correctly, no errors to be found. I also have:

Local & Remote Connections using TCP/IP only turne don

SQL Browser is running as well.

I have tried connecting with the most recent CTP of Microsoft SQL Server Management Studio Express 9.00.1399.00

When trying to connect using the SA account I recieve:

'An error has occured while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (Provider: Named Pipes Provider, error 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

After that failed I tried creating a connection locally on the server using ODBC Manager with no luck as well.

Microsoft SQL Native Client Version 09.00.1399

Running connectivity tests...

Attempting connection
[Microsoft][SQL Native Client]TCP Provider: No connection could be made because the target machine actively refused it.

[Microsoft][SQL Native Client]Login timeout expired
[Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

TESTS FAILED!

Any help would be appreciated.


Try this.

Start > All Programs > Microsoft SQL Server 2005 > Configuration tools > SQL Server Surface Area Configuration

Then click Surface Area Configuration for Services and Connection. Select your instance of sql server (by default MSSQLSERVER). Then expand Database Engine and click on remote connections. On the right side select Local and remote connections > Using both TCO/IP and named pipes.

|||

I'm having the same issue, i've tried all of the above. My server has 9 active IP addresses, and I've tried connecting to the one which I use to remote in to the server. Is this the correct approach?

Also, in the SQL Server Configuration Manager, I've set that IP address to 'Active' and 'Enabled' with no luck. Same error as the gentleman above.

Any other suggestions?

Thank you,

Bret

|||I still can't get it to work. I've even tried the old remove and reinstall approach. This is very aggravating as I've tried everything under the sun that I can think of.|||

Got it working:

Under Protocols for SQLEXPRESS and tcp/ip and the ip addresses tab

Tcp dynamic ports – set to blank

Disabled other ips except the loopback

At the bottom, set dynamic ports to blank and the tcp port to 1433

Stopped and restarted the sql server.