Error 1920. Service 'ReportServer' (ReportServer) failed to start

Hello, I cannot install Reporting Services Developer Version, at the end of
the setup I got a message like:
Error 1920. Service 'ReportServer' (ReportServer) failed to start. Verify
that you have sufficient privileges to start system services.
I have SQL SP3a, IIS, .NET 2003 all in the same computer.
Just cannot find how to solve the problem, seems to be something with the
account used to start the service, but with neither the built in account, not
a computer admin account can continue. Have no problem creating the database,
just to start the service.
Help pleaseMy problem is solved; I think you only need to change the installation path
of RS during the setup, but the following are the steps I follow:
1. Uninstall RS
2. Clean all signs of RS in the registry, the service and components
Delete in the registry the entries in
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\RS Rep..
Delete the service from the command prompt
sc delete ReportServer
Delete the components in Component Services in
the control panel Administrative Tools in the COM+ Applications for the ISS
3. Install RS in a different path
I install RS in C:\Program Files\Microsoft SQL ServerRS
Also i rename the services in the setup to MSReportService, MSReports for
the
IIS part.
I have Windows XP with all in one box; I use a domain account, for the
services
and for the SQL login.

Error 18456: Login failed for user 'DOMAIN\user'

Hi,
I've just installed SQL Server 2005 Beta 2 and added Active Directory
account to our SQL Server (under Database/Security/Logins). However, when I
try to login using the Windows Authentication, I get this error message:
Login failed for user 'DOMAIN\user'. (Microsoft SQL Server, Error: 18456)
where DOMAIN\user is really my domain-account, which I rather not publish.
When I try to login using 'sa' and SQL Server Authentication there is no
problem.
I've tried to find out what error 18456 is but no luck. Could anyone help me
please?
Cheers,
ChrisI take it that either no one has ever heard of this error or that is so
common that its in every FAQ. In the latter case, could someone please point
me to a FAQ with a solution...
Cheers,
Chris
"Christoffer" <christoffer@.nospam.com> wrote in message
news:%23alyI3zjEHA.536@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I've just installed SQL Server 2005 Beta 2 and added Active Directory
> account to our SQL Server (under Database/Security/Logins). However, when
> I try to login using the Windows Authentication, I get this error message:
> Login failed for user 'DOMAIN\user'. (Microsoft SQL Server, Error: 18456)
> where DOMAIN\user is really my domain-account, which I rather not publish.
> When I try to login using 'sa' and SQL Server Authentication there is no
> problem.
> I've tried to find out what error 18456 is but no luck. Could anyone help
> me please?
> Cheers,
> Chris
>|||Error 18456 is "login failed for user xxx"...the error you
are getting. You have something incorrect with adding the
windows account to the logins or the permissions you have
set for the login. Try deleting the login and then try
adding it again. Make sure the login has access to whatever
database you have set up as the default database.
-Sue
On Tue, 31 Aug 2004 11:34:56 +0200, "Christoffer"
<christoffer@.nospam.com> wrote:

>Hi,
>I've just installed SQL Server 2005 Beta 2 and added Active Directory
>account to our SQL Server (under Database/Security/Logins). However, when I
>try to login using the Windows Authentication, I get this error message:
>Login failed for user 'DOMAIN\user'. (Microsoft SQL Server, Error: 18456)
>where DOMAIN\user is really my domain-account, which I rather not publish.
>When I try to login using 'sa' and SQL Server Authentication there is no
>problem.
>I've tried to find out what error 18456 is but no luck. Could anyone help m
e
>please?
>Cheers,
>Chris
>|||Hello
I deleted and re-added the account and I also gave it access to every
database with db_owner on every database. I also made the account a member
of the sysadmin role. Still no luck
The account is in a Active Directory, could this be the problem?
Cheers,
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:9rlpj0982j03evgpta2vla52c2jrtlg9md@.
4ax.com...
> Error 18456 is "login failed for user xxx"...the error you
> are getting. You have something incorrect with adding the
> windows account to the logins or the permissions you have
> set for the login. Try deleting the login and then try
> adding it again. Make sure the login has access to whatever
> database you have set up as the default database.
> -Sue
> On Tue, 31 Aug 2004 11:34:56 +0200, "Christoffer"
> <christoffer@.nospam.com> wrote:
>
>|||Are you a member of a group that has been denied access to
the server? Did you try another Windows account and test
with that?
-Sue
On Tue, 7 Sep 2004 14:53:32 +0200, "Christoffer"
<christoffer@.nospam.com> wrote:

>Hello
>I deleted and re-added the account and I also gave it access to every
>database with db_owner on every database. I also made the account a member
>of the sysadmin role. Still no luck
>The account is in a Active Directory, could this be the problem?
>Cheers,
>Chris
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:9rlpj0982j03evgpta2vla52c2jrtlg9md@.
4ax.com...
>|||Hello,
I think I have found the problem. When I add my login (DOMAIN\USER) using
the Microsoft SQL Server Management Studio (2005 Beta 2), the property
"Server Access" is set to "Via Group Membership". If I change this to
"Permit" I can login!
My question is: What is "Via Group Membership" and is this the best practice
when adding Windows logins?
Thanks,
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:90psj0p1dethn063mh6sd61u9fi93c1ec9@.
4ax.com...
> Are you a member of a group that has been denied access to
> the server? Did you try another Windows account and test
> with that?
> -Sue
> On Tue, 7 Sep 2004 14:53:32 +0200, "Christoffer"
> <christoffer@.nospam.com> wrote:
>
>|||Via group membership means the login was has access to SQL
Server through their membership in a windows group.
Managing logins through windows group can definitely make
the management of logins much easier.
-Sue
On Wed, 8 Sep 2004 10:31:06 +0200, "Christoffer"
<christoffer@.nospam.com> wrote:

>Hello,
>I think I have found the problem. When I add my login (DOMAIN\USER) using
>the Microsoft SQL Server Management Studio (2005 Beta 2), the property
>"Server Access" is set to "Via Group Membership". If I change this to
>"Permit" I can login!
>My question is: What is "Via Group Membership" and is this the best practic
e
>when adding Windows logins?
>Thanks,
>Chris
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:90psj0p1dethn063mh6sd61u9fi93c1ec9@.
4ax.com...
>|||I see, the thing is, there is no added Windows groups login in the SQL
Server. I tried adding DOMAIN\Administrators but I got the errore message:
"The login 'DOMAIN\Administrators' does not exist. (Microsoft SQL Server,
Error: 15007)"
But I'm sure it exists since I browsed to it using the Active Directory. Is
there some limitation to adding the DOMAIN\Administrators group? Should I
try to set up yet another group for database access?
Thanks for your help!
/Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8pttj05a5jihmdoqe1ekg4iufo7er08j5f@.
4ax.com...
> Via group membership means the login was has access to SQL
> Server through their membership in a windows group.
> Managing logins through windows group can definitely make
> the management of logins much easier.
> -Sue
> On Wed, 8 Sep 2004 10:31:06 +0200, "Christoffer"
> <christoffer@.nospam.com> wrote:
>
>|||Chris,
I'm not real clear on when you are receiving this error. It doesn't
look like something you would get when you actually try to add the
login. Try add the account using Query Analyzer instead and executing
sp_grantlogin. The help file has more information on sp_grantlogin.
Whether you set up another group or not depends upon how you are going
to design your security model. Using Windows groups certainly can be
easier but whether that works for you or not depends on how your
windows groups are set up, how well they reflect the access, security
needs of the applications that will use the databases on the server,
etc.
-Sue
On Wed, 8 Sep 2004 14:21:49 +0200, "Christoffer"
<christoffer@.nospam.com> wrote:

