Showing posts with label connecting. Show all posts
Showing posts with label connecting. Show all posts

Sunday, March 11, 2012

Data connection problem between Assess front end and SQL server behind firewall

I have an Access 2000 front end (on win 98) for a SQL 2000 database (on win 2000 server) behind a firewall. A port (1433) was opened for connecting the Access front end to the SQL database. The odbc system DSN connection showed data source "TESTS COMPLETED SUCCESSFULLY!". However, the Access front end still does not work. The same Access program works well within the firewall. Could anyone tell me what could possible be wrong?What error does Access return?

Saturday, February 25, 2012

Data access using Ent. Library Jan. 2006 release

Hello ...

Using Ent. Library Jan. 2006 release and .Net Framework 2.0, I'm connecting to SQL Server 2000 using Microsoft.Practices.EnterpriseLibrary.Data.Sql.

I have a windows service that processes jobs asynchronously and from time to time, I'm getting the following error --

"A connection was successfully established with the server, but then an error occurred during the pre-login handshake. 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. (TCP Provider error: 0 - An existing connection was forcibly closed by the remote host. "

What's surprising is the error message saying SQL Server 2005. Has anyone encountered and resolved this?

Thanks.

allanroy

I guess you installed the SNAC on your system, right ? Thats where the message comes from.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

What is SNAC?

Thanks.

allan

|||Nothing to eat ;-) It s the SQL Native Client.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

The SQL Native Client is installed in my client machine and not on the server that host the SQL Server 2000 and my windows services. Ones a job is requested from a client machine, the process is asynchronous and processing happens only on the server.

allan

|||Are you using connection pooling, if yes it could be that the connection used is not released from the pool, leading to the error message, that the server cannot be contacted.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Tuesday, February 14, 2012

Customizing Toolbar in Reporting Service

Hi

I use SSRS 2005; i have a report with Drill down feature, connecting to another report. when i preview the report in the VS2005; i get a backup button in the RS toolbar to move from the second report to the main report after the drill down.

but once i deploy it on the server and when the user views the report on the web i dont get to see the BACK button.

Is it possible to do so?

anybody have tried and seen before....

/chandresh soni

There is no back button on the web-based toolbar. We thought that people would get confused with having a back button in the browser along with one on the toolbar. The back button on the browser will generally work except it will include other actions like toggles and sorts.|||

thanks Brain, for replying.

i will try something alternative. or ask the user to use the browser back button.