Does SqlDataSource hold the connection ?

If we bind a GridView to a SQLDataSource, is it not a connected usage, which locks up one connection thread ?I don't think so. Once it's databound the connection should be closed. Any sorting or paging will open a new connection.|||No, the connection will be closed. However, you may tie up a connection on the server for a little while if you have connection pooling turned on.

Does personal edition sql server support jdbc connection?

if it does, what are the settings I must do in the server?
since I got the following error when connect :
com.inet.tds.SQLException: Connection refused: connect
java.net.ConnectException: Connection refused: connect
thanksHi
Yes it does. Check your connection string. AFAIK, Integrated Security is not
supported so make sure that you supply a username and password. Check that
the username/password combination work through query analyzer.
The SQL Event log might show an audit failure (if not, turn auditing on for
failures, restart SQL Server and try again).
Regards
Mike
"Friend" wrote:
> if it does, what are the settings I must do in the server?
> since I got the following error when connect :
> com.inet.tds.SQLException: Connection refused: connect
> java.net.ConnectException: Connection refused: connect
> thanks
>

Does personal edition sql server support jdbc connection?

if it does, what are the settings I must do in the server?
since I got the following error when connect :
com.inet.tds.SQLException: Connection refused: connect
java.net.ConnectException: Connection refused: connect
thanks
Hi
Yes it does. Check your connection string. AFAIK, Integrated Security is not
supported so make sure that you supply a username and password. Check that
the username/password combination work through query analyzer.
The SQL Event log might show an audit failure (if not, turn auditing on for
failures, restart SQL Server and try again).
Regards
Mike
"Friend" wrote:

> if it does, what are the settings I must do in the server?
> since I got the following error when connect :
> com.inet.tds.SQLException: Connection refused: connect
> java.net.ConnectException: Connection refused: connect
> thanks
>

Does personal edition sql server support jdbc connection?

if it does, what are the settings I must do in the server?
since I got the following error when connect :
com.inet.tds.SQLException: Connection refused: connect
java.net.ConnectException: Connection refused: connect
thanksHi
Yes it does. Check your connection string. AFAIK, Integrated Security is not
supported so make sure that you supply a username and password. Check that
the username/password combination work through query analyzer.
The SQL Event log might show an audit failure (if not, turn auditing on for
failures, restart SQL Server and try again).
Regards
Mike
"Friend" wrote:

> if it does, what are the settings I must do in the server?
> since I got the following error when connect :
> com.inet.tds.SQLException: Connection refused: connect
> java.net.ConnectException: Connection refused: connect
> thanks
>sql

Does file connection manager not work offline?

Hi there

I have a connectin manager for file( New File Connection..) along with some oledb connection managers.

Now If a put SSIS work Offline as True (I need this for some reason). Connection manager for File gives error as something --

"Connection manager for File connection failed with error code-0xc0014019,Connections cannot acquire connections while work offline is true."

But other connections of olddb work fine.

so do we have to change some more settings with file connection or with file connection we can't work offline?

Thanks and Regards

Rahul Kumar

logtorahul wrote:

"Connection manager for File connection failed with error code-0xc0014019,Connections cannot acquire connections while work offline is true."

Rahul,

The answer seems to be in the error message itself. I don't know your reason for working offline; but when I use it I do not expect any of the connections to work. I guess that option was put there to allow you to open packages while 'no-online' without receiving error messages in your connections.

|||

Yes Rafael,

You are right when working offline we donot expect connections to work,even i do not.

But any other connection manager does not give you this error when we run the package.

Let me explain with a scenario:

Suppose we have a oledb connection ( for our source and destination DB) and a file connection for our log file and all the connection string is being provided by package configuration file.Given work offline as true and delayValidation is also true.

Now if we run the package, all other connection managers pick connection string from the package config file but the file connection gives error as

"it cannot acquire connection while working offline."

Now this sounds little wired to me as all the connection manager can acquire connection while working offline and file connection cannot.

Does an embedded XML DataSet have to be hardcoded?

I have an XML DataSource in my report which does not specify a connection
string, because I want to use an embedded XML DataSet. However I would like
the XML DataSet text to be defined using an expression (actually a function
call in my custom assembly). Even though you can define an expression for the
XML DataSet, doing so generates a design time error like this:
"The XmlDP query is invalid. Syntax error at line 1, character 3 of the
ElementPath. (Microsoft.ReportingServices.DataExtensions)"
If I define the DataSet text like this it works fine:
============================================= <Query>
<ElementPath>Root /Parameter {@.ParamName, @.ParamValue} </ElementPath>
<XmlData>
<Root>
<Parameter ParamName="Param1" ParamValue="Value1"></Parameter>
<Parameter ParamName="Param2" ParamValue="Value2"></Parameter>
<Parameter ParamName="Param3" ParamValue="Value3"></Parameter>
<Parameter ParamName="Param4" ParamValue="Value4"></Parameter>
<Parameter ParamName="Param5" ParamValue="Value5"></Parameter>
</Root>
</XmlData>
</Query>
=============================================
If I define the DataSet text like this I get the error message:
============================================= = "<Query>"
+ "<ElementPath>Root /Parameter {@.ParamName, @.ParamValue} </ElementPath>"
+ "<XmlData>"
+ "<Root>"
+ "<Parameter ParamName=""Param1"" ParamValue=""Value1""></Parameter>"
+ "<Parameter ParamName=""Param2"" ParamValue=""Value2""></Parameter>"
+ "<Parameter ParamName=""Param3"" ParamValue=""Value3""></Parameter>"
+ "<Parameter ParamName=""Param4"" ParamValue=""Value4""></Parameter>"
+ "<Parameter ParamName=""Param5"" ParamValue=""Value5""></Parameter>"
+ "</Root>"
+ "</XmlData>"
+ "</Query>"
=============================================
The above is just an expression that shows the error message. Ideally my
DataSet text will look like this:
=Code.RptLib.ReportParametersXML()
It looks like I am up against a limitation in the product. Can you confirm
that this is a limitation in trhe product (embedded XML DataSets MUST be
hardcoded), or is there a workaround or technique that I am missing?
Thanks!
-- Chris
--
Chris, SSSIHello Chirs,
I have reproduced this issue on my side.
I will do some research on this. I appreciate your patience.
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
=====================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix
issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================.|||Hi Wei Lu,
I found an interesting thing.
By accident I tried =Code.RptLib.ReportParametersXML instead of
=Code.RptLib.ReportParametersXML() and that worked.
Because my method does not take any parameters, I guess VB.NET does not like
the empty parenthesis and for some reason the Report Designer gives a
misleading error message about this problem.
So I solved my problem and I do not have to hard code the XML. It is coming
from my custom assembly.
However, I have no idea why the expression syntax ="..." does not work. But
since I do not need that approach it is not a problem for me right now.
Still, you might want to pass this "bug" on to the developers of SSRS.
-- Chris
Chris, SSSI
"Wei Lu [MSFT]" wrote:
> Hello Chirs,
> I have reproduced this issue on my side.
> I will do some research on this. I appreciate your patience.
> Sincerely yours,
> Wei Lu
> Microsoft Online Partner Support
> =====================================================> PLEASE NOTE: The partner managed newsgroups are provided to assist with
> break/fix
> issues and simple how to questions.
> We also love to hear your product feedback!
> Let us know what you think by posting
> - from the web interface: Partner Feedback
> - from your newsreader: microsoft.private.directaccess.partnerfeedback.
> We look forward to hearing from you!
> ======================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others
> may learn and benefit from this issue.
> ======================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
> ======================================================.
>