>I see, the thing is, there is no added Windows groups login in the SQL
>Server. I tried adding DOMAIN\Administrators but I got the errore message:
>"The login 'DOMAIN\Administrators' does not exist. (Microsoft SQL Server,
>Error: 15007)"
>But I'm sure it exists since I browsed to it using the Active Directory. Is
>there some limitation to adding the DOMAIN\Administrators group? Should I
>try to set up yet another group for database access?
>Thanks for your help!
>/Chris
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:8pttj05a5jihmdoqe1ekg4iufo7er08j5f@.
4ax.com...
>|||Hi,
When I use the Microsoft SQL Server Management Studio, which is in SQL
Server 2005 and is equivalent to Enterprise Manager for SQL Server 2000, to
add a Windows login, the login's Server access property is set to "Via group
membership".
If I use the stored procedures sp_grantlogin on SQL Server 2005, the login's
Server access property is set to "Permit".
If I use the old Enterprise Manager for SQL Server 2000, the login's Server
access property is set to "Permit".
Why does the SQL Server Management Studio (2005) set the Server access
property to "Via group membership" instead of "Permit". I know this is a
beta and an answer might not be possible to give...
Thanks for helping me out, I no longer experience the 18456 error, this is
just out of curiousity
/Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:iq7uj0tv8g78vlco9b6dr4m36uq1b3n1tc@.
4ax.com...
> Chris,
> I'm not real clear on when you are receiving this error. It doesn't
> look like something you would get when you actually try to add the
> login. Try add the account using Query Analyzer instead and executing
> sp_grantlogin. The help file has more information on sp_grantlogin.
> Whether you set up another group or not depends upon how you are going
> to design your security model. Using Windows groups certainly can be
> easier but whether that works for you or not depends on how your
> windows groups are set up, how well they reflect the access, security
> needs of the applications that will use the databases on the server,
> etc.
> -Sue
> On Wed, 8 Sep 2004 14:21:49 +0200, "Christoffer"
> <christoffer@.nospam.com> wrote:
>
>

Error 18456: Login failed for user 'Distributor_admin'

Hi,
When going through the replication wizard to setup transactional replication
the following error is returned when it starts to setup replication.
SQL Server Enterprise Manager could not configure '<four part servername>'
as the distributor for '<four part servername>'
Error 18456: Login failed for user 'Distributor_admin'
Can someone please help. Is it because of the four part server name?
Thanks
It could be. What happens when you create an alias using the client network
utility. After doing this de-register your server in EM, and then reregister
it with the new one part alias.
Is the distributor local?
"mm" <postto@.news.com> wrote in message
news:eIM2gdb$EHA.2196@.TK2MSFTNGP14.phx.gbl...
> Hi,
> When going through the replication wizard to setup transactional
> replication
> the following error is returned when it starts to setup replication.
> SQL Server Enterprise Manager could not configure '<four part servername>'
> as the distributor for '<four part servername>'
> Error 18456: Login failed for user 'Distributor_admin'
>
> Can someone please help. Is it because of the four part server name?
> Thanks
>
>
|||Hi Hilary,
There is no alisa defined in the the client network utility.
This happens when trying to setup a local distributor. However there is a
database on the SQL server that subscribes to a remote distributor.
Thanks
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eiLeJZi$EHA.3472@.TK2MSFTNGP14.phx.gbl...
> It could be. What happens when you create an alias using the client
network
> utility. After doing this de-register your server in EM, and then
reregister[vbcol=seagreen]
> it with the new one part alias.
> Is the distributor local?
>
> "mm" <postto@.news.com> wrote in message
> news:eIM2gdb$EHA.2196@.TK2MSFTNGP14.phx.gbl...
servername>'
>

Error 18456 Severity 14 State 16

I am getting the following error in my Sql logs and in my Application Event
viewer:
03/16/2007 07:56:00,Logon,Unknown,Login failed for user
'CTPC\Administrator'. [CLIENT: <local machine>]
03/16/2007 07:56:00,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 1
6.
0000: 18 48 00 00 0e 00 00 00 .H.....
0008: 09 00 00 00 49 00 4e 00 ...I.N.
0010: 54 00 52 00 41 00 4e 00 T.R.A.N.
0018: 45 00 54 00 00 00 07 00 E.T....
0020: 00 00 6d 00 61 00 73 00 ..m.a.s.
0028: 74 00 65 00 72 00 00 00 t.e.r...
I have tried figure out what process is trying to hit this database but to
no avail, how should I go about troubleshooting this? It logs this every on
e
minute and it is on our Portal server.
Thanks,
RobYou can run a trace or Profiler when a login fails and see
what shows up for the application name when auditing the
Login Failures.
It's on the same box as SQL Server so you could also check
what services may be running under the local administrator
account.The security logs may have more information as well
if you track the logins and details for the logins.
-Sue
On Fri, 16 Mar 2007 06:02:16 -0700, Rob
<Rob@.discussions.microsoft.com> wrote:

>I am getting the following error in my Sql logs and in my Application Event
>viewer:
>03/16/2007 07:56:00,Logon,Unknown,Login failed for user
>'CTPC\Administrator'. [CLIENT: <local machine>]
>03/16/2007 07:56:00,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State:
16.
>0000: 18 48 00 00 0e 00 00 00 .H.....
>0008: 09 00 00 00 49 00 4e 00 ...I.N.
>0010: 54 00 52 00 41 00 4e 00 T.R.A.N.
>0018: 45 00 54 00 00 00 07 00 E.T....
>0020: 00 00 6d 00 61 00 73 00 ..m.a.s.
>0028: 74 00 65 00 72 00 00 00 t.e.r...
>I have tried figure out what process is trying to hit this database but to
>no avail, how should I go about troubleshooting this? It logs this every o
ne
>minute and it is on our Portal server.
>Thanks,
>Rob

Error 18456 Login failed for user domain\user

We have an application that logs into our SQL Server 2000 using ODBC. All
service packs and critical updates are current on the server and clients.
SQL Server uses mixed authentification and runs under a domain account, the
users login with their domain\username, or at least they used to. Nobody
seems to know exactly when this stopped working, and of course, nobody said
anything until this week. Attempting to login now fails with error 18456
login failed for user domain\username. I've foolwed all the debugging info I
can find on Microsofts site. Running osql, I can log in using windows
authentification and SQL Server accounts with no problem. Trying to use
domain\username fails. I've been through everything from DNS to SQL Server
settings to client settings with no resolution. Anybody have an idea where
else to look?
Any hints would be greatly appreciated.
BruceHi Bruce,
Thank you for use the newsgroup and it is my pleasure to help you with you
issue.
From you information, you application, which used to work fine now got
error message
Could you check if the ODBC connection is made through the standard
security of SQL Server of trusted connection security? Is the SQL Server
authentication mode match the security option of ODBC connection? Could you
using the Query Analyzer to connect the SQL Server? That is, if you use the
standard security, such as use the account 'sa', when using 'sa' in Query
Analyzer, could it connect the SQL Server. When it is a Windows
authentication, when connect the SQL Server by Query Analyzer, you should
choose the Windows Authenticatin in the Query Analyzer.
Looking forward to your response. Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Baisong:
Using Windows Authentification or Sql Server Authentification both work
fine.
If I'm logged into the domain I can run
osql -S SERVER -d Test -E
or
osql -S SERVER -d Test -U SA -P password
with no problem I can connect through Query analyzer either way.
if I try
osql -S SERVER -d Test -U domain\username -P password
it fails with the message Error 18456 Login failed for user domain\username.
The application we are using was working with the domain\username login, I
can't use Windows Integrated security with it, and I really do not want to
setup and manage 50+ SQL Server accounts. I am assuming that something has
changed in the authentification / delegation process and am working through
that now. As far as I can tell nothing has changed, but obviously something
has.
Any ideas would be appreciated.
Bruce
"Baisong Wei[MSFT]" <v-baiwei@.online.microsoft.com> wrote in message
news:EKzqmHs7DHA.1992@.cpmsftngxa07.phx.gbl...
> Hi Bruce,
> Thank you for use the newsgroup and it is my pleasure to help you with you
> issue.
> From you information, you application, which used to work fine now got
> error message
> Could you check if the ODBC connection is made through the standard
> security of SQL Server of trusted connection security? Is the SQL Server
> authentication mode match the security option of ODBC connection? Could
you
> using the Query Analyzer to connect the SQL Server? That is, if you use
the
> standard security, such as use the account 'sa', when using 'sa' in Query
> Analyzer, could it connect the SQL Server. When it is a Windows
> authentication, when connect the SQL Server by Query Analyzer, you should
> choose the Windows Authenticatin in the Query Analyzer.
> Looking forward to your response. Thanks.
> Best regards
> Baisong Wei
> Microsoft Online Support
> ----
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only. Thanks.
>|||Hi Bruce,
Thank you for your update.
For the 'osql -S SERVER -d Test -U domain\username -P password' which
failed with the error message, could you check if it is a valid SQL Server
login? You could check it by unfolder the database, unfoulder the
'Security', then in the logins, is the above 'domain\username' in the
logins?
Looking forward to your response. Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Yes, it is a valid login and the password is correct. The account also has
privledges (dbowner + our SQL_Admin role) to access the test database. It
works fine with Windows Integrated Security, so I don't think it is related
to SQL Server privledges, my guess is that something has changed in the
authentification authorization or delegation between the domain and the
server or the client.
The client computers are running MDAC 2.8 or 2.7RTM, and component checker
says they are current and all is well. Servers and clients are current on
patches, SQL Server is current. I've been throgh every article I can find on
MSDN that remotely deals with this error, and everything seems to check out.
I'm sure there is some little thing I'm overlooking, but I'm totally stumped
at this point.
Bruce
"Baisong Wei[MSFT]" <v-baiwei@.online.microsoft.com> wrote in message
news:ZZofg867DHA.2508@.cpmsftngxa07.phx.gbl...
> Hi Bruce,
> Thank you for your update.
> For the 'osql -S SERVER -d Test -U domain\username -P password' which
> failed with the error message, could you check if it is a valid SQL Server
> login? You could check it by unfolder the database, unfoulder the
> 'Security', then in the logins, is the above 'domain\username' in the
> logins?
> Looking forward to your response. Thanks.
> Best regards
> Baisong Wei
> Microsoft Online Support
> ----
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only. Thanks.
>|||Bruce,
The exact same thing happen here - ODBC connections that had worked
stopped working. We THINK it was related to installing patches but not
the full SP3a running on SQL 2000. We know installing SP3a fixed it.
An easy test to see if it's the same problem - in the ODBC config, set
the server name servername.subdomain.domain.?, check with the network
people for the full name if you need to.
If it works then maybe install/reinstall SP3a on the server will help.
SQL DBA in Richmond, VA
PS - I know 4 locales that suddenly experienced this same problem.
Maybe triggered by Windows critical update?
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!

