FTP Task Connection Problem

Problem: my FTP Connection Manager cannot connect to the FTP service specified in its configuration parameters. When I execute the FTP Task hooked to that connection manager I get the following error:

[FTP Task] Error: Unable to connect to FTP server using "FTP Connection Manager".

When I test the FTP service using FTP from a command prompt on the same workstation using the same parameters it connects just fine.

When I attempt to edit the settings in the FTP Connection Manager, the editor window pops up and then immediately disappears which is another problem. As I watch closely I can see that the username property is set to my domain login, not the value I typed in when I created it.

So I used the property sheet for the manager to set all the parameters correctly. However it still will not connect. Am I missing something? I've seen posts concerning issues connecting to UNIX/LINUX based FTP services. This particular service is hosted on a LINUX box. TIA.

I am not sure if this gona work for you or not but no harm trying it out, because this worked out for me. For example:

ftp://myservername/

if you type this in windows explorer then it prompts you for username and password.

Fillout the property page as follows:

Server Name: myservername (Do not use ftp:// prefix or the / suffix)

Port No.: 21 (in not changed)

Verify this with 'Test Connection' button.

FTP Task Completes but No File

I have an FTP task that once the file is loaded a script task is activated and then a data flow process starts. I can connect to the FTP server with the Test connection and I can see the file in the remote directory "/HRData.txt" however even with the Delay validation set to true it does not download the file.the only thing i can think of is to try re-creating the task.|||I have already tried this with no affect. I guess I am going to try to write a FTP download into my script that I am executing.

FTP Task : Put a wait in the FTP task

Hi,

I have a scenario where I want the FTP task to connect to a particular FTP server and download files. But if the files are not available on the FTP server then wait for 10 mins and then try again. Continue this till 3:00 am in the morning and if the files are still not there then raise an error notification.

Do I have to create a custom task for this? Or can it be achevied by using the existing SSIS components?

Your guidance is required to start me in the correct direction.

Thanks for your time.

$wapnil

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1178124&SiteID=1

The forum search is your friend.|||

Thanks again Phil.

Will be trying this out now.

$wapnil

FTP Connection problem with "The Password was not allowed" error message

Hi

I have a simple FTP task that I am trying to connect to an FTP server. I can test the connection fine, however, when I try and execute the package from Visual Studio 2005 I get the "The Password was not allowed" message. I have found some threads that mention setting the protection level on the package to EncryptSensitiveWithPassword, however, I still get the same message appearing.

Has anyone any idea as to what is causing this and how I can get around it

Thanks

Darrell

The error comes from the FTP server due to a invalid password. Can you tell me what is the value ProtectionLevel property in the Package?

Thanks,

Ovidiu Burlacu

|||EncryptSensitiveWithPassword means you have to enter a password in the package properties. You have specified the wrong password there, most likely.

For running in BIDS, EncryptSensitiveWithUserKey is just fine.|||

I had set the PackageProtection to EncryptSensitiveWithPassword, but that didn't work either.

As for an incorrect password, this can't be correct, because when I test the FTP connection it works fine

Any other thoughts ?

Thanks

D

FTP broken after install SQL 2005

Hi Guys,

I have a server which run IIS6 and FTP server. I have able to connect in and upload with any issues.

After an install of SQL management and connectivity, we lost(write) the upload access to the FTP server.

We have checked the permissions on IIS and file system. All are correct.

Any ideas if SQL would break this or other ideas?

Cheers

Craig.

I don't think this is a SQL related issue, but what was the error you are getting when trying to upload or access the FTP server. Might check any hotfix or service pack on windows version.

Frustrated with two clients that can't connect...

I have a SQL server that I am trying to access from across a WAN. 1 machine
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev
"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?

> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.

Frustrated with two clients that can't connect...

I have a SQL server that I am trying to access from across a WAN. 1 machine
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?

> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.

Frustrated with two clients that can't connect...

I have a SQL server that I am trying to access from across a WAN. 1 machine
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?
> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.

French character problems

I am having a problem where if I connect with our application to the sql
server from a windows2000 terminal server I see the French character properly
but if I connect to the same database from windows2003 i only see wird
character insted of é or è.
it's hard to explane but dose anyone know what this could be the 2003 server
is all up to date and patched
What are your regional settings on win2k and win2003?
See if its different, change it and try.
"Mart" wrote:

> I am having a problem where if I connect with our application to the sql
> server from a windows2000 terminal server I see the French character properly
> but if I connect to the same database from windows2003 i only see wird
> character insted of é or è.
> it's hard to explane but dose anyone know what this could be the 2003 server
> is all up to date and patched
|||I had tryed that but now I found that the Mdac's were the problem
thanks
"Me" wrote:
[vbcol=seagreen]
> What are your regional settings on win2k and win2003?
> See if its different, change it and try.
>
> "Mart" wrote:

French character problems

I am having a problem where if I connect with our application to the sql
server from a windows2000 terminal server I see the French character properl
y
but if I connect to the same database from windows2003 i only see wird
character insted of é or è.
it's hard to explane but dose anyone know what this could be the 2003 server
is all up to date and patchedWhat are your regional settings on win2k and win2003?
See if its different, change it and try.
"Mart" wrote:

> I am having a problem where if I connect with our application to the sql
> server from a windows2000 terminal server I see the French character prope
rly
> but if I connect to the same database from windows2003 i only see wird
> character insted of é or è.
> it's hard to explane but dose anyone know what this could be the 2003 serv
er
> is all up to date and patched|||I had tryed that but now I found that the Mdac's were the problem
thanks
"Me" wrote:
[vbcol=seagreen]
> What are your regional settings on win2k and win2003?
> See if its different, change it and try.
>
> "Mart" wrote:
>

French character problems

I am having a problem where if I connect with our application to the sql
server from a windows2000 terminal server I see the French character properly
but if I connect to the same database from windows2003 i only see wird
character insted of é or è.
it's hard to explane but dose anyone know what this could be the 2003 server
is all up to date and patchedWhat are your regional settings on win2k and win2003?
See if its different, change it and try.
"Mart" wrote:
> I am having a problem where if I connect with our application to the sql
> server from a windows2000 terminal server I see the French character properly
> but if I connect to the same database from windows2003 i only see wird
> character insted of é or è.
> it's hard to explane but dose anyone know what this could be the 2003 server
> is all up to date and patched|||I had tryed that but now I found that the Mdac's were the problem
thanks
"Me" wrote:
> What are your regional settings on win2k and win2003?
> See if its different, change it and try.
>
> "Mart" wrote:
> > I am having a problem where if I connect with our application to the sql
> > server from a windows2000 terminal server I see the French character properly
> > but if I connect to the same database from windows2003 i only see wird
> > character insted of é or è.
> >
> > it's hard to explane but dose anyone know what this could be the 2003 server
> > is all up to date and patched

Framework 1:1 net

If you connect to a server and open a query in SQL Managment studio (2005) and looses connection and then regain the connection, when you try to run the query it gives me a "TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host."

This happens against both 2005 and 2000 servers.

If I re-run the query it works.

However, this happens in our VB.NET app as well for clients with Wireless connections.

So, something has changed in Framework 2.0 regarding this, does anyone know how to tell the client to not throw this error and just try connecting the server instead which will work?

Hi,

The SqlClient provider does not retry operations if the underlying connection is "broken" (e.g. closed by the server or by a glitch in the network). SQL Server Management Studio retries by trying to open the connection again.

One factor that affects this behavior is whether or not you have connection pooling enabled. Did you include "pooling=false" in your connection string?

This behavior should not have changed from 1.1 to 2.0. Did your 1.1 application behave differently? What error did you get (if any) on 1.1?

Pablo Castro
Program Manager - ADO.NET Team
Microsoft Corp.|||I have not changed anything from 1.1 to 2.0.
(its a 1.1 converted project to 2.0)

No, I did not get any errors like this in 1.1

I dont have Pooling=False, Neither do I want it that way (large app with tons of connections).

as stated it happens BOTH in Sql Management Studio as well as in any VB.NET app, it happens on several diffrent companies on diffrent continents, against diffrent SQL Servers.

VPN Clients, WIFI Clients are hit hardest (they have tiny drops in connections often)|||Bumping this.

Any resolution yet?

Basically, I cannot run any long running queries on computers with SQL Management Studio + Framework 2.0 installed over VPN, Not even in the OLD Query Analyzer anymore(diffrent error, same meaning).

However, on my untouched laptop, that has the old SQL Server Client Tools installed, it works fine on the same VPN connection.

Even on LAN it happens quite frequently, I got my app on about 150 clients, they catched this error about 40 times today.|||This looks really weird. I'll talk to a few other folks in the protocols team to see if I get more ideas to help you out.

There is one bit that particularly gets my attention: the OLD query analyzer uses the old native data-access stack; the SQL Server 2005 setup, or the VS 2005 setup, do not touch any of those bits at all. So, if you're getting the same behavior from the old query analyzer, that may indicate that there was something else that changed and may be causing this glitch. Do you get failures in QA as often as you get with the other clients? What error do you get in the QA case?

I'll reply again to this thread once I have more details or have someone do it.

Regards,
Pablo Castro
Program Manager - ADO.NET Team
Microsoft Corporation|||Hi Fredrik,

It appears that Sqlclient grabs a connection from the pool that has already been closed because of a network error and reports an error when it tries to write to the socket. I can't understand why the 1.1 framework would be less susceptible to these network errors than the 2.0 framework. Would you be able to take a client-side trace that captures the error and send it to me along with the server's error log? You can email me the files at ilsung@.microsoft.com. The instructions for setting up the trace are here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnadonet/html/tracingdataaccess.asp . Also, if you know of a way for us to repro this, that would be great.

Thanks,

Il-Sung Lee
Program Manager, SQL Server Protocols
Microsoft Corp.

This posting is provided "AS IS" with no warranties, and confers no rights.|||I will test the tracing on my home computer which is connected over VPN.

However, Reproducing it in 2.0 enviroment is easy.

Open a SQL Query in SQL Management studio to a server.

Enter a simple query, Run the query, when its completed, disable the network connection, and immediatly enable it again, re-run the query when the network is back up again and you will get the error:

A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

- Fredrik|||The link you gave refers to Beta 1, is there a updated document for the release version of Framework 2.0?|||I just received this same error today in our production environment. Had not appeared in dev, test or uat. Our application was built in asp.net 2.0 beta 2 and later upgraded to RTM. Besides changing pooling, any suggestions on how to prevent this?|||

If I remember correctly, the same procedure should work for RTM bits. Is it not working for you?

Thanks,
Pablo Castro
Program Manager - ADO.NET Team
Microsoft Corporation

|||

No, I did not get the debug trace function to work, it simply dont dump any data, dont know why.

Anyway.

I found a setting in the SQL Configuration Manager, on TCP/IP Protocol (native) there is KeepAlive and KeepAliveInterval that I am testing a little with.

I sat those settings to zero, eg no keepalive checking I guess, will see how that turns out.

|||Please let everyone know how this goes. I'm having the exact same issue with my application. Thanks!|||

So far 100% success, I left my app running yesterday, and it hadnt crashed still today, one day later. Before the change it only took about 10 minutes on my WiFi before I got a error.

Question is how you can change those values for clients only have .NET framework 2.0 installed (there is no registry entry for that one pre-defined). Registry entry is only present on those clients that have SQL 2005 Client tools installed.

I gonna look a little further with Regmon later this week and see if its just enough to create the registry entry on a "normal" client.

|||

I get the same error. It even occurs between my sql server management studio and the sql instance on the network.

The client has the release version while the sql instance is sql server 2005 beta2. Could this be the issue?

Error connecting to SQLSERVER1\ANINSTANCE. Err: A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

This is a project i converted from 1.1 to 2.0.

The old saved 1.1 project connects without any problems.

It really looks like a framework 2.0 issue.

|||

It would be good if you could try this against a final version of SQL Server. The fact that the beta 2 server is dropping the connection during login is not that surprising, it may be due to a protocol version mismatch detected during the login handshake.

So I wouldn't consider this and the other issue discussed in this thread to be the same thing.

Pablo Castro
Program Manager - ADO.NET Team
Microsoft Corporation