Log-shipping failure

Hi All,
sql server 2000 enterprise edition, 8.00.760
Am trying to set logs-shipping between two databases on two different servers on the same domain. Am using same sql server agent account for both the servers.
After log-shipping is configured, am able to see the transaction logs being backed up in the primary server, then copied on to the secondary server folder. But when it is trying to restore the transaction logs on the secondary server, I get the following
error:
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029).
FYI, We are using compatibility level of 65 on the primary server, as this is how we want it. But I can change the compatibility level on secondary server to 80 (if its a must). Am wondering, if this is one of the reason for failure.
More information:
I have confugured it to restore in STANDBY mode and terminate any user connections. And the secondary server is used for monitoring log shipping activities.
Has anybody faced similar problem? Please advise
Thanks much
GYK
> Hi All,
> sql server 2000 enterprise edition, 8.00.760
> Am trying to set logs-shipping between two databases on two
> different servers on the same domain. Am using same sql server
> agent account for both the servers.
> After log-shipping is configured, am able to see the transaction
> logs being backed up in the primary server, then copied on to
> the secondary server folder. But when it is trying to restore the
> transaction logs on the secondary server, I get the following error:
> sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029).
> FYI, We are using compatibility level of 65 on the primary server,
> as this is how we want it. But I can change the compatibility
> level on secondary server to 80 (if its a must). Am wondering,
> if this is one of the reason for failure.
> More information:
> I have confugured it to restore in STANDBY mode and terminate
> any user connections. And the secondary server is used for
> monitoring log shipping activities.
> Has anybody faced similar problem? Please advise
> Thanks much
> GYK
Check that the sql server agent account has enough permissions on the
secondary server.
Run the sqlmaint with the parameters from the command-line and see what
errors are returned.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Log-shipping failure

Hi All,
sql server 2000 enterprise edition, 8.00.760
Am trying to set logs-shipping between two databases on two different server
s on the same domain. Am using same sql server agent account for both the se
rvers.
After log-shipping is configured, am able to see the transaction logs being
backed up in the primary server, then copied on to the secondary server fold
er. But when it is trying to restore the transaction logs on the secondary s
erver, I get the following
error:
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029).
FYI, We are using compatibility level of 65 on the primary server, as this i
s how we want it. But I can change the compatibility level on secondary serv
er to 80 (if its a must). Am wondering, if this is one of the reason for fai
lure.
More information:
I have confugured it to restore in STANDBY mode and terminate any user conne
ctions. And the secondary server is used for monitoring log shipping activit
ies.
Has anybody faced similar problem? Please advise
Thanks much
GYK> Hi All,
> sql server 2000 enterprise edition, 8.00.760
> Am trying to set logs-shipping between two databases on two
> different servers on the same domain. Am using same sql server
> agent account for both the servers.
> After log-shipping is configured, am able to see the transaction
> logs being backed up in the primary server, then copied on to
> the secondary server folder. But when it is trying to restore the
> transaction logs on the secondary server, I get the following error:
> sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029).
> FYI, We are using compatibility level of 65 on the primary server,
> as this is how we want it. But I can change the compatibility
> level on secondary server to 80 (if its a must). Am wondering,
> if this is one of the reason for failure.
> More information:
> I have confugured it to restore in STANDBY mode and terminate
> any user connections. And the secondary server is used for
> monitoring log shipping activities.
> Has anybody faced similar problem? Please advise
> Thanks much
> GYK
--
Check that the sql server agent account has enough permissions on the
secondary server.
Run the sqlmaint with the parameters from the command-line and see what
errors are returned.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

logs

SQL Server is running on a domain account.
Domain\test
On the SQL Server logs, in a given day I see multiple successful logon
attempts for domain\test.
Is that ok?
The SQL Server is running, so why do I see successful logon for domain\test?
Help!Hi,
Does the logs seems like below?
*************
2005-11-21 10:07:18.54 logon Login succeeded for user 'domain\test'.
Connection: Trusted.
2005-11-21 10:07:19.36 spid53 Using 'xpsqlbot.dll' version
'2000.80.2039' to execute extended stored procedure 'xp_qv'.
2005-11-21 10:07:28.30 logon Login succeeded for user 'domain\test'.
Connection: Trusted.
2005-11-21 10:07:28.31 logon Login succeeded for user 'domain\test'.
Connection: Trusted.
2005-11-21 10:07:28.33 logon Login succeeded for user 'domain\test'.
Connection: Trusted.
2005-11-21 10:07:28.97 spid55 Using 'xpstar.dll' version '2000.80.2039'
to execute extended stored procedure 'xp_sqlagent_monitor'.
2005-11-21 10:07:29.01 logon Login succeeded for user 'domain\test'.
Connection: Trusted.
2005-11-21 10:07:29.42 logon Login succeeded for user 'sa'. Connection:
Non-Trusted.
*************
If so, you may have enabled All / Success for SQL Audit. Please check topic
"Auditing SQL Server Activity" in BOL.
If not, would you please attach the log here?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi,
as audit levet set to all it logs everything (sucess,failour,warning and
information) it should because of Auditing level is set to all please set it
to only for Failure and Warning ... or as suggested attach it for our
references.
Regards
--
Andy Davis
Activecrypt Team
---
SQL Server Encryption Software
http://www.activecrypt.com
"docsql" wrote:

> SQL Server is running on a domain account.
> Domain\test
> On the SQL Server logs, in a given day I see multiple successful logon
> attempts for domain\test.
> Is that ok?
> The SQL Server is running, so why do I see successful logon for domain\tes
t?
> Help!
>
>

logon window

Hi,
Whenever I click on a report to open it, it asks me for my Windows user ID
and password. I am connected to my desktop using my domain account and
report server is installed on SQL Server (domain controller as well).
The report is using NT authentication method.
Does anybody know how can I get rid of the login information window?
ThanksHi,
If You are using a shared datasource then rightclick on the datasource
->open
In the credentials tab check what is the option selected it should be "Use
Windows Authentication(integrated security)" If you have windows
authentication for you Sql server. If the option selected in this tab is
"Prompt for credentials" then the report promt for user credentials every
time it launches.
Incase u are not using shared datasource then u canget the above tab from
the data tab of the reportdesigner and then browsing on the datasource
dropdown.
Leme know if this solves ur problem
Thanks,
siaj
"Alex" wrote:
> Hi,
> Whenever I click on a report to open it, it asks me for my Windows user ID
> and password. I am connected to my desktop using my domain account and
> report server is installed on SQL Server (domain controller as well).
> The report is using NT authentication method.
> Does anybody know how can I get rid of the login information window?
> Thanks
>
>|||Make sure that your IE and IIS settings are correct. Within IE go to tools
internet options and then security. You will want to make sure the RS web
site is in your local intranet zone. Once it is there, make sure that the
"User Authentication" section of the settings are set to "Automatic logon
with current username and password." This tells IE to send the username and
password to the server. On IIS make sure that "Integrated Windows
authentication" is checked for the web site and uncheck the remaining boxes.
"Alex" wrote:
> Hi,
> Whenever I click on a report to open it, it asks me for my Windows user ID
> and password. I am connected to my desktop using my domain account and
> report server is installed on SQL Server (domain controller as well).
> The report is using NT authentication method.
> Does anybody know how can I get rid of the login information window?
> Thanks
>
>|||Thanks. This one solved my problem.
"MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
news:11CE3B20-F0A0-4A9C-84D2-2DDDA6B3C226@.microsoft.com...
> Make sure that your IE and IIS settings are correct. Within IE go to tools
> internet options and then security. You will want to make sure the RS web
> site is in your local intranet zone. Once it is there, make sure that the
> "User Authentication" section of the settings are set to "Automatic logon
> with current username and password." This tells IE to send the username
and
> password to the server. On IIS make sure that "Integrated Windows
> authentication" is checked for the web site and uncheck the remaining
boxes.
>
> "Alex" wrote:
> > Hi,
> >
> > Whenever I click on a report to open it, it asks me for my Windows user
ID
> > and password. I am connected to my desktop using my domain account and
> > report server is installed on SQL Server (domain controller as well).
> > The report is using NT authentication method.
> > Does anybody know how can I get rid of the login information window?
> >
> > Thanks
> >
> >
> >|||I have the same problem... and tried your suggestions with no luck.
Administrators and users can browse the Reports application. Administrators
can view the reports, but users get an authentication prompt.
Both the Reports and ReportServer application use Windows Integrated Auth
and have Anonymous disabled.
What would the difference be if the user can view Reports but not
ReportServer? (I tried https://{server}/ReportServer and still got the prompt)
There's got to be some difference between
"Alex" wrote:
> Thanks. This one solved my problem.
> "MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
> news:11CE3B20-F0A0-4A9C-84D2-2DDDA6B3C226@.microsoft.com...
> > Make sure that your IE and IIS settings are correct. Within IE go to tools
> > internet options and then security. You will want to make sure the RS web
> > site is in your local intranet zone. Once it is there, make sure that the
> > "User Authentication" section of the settings are set to "Automatic logon
> > with current username and password." This tells IE to send the username
> and
> > password to the server. On IIS make sure that "Integrated Windows
> > authentication" is checked for the web site and uncheck the remaining
> boxes.
> >
> >
> > "Alex" wrote:
> >
> > > Hi,
> > >
> > > Whenever I click on a report to open it, it asks me for my Windows user
> ID
> > > and password. I am connected to my desktop using my domain account and
> > > report server is installed on SQL Server (domain controller as well).
> > > The report is using NT authentication method.
> > > Does anybody know how can I get rid of the login information window?
> > >
> > > Thanks
> > >
> > >
> > >
>
>|||I had to set up the user/group in question with permissions to Reports and
ReportServer in IIS.
"Peter Capazzi" wrote:
> I have the same problem... and tried your suggestions with no luck.
> Administrators and users can browse the Reports application. Administrators
> can view the reports, but users get an authentication prompt.
> Both the Reports and ReportServer application use Windows Integrated Auth
> and have Anonymous disabled.
> What would the difference be if the user can view Reports but not
> ReportServer? (I tried https://{server}/ReportServer and still got the prompt)
> There's got to be some difference between
> "Alex" wrote:
> > Thanks. This one solved my problem.
> >
> > "MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
> > news:11CE3B20-F0A0-4A9C-84D2-2DDDA6B3C226@.microsoft.com...
> > > Make sure that your IE and IIS settings are correct. Within IE go to tools
> > > internet options and then security. You will want to make sure the RS web
> > > site is in your local intranet zone. Once it is there, make sure that the
> > > "User Authentication" section of the settings are set to "Automatic logon
> > > with current username and password." This tells IE to send the username
> > and
> > > password to the server. On IIS make sure that "Integrated Windows
> > > authentication" is checked for the web site and uncheck the remaining
> > boxes.
> > >
> > >
> > > "Alex" wrote:
> > >
> > > > Hi,
> > > >
> > > > Whenever I click on a report to open it, it asks me for my Windows user
> > ID
> > > > and password. I am connected to my desktop using my domain account and
> > > > report server is installed on SQL Server (domain controller as well).
> > > > The report is using NT authentication method.
> > > > Does anybody know how can I get rid of the login information window?
> > > >
> > > > Thanks
> > > >
> > > >
> > > >
> >
> >
> >

Logon to DTS from a different domain

I have a series of DTS's that need to be executed in a certain order and therefore have created a VB app that would execute the DTS's and perform a few administrative funtions for the user if successful.

The DBA for the SQL Server has given me a certain Windows Logon and I must logon via Terminal Server when I need to gain access to the SQL Server Manager. This is where I have created the DTS's - all created and owned by that user logon with certain rights. My VB application will be run from a different user machine on a different domain and therefore has a different logon- normal Windows logon. This user does not have access to the SQL Server and the DTS's need to logon with the same logon as under which it was created.

BUT...
LoadFromSQLServer offers only a SQL or Trusted connection by which one can let the user connect. By using the Windows connection flag, the LoadFromSQLServer function now ignores the logon username & password and posts the normal Windows logon. Obviously, the logon now fails for the user.

How can I let the LoadFromSQLServer funtion logon to the DTS Package with a different domain, username & password than the local Windows Logon information ?

GrahamAnybody out there ?

Logon failure: the user has not been granted the requested logon t

I get the following error when I try running a report using Reporting
Services 2005. The Data Source gets to SQL Server using a domain account. The
Application Pool is running under NETWORK SERVICE.
I see a lot of postings about allowing for Logon Locally. I am sure this
could fix the issue, but why is that standard practice? I don't allow that
for impersonating a user in a standard web application (with web.config --
impersonate user).
===== Error ========= An error has occurred during report processing.
Cannot impersonate user for data source 'DataSourceName'.
Logon failed.
Logon failure: the user has not been granted the requested logon type at
this computer. (Exception from HRESULT: 0x80070569)We don't use logon locally rights...
Instead, we grant NETWORK SERVICE account the right to connect to the SQL
Server database (the specific database) instead.
Some administrators would flip out if they had to change their local
security policy. At least as a DBA I can make this change without having to
involve layers of people to get it implemented.
=-Chris
"Sanjay T" <SanjayT@.discussions.microsoft.com> wrote in message
news:2D831614-9BF9-4C7A-B290-13A1DCD23498@.microsoft.com...
>I get the following error when I try running a report using Reporting
> Services 2005. The Data Source gets to SQL Server using a domain account.
> The
> Application Pool is running under NETWORK SERVICE.
> I see a lot of postings about allowing for Logon Locally. I am sure this
> could fix the issue, but why is that standard practice? I don't allow that
> for impersonating a user in a standard web application (with web.config --
> impersonate user).
>
> ===== Error =========> An error has occurred during report processing.
> Cannot impersonate user for data source 'DataSourceName'.
> Logon failed.
> Logon failure: the user has not been granted the requested logon type at
> this computer. (Exception from HRESULT: 0x80070569)

logon failure error in Reporting Services (rskeymgmt error)

Hi,
I have Reporting Services 2000 installed and I have a remote report server
database.
The Report Server is configured to use a domain user account to connect to
the report server database.
The password of the domain user account is changed a few days ago and I
updated the ReportServerConfig using rsconfig utility.
But, I am still getting the error logon failed error :
â'The report server cannot open a connection to the report server database.
The logon failed. (rsReportServerDatabaseLogonFailed) Get Online Help
Logon failure: unknown user name or bad password.
When I tried to take a backup (extract) of the existing symmetric keys using
rskeymgmt utility, I get the error, unable to connect to the database.
Can somebody provide me the resolution? Can I delete the keys without taking
a backup?
Thanks,
MujirDid you get this resolved we are experiencing the same thing?
"Mujir" wrote:
> Hi,
>
> I have Reporting Services 2000 installed and I have a remote report server
> database.
> The Report Server is configured to use a domain user account to connect to
> the report server database.
>
> The password of the domain user account is changed a few days ago and I
> updated the ReportServerConfig using rsconfig utility.
> But, I am still getting the error logon failed error :
> â'The report server cannot open a connection to the report server database.
> The logon failed. (rsReportServerDatabaseLogonFailed) Get Online Help
> Logon failure: unknown user name or bad password.
>
> When I tried to take a backup (extract) of the existing symmetric keys using
> rskeymgmt utility, I get the error, unable to connect to the database.
> Can somebody provide me the resolution? Can I delete the keys without taking
> a backup?
>
> Thanks,
> Mujir
>|||Not exactly, I configured it to use a different account and it works now.
"OriginalStealth" wrote:
> Did you get this resolved we are experiencing the same thing?
> "Mujir" wrote:
> > Hi,
> >
> >
> >
> > I have Reporting Services 2000 installed and I have a remote report server
> > database.
> >
> > The Report Server is configured to use a domain user account to connect to
> > the report server database.
> >
> >
> >
> > The password of the domain user account is changed a few days ago and I
> > updated the ReportServerConfig using rsconfig utility.
> >
> > But, I am still getting the error logon failed error :
> >
> > â'The report server cannot open a connection to the report server database.
> > The logon failed. (rsReportServerDatabaseLogonFailed) Get Online Help
> >
> > Logon failure: unknown user name or bad password.
> >
> >
> >
> > When I tried to take a backup (extract) of the existing symmetric keys using
> > rskeymgmt utility, I get the error, unable to connect to the database.
> >
> > Can somebody provide me the resolution? Can I delete the keys without taking
> > a backup?
> >
> >
> > Thanks,
> > Mujir
> >

Login With Domain Account

I doing some testing with security and ran into the following problem.

I want to log into the SQL server (from Query Analyzer) using my
domain account. To allow this, I went into Logins section in
Enterprise Manager and added my user account as a Windows User.

If I set Analyzer to use Windows authentication I am to log in with no
problems. But if it is set to SQL Server authentication and I type in
my username (in the format domain\username or username@.domain) and
password I get a login error.

Is there a way to login in to SQL using domain account without using
windows authentication?

Thanks,
JasonHi

If you are wanting to use the windows accounts to log into the database
server, then you will have to use windows authentication.

John

"Jason" <JayCallas@.hotmail.com> wrote in message
news:f01a7c89.0407010728.1ba158c2@.posting.google.c om...
> I doing some testing with security and ran into the following problem.
> I want to log into the SQL server (from Query Analyzer) using my
> domain account. To allow this, I went into Logins section in
> Enterprise Manager and added my user account as a Windows User.
> If I set Analyzer to use Windows authentication I am to log in with no
> problems. But if it is set to SQL Server authentication and I type in
> my username (in the format domain\username or username@.domain) and
> password I get a login error.
> Is there a way to login in to SQL using domain account without using
> windows authentication?
> Thanks,
> Jason|||Jason (JayCallas@.hotmail.com) writes:
> If I set Analyzer to use Windows authentication I am to log in with no
> problems. But if it is set to SQL Server authentication and I type in
> my username (in the format domain\username or username@.domain) and
> password I get a login error.

To log in with SQL authentication, you first need to create an SQL
login with sp_addlogin.

> Is there a way to login in to SQL using domain account without using
> windows authentication?

No. I tried:

sp_addlogin '[KESMETS\Sommar]'

and was rewarded with:

Server: Msg 15006, Level 16, State 1, Procedure sp_addlogin, Line 42
'[KESMETS\Sommar]' is not a valid name because it contains invalid
characters.

And in case, that would not be a reasonable thing to do.

What SQL authentication is, is a username and password defined in SQL
Server only. This is generally more unsafe than Windows authentication,
because of two reasons:
1) There is no protection against brute-force attacks.
2) Passwords are easy to sniff, because encryption is poor.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