Error 18456 Login failed for user 'distributor_admin'

Hello,
Each time I try to configure my SQL 2000 server as a distributor using the
Wizard I get the following error message:
Error 18456 Login failed for user 'distributor_admin'
Can anyone help with this?
Regards
Dave
are you using a remote distributor?
If do your Publisher has the incorrect administrative link password. Connect
to your Publisher in EM. Go to Tools, replication, configure publishers,
Subscribers, and distributor, and click on the Publisher's tab. In the
Administrative link password dialog enter the administrative link password.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Dave" <dave.cartlidge@.gmail.com> wrote in message
news:9401f534.0407170459.625c7ba7@.posting.google.c om...
> Hello,
> Each time I try to configure my SQL 2000 server as a distributor using the
> Wizard I get the following error message:
> Error 18456 Login failed for user 'distributor_admin'
> Can anyone help with this?
> Regards
> Dave
|||Check to make sure that the computer you are trying to access which has the
group 'distributor_admin' actually has the administrative access it
requires, both in the security file for the server and in the user security
for the individual database. If you play with file permissions, you may
want to check those as well. If you don't work with the file permissions
forget I added this. If you are on a network and the network administrator
has not enabled the administrator rights for the 'distributor_admin' group,
you may need to ask the administrator to grant the permission over the
network.
Giac
"Dave" <dave.cartlidge@.gmail.com> wrote in message
news:9401f534.0407170459.625c7ba7@.posting.google.c om...
> Hello,
> Each time I try to configure my SQL 2000 server as a distributor using the
> Wizard I get the following error message:
> Error 18456 Login failed for user 'distributor_admin'
> Can anyone help with this?
> Regards
> Dave
|||Sorry, I should have given a bit more info. I'm trying to set up one
machine to replicate the contents of one table to a second machine
(not located in the same place)
I figured I needed to set Machine A up as a distibutor and then allow
Machine B to have a subscription.
I don't have the 'Publisher's tab' as I have not configured it to be a
publisher yet, this I can't do as I get the aforementioned error.
I can't see a login 'distributor_admin' in Ent Mgr.
I was assuming (maybe incorrectly) that I don't need to do anything on
Machine B in order to be able to set up the publishing side on Machine
A.
Hope this helps you to help me
Dave
|||Dave,
You're in over my head, but it sounds like a permissions error.
If you go to services and select the properties of your server, you'll see
the account that the machine starts in. Check to see that account is
someone who is in the 'distributor_admin' group. You can browse for it
there - and both sides need to be members of that group since it appears to
have the permission to run the transaction.
Hope this helps.
Giac
"Dave" <dave.cartlidge@.gmail.com> wrote in message
news:9401f534.0407180039.1d325c91@.posting.google.c om...
> Sorry, I should have given a bit more info. I'm trying to set up one
> machine to replicate the contents of one table to a second machine
> (not located in the same place)
> I figured I needed to set Machine A up as a distibutor and then allow
> Machine B to have a subscription.
> I don't have the 'Publisher's tab' as I have not configured it to be a
> publisher yet, this I can't do as I get the aforementioned error.
> I can't see a login 'distributor_admin' in Ent Mgr.
> I was assuming (maybe incorrectly) that I don't need to do anything on
> Machine B in order to be able to set up the publishing side on Machine
> A.
> Hope this helps you to help me
> Dave
|||"Giacomo" <anonymous@.msnewsgroups.com> wrote in message news:<#HHn#qLbEHA.3792@.TK2MSFTNGP09.phx.gbl>...
> Dave,
> You're in over my head, but it sounds like a permissions error.
> If you go to services and select the properties of your server, you'll see
> the account that the machine starts in. Check to see that account is
> someone who is in the 'distributor_admin' group. You can browse for it
> there - and both sides need to be members of that group since it appears to
> have the permission to run the transaction.
> Hope this helps.
> Giac
I don't have a 'distributor_admin' group in either Ent Mgr or Computer Manager.
|||Dave,
see if this link applies to you - there are 2 workarounds suggested, one of
which is the same as Hilary's first reply.
http://support.microsoft.com/default...;en-us;Q225129
HTH,
Paul Ibison
|||Thanks for the suggestions. I had set up an alias sql server as the
default had been set up as (local) which would not work.
In the end I just removed and re-added the only registration so that
it had the same name as the server and all worked fine.
Thanks again
sql

Error 18456 - ODBC connection failed for domain user account

I have a user that her domain user account is failing to access a sql server
database while another persons domain account with the same permission to th
e
database works just fine. I remote into the workstation and test the odbc
connection with my user account and it worked just fine. Any help.
I am getting this message below
Connection failed Sql state 28000 error 18456 microsoft odbc connection
login failed for user bhcs/connie'Aboki,
This should be a straight-forward error that means: bhcs/connie has no right
to login on the server.
Check to be sure: the login is the proper one (not one spelled almost the
same), that connie was not denied login, etc.
RLF
"Aboki" <Aboki@.discussions.microsoft.com> wrote in message
news:4C4AD587-76B4-498F-9D1A-99ED809F7294@.microsoft.com...
>I have a user that her domain user account is failing to access a sql
>server
> database while another persons domain account with the same permission to
> the
> database works just fine. I remote into the workstation and test the odbc
> connection with my user account and it worked just fine. Any help.
> I am getting this message below
> Connection failed Sql state 28000 error 18456 microsoft odbc connection
> login failed for user bhcs/connie'

Error 18456 - ODBC connection failed for domain user account

I have a user that her domain user account is failing to access a sql server
database while another persons domain account with the same permission to the
database works just fine. I remote into the workstation and test the odbc
connection with my user account and it worked just fine. Any help.
I am getting this message below
Connection failed Sql state 28000 error 18456 microsoft odbc connection
login failed for user bhcs/connie'
Aboki,
This should be a straight-forward error that means: bhcs/connie has no right
to login on the server.
Check to be sure: the login is the proper one (not one spelled almost the
same), that connie was not denied login, etc.
RLF
"Aboki" <Aboki@.discussions.microsoft.com> wrote in message
news:4C4AD587-76B4-498F-9D1A-99ED809F7294@.microsoft.com...
>I have a user that her domain user account is failing to access a sql
>server
> database while another persons domain account with the same permission to
> the
> database works just fine. I remote into the workstation and test the odbc
> connection with my user account and it worked just fine. Any help.
> I am getting this message below
> Connection failed Sql state 28000 error 18456 microsoft odbc connection
> login failed for user bhcs/connie'

Error 18456 - ODBC connection failed for domain user account

