Showing posts with label configured. Show all posts
Showing posts with label configured. Show all posts

Tuesday, March 20, 2012

Connection Managers are recognized after migrating to another server

Hi,

My database admin just migrated my packages from development to user testing server.

My packages configured to read the connection manager properties from the .dtsconfig.

But I am getting "The connection "CRPRDNMSQEZ.CIReporting2" is not found"

CRPRDNMSQEZ.CIReporting2 is being my connection manager.

I did find and replace server name in the dtsconfig but I guess it didn't work.

Any help is appreciated.

At a guess your connection manager name contained the orginal server name. The connection manager's connection string property ( you may have used other properties such as ServerName) would also have included the server name. When you did the find and replace you change both the connection name and the property values. The connection name should not have changed as that is the object in the package that you are trying to address.

For example take this config file snippet -

<Configuration ConfiguredType="Property" Path="\Package.Connections[ConnName].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=MachineNameInstance;User ID=FunnyName;Password=somethingsecure;</ConfiguredValue>
</Configuration>

ConnName is the connection name, what you see in the Connections tray in the package.

MachineNameInstance is the bit to change. It is probably if you just accepted the defaults the designer gave you that your config file looked a bit like this-

<Configuration ConfiguredType="Property" Path="\Package.Connections[CRPRDNMSQEZ.CIReporting2].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=CRPRDNMSQEZ;Initial Catalog=CIReporting2</ConfiguredValue>
</Configuration>

Doing a find and replace on CRPRDNMSQEZ would have found two hits, one of them being incorrect from your point of view. I strongly recomend when building packages you name things such as connections with functional or logical names, not physical names. It means the name continues to sensible over entire the package lifetime, e.g.

<Configuration ConfiguredType="Property" Path="\Package.Connections[DWReportServer].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=CRPRDNMSQEZ;Initial Catalog=CIReporting2</ConfiguredValue>
</Configuration>

|||Sounds like the name of the connection manager in the .dtsconfig file does not match the name of a connection manager inside the package. Double check that it does.

Connection Managers are NOT recognized after migrating to another server

Hi,

My database admin just migrated my packages from development to user testing server.

My packages configured to read the connection manager properties from the .dtsconfig.

But I am getting "The connection "CRPRDNMSQEZ.CIReporting2" is not found"

CRPRDNMSQEZ.CIReporting2 is being my connection manager.

I did find and replace server name in the dtsconfig but I guess it didn't work.

Any help is appreciated.

At a guess your connection manager name contained the orginal server name. The connection manager's connection string property ( you may have used other properties such as ServerName) would also have included the server name. When you did the find and replace you change both the connection name and the property values. The connection name should not have changed as that is the object in the package that you are trying to address.

For example take this config file snippet -

<Configuration ConfiguredType="Property" Path="\Package.Connections[ConnName].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=MachineNameInstance;User ID=FunnyName;Password=somethingsecure;</ConfiguredValue>
</Configuration>

ConnName is the connection name, what you see in the Connections tray in the package.

MachineNameInstance is the bit to change. It is probably if you just accepted the defaults the designer gave you that your config file looked a bit like this-

<Configuration ConfiguredType="Property" Path="\Package.Connections[CRPRDNMSQEZ.CIReporting2].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=CRPRDNMSQEZ;Initial Catalog=CIReporting2</ConfiguredValue>
</Configuration>

Doing a find and replace on CRPRDNMSQEZ would have found two hits, one of them being incorrect from your point of view. I strongly recomend when building packages you name things such as connections with functional or logical names, not physical names. It means the name continues to sensible over entire the package lifetime, e.g.

<Configuration ConfiguredType="Property" Path="\Package.Connections[DWReportServer].Properties[ConnectionString]" ValueType="String">
<ConfiguredValue>Data Source=CRPRDNMSQEZ;Initial Catalog=CIReporting2</ConfiguredValue>
</Configuration>

|||Sounds like the name of the connection manager in the .dtsconfig file does not match the name of a connection manager inside the package. Double check that it does.sqlsql

Monday, March 19, 2012

Connection Issue

Hello EveryBody,
If SQL SERVER is configured as a Maximun concurrent user connections = 1 (I
know 0 = unlimited) in Connection tab of server property ? Who will able to
login to server ?
Because i have a similar case and not able to login with any other sql
server Login.
Is SQL SERVER admin (sa) will able to login ?
Pls let me know
I assume your single login is being used by Agent when it starts up so
nobody will be able to log in.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"mvp" <mvp@.discussions.microsoft.com> wrote in message
news:88C5F9E7-30C7-4B59-A9F5-06BDBF159CA7@.microsoft.com...
> Hello EveryBody,
> If SQL SERVER is configured as a Maximun concurrent user connections = 1
> (I
> know 0 = unlimited) in Connection tab of server property ? Who will able
> to
> login to server ?
> Because i have a similar case and not able to login with any other sql
> server Login.
> Is SQL SERVER admin (sa) will able to login ?
> Pls let me know