Login to SQL with non domain account

I have a problem accessing a SQL instance from a VB script that uses a SQL
user, and is executed with a local computer user.
When I use the same VB script while logged on with any domain user it
executes successfully.
All SQL tools like query analyzer and enterprise admin have not problems.
What can cause this problem?
Any help would be appreciated.
Thanks in advance,
Ido Friedman
Hi,
Looks liks your SQL Server is setup for Windows Authentication only. In that
case to communicate to
SQL Server you may need to login to client with an domain user which has
access to SQL Server. Incase
if you can not do that then change the authetication mode to Windows and SQL
Server authentication.
In this you could connect to SQL Server using SQL Server Authentication.
Thanks
Hari
"Ido friedman" <Idofriedman@.discussions.microsoft.com> wrote in message
news:85A4A648-23E0-4AF6-870D-BE7380734DBC@.microsoft.com...
>I have a problem accessing a SQL instance from a VB script that uses a SQL
> user, and is executed with a local computer user.
> When I use the same VB script while logged on with any domain user it
> executes successfully.
> All SQL tools like query analyzer and enterprise admin have not problems.
> What can cause this problem?
> Any help would be appreciated.
>
> Thanks in advance,
> Ido Friedman

Login to SQL Server

I have registered SQL server instance (SQLServer1) in SQL Server group,
and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
to connect usinng string:
"PROVIDER=SQLOLEDB.1;DATA
SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx ;"
i'm geting the message:
"Login failed for user 'ABCABC'. Reason: Not associated with a trusted
SQL Server connection"
Why is that so?
thanks.
*** Sent via Developersdex http://www.codecomments.com ***
Seems like SQL Server only accepts Windows logins.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"George Ivanov" <gsivanov@.yahoo.com> wrote in message news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx ;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***
|||Hi George
This connection string will connect using SQL authentication. If you want
Domain authentication you must use something similar to
"Persist Security Info=False;Integrated
Security=SSPI;database=northwind;server=mySQLServe r"
Integrated Security=SSPI; is the key item here and means that the already
domain authenticated user who is starting your application will be used to
access SQL server. This could be the interactive user on the desktop, IIS or
another application so you will need to make sure that whatever starts your
application is already logged on with the required account.
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"George Ivanov" <gsivanov@.yahoo.com> wrote in message
news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx ;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***
|||It seems like you are using Windows user (you have provide domain name on
your message) not sql user.
But it seems on your connection string you are using sql user.
So if you want to use Trusted Connection you need to change your connection
string.
Check out:
http://www.connectionstrings.com/
"George Ivanov" wrote:

> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx ;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***
>

Login to SQL Server

I have registered SQL server instance (SQLServer1) in SQL Server group,
and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
to connect usinng string:
"PROVIDER=SQLOLEDB.1;DATA
SOURCE=SQLServer1;DATABASE=DB1;UID=ABCAB
C;PWD=xxxx;"
i'm geting the message:
"Login failed for user 'ABCABC'. Reason: Not associated with a trusted
SQL Server connection"
Why is that so?
thanks.
*** Sent via Developersdex http://www.codecomments.com ***Seems like SQL Server only accepts Windows logins.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"George Ivanov" <gsivanov@.yahoo.com> wrote in message news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx
.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCAB
C;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***|||Hi George
This connection string will connect using SQL authentication. If you want
Domain authentication you must use something similar to
"Persist Security Info=False;Integrated
Security=SSPI;database=northwind;server=
mySQLServer"
Integrated Security=SSPI; is the key item here and means that the already
domain authenticated user who is starting your application will be used to
access SQL server. This could be the interactive user on the desktop, IIS or
another application so you will need to make sure that whatever starts your
application is already logged on with the required account.
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"George Ivanov" <gsivanov@.yahoo.com> wrote in message
news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCAB
C;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***|||It seems like you are using Windows user (you have provide domain name on
your message) not sql user.
But it seems on your connection string you are using sql user.
So if you want to use Trusted Connection you need to change your connection
string.
Check out:
http://www.connectionstrings.com/
"George Ivanov" wrote:

> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCAB
C;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.codecomments.com ***
>

Login to SQL Server

I have registered SQL server instance (SQLServer1) in SQL Server group,
and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
to connect usinng string:
"PROVIDER=SQLOLEDB.1;DATA
SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx;"
i'm geting the message:
"Login failed for user 'ABCABC'. Reason: Not associated with a trusted
SQL Server connection"
Why is that so?
thanks.
*** Sent via Developersdex http://www.developersdex.com ***Seems like SQL Server only accepts Windows logins.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"George Ivanov" <gsivanov@.yahoo.com> wrote in message news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.developersdex.com ***|||Hi George
This connection string will connect using SQL authentication. If you want
Domain authentication you must use something similar to
"Persist Security Info=False;Integrated
Security=SSPI;database=northwind;server=mySQLServer"
Integrated Security=SSPI; is the key item here and means that the already
domain authenticated user who is starting your application will be used to
access SQL server. This could be the interactive user on the desktop, IIS or
another application so you will need to make sure that whatever starts your
application is already logged on with the required account.
--
Nik Marshall-Blank MCSD/MCDBA
Linz, Austria
"George Ivanov" <gsivanov@.yahoo.com> wrote in message
news:On9qlKI1FHA.4032@.TK2MSFTNGP15.phx.gbl...
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.developersdex.com ***|||It seems like you are using Windows user (you have provide domain name on
your message) not sql user.
But it seems on your connection string you are using sql user.
So if you want to use Trusted Connection you need to change your connection
string.
Check out:
http://www.connectionstrings.com/
"George Ivanov" wrote:
> I have registered SQL server instance (SQLServer1) in SQL Server group,
> and User login 'ABCABC' from domain 'DATA_DOMAIN', but when i'm trying
> to connect usinng string:
> "PROVIDER=SQLOLEDB.1;DATA
> SOURCE=SQLServer1;DATABASE=DB1;UID=ABCABC;PWD=xxxx;"
> i'm geting the message:
> "Login failed for user 'ABCABC'. Reason: Not associated with a trusted
> SQL Server connection"
> Why is that so?
> thanks.
> *** Sent via Developersdex http://www.developersdex.com ***
>