I have a user that her domain user account is failing to access a sql server
database while another persons domain account with the same permission to the
database works just fine. I remote into the workstation and test the odbc
connection with my user account and it worked just fine. Any help.
I am getting this message below
Connection failed Sql state 28000 error 18456 microsoft odbc connection
login failed for user bhcs/connie'Aboki,
This should be a straight-forward error that means: bhcs/connie has no right
to login on the server.
Check to be sure: the login is the proper one (not one spelled almost the
same), that connie was not denied login, etc.
RLF
"Aboki" <Aboki@.discussions.microsoft.com> wrote in message
news:4C4AD587-76B4-498F-9D1A-99ED809F7294@.microsoft.com...
>I have a user that her domain user account is failing to access a sql
>server
> database while another persons domain account with the same permission to
> the
> database works just fine. I remote into the workstation and test the odbc
> connection with my user account and it worked just fine. Any help.
> I am getting this message below
> Connection failed Sql state 28000 error 18456 microsoft odbc connection
> login failed for user bhcs/connie'sql

Error 18456 - Connecting via DSN

Hi,
My MS Access application needs to connect to a SQL server via a system
dsn. However, I keep getting the error 18456 - Login failed for user 'xxxx'.
The surprising bit is I am able to use the same password and user id and
connect to the server using Enterprise Manager. Any ideas on why the dsn is
throwing this error? Connection is via SQL authentication.
Any help would be much appreciated.
Rgds,
San
Any success with this? I'm having the exact same problem. I was doing
some permissions stuff the other day so I'm sure I hosed something up.
goosesr
Posted via http://www.codecomments.com
|||Yeah, I was able to resolve the issue by updating the links in Access. Right
click on the link table, select Link Table Manager, select, promt for new
location,a nd on ok, select the DSN again...
Hope it works for you too !
~San
"goosesr" wrote:

> Any success with this? I'm having the exact same problem. I was doing
> some permissions stuff the other day so I'm sure I hosed something up.
>
> --
> goosesr
> Posted via http://www.codecomments.com
>

Error 18456 - Connecting via DSN

Hi,
My MS Access application needs to connect to a SQL server via a system
dsn. However, I keep getting the error 18456 - Login failed for user 'xxxx'.
The surprising bit is I am able to use the same password and user id and
connect to the server using Enterprise Manager. Any ideas on why the dsn is
throwing this error? Connection is via SQL authentication.
Any help would be much appreciated.
Rgds,
SanAny success with this? I'm having the exact same problem. I was doing
some permissions stuff the other day so I'm sure I hosed something up.
goosesr
---
Posted via http://www.codecomments.com
---|||Yeah, I was able to resolve the issue by updating the links in Access. Right
click on the link table, select Link Table Manager, select, promt for new
location,a nd on ok, select the DSN again...
Hope it works for you too !
~San
"goosesr" wrote:

> Any success with this? I'm having the exact same problem. I was doing
> some permissions stuff the other day so I'm sure I hosed something up.
>
> --
> goosesr
> ---
> Posted via http://www.codecomments.com
> ---
>

Error 18456

Hello I am getting:
"login failed" (Error 18456) error messages in SQL Server 2005 Error is
18456, Severity: 14, State: 8.
I have tried to logon to other databases and this isnt possible. I get the
same error message. Creating new logins, and triple-checking the passwords
did not help. The database engine will not allow any logons to any
database. The other engines seem to be fine.
This still means that I do not have permissions for any of the databases.
This is using any of the local or domain accounts. I cannot log onto any of
the databases. I have tried to attach using SQLCMD and I cannot get logged
in to the database.
The log files show success from earlier in the day and week for these same
accounts.
I created this problem by detaching one database running on the server. I
went to connect the datafiles and now I cannot get into the server at all.
I am using SQL2005, Sharepoint services and a Windows 2003 server.
I would appreciate any insight or suggestions.State 8 is an invalid password.
Passwords in SQL Server 2005 are case sensitive so make sure
you are checking that as well. If you can't log in at all
and no one can log in, try logging in as local administrator
on the box and then log into SQL Server using windows
authentication.
-Sue
On Wed, 15 Mar 2006 19:34:00 -0600, "JimS"
<noholycowsspam@.ya_NoJunk_hoo.com> wrote:

>Hello I am getting:
>"login failed" (Error 18456) error messages in SQL Server 2005 Error is
>18456, Severity: 14, State: 8.
>I have tried to logon to other databases and this isnt possible. I get th
e
>same error message. Creating new logins, and triple-checking the passwords
>did not help. The database engine will not allow any logons to any
>database. The other engines seem to be fine.
>This still means that I do not have permissions for any of the databases.
>This is using any of the local or domain accounts. I cannot log onto any o
f
>the databases. I have tried to attach using SQLCMD and I cannot get logged
>in to the database.
>The log files show success from earlier in the day and week for these same
>accounts.
>I created this problem by detaching one database running on the server. I
>went to connect the datafiles and now I cannot get into the server at all.
>I am using SQL2005, Sharepoint services and a Windows 2003 server.
>I would appreciate any insight or suggestions.
>|||Thanks for the help....
We detached a database in order to copy the files. When I detached the
database it seemed to lock all users with access to that database out any
access to this SQL2005 server.
I was able to use SQLCMD to gain access and rebuild access for my database
admin account. I was then able to use this account to reattach the detached
database. When I did this the database and all user access to SQL2005 was
back to normal. I am not sure why this happened. We have about ten other
databases on this SQL server. The same users had access to these tables as
well as the detached table so the detached table was not the only table for
which they had access. The detached table was just a table of 'production'
data. I will try and see if I can recreate the problem but will wait for
the weekend to try that!
Thanks
"JimS" <noholycowsspam@.ya_NoJunk_hoo.com> wrote in message
news:%23EnC0mJSGHA.1576@.tk2msftngp13.phx.gbl...
Hello I am getting:
"login failed" (Error 18456) error messages in SQL Server 2005 Error is
18456, Severity: 14, State: 8.
I have tried to logon to other databases and this isnt possible. I get the
same error message. Creating new logins, and triple-checking the passwords
did not help. The database engine will not allow any logons to any
database. The other engines seem to be fine.
This still means that I do not have permissions for any of the databases.
This is using any of the local or domain accounts. I cannot log onto any of
the databases. I have tried to attach using SQLCMD and I cannot get logged
in to the database.
The log files show success from earlier in the day and week for these same
accounts.
I created this problem by detaching one database running on the server. I
went to connect the datafiles and now I cannot get into the server at all.
I am using SQL2005, Sharepoint services and a Windows 2003 server.
I would appreciate any insight or suggestions.

Error 18456

I am repeatedly receiving the following error:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
This has been occuring since a network wide password
change ( for an employee leaving the company ) and I do
realize that there is some process trying to connect, but
I do not know how to find out what the process is, or
what it is trying to connect as. Is there a way to trace
this information?You may be able to catch this with SQL Profiler and/or a network trace.
The network trace will only work if the connection is coming from a remote
machine.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Have tried the profiler and don't get enough information
to track. Haven't tried a network trace, I will try, but
I don't think it is a remote connection. Thanks for your
help.
Rachel

>--Original Message--
>You may be able to catch this with SQL Profiler and/or a
network trace.
>The network trace will only work if the connection is
coming from a remote
>machine.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>

Error 18452 Login failed for user <null>. The user account is not

We have a SQL 2005 installation using SQL and Windows Authentication. We
have a login that is mapped to a active directory group and has the
appropriate permissions to the database. However, when we try to create
an ODBC connection to the server from an XP client (and the user is a
member of the appropriate domain group) we get the above mentioned error.
Also logged on the SQL server is the following error:
SSPI handshake failed with error code 0x8009030c...
The only info I can find on this error has to do with IIS
configurations, but I don't see what IIS has to do with this as we are
only trying to make an ODBC connection.Maybe your service account is Local System.
You can change to AD Service account.
"Jan Leste"?? ??? ??:

> We have a SQL 2005 installation using SQL and Windows Authentication. We
> have a login that is mapped to a active directory group and has the
> appropriate permissions to the database. However, when we try to create
> an ODBC connection to the server from an XP client (and the user is a
> member of the appropriate domain group) we get the above mentioned error.
> Also logged on the SQL server is the following error:
> SSPI handshake failed with error code 0x8009030c...
> The only info I can find on this error has to do with IIS
> configurations, but I don't see what IIS has to do with this as we are
> only trying to make an ODBC connection.
>

Error 18452