Connection Issue

Hello EveryBody,
If SQL SERVER is configured as a Maximun concurrent user connections = 1 (I
know 0 = unlimited) in Connection tab of server property ? Who will able to
login to server ?
Because i have a similar case and not able to login with any other sql
server Login.
Is SQL SERVER admin (sa) will able to login ?
Pls let me knowI assume your single login is being used by Agent when it starts up so
nobody will be able to log in.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"mvp" <mvp@.discussions.microsoft.com> wrote in message
news:88C5F9E7-30C7-4B59-A9F5-06BDBF159CA7@.microsoft.com...
> Hello EveryBody,
> If SQL SERVER is configured as a Maximun concurrent user connections = 1
> (I
> know 0 = unlimited) in Connection tab of server property ? Who will able
> to
> login to server ?
> Because i have a similar case and not able to login with any other sql
> server Login.
> Is SQL SERVER admin (sa) will able to login ?
> Pls let me know

Sunday, February 19, 2012

Connection : trusted

Hi all, in one of my newly configured SQL server logs, I found a error
message like this:
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server
connection.
Also in both of my new servers , SQL server logs following message repeated
all the time with differefnt date.
Login succeeded for user 'domain\user1'. Connection: Trusted.
And I couldn't find any similar log messages from the current production
server.
Any ideas? did I do something wrong when I set up new servers?
Thanks a lot.
Your server is not configures for mixed authentication, that why he is
accepting domain users but not the SQL Users:
http://msdn.microsoft.com/library/de...urity_47u6.asp
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Catelin Wang" <CatelinWang@.discussions.microsoft.com> schrieb im
Newsbeitrag news:C3AF754C-DF7F-4D5F-A75E-2A11F9D9559A@.microsoft.com...
> Hi all, in one of my newly configured SQL server logs, I found a error
> message like this:
> Login failed for user 'sa'. Reason: Not associated with a trusted SQL
> Server
> connection.
> Also in both of my new servers , SQL server logs following message
> repeated
> all the time with differefnt date.
> Login succeeded for user 'domain\user1'. Connection: Trusted.
> And I couldn't find any similar log messages from the current production
> server.
> Any ideas? did I do something wrong when I set up new servers?
> Thanks a lot.
|||thanks. But my production server is using the same authentication, why I did
not see the same logs messages?
"Jens Sü?meyer" wrote:

> Your server is not configures for mixed authentication, that why he is
> accepting domain users but not the SQL Users:
> http://msdn.microsoft.com/library/de...urity_47u6.asp
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Catelin Wang" <CatelinWang@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:C3AF754C-DF7F-4D5F-A75E-2A11F9D9559A@.microsoft.com...
>
>
|||Then you have not set the same security options for the new server.
Apparently one of the servers is set to audit all login attempts, the other
is set to audit successful logins.
|||You are right, I set different audit trace for the two servers, but I how can
I find if I set to log successful logins ?
Thanks a lot!
"Scott Morris" wrote:

> Then you have not set the same security options for the new server.
> Apparently one of the servers is set to audit all login attempts, the other
> is set to audit successful logins.
>
>
|||Documentation? BOL -> Search -> "login failure"
|||Thnaks, I found it.
"Scott Morris" wrote:

> Documentation? BOL -> Search -> "login failure"
>
>

Connection : trusted

Hi all, in one of my newly configured SQL server logs, I found a error
message like this:
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server
connection.
Also in both of my new servers , SQL server logs following message repeated
all the time with differefnt date.
Login succeeded for user 'domain\user1'. Connection: Trusted.
And I couldn't find any similar log messages from the current production
server.
Any ideas? did I do something wrong when I set up new servers?
Thanks a lot.Your server is not configures for mixed authentication, that why he is
accepting domain users but not the SQL Users:
http://msdn.microsoft.com/library/d...>
ity_47u6.asp
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Catelin Wang" <CatelinWang@.discussions.microsoft.com> schrieb im
Newsbeitrag news:C3AF754C-DF7F-4D5F-A75E-2A11F9D9559A@.microsoft.com...
> Hi all, in one of my newly configured SQL server logs, I found a error
> message like this:
> Login failed for user 'sa'. Reason: Not associated with a trusted SQL
> Server
> connection.
> Also in both of my new servers , SQL server logs following message
> repeated
> all the time with differefnt date.
> Login succeeded for user 'domain\user1'. Connection: Trusted.
> And I couldn't find any similar log messages from the current production
> server.
> Any ideas? did I do something wrong when I set up new servers?
> Thanks a lot.|||thanks. But my production server is using the same authentication, why I did
not see the same logs messages?
"Jens Sü?meyer" wrote:

> Your server is not configures for mixed authentication, that why he is
> accepting domain users but not the SQL Users:
> http://msdn.microsoft.com/library/d...
urity_47u6.asp
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Catelin Wang" <CatelinWang@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:C3AF754C-DF7F-4D5F-A75E-2A11F9D9559A@.microsoft.com...
>
>|||Then you have not set the same security options for the new server.
Apparently one of the servers is set to audit all login attempts, the other
is set to audit successful logins.|||You are right, I set different audit trace for the two servers, but I how ca
n
I find if I set to log successful logins '
Thanks a lot!
"Scott Morris" wrote:

> Then you have not set the same security options for the new server.
> Apparently one of the servers is set to audit all login attempts, the othe
r
> is set to audit successful logins.
>
>|||Documentation? BOL -> Search -> "login failure"|||Thnaks, I found it.
"Scott Morris" wrote:

> Documentation? BOL -> Search -> "login failure"
>
>

Connection : trusted

Hi all, in one of my newly configured SQL server logs, I found a error
message like this:
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server
connection.
Also in both of my new servers , SQL server logs following message repeated
all the time with differefnt date.
Login succeeded for user 'domain\user1'. Connection: Trusted.
And I couldn't find any similar log messages from the current production
server.
Any ideas? did I do something wrong when I set up new servers?
Thanks a lot.Your server is not configures for mixed authentication, that why he is
accepting domain users but not the SQL Users:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_47u6.asp
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"Catelin Wang" <CatelinWang@.discussions.microsoft.com> schrieb im
Newsbeitrag news:C3AF754C-DF7F-4D5F-A75E-2A11F9D9559A@.microsoft.com...
> Hi all, in one of my newly configured SQL server logs, I found a error
> message like this:
> Login failed for user 'sa'. Reason: Not associated with a trusted SQL
> Server
> connection.
> Also in both of my new servers , SQL server logs following message
> repeated
> all the time with differefnt date.
> Login succeeded for user 'domain\user1'. Connection: Trusted.
> And I couldn't find any similar log messages from the current production
> server.
> Any ideas? did I do something wrong when I set up new servers?
> Thanks a lot.|||thanks. But my production server is using the same authentication, why I did
not see the same logs messages?
"Jens Sü�meyer" wrote:
> Your server is not configures for mixed authentication, that why he is
> accepting domain users but not the SQL Users:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_47u6.asp
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Catelin Wang" <CatelinWang@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:C3AF754C-DF7F-4D5F-A75E-2A11F9D9559A@.microsoft.com...
> > Hi all, in one of my newly configured SQL server logs, I found a error
> > message like this:
> > Login failed for user 'sa'. Reason: Not associated with a trusted SQL
> > Server
> > connection.
> >
> > Also in both of my new servers , SQL server logs following message
> > repeated
> > all the time with differefnt date.
> >
> > Login succeeded for user 'domain\user1'. Connection: Trusted.
> >
> > And I couldn't find any similar log messages from the current production
> > server.
> > Any ideas? did I do something wrong when I set up new servers?
> >
> > Thanks a lot.
>
>|||Then you have not set the same security options for the new server.
Apparently one of the servers is set to audit all login attempts, the other
is set to audit successful logins.|||You are right, I set different audit trace for the two servers, but I how can
I find if I set to log successful logins '
Thanks a lot!
"Scott Morris" wrote:
> Then you have not set the same security options for the new server.
> Apparently one of the servers is set to audit all login attempts, the other
> is set to audit successful logins.
>
>|||Documentation? BOL -> Search -> "login failure"|||Thnaks, I found it.
"Scott Morris" wrote:
> Documentation? BOL -> Search -> "login failure"
>
>

Friday, February 17, 2012

Connecting two servers

Hello there
After i create remote server on my current server i got an error:
Server 'Win2000Serv' is not configured for DATA ACCESS.
what can i do to solve it?Roy
exec sp_serveroption 'Win2000Serv' ,'data access','true'
"Roy Goldhammer" <roy@.hotmail.com> wrote in message
news:%23RfL8da9FHA.220@.TK2MSFTNGP14.phx.gbl...
> Hello there
> After i create remote server on my current server i got an error:
> Server 'Win2000Serv' is not configured for DATA ACCESS.
> what can i do to solve it?
>|||Hi,
sp_addlinkedserver
and
sp_addlinkedsrvlogin
:-)
Regards
--
Andy Davis
Activecrypt Team
---
SQL Server Encryption Software
http://www.activecrypt.com
"Roy Goldhammer" wrote:

> Hello there
> After i create remote server on my current server i got an error:
> Server 'Win2000Serv' is not configured for DATA ACCESS.
> what can i do to solve it?
>
>

Tuesday, February 14, 2012

Connecting to SQL via ODBC : How to change the default database configured with DSN