Login succeeded followed by Logon Failed

We are experiencing some strange behaviour on SQL Server 2000. Certain
members of a domain group are unable to login. The error log says something
like
2007-04-27 08:45:14.33 logon Login succeeded for user 'Accounts\joe'.
Connection: Trusted.
2007-04-27 08:45:14.33 logon Login failed for user 'Accounts\joe'.
This is only affecting certain members of the group. (The SQL Server Error
msg says the user can not access their default database).Any suggestions as
to why this might be happening.stu,
If you are granting access to the server through domain groups rather that
to individual user accounts, then Accounts\Joe may be in several groups.
If he is in a group that has been assigned a default database to which he
does not have rights, then he _may_ fail to attach to his default database.
(Why won't everyone fail? Because they are not all members of the same
group and (as far as I have been able to discover) which group will provide
the default database for the user login is not deterministic.)
Actions:
1) Check to see if any Group Logins have a default database assignment to a
database in which they have no rights. If so, correct this.
2) Explicitly set the default database for the logins that are failing.
Even though all rights will still be granted through their group
memberships, the login account default database will have priority over any
group settings.
sp_defaultdb 'Accounts\Joe', 'GoodDefaultDB'
You do not have to create an Accounts\Joe login, but the sp_defaultdb will
create one for you in this case.
RLF
"stu" <stu@.discussions.microsoft.com> wrote in message
news:F8CDE8B3-B206-473A-94C5-F6A408B61064@.microsoft.com...
> We are experiencing some strange behaviour on SQL Server 2000. Certain
> members of a domain group are unable to login. The error log says
> something
> like
> 2007-04-27 08:45:14.33 logon Login succeeded for user 'Accounts\joe'.
> Connection: Trusted.
> 2007-04-27 08:45:14.33 logon Login failed for user 'Accounts\joe'.
> This is only affecting certain members of the group. (The SQL Server Error
> msg says the user can not access their default database).Any suggestions
> as
> to why this might be happening.

Login Question

Hi
Current configuration: SQL Server with SQL Security.
A disc where the backup file is written is protected and ony the members of
the domain are allowed to write to it.
Problem when a user sends a request to the SQL Server for a backup some sort
of errors occurs because the database doesn't have the permission to write
to the disc
I would expect that although the database does the backup the permission to
write to the disc will be based on the user that sent the request.
Can anyone please clarify the situation
Thank you in advance,
Shmuel Shulman
SBS Technologies LTDHi,
No, that depends up the SQL Server service startup account.
Thanks
Hari
SQL Server MVP
"S Shulman" <smshulman@.hotmail.com> wrote in message
news:ugJEuqtlFHA.3256@.TK2MSFTNGP12.phx.gbl...
> Hi
> Current configuration: SQL Server with SQL Security.
> A disc where the backup file is written is protected and ony the members
> of the domain are allowed to write to it.
> Problem when a user sends a request to the SQL Server for a backup some
> sort of errors occurs because the database doesn't have the permission to
> write to the disc
> I would expect that although the database does the backup the permission
> to write to the disc will be based on the user that sent the request.
> Can anyone please clarify the situation
> Thank you in advance,
> Shmuel Shulman
> SBS Technologies LTD
>|||Thnks,
Shmuel
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:eoioCEulFHA.3256@.TK2MSFTNGP12.phx.gbl...
> Hi,
> No, that depends up the SQL Server service startup account.
> Thanks
> Hari
> SQL Server MVP
> "S Shulman" <smshulman@.hotmail.com> wrote in message
> news:ugJEuqtlFHA.3256@.TK2MSFTNGP12.phx.gbl...
>

login probs after restore