Hi,
I am getting Login failed for user 'sa'. Reason: Not associated with a
trusted SQL Server connection. [SQLSTATE 28000] when try to run a RPC call
from one sql server 2000 to an other sql 2000. I have setup/configure the
remote server connection on both servers and they have the same sa password
and same domain ids for the sql server and sql agent accounts. I have no
problem to run the same RPC command in query analyzer. But I get this error
when I try to run the call within a sql job and the job is own by sa. Any
help would be great.
This error is thrown when you try to connect to a SQL Server using a
"standard" SQL login (such as the sa account) but your SQL server is
configured to only accept Windows logins. To allow standard logins you
would need to to set up Mixed Mode security:
In enterprise manager:
Expand a server group.
Right-click a server, and then click Properties.
Click the Security tab.
Under Authentication, click SQL Server and Windows.
References:
See Books Online topic: Authentication Modes
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Yes, I use mix mode on all our sql servers and they have the same sp3a. The
funny things is that I have no problem run this RPC on all remote servers
(within the same site) but having this problem when I try to run the RPC to
remote servers (out of state and out of USA). Also I don't have this problem
on SQL 7.0 environment, I can run RPC to any where (local site or remote
site). As I stated below, I can run the RPC call in Query Analyzer login as
SA but I having problem to run that call in the sql job.
Thanks,
"Fany Vargas [MSFT]" wrote:

> This error is thrown when you try to connect to a SQL Server using a
> "standard" SQL login (such as the sa account) but your SQL server is
> configured to only accept Windows logins. To allow standard logins you
> would need to to set up Mixed Mode security:
> In enterprise manager:
> Expand a server group.
> Right-click a server, and then click Properties.
> Click the Security tab.
> Under Authentication, click SQL Server and Windows.
> References:
> See Books Online topic: Authentication Modes
> Fany Vargas
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
> Microsoft software to better protect against viruses and security
> vulnerabilities. The easiest way to do this is to visit the following
> websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>
|||1. Recreate your linked server. Provide more details on how your linked
server is created as well. Is it using sa login or NT authentication?
2. In enterprise manager -> Management->SQL Agent ->Properties->Connection
tab, try specifying sa account and with nt authentication. Does it now
execute successfully?
3. If job is not owned by sa does it run successfully - (try changing job
owner to a different account)?
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Error 18452

Hi,
I am getting Login failed for user 'sa'. Reason: Not associated with a
trusted SQL Server connection. [SQLSTATE 28000] when try to run a RPC ca
ll
from one sql server 2000 to an other sql 2000. I have setup/configure the
remote server connection on both servers and they have the same sa password
and same domain ids for the sql server and sql agent accounts. I have no
problem to run the same RPC command in query analyzer. But I get this error
when I try to run the call within a sql job and the job is own by sa. Any
help would be great.This error is thrown when you try to connect to a SQL Server using a
"standard" SQL login (such as the sa account) but your SQL server is
configured to only accept Windows logins. To allow standard logins you
would need to to set up Mixed Mode security:
In enterprise manager:
Expand a server group.
Right-click a server, and then click Properties.
Click the Security tab.
Under Authentication, click SQL Server and Windows.
References:
See Books Online topic: Authentication Modes
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx|||Yes, I use mix mode on all our sql servers and they have the same sp3a. The
funny things is that I have no problem run this RPC on all remote servers
(within the same site) but having this problem when I try to run the RPC to
remote servers (out of state and out of USA). Also I don't have this problem
on SQL 7.0 environment, I can run RPC to any where (local site or remote
site). As I stated below, I can run the RPC call in Query Analyzer login as
SA but I having problem to run that call in the sql job.
Thanks,
"Fany Vargas [MSFT]" wrote:

> This error is thrown when you try to connect to a SQL Server using a
> "standard" SQL login (such as the sa account) but your SQL server is
> configured to only accept Windows logins. To allow standard logins you
> would need to to set up Mixed Mode security:
> In enterprise manager:
> Expand a server group.
> Right-click a server, and then click Properties.
> Click the Security tab.
> Under Authentication, click SQL Server and Windows.
> References:
> See Books Online topic: Authentication Modes
> Fany Vargas
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
> Microsoft software to better protect against viruses and security
> vulnerabilities. The easiest way to do this is to visit the following
> websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>|||1. Recreate your linked server. Provide more details on how your linked
server is created as well. Is it using sa login or NT authentication?
2. In enterprise manager -> Management->SQL Agent ->Properties->Connection
tab, try specifying sa account and with nt authentication. Does it now
execute successfully?
3. If job is not owned by sa does it run successfully - (try changing job
owner to a different account)?
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Error 1413 during setting up mirroring session

hi guys , does anyone of you have a good solution on the Error 1413: Communications to the remote server instance failed before database mirroring was fully started issue?

Best Regards,

Hans

Do you see any network issues between Principal and mirror?

Explain when and where you are getting this error and if this is during the failover then work around for this problem:

1. Restart the SQL Server service on the mirror server. 2. Wait for the databases to be synchronized. 3. Issue the failover command again.

If there is an issue with NIC on the servers that are in DBMirroring then you would see these alerts.

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

Error 1203

I am finding Error 1203 Severity 20 periodically in my trace.
This seems to correlate with intermittent failed insert statements performed
by a stored procedure. The stored procedure is executed shortly before this
error is recorded.
Nothing is written to the SQL Server log.
The error is occurring on SQL Server 2000 Enterprise, SP 2, build 2195,
running on W2K server.
The same error occurs in a test database on SQL Server 2000 Standard, no
service packs, build 3790.
I found one reference to it in response to a question on winnetmag.com:
What is error msg 1203, "attempting to unlock unowned resource "?
Answered: This error indicates a bug in SQL Server. Several bugs that caused
this error were fixed in SQL Server 2000, service pack 1. If you can create
a script that will allow anyone to reproduce this problem, you should send
it in to Microsoft SQL Server support.
I can't reproduce this except in our database. dbcc checkdb indicates no
errors.
I am concerned about data loss without any error to detect it. Can anyone
help me with this?
Thanks
Bill
Hi
Error 1203 is bad. Process ID %d attempting to unlock unowned resource %.*ls.
There are a number of KB articles indicating that it occurs up to version
8.00.661 (KB 326999). SP3a is 8.00.760. Get your servers to at least SQL
Server sp3a and see if the error still occurs. Plus, if you are not on SQL
Server 2000 sp3a, you are exposed to the Slammer virus.
Regards
Mike
"bill" wrote:

> I am finding Error 1203 Severity 20 periodically in my trace.
> This seems to correlate with intermittent failed insert statements performed
> by a stored procedure. The stored procedure is executed shortly before this
> error is recorded.
> Nothing is written to the SQL Server log.
> The error is occurring on SQL Server 2000 Enterprise, SP 2, build 2195,
> running on W2K server.
> The same error occurs in a test database on SQL Server 2000 Standard, no
> service packs, build 3790.
> I found one reference to it in response to a question on winnetmag.com:
> What is error msg 1203, "attempting to unlock unowned resource "?
> Answered: This error indicates a bug in SQL Server. Several bugs that caused
> this error were fixed in SQL Server 2000, service pack 1. If you can create
> a script that will allow anyone to reproduce this problem, you should send
> it in to Microsoft SQL Server support.
> I can't reproduce this except in our database. dbcc checkdb indicates no
> errors.
> I am concerned about data loss without any error to detect it. Can anyone
> help me with this?
> Thanks
> Bill
>
>
|||Mike:
SQL Server SP3a DOES NOT contain the fix for the "Slammer Worm" virus,
MS03-031. This was originally launched as build 817 but caused a but in the
DtsGui.dll. This fix replaced the previous edition to build 818. This
release caused a password issue when using SEM. This fix is build 819.
SP3a is build 760.
The newly released SQL Server 2000 Release A is a slipstream of the pre SP3a
release code. If one uses this, then only SP3a need to be applied.
Build 818:
http://support.microsoft.com/?scid=k...852&sid=global
Build 819:
http://support.microsoft.com/kb/826161
Release A:
http://support.microsoft.com/default...b;en-us;826818
Sincerely,
Anthony Thomas

