I created a DTS FTP task to connect to an FTP site. The problem I'm having is the folder I want to access you cannot see under the Files Tab. So if I put the ftp site/subdirectory in the FTP Site box, I get the error "Unable to connect to internet! Please check the source site information, your username and password"
If I go to the FTP site/subdirectory in IE all the files show up fine. I believe this is limitation of DTS, but I would like to hear from you all first.
To see what error I'm talking about:
Create a DTS FTP task
Use: ftp.microsoft.com/bussys/ with no username or password
Click the Files Tab
Normally you can just put the server name in, and see all the folders/files, but the way my FTP site is set up I cannot see the folder I want, I can only access it.What do you see in the Address field of the browser when you click on this site? Something like this?
ftp://<user_id>:<password>@.ftp_site.com
If this is the case then that's the reason why you can see files and folders using your browser vs. DTS package designer.
You NEED to specify user_id and password to access FTP sites unless they are set up to allow anonymous access.
Exception to it would be a setting on an FTP site where browsing is not allowed while accessing a specific file is. Consult with the FTP site admin.
Showing posts with label unable. Show all posts
Showing posts with label unable. Show all posts
Thursday, March 29, 2012
Sunday, February 19, 2012
dtctest fails and nobody here has any clue why
Hi,
My machine is unable to establish a connection for the purposes of
making distributed transactions. The problem appears to be that my
machine is blocking the machine to which I am trying to connect from
establishing RPC Binding with my machine. Here's a message from my
Event Viewer:
MS DTC is unable to communicate with MS DTC on a remote system. MS
DTC on the primary system established an RPC binding with MS DTC on
the secondary system. However, the secondary system did not create
the reverse RPC binding to the primary MS DTC system before the
timeout period expired. Please ensure that there is network
connectivity between the two systems. Error
Specifics:d:\nt_qxp\com\com1x\dtc\dtc\cm
\src\cso.cpp:1977, CmdLine:
C:\WINNT\System32\msdtc.exe, Pid: 1300
No Callstack (0)
What's curious is that my PC is the ONLY one in our network that has
this problem.
I've run dtctester againat various machines using various DSNs and
ALWAYS get the following:
Error:
SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL
Server Driver]Distributed transaction error'
Error:
SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server
Driver]Invalid cursor state
Typical Errors in DTC Output When
a. Firewall Has Ports Closed
-OR-
b. Bad WINS/DNS entries
-OR-
c. Misconfigured network
-OR-
d. Misconfigured SQL Server machine that has multiple netcards.
To my knowledge, my PC is the only one here (out of hundreds) that
flunks the dtctester.
From all appearances, my PC appears to be configured identically to
those of many other people here who are not experiencing any problems.
Specifically, I've checked all MSDTC registry settings of which I've
read, I've been into Component Services and checked the properties of
anything msdtc related, and I've ensured that the services I need are
actually running. I'm running XP, but I have the firewall turned off,
and have never installed any third party firewall. My network
connectivity is ok. I can see the target machine, and can even access
the database to which I am trying to connect and do whatever I want,
so long as I don't use distributed transactions. The version of msdtc
that I am using is identical to those of everyone else around here.
The latest advice I'm getting is to reinstall XP and hope for the
best. Seems pretty drastic to me, especially seeing how it's no
guarantee! Does anyone out there have any idea what could be causing
this? General consensus is that it is some stupid check box somewhere,
but we've pretty much run out of ideas where to look.
-Dave
I have read dozens of emails and solutions to this and similar issues
and tried them all, and nothing seems to work.Dave, I am having the same problem here. Have you found a resolution to
this. Just curious.
Cory
ccundy
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message724716.html
My machine is unable to establish a connection for the purposes of
making distributed transactions. The problem appears to be that my
machine is blocking the machine to which I am trying to connect from
establishing RPC Binding with my machine. Here's a message from my
Event Viewer:
MS DTC is unable to communicate with MS DTC on a remote system. MS
DTC on the primary system established an RPC binding with MS DTC on
the secondary system. However, the secondary system did not create
the reverse RPC binding to the primary MS DTC system before the
timeout period expired. Please ensure that there is network
connectivity between the two systems. Error
Specifics:d:\nt_qxp\com\com1x\dtc\dtc\cm
\src\cso.cpp:1977, CmdLine:
C:\WINNT\System32\msdtc.exe, Pid: 1300
No Callstack (0)
What's curious is that my PC is the ONLY one in our network that has
this problem.
I've run dtctester againat various machines using various DSNs and
ALWAYS get the following:
Error:
SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL
Server Driver]Distributed transaction error'
Error:
SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server
Driver]Invalid cursor state
Typical Errors in DTC Output When
a. Firewall Has Ports Closed
-OR-
b. Bad WINS/DNS entries
-OR-
c. Misconfigured network
-OR-
d. Misconfigured SQL Server machine that has multiple netcards.
To my knowledge, my PC is the only one here (out of hundreds) that
flunks the dtctester.
From all appearances, my PC appears to be configured identically to
those of many other people here who are not experiencing any problems.
Specifically, I've checked all MSDTC registry settings of which I've
read, I've been into Component Services and checked the properties of
anything msdtc related, and I've ensured that the services I need are
actually running. I'm running XP, but I have the firewall turned off,
and have never installed any third party firewall. My network
connectivity is ok. I can see the target machine, and can even access
the database to which I am trying to connect and do whatever I want,
so long as I don't use distributed transactions. The version of msdtc
that I am using is identical to those of everyone else around here.
The latest advice I'm getting is to reinstall XP and hope for the
best. Seems pretty drastic to me, especially seeing how it's no
guarantee! Does anyone out there have any idea what could be causing
this? General consensus is that it is some stupid check box somewhere,
but we've pretty much run out of ideas where to look.
-Dave
I have read dozens of emails and solutions to this and similar issues
and tried them all, and nothing seems to work.Dave, I am having the same problem here. Have you found a resolution to
this. Just curious.
Cory
ccundy
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message724716.html
dtctest fails and nobody here has any clue why
Hi,
My machine is unable to establish a connection for the purposes of
making distributed transactions. The problem appears to be that my
machine is blocking the machine to which I am trying to connect from
establishing RPC Binding with my machine. Here's a message from my
Event Viewer:
MS DTC is unable to communicate with MS DTC on a remote system. MS
DTC on the primary system established an RPC binding with MS DTC on
the secondary system. However, the secondary system did not create
the reverse RPC binding to the primary MS DTC system before the
timeout period expired. Please ensure that there is network
connectivity between the two systems. Error
Specifics:d:\nt_qxp\com\com1x\dtc\dtc\cm\src\cso.c pp:1977, CmdLine:
C:\WINNT\System32\msdtc.exe, Pid: 1300
No Callstack (0)
What's curious is that my PC is the ONLY one in our network that has
this problem.
I've run dtctester againat various machines using various DSNs and
ALWAYS get the following:
Error:
SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL
Server Driver]Distributed transaction error'
Error:
SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server
Driver]Invalid cursor state
Typical Errors in DTC Output When
a. Firewall Has Ports Closed
-OR-
b. Bad WINS/DNS entries
-OR-
c. Misconfigured network
-OR-
d. Misconfigured SQL Server machine that has multiple netcards.
To my knowledge, my PC is the only one here (out of hundreds) that
flunks the dtctester.
From all appearances, my PC appears to be configured identically to
those of many other people here who are not experiencing any problems.
Specifically, I've checked all MSDTC registry settings of which I've
read, I've been into Component Services and checked the properties of
anything msdtc related, and I've ensured that the services I need are
actually running. I'm running XP, but I have the firewall turned off,
and have never installed any third party firewall. My network
connectivity is ok. I can see the target machine, and can even access
the database to which I am trying to connect and do whatever I want,
so long as I don't use distributed transactions. The version of msdtc
that I am using is identical to those of everyone else around here.
The latest advice I'm getting is to reinstall XP and hope for the
best. Seems pretty drastic to me, especially seeing how it's no
guarantee! Does anyone out there have any idea what could be causing
this? General consensus is that it is some stupid check box somewhere,
but we've pretty much run out of ideas where to look.
-Dave
I have read dozens of emails and solutions to this and similar issues
and tried them all, and nothing seems to work.
Dave, I am having the same problem here. Have you found a resolution to this. Just curious.
Cory
My machine is unable to establish a connection for the purposes of
making distributed transactions. The problem appears to be that my
machine is blocking the machine to which I am trying to connect from
establishing RPC Binding with my machine. Here's a message from my
Event Viewer:
MS DTC is unable to communicate with MS DTC on a remote system. MS
DTC on the primary system established an RPC binding with MS DTC on
the secondary system. However, the secondary system did not create
the reverse RPC binding to the primary MS DTC system before the
timeout period expired. Please ensure that there is network
connectivity between the two systems. Error
Specifics:d:\nt_qxp\com\com1x\dtc\dtc\cm\src\cso.c pp:1977, CmdLine:
C:\WINNT\System32\msdtc.exe, Pid: 1300
No Callstack (0)
What's curious is that my PC is the ONLY one in our network that has
this problem.
I've run dtctester againat various machines using various DSNs and
ALWAYS get the following:
Error:
SQLSTATE=25S12,Native error=-2147168242,msg='[Microsoft][ODBC SQL
Server Driver]Distributed transaction error'
Error:
SQLSTATE=24000,Native error=0,msg=[Microsoft][ODBC SQL Server
Driver]Invalid cursor state
Typical Errors in DTC Output When
a. Firewall Has Ports Closed
-OR-
b. Bad WINS/DNS entries
-OR-
c. Misconfigured network
-OR-
d. Misconfigured SQL Server machine that has multiple netcards.
To my knowledge, my PC is the only one here (out of hundreds) that
flunks the dtctester.
From all appearances, my PC appears to be configured identically to
those of many other people here who are not experiencing any problems.
Specifically, I've checked all MSDTC registry settings of which I've
read, I've been into Component Services and checked the properties of
anything msdtc related, and I've ensured that the services I need are
actually running. I'm running XP, but I have the firewall turned off,
and have never installed any third party firewall. My network
connectivity is ok. I can see the target machine, and can even access
the database to which I am trying to connect and do whatever I want,
so long as I don't use distributed transactions. The version of msdtc
that I am using is identical to those of everyone else around here.
The latest advice I'm getting is to reinstall XP and hope for the
best. Seems pretty drastic to me, especially seeing how it's no
guarantee! Does anyone out there have any idea what could be causing
this? General consensus is that it is some stupid check box somewhere,
but we've pretty much run out of ideas where to look.
-Dave
I have read dozens of emails and solutions to this and similar issues
and tried them all, and nothing seems to work.
Dave, I am having the same problem here. Have you found a resolution to this. Just curious.
Cory
DTC Problem - Unable to begin a transaction
I have a strange one. I have 2 Win2K3 servers, one running SQL 2K5 and the
other 2K SP4. From the 2K5 SQL Server I issue the following query ...
declare @.tmpStr varchar(2000);
declare @.ib table (EventType nvarchar(30), Parameters int, EventInfo
nvarchar(255));
set @.tmpstr = 'exec(''dbcc inputbuffer(71) WITH NO_INFOMSGS'') at
[SQL200Server];';
insert into @.ib
exec (@.tmpStr);
and I get the following error messages ...
OLE DB provider "SQLNCLI" for linked server "SQL2000Server" returned message
"No transaction is active.".
Msg 7391, Level 16, State 2, Line 1
The operation could not be performed because OLE DB provider "SQLNCLI" for
linked server "SQL2000Server" was unable to begin a distributed transaction.
If I simply comment out the 'insert into @.ib' line, it works fine. We
apparently still have something misconfigured in DTC between the servers, bu
t
I can't figure out what? Any ideas anyone? Thanks in advance.Arghknork wrote:
> If I simply comment out the 'insert into @.ib' line, it works fine. We
> apparently still have something misconfigured in DTC between the servers,
but
> I can't figure out what? Any ideas anyone? Thanks in advance.
>
Network access to MSDTC is disabled by default on a Windows 2003 Server
machine.
http://blogs.msdn.com/mab/archive/2.../30/508273.aspx|||Arghknork wrote:
> If I simply comment out the 'insert into @.ib' line, it works fine. We
> apparently still have something misconfigured in DTC between the servers,
but
> I can't figure out what? Any ideas anyone? Thanks in advance.
>
Network access to MSDTC is disabled by default on a Windows 2003 Server
machine.
http://blogs.msdn.com/mab/archive/2.../30/508273.aspx|||True, and we have it enabled. This has to be something more subtile than
that. Both these machines participate in other DTC activity with other
servers, they just don't want to play nice together in this one specific
incident. As I mentioned, I can comment out the onbe line and get a correct
response. It's only when I try to return the result set back into a table
variable that I get the failure. Thanks for the response.
"Tracy McKibben" wrote:
> Arghknork wrote:
> Network access to MSDTC is disabled by default on a Windows 2003 Server
> machine.
> http://blogs.msdn.com/mab/archive/2.../30/508273.aspx
>|||True, and we have it enabled. This has to be something more subtile than
that. Both these machines participate in other DTC activity with other
servers, they just don't want to play nice together in this one specific
incident. As I mentioned, I can comment out the onbe line and get a correct
response. It's only when I try to return the result set back into a table
variable that I get the failure. Thanks for the response.
"Tracy McKibben" wrote:
> Arghknork wrote:
> Network access to MSDTC is disabled by default on a Windows 2003 Server
> machine.
> http://blogs.msdn.com/mab/archive/2.../30/508273.aspx
>
other 2K SP4. From the 2K5 SQL Server I issue the following query ...
declare @.tmpStr varchar(2000);
declare @.ib table (EventType nvarchar(30), Parameters int, EventInfo
nvarchar(255));
set @.tmpstr = 'exec(''dbcc inputbuffer(71) WITH NO_INFOMSGS'') at
[SQL200Server];';
insert into @.ib
exec (@.tmpStr);
and I get the following error messages ...
OLE DB provider "SQLNCLI" for linked server "SQL2000Server" returned message
"No transaction is active.".
Msg 7391, Level 16, State 2, Line 1
The operation could not be performed because OLE DB provider "SQLNCLI" for
linked server "SQL2000Server" was unable to begin a distributed transaction.
If I simply comment out the 'insert into @.ib' line, it works fine. We
apparently still have something misconfigured in DTC between the servers, bu
t
I can't figure out what? Any ideas anyone? Thanks in advance.Arghknork wrote:
> If I simply comment out the 'insert into @.ib' line, it works fine. We
> apparently still have something misconfigured in DTC between the servers,
but
> I can't figure out what? Any ideas anyone? Thanks in advance.
>
Network access to MSDTC is disabled by default on a Windows 2003 Server
machine.
http://blogs.msdn.com/mab/archive/2.../30/508273.aspx|||Arghknork wrote:
> If I simply comment out the 'insert into @.ib' line, it works fine. We
> apparently still have something misconfigured in DTC between the servers,
but
> I can't figure out what? Any ideas anyone? Thanks in advance.
>
Network access to MSDTC is disabled by default on a Windows 2003 Server
machine.
http://blogs.msdn.com/mab/archive/2.../30/508273.aspx|||True, and we have it enabled. This has to be something more subtile than
that. Both these machines participate in other DTC activity with other
servers, they just don't want to play nice together in this one specific
incident. As I mentioned, I can comment out the onbe line and get a correct
response. It's only when I try to return the result set back into a table
variable that I get the failure. Thanks for the response.
"Tracy McKibben" wrote:
> Arghknork wrote:
> Network access to MSDTC is disabled by default on a Windows 2003 Server
> machine.
> http://blogs.msdn.com/mab/archive/2.../30/508273.aspx
>|||True, and we have it enabled. This has to be something more subtile than
that. Both these machines participate in other DTC activity with other
servers, they just don't want to play nice together in this one specific
incident. As I mentioned, I can comment out the onbe line and get a correct
response. It's only when I try to return the result set back into a table
variable that I get the failure. Thanks for the response.
"Tracy McKibben" wrote:
> Arghknork wrote:
> Network access to MSDTC is disabled by default on a Windows 2003 Server
> machine.
> http://blogs.msdn.com/mab/archive/2.../30/508273.aspx
>
DTC Problem - Unable to begin a transaction
I have a strange one. I have 2 Win2K3 servers, one running SQL 2K5 and the
other 2K SP4. From the 2K5 SQL Server I issue the following query ...
declare @.tmpStr varchar(2000);
declare @.ib table (EventType nvarchar(30), Parameters int, EventInfo
nvarchar(255));
set @.tmpstr = 'exec(''dbcc inputbuffer(71) WITH NO_INFOMSGS'') at
[SQL200Server];';
insert into @.ib
exec (@.tmpStr);
and I get the following error messages ...
OLE DB provider "SQLNCLI" for linked server "SQL2000Server" returned message
"No transaction is active.".
Msg 7391, Level 16, State 2, Line 1
The operation could not be performed because OLE DB provider "SQLNCLI" for
linked server "SQL2000Server" was unable to begin a distributed transaction.
If I simply comment out the 'insert into @.ib' line, it works fine. We
apparently still have something misconfigured in DTC between the servers, but
I can't figure out what? Any ideas anyone? Thanks in advance.Arghknork wrote:
> If I simply comment out the 'insert into @.ib' line, it works fine. We
> apparently still have something misconfigured in DTC between the servers, but
> I can't figure out what? Any ideas anyone? Thanks in advance.
>
Network access to MSDTC is disabled by default on a Windows 2003 Server
machine.
http://blogs.msdn.com/mab/archive/2005/12/30/508273.aspx|||True, and we have it enabled. This has to be something more subtile than
that. Both these machines participate in other DTC activity with other
servers, they just don't want to play nice together in this one specific
incident. As I mentioned, I can comment out the onbe line and get a correct
response. It's only when I try to return the result set back into a table
variable that I get the failure. Thanks for the response.
"Tracy McKibben" wrote:
> Arghknork wrote:
> > If I simply comment out the 'insert into @.ib' line, it works fine. We
> > apparently still have something misconfigured in DTC between the servers, but
> > I can't figure out what? Any ideas anyone? Thanks in advance.
> >
> >
> Network access to MSDTC is disabled by default on a Windows 2003 Server
> machine.
> http://blogs.msdn.com/mab/archive/2005/12/30/508273.aspx
>
other 2K SP4. From the 2K5 SQL Server I issue the following query ...
declare @.tmpStr varchar(2000);
declare @.ib table (EventType nvarchar(30), Parameters int, EventInfo
nvarchar(255));
set @.tmpstr = 'exec(''dbcc inputbuffer(71) WITH NO_INFOMSGS'') at
[SQL200Server];';
insert into @.ib
exec (@.tmpStr);
and I get the following error messages ...
OLE DB provider "SQLNCLI" for linked server "SQL2000Server" returned message
"No transaction is active.".
Msg 7391, Level 16, State 2, Line 1
The operation could not be performed because OLE DB provider "SQLNCLI" for
linked server "SQL2000Server" was unable to begin a distributed transaction.
If I simply comment out the 'insert into @.ib' line, it works fine. We
apparently still have something misconfigured in DTC between the servers, but
I can't figure out what? Any ideas anyone? Thanks in advance.Arghknork wrote:
> If I simply comment out the 'insert into @.ib' line, it works fine. We
> apparently still have something misconfigured in DTC between the servers, but
> I can't figure out what? Any ideas anyone? Thanks in advance.
>
Network access to MSDTC is disabled by default on a Windows 2003 Server
machine.
http://blogs.msdn.com/mab/archive/2005/12/30/508273.aspx|||True, and we have it enabled. This has to be something more subtile than
that. Both these machines participate in other DTC activity with other
servers, they just don't want to play nice together in this one specific
incident. As I mentioned, I can comment out the onbe line and get a correct
response. It's only when I try to return the result set back into a table
variable that I get the failure. Thanks for the response.
"Tracy McKibben" wrote:
> Arghknork wrote:
> > If I simply comment out the 'insert into @.ib' line, it works fine. We
> > apparently still have something misconfigured in DTC between the servers, but
> > I can't figure out what? Any ideas anyone? Thanks in advance.
> >
> >
> Network access to MSDTC is disabled by default on a Windows 2003 Server
> machine.
> http://blogs.msdn.com/mab/archive/2005/12/30/508273.aspx
>
Subscribe to:
Posts (Atom)