Hello All,

Does anybody know how to achive that?

<

addname="ConnectionString"connectionString="Dsn=dsn_name;uid=user;pwd=password"providerName="System.Data.Odbc" />

I have got this created by the wizard for my sqlDataSource. I am able to get data from tables in the default database specified with the DSN.

But I want to go to other database than the default.

Thanks a lot in advamce for your help!

Kazu

DSN is tied to a particular database, which in your case is the default database. You can either a) create a new DSN and link it with the database you want to connect with or b) rewrite the connection string so that you aren't using a DSN. this link should help you write the connection stringhttp://www.sqlstrings.com/SQL-Server-connection-strings.htmhttp://www.sqlstrings.com/SQL-Server-connection-strings.htm

|||

thanks. But..

> DSN is tied to a particular database...

Not really. I have finally achived what I wanted, by simply adding "Database=" parameter to the connectionstring.

|||

> DSN is tied to a particulardefault database... Wink

Sunday, February 12, 2012

Connecting to SQL Server with an alias

We have a soon-to-be legacy Sql Server called X. We have several queries on
various other servers configured to talk to X thru a linked server that go
something like:
SELECT [columnName] FROM [X].[DBName].[dbo].[TableName]
X will now be hosted on a new machine called Y.
So my question is, is there a way of aliasing our new server called "Y" so
that it can be refered to as "X"?
TIA//
I believe that you can do this using sp_addlinkedserver. Check out Books Online
(sp_addlinkedserver), the second example in the table. This suggests that you can specify some other
name for the linked server than the network name.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Newby" <Chris.Newby@.Rockcreekglobal.com> wrote in message
news:%23LXjZH6FGHA.1676@.TK2MSFTNGP09.phx.gbl...
> We have a soon-to-be legacy Sql Server called X. We have several queries on various other servers
> configured to talk to X thru a linked server that go something like:
> SELECT [columnName] FROM [X].[DBName].[dbo].[TableName]
> X will now be hosted on a new machine called Y.
> So my question is, is there a way of aliasing our new server called "Y" so that it can be refered
> to as "X"?
> TIA//
>
|||So you are using a linked server to achive the connection to the server
X. Defining a server alias within the network client tool should do the
trick.
HTH, jens Suessmeyer.

Connecting to SQL Server with an alias

We have a soon-to-be legacy Sql Server called X. We have several queries on
various other servers configured to talk to X thru a linked server that go
something like:
SELECT [columnName] FROM [X].[DBName].[dbo].[TableName]
X will now be hosted on a new machine called Y.
So my question is, is there a way of aliasing our new server called "Y" so
that it can be refered to as "X"?
TIA//I believe that you can do this using sp_addlinkedserver. Check out Books Online
(sp_addlinkedserver), the second example in the table. This suggests that you can specify some other
name for the linked server than the network name.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Newby" <Chris.Newby@.Rockcreekglobal.com> wrote in message
news:%23LXjZH6FGHA.1676@.TK2MSFTNGP09.phx.gbl...
> We have a soon-to-be legacy Sql Server called X. We have several queries on various other servers
> configured to talk to X thru a linked server that go something like:
> SELECT [columnName] FROM [X].[DBName].[dbo].[TableName]
> X will now be hosted on a new machine called Y.
> So my question is, is there a way of aliasing our new server called "Y" so that it can be refered
> to as "X"?
> TIA//
>|||So you are using a linked server to achive the connection to the server
X. Defining a server alias within the network client tool should do the
trick.
HTH, jens Suessmeyer.

Connecting to SQL Server with an alias

We have a soon-to-be legacy Sql Server called X. We have several queries on
various other servers configured to talk to X thru a linked server that go
something like:
SELECT [columnName] FROM [X].[DBName].[dbo].[TableName]
X will now be hosted on a new machine called Y.
So my question is, is there a way of aliasing our new server called "Y" so
that it can be refered to as "X"?
TIA//I believe that you can do this using sp_addlinkedserver. Check out Books Onl
ine
(sp_addlinkedserver), the second example in the table. This suggests that yo
u can specify some other
name for the linked server than the network name.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Chris Newby" <Chris.Newby@.Rockcreekglobal.com> wrote in message
news:%23LXjZH6FGHA.1676@.TK2MSFTNGP09.phx.gbl...
> We have a soon-to-be legacy Sql Server called X. We have several queries o
n various other servers
> configured to talk to X thru a linked server that go something like:
> SELECT [columnName] FROM [X].[DBName].[dbo].[TableName
]
> X will now be hosted on a new machine called Y.
> So my question is, is there a way of aliasing our new server called "Y" so
that it can be refered
> to as "X"?
> TIA//
>|||So you are using a linked server to achive the connection to the server
X. Defining a server alias within the network client tool should do the
trick.
HTH, jens Suessmeyer.