"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:94447A54-2C1F-483F-8D71-1584645C4BCA@.microsoft.com...
> Hi
> Error 1203 is bad. Process ID %d attempting to unlock unowned resource
%.*ls.[vbcol=seagreen]
> There are a number of KB articles indicating that it occurs up to version
> 8.00.661 (KB 326999). SP3a is 8.00.760. Get your servers to at least SQL
> Server sp3a and see if the error still occurs. Plus, if you are not on SQL
> Server 2000 sp3a, you are exposed to the Slammer virus.
> Regards
> Mike
>
> "bill" wrote:
performed[vbcol=seagreen]
this[vbcol=seagreen]
caused[vbcol=seagreen]
create[vbcol=seagreen]
send[vbcol=seagreen]
no[vbcol=seagreen]
anyone[vbcol=seagreen]
|||Anthony,
SQL Server 2000 Service Pack 3a does protect against Slammer. The
original patch to protect against Slammer was MS02-039. SQL Server
SP3a, available at
http://www.microsoft.com/downloads/d...isplaylang=en,
"corrects vulnerabilities including the Slammer (W32.slammer) virus."
It will not remove Slammer if it is present, and the page says "SQL 2000
Servers infected by the "Slammer" worm virus should follow instructions
on the Microsoft TechNet Web site before installing SP3a."
According to
http://www.microsoft.com/downloads/d...isplayLang=en,
"Instances of SQL Server 2000 with Service Pack 2 (SP2) and security
patch MS02-039, MS02-043, MS02-056, or MS02-061, or instances with SP3
or later, are not vulnerable to the slammer worm."
Release A also protects against Slammer, but does not contain other
fixes from SP3a.
Steve Kass
Drew University
AnthonyThomas wrote:

>Mike:
>SQL Server SP3a DOES NOT contain the fix for the "Slammer Worm" virus,
>MS03-031. This was originally launched as build 817 but caused a but in the
>DtsGui.dll. This fix replaced the previous edition to build 818. This
>release caused a password issue when using SEM. This fix is build 819.
>SP3a is build 760.
>The newly released SQL Server 2000 Release A is a slipstream of the pre SP3a
>release code. If one uses this, then only SP3a need to be applied.
>Build 818:
>http://support.microsoft.com/?scid=k...852&sid=global
>
>Build 819:
>http://support.microsoft.com/kb/826161
>
>Release A:
>http://support.microsoft.com/default...b;en-us;826818
>
>Sincerely,
>
>Anthony Thomas
>
>
|||Then why the need for MS03-031 for post SP3 or SP3a, both of which are only the 760 builds, while the MS03-031 was originally 817, then 818, closely followed by 819? Since the hot fixes and service packs are cumulative, why didn't the post SP2 hot fixes make it into the SP3(a) releases? Again, if they did, then why the need for the 817 through 819 builds?
Sincerely,
Anthony Thomas

"Steve Kass" <skass@.drew.edu> wrote in message news:%23qrsygtyEHA.1300@.TK2MSFTNGP14.phx.gbl...
Anthony,
SQL Server 2000 Service Pack 3a does protect against Slammer. The
original patch to protect against Slammer was MS02-039. SQL Server
SP3a, available at
http://www.microsoft.com/downloads/d...isplaylang=en,
"corrects vulnerabilities including the Slammer (W32.slammer) virus."
It will not remove Slammer if it is present, and the page says "SQL 2000
Servers infected by the "Slammer" worm virus should follow instructions
on the Microsoft TechNet Web site before installing SP3a."
According to
http://www.microsoft.com/downloads/d...isplayLang=en,
"Instances of SQL Server 2000 with Service Pack 2 (SP2) and security
patch MS02-039, MS02-043, MS02-056, or MS02-061, or instances with SP3
or later, are not vulnerable to the slammer worm."
Release A also protects against Slammer, but does not contain other
fixes from SP3a.
Steve Kass
Drew University
AnthonyThomas wrote:

>Mike:
>
>SQL Server SP3a DOES NOT contain the fix for the "Slammer Worm" virus,
>MS03-031. This was originally launched as build 817 but caused a but in the
>DtsGui.dll. This fix replaced the previous edition to build 818. This
>release caused a password issue when using SEM. This fix is build 819.
>SP3a is build 760.
>
>The newly released SQL Server 2000 Release A is a slipstream of the pre SP3a
>release code. If one uses this, then only SP3a need to be applied.
>
>Build 818:
>
>http://support.microsoft.com/?scid=k...852&sid=global
>
>
>Build 819:
>
>http://support.microsoft.com/kb/826161
>
>
>Release A:
>
>http://support.microsoft.com/default...b;en-us;826818
>
>
>Sincerely,
>
>
>Anthony Thomas
>
>
>
>|||I don't understand your question at all. Here's what I said:
Anthony,
SQL Server 2000 Service Pack 3a does protect against Slammer. The
original patch to protect against Slammer was MS02-039. SQL Server
SP3a, available at
http://www.microsoft.com/downloads/d...isplaylang=en,
"corrects vulnerabilities including the Slammer (W32.slammer)
virus." It will not remove Slammer if it is present, and the page
says "SQL 2000 Servers infected by the "Slammer" worm virus should
follow instructions on the Microsoft TechNet Web site before
installing SP3a."
According to
http://www.microsoft.com/downloads/d...isplayLang=en,
"Instances of SQL Server 2000 with Service Pack 2 (SP2) and security
patch MS02-039, MS02-043, MS02-056, or MS02-061, or instances with
SP3 or later, are not vulnerable to the slammer worm."
Release A also protects against Slammer, but does not contain other
fixes from SP3a.
Steve Kass
Drew University
You had incorrectly stated "SQL Server SP3a DOES NOT contain the fix for
the "Slammer Worm" virus MS03-031," and I corrected your misstatement.
It does. SQL Server build 818 appeared after Service Pack 3 (Service
Pack 3/3a is build 760), and build 818 corrected three post-Slammer
security vulnerabilities identified in MS03-031.
Slammer appeared after sp3 had been released, and it did not affect
anyone who had already installed sp3, or who had installed the even
early post-sp2 fix correcting the vulnerability ultimately exploited by
Slammer (pre-Slammer, pre-sp2 bulletin MS02-039). Everything to do with
Slammer (recognition of the vulnerability, the security bulletin, the
patch, the service pack that contained the patch, and finally the
exploit) happened well before the later and unrelated bulletin MS03-031
(build 818, which was post-sp3, not pre-sp3).
SK
AnthonyThomas wrote:

>Then why the need for MS03-031 for post SP3 or SP3a, both of which are only the 760 builds, while the MS03-031 was originally 817, then 818, closely followed by 819? Since the hot fixes and service packs are cumulative, why didn't the post SP2 hot fixes
make it into the SP3(a) releases? Again, if they did, then why the need for the 817 through 819 builds?
>Sincerely,
>
>Anthony Thomas
>
>

Error 1203

