I have a laptop that authenticates locally to itself. I have the
username/password for this laptop match our small-business server network,
and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as an
INSTANCE of SQL on the laptop.
This laptop has a modem that I can also use to RAS into a customer site,
where the username is the same, but the password is different (at the same
time that I am nic'd to my local small business server network). Somehow
when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
instances on that network as well (there are 3 server instances here).
Well, I like to keep passwords the same across all my login locations, it
makes mapping netword drives a lot easier.
Last week I changed the PASSWORD at this "RAS-in" site to match, and all of
a sudden, I could no longer EM to those SERVER's. I quickly changed it back
to what it was before, and that restored the ability to see the server's
there.
If I look at the Registered SQL Server Properties on all these servers, they
are "Windows Authentication".
I am concerned about loosing access by changing the password - since I need
to support this site, but would like to get the password inline with my
"current" password.
Is there a delay before a password change at a large site propagates to all
the servers? How am I actually authenticating to three SQL boxes through a
RAS box from a laptop anyway - especially if the laptop password doesn't
match that networks password for my username?
Hope this makes sense.
Hey, I was wondering if anyone could give me a clue about this issue. I've
posted it on XP Help/Support site also but have gotten no replies.
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:eJiev2RNEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have a laptop that authenticates locally to itself. I have the
> username/password for this laptop match our small-business server network,
> and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as
an
> INSTANCE of SQL on the laptop.
> This laptop has a modem that I can also use to RAS into a customer site,
> where the username is the same, but the password is different (at the same
> time that I am nic'd to my local small business server network). Somehow
> when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
> instances on that network as well (there are 3 server instances here).
> Well, I like to keep passwords the same across all my login locations, it
> makes mapping netword drives a lot easier.
> Last week I changed the PASSWORD at this "RAS-in" site to match, and all
of
> a sudden, I could no longer EM to those SERVER's. I quickly changed it
back
> to what it was before, and that restored the ability to see the server's
> there.
> If I look at the Registered SQL Server Properties on all these servers,
they
> are "Windows Authentication".
> I am concerned about loosing access by changing the password - since I
need
> to support this site, but would like to get the password inline with my
> "current" password.
> Is there a delay before a password change at a large site propagates to
all
> the servers? How am I actually authenticating to three SQL boxes through
a
> RAS box from a laptop anyway - especially if the laptop password doesn't
> match that networks password for my username?
> Hope this makes sense.
>
Showing posts with label password. Show all posts
Showing posts with label password. Show all posts
Monday, March 19, 2012
Odd authentication issues
I have a laptop that authenticates locally to itself. I have the
username/password for this laptop match our small-business server network,
and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as an
INSTANCE of SQL on the laptop.
This laptop has a modem that I can also use to RAS into a customer site,
where the username is the same, but the password is different (at the same
time that I am nic'd to my local small business server network). Somehow
when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
instances on that network as well (there are 3 server instances here).
Well, I like to keep passwords the same across all my login locations, it
makes mapping netword drives a lot easier.
Last week I changed the PASSWORD at this "RAS-in" site to match, and all of
a sudden, I could no longer EM to those SERVER's. I quickly changed it back
to what it was before, and that restored the ability to see the server's
there.
If I look at the Registered SQL Server Properties on all these servers, they
are "Windows Authentication".
I am concerned about loosing access by changing the password - since I need
to support this site, but would like to get the password inline with my
"current" password.
Is there a delay before a password change at a large site propagates to all
the servers? How am I actually authenticating to three SQL boxes through a
RAS box from a laptop anyway - especially if the laptop password doesn't
match that networks password for my username?
Hope this makes sense.Hey, I was wondering if anyone could give me a clue about this issue. I've
posted it on XP Help/Support site also but have gotten no replies.
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:eJiev2RNEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have a laptop that authenticates locally to itself. I have the
> username/password for this laptop match our small-business server network,
> and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as
an
> INSTANCE of SQL on the laptop.
> This laptop has a modem that I can also use to RAS into a customer site,
> where the username is the same, but the password is different (at the same
> time that I am nic'd to my local small business server network). Somehow
> when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
> instances on that network as well (there are 3 server instances here).
> Well, I like to keep passwords the same across all my login locations, it
> makes mapping netword drives a lot easier.
> Last week I changed the PASSWORD at this "RAS-in" site to match, and all
of
> a sudden, I could no longer EM to those SERVER's. I quickly changed it
back
> to what it was before, and that restored the ability to see the server's
> there.
> If I look at the Registered SQL Server Properties on all these servers,
they
> are "Windows Authentication".
> I am concerned about loosing access by changing the password - since I
need
> to support this site, but would like to get the password inline with my
> "current" password.
> Is there a delay before a password change at a large site propagates to
all
> the servers? How am I actually authenticating to three SQL boxes through
a
> RAS box from a laptop anyway - especially if the laptop password doesn't
> match that networks password for my username?
> Hope this makes sense.
>
username/password for this laptop match our small-business server network,
and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as an
INSTANCE of SQL on the laptop.
This laptop has a modem that I can also use to RAS into a customer site,
where the username is the same, but the password is different (at the same
time that I am nic'd to my local small business server network). Somehow
when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
instances on that network as well (there are 3 server instances here).
Well, I like to keep passwords the same across all my login locations, it
makes mapping netword drives a lot easier.
Last week I changed the PASSWORD at this "RAS-in" site to match, and all of
a sudden, I could no longer EM to those SERVER's. I quickly changed it back
to what it was before, and that restored the ability to see the server's
there.
If I look at the Registered SQL Server Properties on all these servers, they
are "Windows Authentication".
I am concerned about loosing access by changing the password - since I need
to support this site, but would like to get the password inline with my
"current" password.
Is there a delay before a password change at a large site propagates to all
the servers? How am I actually authenticating to three SQL boxes through a
RAS box from a laptop anyway - especially if the laptop password doesn't
match that networks password for my username?
Hope this makes sense.Hey, I was wondering if anyone could give me a clue about this issue. I've
posted it on XP Help/Support site also but have gotten no replies.
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:eJiev2RNEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have a laptop that authenticates locally to itself. I have the
> username/password for this laptop match our small-business server network,
> and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as
an
> INSTANCE of SQL on the laptop.
> This laptop has a modem that I can also use to RAS into a customer site,
> where the username is the same, but the password is different (at the same
> time that I am nic'd to my local small business server network). Somehow
> when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
> instances on that network as well (there are 3 server instances here).
> Well, I like to keep passwords the same across all my login locations, it
> makes mapping netword drives a lot easier.
> Last week I changed the PASSWORD at this "RAS-in" site to match, and all
of
> a sudden, I could no longer EM to those SERVER's. I quickly changed it
back
> to what it was before, and that restored the ability to see the server's
> there.
> If I look at the Registered SQL Server Properties on all these servers,
they
> are "Windows Authentication".
> I am concerned about loosing access by changing the password - since I
need
> to support this site, but would like to get the password inline with my
> "current" password.
> Is there a delay before a password change at a large site propagates to
all
> the servers? How am I actually authenticating to three SQL boxes through
a
> RAS box from a laptop anyway - especially if the laptop password doesn't
> match that networks password for my username?
> Hope this makes sense.
>
Odd authentication issues
I have a laptop that authenticates locally to itself. I have the
username/password for this laptop match our small-business server network,
and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as an
INSTANCE of SQL on the laptop.
This laptop has a modem that I can also use to RAS into a customer site,
where the username is the same, but the password is different (at the same
time that I am nic'd to my local small business server network). Somehow
when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
instances on that network as well (there are 3 server instances here).
Well, I like to keep passwords the same across all my login locations, it
makes mapping netword drives a lot easier.
Last week I changed the PASSWORD at this "RAS-in" site to match, and all of
a sudden, I could no longer EM to those SERVER's. I quickly changed it back
to what it was before, and that restored the ability to see the server's
there.
If I look at the Registered SQL Server Properties on all these servers, they
are "Windows Authentication".
I am concerned about loosing access by changing the password - since I need
to support this site, but would like to get the password inline with my
"current" password.
Is there a delay before a password change at a large site propagates to all
the servers? How am I actually authenticating to three SQL boxes through a
RAS box from a laptop anyway - especially if the laptop password doesn't
match that networks password for my username?
Hope this makes sense.Hey, I was wondering if anyone could give me a clue about this issue. I've
posted it on XP Help/Support site also but have gotten no replies.
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:eJiev2RNEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have a laptop that authenticates locally to itself. I have the
> username/password for this laptop match our small-business server network,
> and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as
an
> INSTANCE of SQL on the laptop.
> This laptop has a modem that I can also use to RAS into a customer site,
> where the username is the same, but the password is different (at the same
> time that I am nic'd to my local small business server network). Somehow
> when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
> instances on that network as well (there are 3 server instances here).
> Well, I like to keep passwords the same across all my login locations, it
> makes mapping netword drives a lot easier.
> Last week I changed the PASSWORD at this "RAS-in" site to match, and all
of
> a sudden, I could no longer EM to those SERVER's. I quickly changed it
back
> to what it was before, and that restored the ability to see the server's
> there.
> If I look at the Registered SQL Server Properties on all these servers,
they
> are "Windows Authentication".
> I am concerned about loosing access by changing the password - since I
need
> to support this site, but would like to get the password inline with my
> "current" password.
> Is there a delay before a password change at a large site propagates to
all
> the servers? How am I actually authenticating to three SQL boxes through
a
> RAS box from a laptop anyway - especially if the laptop password doesn't
> match that networks password for my username?
> Hope this makes sense.
>
username/password for this laptop match our small-business server network,
and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as an
INSTANCE of SQL on the laptop.
This laptop has a modem that I can also use to RAS into a customer site,
where the username is the same, but the password is different (at the same
time that I am nic'd to my local small business server network). Somehow
when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
instances on that network as well (there are 3 server instances here).
Well, I like to keep passwords the same across all my login locations, it
makes mapping netword drives a lot easier.
Last week I changed the PASSWORD at this "RAS-in" site to match, and all of
a sudden, I could no longer EM to those SERVER's. I quickly changed it back
to what it was before, and that restored the ability to see the server's
there.
If I look at the Registered SQL Server Properties on all these servers, they
are "Windows Authentication".
I am concerned about loosing access by changing the password - since I need
to support this site, but would like to get the password inline with my
"current" password.
Is there a delay before a password change at a large site propagates to all
the servers? How am I actually authenticating to three SQL boxes through a
RAS box from a laptop anyway - especially if the laptop password doesn't
match that networks password for my username?
Hope this makes sense.Hey, I was wondering if anyone could give me a clue about this issue. I've
posted it on XP Help/Support site also but have gotten no replies.
"Steve Z" <szlamany@.antarescomputing_no_spam.com> wrote in message
news:eJiev2RNEHA.3636@.TK2MSFTNGP09.phx.gbl...
> I have a laptop that authenticates locally to itself. I have the
> username/password for this laptop match our small-business server network,
> and it effortlessly can open an INSTANCE of SQL on the SERVER, as well as
an
> INSTANCE of SQL on the laptop.
> This laptop has a modem that I can also use to RAS into a customer site,
> where the username is the same, but the password is different (at the same
> time that I am nic'd to my local small business server network). Somehow
> when RAS'd in to this customer, ENTERPRISE MANAGER can open the SQL
> instances on that network as well (there are 3 server instances here).
> Well, I like to keep passwords the same across all my login locations, it
> makes mapping netword drives a lot easier.
> Last week I changed the PASSWORD at this "RAS-in" site to match, and all
of
> a sudden, I could no longer EM to those SERVER's. I quickly changed it
back
> to what it was before, and that restored the ability to see the server's
> there.
> If I look at the Registered SQL Server Properties on all these servers,
they
> are "Windows Authentication".
> I am concerned about loosing access by changing the password - since I
need
> to support this site, but would like to get the password inline with my
> "current" password.
> Is there a delay before a password change at a large site propagates to
all
> the servers? How am I actually authenticating to three SQL boxes through
a
> RAS box from a laptop anyway - especially if the laptop password doesn't
> match that networks password for my username?
> Hope this makes sense.
>
Monday, March 12, 2012
ODBC via Windows authentication
Hello,
We have an internal application that accesses SQL Server 2000 via ODBC.
The connecton is established with user id and password. We recently
received a business request to allow the software to work with Windows
authentication scheme going forward. This implies that users will no
longer have passwords to login to the database. The Windows PC would
take care of the authentication.
Is there a way (perhaps a connection string) to allow ODBC to connect
to the database in this new environment? I would appreciate any tips
or pointers.<tunity5@.yahoo.com> wrote in message
news:1105712559.798067.299450@.c13g2000cwb.googlegr oups.com...
> Hello,
> We have an internal application that accesses SQL Server 2000 via ODBC.
> The connecton is established with user id and password. We recently
> received a business request to allow the software to work with Windows
> authentication scheme going forward. This implies that users will no
> longer have passwords to login to the database. The Windows PC would
> take care of the authentication.
> Is there a way (perhaps a connection string) to allow ODBC to connect
> to the database in this new environment? I would appreciate any tips
> or pointers.
There are some sample connection strings for trusted connections here:
http://www.able-consulting.com/MDAC...verForSQLServer
Simon|||I think you can call SQLConnect with an empty user name and password
information.
Also, for using SQLDriverConnect, try to add "Trusted_Connection = yes" into
your connect string.
t> The connecton is established with user id and password. We recently
t> received a business request to allow the software to work with
t> Windows authentication scheme going forward. This implies that users
t> will no longer have passwords to login to the database. The Windows
t> PC would take care of the authentication.
Igor Shekalev, http://www.sqledit.com, SQL editor with ODBC support
Saturday, February 25, 2012
ODBC password not saved in configuration file
Hi,
I have an SSIS package that pipes data from an iSeries data source to a SQL Server table. The connection manager I am using is the .Net Providers\Odbc Data Provider
When I run this SSIS package on my developer PC (from inside BIDS or using the Management Studio Execute Package Utility) it works. However when I run the package from within a SQL Server Agent Job it fails.
I have enabled logging and the error message given is:
System.Data.Odbc.OdbcException: ERROR [28000] [IBM][iSeries Access ODBC Driver]Communication link failure. comm rc=8002 - CWBSY0002 - Password for user MALLPRESS on server SMICHC is not correct, Password length = 0, Prompt Mode = Never, System IP Address = 172.16.0.4 ERROR [28000] [IBM][iSeries Access ODBC Driver]Communication link failure. comm rc=8002 - CWBSY0002 - Password for user MALLPRESS on server SMICHC is not correct, Password length = 0, Prompt Mode = Never, System IP Address = 172.16.0.4
It gives the message “Password length = 0” despite the fact that I have specified a password in the package.
To try to get around this I have added an XML configuration file to the SSIS package. In this configuration file I’ve set values for the ConnectionString, UserName, and Password.
I still get the above error about a password length of 0.
I have also tried to execute the package using dtexec, but this gives a similar error.
The SQL used to run this is:
xp_cmdshell 'dtexec /sq "\SCSRV-06\DTS Packages\Staging\StagingBranchImport"'
This has got me stumped, and I’m not sure where to go from here as these packages need to be programmatically run each morning. At the moment I am manually running them from within BIDS.
All packages that don’t use an iSeries connection manager run successfully in SQL Agent jobs.
I have also tried using the OLEDB connection manager (ibm db2 udb for iseries ibmda400 ole db provider) without success.
Any help would be very appreciated.
Thanks, Matt
SSIS will NOT store the password in the file for you. You have to edit the file manually to put the password in there. Have you done that?
-Jamie
|||Hi Jamie,
Yes I have manually edited the config file and entered the password.
Matt
|||Just to let anyone who's interested know....
I now have it working. The problem was that I did not have administrator access to the server, and so was using a network share to store the configuration file. I now how admin access to the windows server, and have moved the config file to the server's C:\, which has fixed the problem.
Matt
|||Thanks for posting the solution, I am just ran into that problem today - ODBC works fine on local machine but when I move to production I get the password length error, even though I set the password in my package. I will try the package configuration file tomorrow.
I'm having the same problem with the iSeries Access OLEDB drivers - I can't seem to get them to work. Did you ever get them to work? I'm using 5v3 iSeries Access.
ODBC password not saved in configuration file
Hi,
I have an SSIS package that pipes data from an iSeries data source to a SQL Server table. The connection manager I am using is the .Net Providers\Odbc Data Provider
When I run this SSIS package on my developer PC (from inside BIDS or using the Management Studio Execute Package Utility) it works. However when I run the package from within a SQL Server Agent Job it fails.
I have enabled logging and the error message given is:
System.Data.Odbc.OdbcException: ERROR [28000] [IBM][iSeries Access ODBC Driver]Communication link failure. comm rc=8002 - CWBSY0002 - Password for user MALLPRESS on server SMICHC is not correct, Password length = 0, Prompt Mode = Never, System IP Address = 172.16.0.4 ERROR [28000] [IBM][iSeries Access ODBC Driver]Communication link failure. comm rc=8002 - CWBSY0002 - Password for user MALLPRESS on server SMICHC is not correct, Password length = 0, Prompt Mode = Never, System IP Address = 172.16.0.4
It gives the message “Password length = 0” despite the fact that I have specified a password in the package.
To try to get around this I have added an XML configuration file to the SSIS package. In this configuration file I’ve set values for the ConnectionString, UserName, and Password.
I still get the above error about a password length of 0.
I have also tried to execute the package using dtexec, but this gives a similar error.
The SQL used to run this is:
xp_cmdshell 'dtexec /sq "\SCSRV-06\DTS Packages\Staging\StagingBranchImport"'
This has got me stumped, and I’m not sure where to go from here as these packages need to be programmatically run each morning. At the moment I am manually running them from within BIDS.
All packages that don’t use an iSeries connection manager run successfully in SQL Agent jobs.
I have also tried using the OLEDB connection manager (ibm db2 udb for iseries ibmda400 ole db provider) without success.
Any help would be very appreciated.
Thanks, Matt
SSIS will NOT store the password in the file for you. You have to edit the file manually to put the password in there. Have you done that?
-Jamie
|||
Hi Jamie,
Yes I have manually edited the config file and entered the password.
Matt
|||Just to let anyone who's interested know....
I now have it working. The problem was that I did not have administrator access to the server, and so was using a network share to store the configuration file. I now how admin access to the windows server, and have moved the config file to the server's C:\, which has fixed the problem.
Matt
|||Thanks for posting the solution, I am just ran into that problem today - ODBC works fine on local machine but when I move to production I get the password length error, even though I set the password in my package. I will try the package configuration file tomorrow.
I'm having the same problem with the iSeries Access OLEDB drivers - I can't seem to get them to work. Did you ever get them to work? I'm using 5v3 iSeries Access.
Subscribe to:
Posts (Atom)