sql2k sp3
About once a month Im asked to take a backup from
production and restore it in a development environment.
(these are in the same domain) After the restore, I can
see the users in the db, but those users cant see the db
from tools like Query Analyzer. I have to actually drop/
recreate the users from the db and then reset the perms to
get them going. Not a big deal for me, but there has got
to be a better way? Any ideas?
TIA, ChrisRHi,
Yes, the better way is to execute "sp_change_users_login" procedure from the
restored database.
See the details of sp_change_users_login procedure in books online.
Thanks
Hari
MCDBA
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:1ab6401c44ef9$173fb1d0$a501280a@.phx.gbl...
> sql2k sp3
> About once a month Im asked to take a backup from
> production and restore it in a development environment.
> (these are in the same domain) After the restore, I can
> see the users in the db, but those users cant see the db
> from tools like Query Analyzer. I have to actually drop/
> recreate the users from the db and then reset the perms to
> get them going. Not a big deal for me, but there has got
> to be a better way? Any ideas?
> TIA, ChrisR|||Chris,
the SID in master.dbo.sysxlogins needs to map to the SID
in yourdb.dbo.sysusers and there is a sp to help you remap
them in a backup/restore scenario:
sp_change_users_login
Full details are in BOL, but this procedure will mean you
can retain the users and permissions.
HTH,
Paul Ibison|||Thanks Paul. Do you know what I use for the WINNT guys?
>--Original Message--
>Chris,
>the SID in master.dbo.sysxlogins needs to map to the SID
>in yourdb.dbo.sysusers and there is a sp to help you
remap
>them in a backup/restore scenario:
>sp_change_users_login
>Full details are in BOL, but this procedure will mean you
>can retain the users and permissions.
>HTH,
>Paul Ibison
>.
>|||Chris,
as far as I understand these should be OK as the SID won't
change as you're still in the same domain. You can use
sp_validatelogins to be sure.
Also, Rand from MS has previously posted up this link for
mapping both types of logins :
http://support.microsoft.com/default.aspx?kbid=298897
Regards,
Paul Ibison|||Also, search KB and read about sp_help_revlogin.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:1ab6401c44ef9$173fb1d0$a501280a@.phx.gbl...
> sql2k sp3
> About once a month Im asked to take a backup from
> production and restore it in a development environment.
> (these are in the same domain) After the restore, I can
> see the users in the db, but those users cant see the db
> from tools like Query Analyzer. I have to actually drop/
> recreate the users from the db and then reset the perms to
> get them going. Not a big deal for me, but there has got
> to be a better way? Any ideas?
> TIA, ChrisR

login probs after restore

sql2k sp3
About once a month Im asked to take a backup from
production and restore it in a development environment.
(these are in the same domain) After the restore, I can
see the users in the db, but those users cant see the db
from tools like Query Analyzer. I have to actually drop/
recreate the users from the db and then reset the perms to
get them going. Not a big deal for me, but there has got
to be a better way? Any ideas?
TIA, ChrisR
Hi,
Yes, the better way is to execute "sp_change_users_login" procedure from the
restored database.
See the details of sp_change_users_login procedure in books online.
Thanks
Hari
MCDBA
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:1ab6401c44ef9$173fb1d0$a501280a@.phx.gbl...
> sql2k sp3
> About once a month Im asked to take a backup from
> production and restore it in a development environment.
> (these are in the same domain) After the restore, I can
> see the users in the db, but those users cant see the db
> from tools like Query Analyzer. I have to actually drop/
> recreate the users from the db and then reset the perms to
> get them going. Not a big deal for me, but there has got
> to be a better way? Any ideas?
> TIA, ChrisR
|||Also, search KB and read about sp_help_revlogin.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:1ab6401c44ef9$173fb1d0$a501280a@.phx.gbl...
> sql2k sp3
> About once a month Im asked to take a backup from
> production and restore it in a development environment.
> (these are in the same domain) After the restore, I can
> see the users in the db, but those users cant see the db
> from tools like Query Analyzer. I have to actually drop/
> recreate the users from the db and then reset the perms to
> get them going. Not a big deal for me, but there has got
> to be a better way? Any ideas?
> TIA, ChrisR

login probs after restore

sql2k sp3
About once a month Im asked to take a backup from
production and restore it in a development environment.
(these are in the same domain) After the restore, I can
see the users in the db, but those users cant see the db
from tools like Query Analyzer. I have to actually drop/
recreate the users from the db and then reset the perms to
get them going. Not a big deal for me, but there has got
to be a better way? Any ideas?
TIA, ChrisRHi,
Yes, the better way is to execute "sp_change_users_login" procedure from the
restored database.
See the details of sp_change_users_login procedure in books online.
Thanks
Hari
MCDBA
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:1ab6401c44ef9$173fb1d0$a501280a@.phx
.gbl...
> sql2k sp3
> About once a month Im asked to take a backup from
> production and restore it in a development environment.
> (these are in the same domain) After the restore, I can
> see the users in the db, but those users cant see the db
> from tools like Query Analyzer. I have to actually drop/
> recreate the users from the db and then reset the perms to
> get them going. Not a big deal for me, but there has got
> to be a better way? Any ideas?
> TIA, ChrisR|||Also, search KB and read about sp_help_revlogin.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"ChrisR" <anonymous@.discussions.microsoft.com> wrote in message
news:1ab6401c44ef9$173fb1d0$a501280a@.phx
.gbl...
> sql2k sp3
> About once a month Im asked to take a backup from
> production and restore it in a development environment.
> (these are in the same domain) After the restore, I can
> see the users in the db, but those users cant see the db
> from tools like Query Analyzer. I have to actually drop/
> recreate the users from the db and then reset the perms to
> get them going. Not a big deal for me, but there has got
> to be a better way? Any ideas?
> TIA, ChrisR

login problems after database move

I'm trying to move a darabase from one sql2005 server to another sql2005 server within the same domain.

I have tried both backup/restore and attach/dettach and get the same problem.

With this database I'm using a SQL Server user, the user name is on both servers with exactly the same password.

On the new sql 2005 server after I have moved the database to it, if I goto security->Users and do properties on the username. It says the user is set to "Without login" how do I change this to "Login name" ?

thanks,

martin

Hi there,

I believe, from your description, that you haven't resolved the user logins after restoring your database backup to the new server.