I am finding Error 1203 Severity 20 periodically in my trace.
This seems to correlate with intermittent failed insert statements performed
by a stored procedure. The stored procedure is executed shortly before this
error is recorded.
Nothing is written to the SQL Server log.
The error is occurring on SQL Server 2000 Enterprise, SP 2, build 2195,
running on W2K server.
The same error occurs in a test database on SQL Server 2000 Standard, no
service packs, build 3790.
I found one reference to it in response to a question on winnetmag.com:
What is error msg 1203, "attempting to unlock unowned resource "?
Answered: This error indicates a bug in SQL Server. Several bugs that caused
this error were fixed in SQL Server 2000, service pack 1. If you can create
a script that will allow anyone to reproduce this problem, you should send
it in to Microsoft SQL Server support.
I can't reproduce this except in our database. dbcc checkdb indicates no
errors.
I am concerned about data loss without any error to detect it. Can anyone
help me with this?
Thanks
BillHi
Error 1203 is bad. Process ID %d attempting to unlock unowned resource %.*ls.
There are a number of KB articles indicating that it occurs up to version
8.00.661 (KB 326999). SP3a is 8.00.760. Get your servers to at least SQL
Server sp3a and see if the error still occurs. Plus, if you are not on SQL
Server 2000 sp3a, you are exposed to the Slammer virus.
Regards
Mike
"bill" wrote:
> I am finding Error 1203 Severity 20 periodically in my trace.
> This seems to correlate with intermittent failed insert statements performed
> by a stored procedure. The stored procedure is executed shortly before this
> error is recorded.
> Nothing is written to the SQL Server log.
> The error is occurring on SQL Server 2000 Enterprise, SP 2, build 2195,
> running on W2K server.
> The same error occurs in a test database on SQL Server 2000 Standard, no
> service packs, build 3790.
> I found one reference to it in response to a question on winnetmag.com:
> What is error msg 1203, "attempting to unlock unowned resource "?
> Answered: This error indicates a bug in SQL Server. Several bugs that caused
> this error were fixed in SQL Server 2000, service pack 1. If you can create
> a script that will allow anyone to reproduce this problem, you should send
> it in to Microsoft SQL Server support.
> I can't reproduce this except in our database. dbcc checkdb indicates no
> errors.
> I am concerned about data loss without any error to detect it. Can anyone
> help me with this?
> Thanks
> Bill
>
>|||Mike:
SQL Server SP3a DOES NOT contain the fix for the "Slammer Worm" virus,
MS03-031. This was originally launched as build 817 but caused a but in the
DtsGui.dll. This fix replaced the previous edition to build 818. This
release caused a password issue when using SEM. This fix is build 819.
SP3a is build 760.
The newly released SQL Server 2000 Release A is a slipstream of the pre SP3a
release code. If one uses this, then only SP3a need to be applied.
Build 818:
http://support.microsoft.com/?scid=kb;en-us;821277&spid=2852&sid=global
Build 819:
http://support.microsoft.com/kb/826161
Release A:
http://support.microsoft.com/default.aspx?scid=kb;en-us;826818
Sincerely,
Anthony Thomas
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:94447A54-2C1F-483F-8D71-1584645C4BCA@.microsoft.com...
> Hi
> Error 1203 is bad. Process ID %d attempting to unlock unowned resource
%.*ls.
> There are a number of KB articles indicating that it occurs up to version
> 8.00.661 (KB 326999). SP3a is 8.00.760. Get your servers to at least SQL
> Server sp3a and see if the error still occurs. Plus, if you are not on SQL
> Server 2000 sp3a, you are exposed to the Slammer virus.
> Regards
> Mike
>
> "bill" wrote:
> > I am finding Error 1203 Severity 20 periodically in my trace.
> >
> > This seems to correlate with intermittent failed insert statements
performed
> > by a stored procedure. The stored procedure is executed shortly before
this
> > error is recorded.
> >
> > Nothing is written to the SQL Server log.
> >
> > The error is occurring on SQL Server 2000 Enterprise, SP 2, build 2195,
> > running on W2K server.
> >
> > The same error occurs in a test database on SQL Server 2000 Standard, no
> > service packs, build 3790.
> >
> > I found one reference to it in response to a question on winnetmag.com:
> >
> > What is error msg 1203, "attempting to unlock unowned resource "?
> > Answered: This error indicates a bug in SQL Server. Several bugs that
caused
> > this error were fixed in SQL Server 2000, service pack 1. If you can
create
> > a script that will allow anyone to reproduce this problem, you should
send
> > it in to Microsoft SQL Server support.
> >
> > I can't reproduce this except in our database. dbcc checkdb indicates
no
> > errors.
> >
> > I am concerned about data loss without any error to detect it. Can
anyone
> > help me with this?
> >
> > Thanks
> > Bill
> >
> >
> >
> >|||Anthony,
SQL Server 2000 Service Pack 3a does protect against Slammer. The
original patch to protect against Slammer was MS02-039. SQL Server
SP3a, available at
http://www.microsoft.com/downloads/details.aspx?FamilyID=90dcd52c-0488-4e46-afbf-acace5369fa3&displaylang=en,
"corrects vulnerabilities including the Slammer (W32.slammer) virus."
It will not remove Slammer if it is present, and the page says "SQL 2000
Servers infected by the "Slammer" worm virus should follow instructions
on the Microsoft TechNet Web site before installing SP3a."
According to
http://www.microsoft.com/downloads/details.aspx?FamilyID=9552d43b-04eb-4af9-9e24-6cde4d933600&DisplayLang=en,
"Instances of SQL Server 2000 with Service Pack 2 (SP2) and security
patch MS02-039, MS02-043, MS02-056, or MS02-061, or instances with SP3
or later, are not vulnerable to the slammer worm."
Release A also protects against Slammer, but does not contain other
fixes from SP3a.
Steve Kass
Drew University
AnthonyThomas wrote:
>Mike:
>SQL Server SP3a DOES NOT contain the fix for the "Slammer Worm" virus,
>MS03-031. This was originally launched as build 817 but caused a but in the
>DtsGui.dll. This fix replaced the previous edition to build 818. This
>release caused a password issue when using SEM. This fix is build 819.
>SP3a is build 760.
>The newly released SQL Server 2000 Release A is a slipstream of the pre SP3a
>release code. If one uses this, then only SP3a need to be applied.
>Build 818:
>http://support.microsoft.com/?scid=kb;en-us;821277&spid=2852&sid=global
>
>Build 819:
>http://support.microsoft.com/kb/826161
>
>Release A:
>http://support.microsoft.com/default.aspx?scid=kb;en-us;826818
>
>Sincerely,
>
>Anthony Thomas
>
>|||I don't understand your question at all. Here's what I said:
Anthony,
SQL Server 2000 Service Pack 3a does protect against Slammer. The
original patch to protect against Slammer was MS02-039. SQL Server
SP3a, available at
http://www.microsoft.com/downloads/details.aspx?FamilyID=90dcd52c-0488-4e46-afbf-acace5369fa3&displaylang=en,
"corrects vulnerabilities including the Slammer (W32.slammer)
virus." It will not remove Slammer if it is present, and the page
says "SQL 2000 Servers infected by the "Slammer" worm virus should
follow instructions on the Microsoft TechNet Web site before
installing SP3a."
According to
http://www.microsoft.com/downloads/details.aspx?FamilyID=9552d43b-04eb-4af9-9e24-6cde4d933600&DisplayLang=en,
"Instances of SQL Server 2000 with Service Pack 2 (SP2) and security
patch MS02-039, MS02-043, MS02-056, or MS02-061, or instances with
SP3 or later, are not vulnerable to the slammer worm."
Release A also protects against Slammer, but does not contain other
fixes from SP3a.
Steve Kass
Drew University
You had incorrectly stated "SQL Server SP3a DOES NOT contain the fix for
the "Slammer Worm" virus MS03-031," and I corrected your misstatement.
It does. SQL Server build 818 appeared after Service Pack 3 (Service
Pack 3/3a is build 760), and build 818 corrected three post-Slammer
security vulnerabilities identified in MS03-031.
Slammer appeared after sp3 had been released, and it did not affect
anyone who had already installed sp3, or who had installed the even
early post-sp2 fix correcting the vulnerability ultimately exploited by
Slammer (pre-Slammer, pre-sp2 bulletin MS02-039). Everything to do with
Slammer (recognition of the vulnerability, the security bulletin, the
patch, the service pack that contained the patch, and finally the
exploit) happened well before the later and unrelated bulletin MS03-031
(build 818, which was post-sp3, not pre-sp3).
SK
AnthonyThomas wrote:
>Then why the need for MS03-031 for post SP3 or SP3a, both of which are only the 760 builds, while the MS03-031 was originally 817, then 818, closely followed by 819? Since the hot fixes and service packs are cumulative, why didn't the post SP2 hot fixes make it into the SP3(a) releases? Again, if they did, then why the need for the 817 through 819 builds?
>Sincerely,
>
>Anthony Thomas
>
>

Error 1203

I am finding Error 1203 Severity 20 periodically in my trace.
This seems to correlate with intermittent failed insert statements performed
by a stored procedure. The stored procedure is executed shortly before this
error is recorded.
Nothing is written to the SQL Server log.
The error is occurring on SQL Server 2000 Enterprise, SP 2, build 2195,
running on W2K server.
The same error occurs in a test database on SQL Server 2000 Standard, no
service packs, build 3790.
I found one reference to it in response to a question on winnetmag.com:
What is error msg 1203, "attempting to unlock unowned resource "?
Answered: This error indicates a bug in SQL Server. Several bugs that caused
this error were fixed in SQL Server 2000, service pack 1. If you can create
a script that will allow anyone to reproduce this problem, you should send
it in to Microsoft SQL Server support.
I can't reproduce this except in our database. dbcc checkdb indicates no
errors.
I am concerned about data loss without any error to detect it. Can anyone
help me with this?
Thanks
BillHi
Error 1203 is bad. Process ID %d attempting to unlock unowned resource %.*ls
.
There are a number of KB articles indicating that it occurs up to version
8.00.661 (KB 326999). SP3a is 8.00.760. Get your servers to at least SQL
Server sp3a and see if the error still occurs. Plus, if you are not on SQL
Server 2000 sp3a, you are exposed to the Slammer virus.
Regards
Mike
"bill" wrote:

> I am finding Error 1203 Severity 20 periodically in my trace.
> This seems to correlate with intermittent failed insert statements perform
ed
> by a stored procedure. The stored procedure is executed shortly before th
is
> error is recorded.
> Nothing is written to the SQL Server log.
> The error is occurring on SQL Server 2000 Enterprise, SP 2, build 2195,
> running on W2K server.
> The same error occurs in a test database on SQL Server 2000 Standard, no
> service packs, build 3790.
> I found one reference to it in response to a question on winnetmag.com:
> What is error msg 1203, "attempting to unlock unowned resource "?
> Answered: This error indicates a bug in SQL Server. Several bugs that caus
ed
> this error were fixed in SQL Server 2000, service pack 1. If you can creat
e
> a script that will allow anyone to reproduce this problem, you should send
> it in to Microsoft SQL Server support.
> I can't reproduce this except in our database. dbcc checkdb indicates no
> errors.
> I am concerned about data loss without any error to detect it. Can anyone
> help me with this?
> Thanks
> Bill
>
>|||Mike:
SQL Server SP3a DOES NOT contain the fix for the "Slammer Worm" virus,
MS03-031. This was originally launched as build 817 but caused a but in the
DtsGui.dll. This fix replaced the previous edition to build 818. This
release caused a password issue when using SEM. This fix is build 819.
SP3a is build 760.
The newly released SQL Server 2000 Release A is a slipstream of the pre SP3a
release code. If one uses this, then only SP3a need to be applied.
Build 818:
http://support.microsoft.com/?scid=...2852&sid=global
Build 819:
http://support.microsoft.com/kb/826161
Release A:
http://support.microsoft.com/defaul...kb;en-us;826818
Sincerely,
Anthony Thomas
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:94447A54-2C1F-483F-8D71-1584645C4BCA@.microsoft.com...
> Hi
> Error 1203 is bad. Process ID %d attempting to unlock unowned resource
%.*ls.[vbcol=seagreen]
> There are a number of KB articles indicating that it occurs up to version
> 8.00.661 (KB 326999). SP3a is 8.00.760. Get your servers to at least SQL
> Server sp3a and see if the error still occurs. Plus, if you are not on SQL
> Server 2000 sp3a, you are exposed to the Slammer virus.
> Regards
> Mike
>
> "bill" wrote:
>
performed[vbcol=seagreen]
this[vbcol=seagreen]
caused[vbcol=seagreen]
create[vbcol=seagreen]
send[vbcol=seagreen]
no[vbcol=seagreen]
anyone[vbcol=seagreen]|||Anthony,
SQL Server 2000 Service Pack 3a does protect against Slammer. The
original patch to protect against Slammer was MS02-039. SQL Server
SP3a, available at
http://www.microsoft.com/downloads/...displaylang=en,
"corrects vulnerabilities including the Slammer (W32.slammer) virus."
It will not remove Slammer if it is present, and the page says "SQL 2000
Servers infected by the "Slammer" worm virus should follow instructions
on the Microsoft technet Web site before installing SP3a."
According to
http://www.microsoft.com/downloads/...DisplayLang=en,
"Instances of SQL Server 2000 with Service Pack 2 (SP2) and security
patch MS02-039, MS02-043, MS02-056, or MS02-061, or instances with SP3
or later, are not vulnerable to the slammer worm."
Release A also protects against Slammer, but does not contain other
fixes from SP3a.
Steve Kass
Drew University
AnthonyThomas wrote:

>Mike:
>SQL Server SP3a DOES NOT contain the fix for the "Slammer Worm" virus,
>MS03-031. This was originally launched as build 817 but caused a but in th
e
>DtsGui.dll. This fix replaced the previous edition to build 818. This
>release caused a password issue when using SEM. This fix is build 819.
>SP3a is build 760.
>The newly released SQL Server 2000 Release A is a slipstream of the pre SP3
a
>release code. If one uses this, then only SP3a need to be applied.
>Build 818:
>http://support.microsoft.com/?scid=...2852&sid=global
>
>Build 819:
>http://support.microsoft.com/kb/826161
>
>Release A:
>http://support.microsoft.com/defaul...kb;en-us;826818
>
>Sincerely,
>
>Anthony Thomas
>
>|||Then why the need for MS03-031 for post SP3 or SP3a, both of which are only
the 760 builds, while the MS03-031 was originally 817, then 818, closely fol
lowed by 819? Since the hot fixes and service packs are cumulative, why did
n't the post SP2 hot fixes make it into the SP3(a) releases? Again, if they
did, then why the need for the 817 through 819 builds?
Sincerely,
Anthony Thomas
--
"Steve Kass" <skass@.drew.edu> wrote in message news:%23qrsygtyEHA.1300@.TK2
MSFTNGP14.phx.gbl...
Anthony,
SQL Server 2000 Service Pack 3a does protect against Slammer. The
original patch to protect against Slammer was MS02-039. SQL Server
SP3a, available at
http://www.microsoft.com/downloads/...displaylang=en,
"corrects vulnerabilities including the Slammer (W32.slammer) virus."
It will not remove Slammer if it is present, and the page says "SQL 2000
Servers infected by the "Slammer" worm virus should follow instructions
on the Microsoft technet Web site before installing SP3a."
According to
http://www.microsoft.com/downloads/...DisplayLang=en,
"Instances of SQL Server 2000 with Service Pack 2 (SP2) and security
patch MS02-039, MS02-043, MS02-056, or MS02-061, or instances with SP3
or later, are not vulnerable to the slammer worm."
Release A also protects against Slammer, but does not contain other
fixes from SP3a.
Steve Kass
Drew University
AnthonyThomas wrote:

>Mike:
>
>SQL Server SP3a DOES NOT contain the fix for the "Slammer Worm" virus,
>MS03-031. This was originally launched as build 817 but caused a but in
the
>DtsGui.dll. This fix replaced the previous edition to build 818. This
>release caused a password issue when using SEM. This fix is build 819.
>SP3a is build 760.
>
>The newly released SQL Server 2000 Release A is a slipstream of the pre S
P3a
>release code. If one uses this, then only SP3a need to be applied.
>
>Build 818:
>
>http://support.microsoft.com/?scid=...2852&sid=global
>
>
>Build 819:
>
>http://support.microsoft.com/kb/826161
>
>
>Release A:
>
>http://support.microsoft.com/defaul...kb;en-us;826818
>
>
>Sincerely,
>
>
>Anthony Thomas
>
>
>
>|||I don't understand your question at all. Here's what I said:
Anthony,
SQL Server 2000 Service Pack 3a does protect against Slammer. The
original patch to protect against Slammer was MS02-039. SQL Server
SP3a, available at
http://www.microsoft.com/downloads/...displaylang=en,
"corrects vulnerabilities including the Slammer (W32.slammer)
virus." It will not remove Slammer if it is present, and the page
says "SQL 2000 Servers infected by the "Slammer" worm virus should
follow instructions on the Microsoft technet Web site before
installing SP3a."
According to
http://www.microsoft.com/downloads/...DisplayLang=en,
"Instances of SQL Server 2000 with Service Pack 2 (SP2) and security
patch MS02-039, MS02-043, MS02-056, or MS02-061, or instances with
SP3 or later, are not vulnerable to the slammer worm."
Release A also protects against Slammer, but does not contain other
fixes from SP3a.
Steve Kass
Drew University
You had incorrectly stated "SQL Server SP3a DOES NOT contain the fix for
the "Slammer Worm" virus MS03-031," and I corrected your misstatement.
It does. SQL Server build 818 appeared after Service Pack 3 (Service
Pack 3/3a is build 760), and build 818 corrected three post-Slammer
security vulnerabilities identified in MS03-031.
Slammer appeared after sp3 had been released, and it did not affect
anyone who had already installed sp3, or who had installed the even
early post-sp2 fix correcting the vulnerability ultimately exploited by
Slammer (pre-Slammer, pre-sp2 bulletin MS02-039). Everything to do with
Slammer (recognition of the vulnerability, the security bulletin, the
patch, the service pack that contained the patch, and finally the
exploit) happened well before the later and unrelated bulletin MS03-031
(build 818, which was post-sp3, not pre-sp3).
SK
AnthonyThomas wrote:

>Then why the need for MS03-031 for post SP3 or SP3a, both of which are only the 760
builds, while the MS03-031 was originally 817, then 818, closely followed by 819?
Since the hot fixes and service packs are cumulative, why didn't the post SP2 hot fi
xes
make it into the SP3(a) releases? Again, if they did, then why the need for the 817 through
819 builds?
>Sincerely,
>
>Anthony Thomas
>
>