You can read more about this in the following article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;240872

You can fix your problem by following the instructions in the article but I'm getting the impression from your post you only want to fix a single user (which is a SQL Server account & not a Windows domain account) so it might be quicker to use the "sp_change_users_login" stored procedure.

You can find more info on the stored proc in Books Online, but here's a link to it on the web:
http://msdn2.microsoft.com/en-us/library/ms174378.aspx

I believe that the syntax you have to use is:

EXEC sp_change_users_login @.Action = 'Update-One', @.userNamePattern = '<Database User Name>', @.login = '<SQL Server Login>'

Hope that helps a bit but sorry if it doesn't
|||

Thanks problem solved.

martin

Login name is <none>

Hi,
SQL 2000. I've created a login for W2K Group Mydomain\Domain admins,
and gave it access to the DB. When I add it as a user, the login name
changes to <none>. I don't understand why. It does not happen to the
other logins.
If I am missing something basic, I would appreciate a pointer to a KB
or technet article or whatever, explaining what that is.
Thanks a lot,
PeterHi Peter,
My name is Michael and I would like to thank you for using Microsoft
newsgroup.
According to your description, I understand that you create a login in SQL
Server 2000 for domain account and add this login as a user of a specific
database. However, the login name changes to <none>. In other words, the
user in the database does not match any logins. If I have misunderstood,
please feel free to let me know.
Based on my experience, it seems that you experience the orphaned user.
Logins are associated to users by the security identifier (SID), and if the
SID is inconsistent after you move a database, SQL Server may deny the user
access to the database. This problem is known as an orphaned user.
The suggestions in the following articles should address your problem.
274188 PRB: "Troubleshooting Orphaned Users" Topic in Books Online is
Incomplete
http://support.microsoft.com/?id=274188
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
Please feel free to post in the group if this solves your problem or if you
would like further assistance.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Hi Michael,
Thanks for the reply.
You understand the problem correctly.
I think I might have orphaned users as well, but I believe I the
answer to this particular problem which involves domain admins group
was in KB 819261
Regards,
Peter
On Wed, 14 Jan 2004 12:41:09 GMT, v-yshao@.online.microsoft.com ("Yuan
Shao") wrote:

quote:

---

>Hi Peter,
>My name is Michael and I would like to thank you for using Microsoft
>newsgroup.
>According to your description, I understand that you create a login in SQL
>Server 2000 for domain account and add this login as a user of a specific
>database. However, the login name changes to <none>. In other words, the
>user in the database does not match any logins. If I have misunderstood,
>please feel free to let me know.
>Based on my experience, it seems that you experience the orphaned user.
>Logins are associated to users by the security identifier (SID), and if the
>SID is inconsistent after you move a database, SQL Server may deny the user
>access to the database. This problem is known as an orphaned user.
>The suggestions in the following articles should address your problem.
>274188 PRB: "Troubleshooting Orphaned Users" Topic in Books Online is
>Incomplete
>http://support.microsoft.com/?id=274188
>314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
>http://support.microsoft.com/?id=314546
>Please feel free to post in the group if this solves your problem or if you
>would like further assistance.
>Regards,
>Michael Shao
>Microsoft Online Partner Support
>Get Secure! - www.microsoft.com/security
>This posting is provided "as is" with no warranties and confers no rights.

---

|||Hi Peter,
Thanks for your feedback. Is this orphaned user problem resolved? Did you
mean you tried the workarounds mentioned in the following article and the
problem was resolved?
819261 BUG: Error 15023, 15024 or 21002 Occurs When You Try to Add a Domain
http://support.microsoft.com/?id=819261
If not, I would like you to try the suggestions(KB 274188 & KB 314546)
mentioned in my previous post to see if it fix the orphaned user problem.
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||HI Michael,
Yes, this particular problem seems to be resolved by following the
workaround in that KB article, although I haven't had time to really
confirm it. Just looking at EM, it seems okay now.
What I was trying to say was I think there is a completely separate
problem with some other ophaned users and I will be looking at those
other articles next week. If they suggest using sp_change_users_login,
then please take a look on a problem I will post later on today on
with that sp in the subject.
Thanks,
Peter
On Thu, 15 Jan 2004 06:33:53 GMT, v-yshao@.online.microsoft.com ("Yuan
Shao") wrote:

quote:

---

>Hi Peter,
>Thanks for your feedback. Is this orphaned user problem resolved? Did you
>mean you tried the workarounds mentioned in the following article and the
>problem was resolved?
>819261 BUG: Error 15023, 15024 or 21002 Occurs When You Try to Add a Domain
>http://support.microsoft.com/?id=819261
>If not, I would like you to try the suggestions(KB 274188 & KB 314546)
>mentioned in my previous post to see if it fix the orphaned user problem.
>I am looking forward to hearing from you soon.
>Regards,
>Michael Shao
>Microsoft Online Partner Support
>Get Secure! - www.microsoft.com/security
>This posting is provided "as is" with no warranties and confers no rights.

---