Error 18452

Hi,
If I connect to SQLServer Express via Windows Authentication it works fine. But if I use SQL Server Authentication it doesn't work with a new created user and sa (with a new password) too. I turned mixed mode on, registry key HKLM\Software\Microsoft\Microsoft Sql Server\MSSQL.1\\MSSQLServer\login has the value 2 and all ports are set to 1433 but there is still error 18452. Any suggestions?

Did you restart the server service ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||Yes, severeal times.
|||I guess the system you configured and the system you are connecting to are tw different ones then.|||No, it's the same system and I have only this one in the moment.
|||

What is the exact error message that you are getting back? Take a look at the errorlog as well to see what message is logged there.

How are you trying to connect? If you're connecting through an application, make sure that you don't specify integrated authentication in the connection string.

Thanks
Laurentiu

|||Restarting the server process was not enough. I had to restart windows and now it works.
Thank you.
sql

Error 15401 windows NT user or group not found+sql 2000

hi all,
i'm doing replication now ...when i add a new login to sqlserver i got
the message if i click ok..."Error 15401 windows NT user or group not
found"...i don't understand......why the error happens.......any one
pls help me!!
--thank youSQL Server cannot resolve the name of the login you specified. The name may
be incorrect, or it may belong to a different domain to which your current
domain does not have access.
Thanks
Laurentiu
Laurentiu Cristofor [MSFT]
Software Development Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"nafi" <hnbnafisha@.gmail.com> wrote in message
news:1168574381.666181.290820@.a75g2000cwd.googlegroups.com...
> hi all,
> i'm doing replication now ...when i add a new login to sqlserver i got
> the message if i click ok..."Error 15401 windows NT user or group not
> found"...i don't understand......why the error happens.......any one
> pls help me!!
> --thank you
>|||hi Mr.Laurentiu Cristofor,
thank u very much....yeh.. correct...my computer doesn't have access
to that domain
Laurentiu Cristofor [MSFT] wrote:[vbcol=seagreen]
> SQL Server cannot resolve the name of the login you specified. The name ma
y
> be incorrect, or it may belong to a different domain to which your current
> domain does not have access.
> Thanks
> Laurentiu
> --
> Laurentiu Cristofor [MSFT]
> Software Development Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "nafi" <hnbnafisha@.gmail.com> wrote in message
> news:1168574381.666181.290820@.a75g2000cwd.googlegroups.com...

Error 0X8007042B while restarting SQLServer Agent 2005

Apologies for cross posting wasn't sure which group does this belong.
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitIn\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while starting
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
Cheers
Annon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>
|||Hi,
This start account is indeed a member of local administrator group.
SQL Server is configured to run under mixed mode.
Tnx
[vbcol=seagreen]
> Annon
> Is this start account a member of the local administrators group?
> What security authentication is the SQL instance configured to use? Is
> it Windows or Mixed?
> "Annon" <Annon@.gmail_.com> wrote in message
> news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
|||Hmmm, strange , have you got the same after restarting windows?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e48c97fb24a3ec914@.msnews.microsoft. com...
> Hi,
> This start account is indeed a member of local administrator group.
> SQL Server is configured to run under mixed mode.
> Tnx
>
>
|||> Hmmm, strange , have you got the same after restarting windows?
Hello Uri,
The machine was shut down when it was moved to new location.
I started to get this error after I turned on the machine and noticed that
SQL Server Agent was not running and when I tried to restart it.
|||
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed
> that
> SQL Server Agent was not running and when I tried to restart it.
I won't be able to reboot the machine until later, I will try to reboot in
about 6 hours time and see if this solves the problem.
Cheers
|||Hi
It seems like Agent couldn't connect.
Try to change the account to SQL Server authentication for only
troubleshooting.
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e78c97fb3c8a7f156@.msnews.microsoft. com...
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed that
> SQL Server Agent was not running and when I tried to restart it.
>
|||> Hi
> It seems like Agent couldn't connect.
> Try to change the account to SQL Server authentication for only
> troubleshooting.
Hi Uri,
SQL Server is already configured to use mixed mode authentication. I also
tried by creating a new user, adding this new user to the Administrator group
and then added this user to serverAdmin/Sysadmin group in SQL Server. I still
get the same error.
Funny thing is I moved two SQL Server machines, one of them is running just
fine without any problem.
The machine in question never had any problems - It was running for last
145 days w/o any problem at all. Fairly strange.
Tnx

Error 0X8007042B while restarting SQLServer Agent 2005

Apologies for cross posting wasn't sure which group does this belong.
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitIn\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while starting
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
CheersAnnon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft.com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>

Error 0X8007042B while restarting SQLServer Agent 2005

Apologies for cross posting wasn't sure which group does this belong.
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitI
n\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while startin
g
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
CheersAnnon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft.com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>|||Hi,
This start account is indeed a member of local administrator group.
SQL Server is configured to run under mixed mode.
Tnx
[vbcol=seagreen]
> Annon
> Is this start account a member of the local administrators group?
> What security authentication is the SQL instance configured to use? Is
> it Windows or Mixed?
> "Annon" <Annon@.gmail_.com> wrote in message
> news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft.com...
>|||Hmmm, strange , have you got the same after restarting windows?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e48c97fb24a3ec914@.msnews.microsoft.com...
> Hi,
> This start account is indeed a member of local administrator group.
> SQL Server is configured to run under mixed mode.
> Tnx
>
>|||> Hmmm, strange , have you got the same after restarting windows?
Hello Uri,
The machine was shut down when it was moved to new location.
I started to get this error after I turned on the machine and noticed that
SQL Server Agent was not running and when I tried to restart it.|||
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed
> that
> SQL Server Agent was not running and when I tried to restart it.
I won't be able to reboot the machine until later, I will try to reboot in
about 6 hours time and see if this solves the problem.
Cheers|||Hi
It seems like Agent couldn't connect.
Try to change the account to SQL Server authentication for only
troubleshooting.
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e78c97fb3c8a7f156@.msnews.microsoft.com...
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed that
> SQL Server Agent was not running and when I tried to restart it.
>|||> Hi
> It seems like Agent couldn't connect.
> Try to change the account to SQL Server authentication for only
> troubleshooting.
Hi Uri,
SQL Server is already configured to use mixed mode authentication. I also
tried by creating a new user, adding this new user to the Administrator grou
p
and then added this user to serverAdmin/Sysadmin group in SQL Server. I stil
l
get the same error.
Funny thing is I moved two SQL Server machines, one of them is running just
fine without any problem.
The machine in question never had any problems - It was running for last
145 days w/o any problem at all. Fairly strange.
Tnx

Error 0X8007042B while restarting SQLServer Agent 2005

Apologies for cross posting wasn't sure which group does this belong.
Hi,
I have just moved SQL Server 2005 to a new domain and am getting an error
with Error code 0X8007042B while trying to restart SQL Server agent. The
message in Errorlog says
SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of Sysadmin
role.
The account under which SQLServer agent is set to run indeed a member of
the Sysadmin role. I have also tried to run SQLServer Agent under the bulitIn\Administrator
as well as domain\Administrator user and get the same error. I also get the
same error while trying to run the SQL Server agent under local System or
network services user. The SQL Server service is currently running under
Domain\Administrator account.
I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
I saw some references on the web about running into this error while starting
SQL Server instance but nothing about SQL Server agent. Can someone please
help?
Any helps gratefully acknowledged.
Cheers
Annon
Is this start account a member of the local administrators group?
What security authentication is the SQL instance configured to use? Is it
Windows or Mixed?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
> Apologies for cross posting wasn't sure which group does this belong.
> Hi,
> I have just moved SQL Server 2005 to a new domain and am getting an error
> with Error code 0X8007042B while trying to restart SQL Server agent. The
> message in Errorlog says
> SQLServerAgent couldn't be started (reason SQLServer Agent must be able to
> conenct to SQLServer as SysAdmin but "(Unknown)" is not a member of
> Sysadmin role.
> The account under which SQLServer agent is set to run indeed a member of
> the Sysadmin role. I have also tried to run SQLServer Agent under the
> bulitIn\Administrator as well as domain\Administrator user and get the
> same error. I also get the same error while trying to run the SQL Server
> agent under local System or network services user. The SQL Server service
> is currently running under Domain\Administrator account.
> I am using Windows 2003 SP 1 and SQL Server 2005 EE SP 1.
> I saw some references on the web about running into this error while
> starting SQL Server instance but nothing about SQL Server agent. Can
> someone please help?
> Any helps gratefully acknowledged.
> Cheers
>
|||Hi,
This start account is indeed a member of local administrator group.
SQL Server is configured to run under mixed mode.
Tnx
[vbcol=seagreen]
> Annon
> Is this start account a member of the local administrators group?
> What security authentication is the SQL instance configured to use? Is
> it Windows or Mixed?
> "Annon" <Annon@.gmail_.com> wrote in message
> news:e689170a63df8c97faf6e02ee4c@.msnews.microsoft. com...
|||Hmmm, strange , have you got the same after restarting windows?
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e48c97fb24a3ec914@.msnews.microsoft. com...
> Hi,
> This start account is indeed a member of local administrator group.
> SQL Server is configured to run under mixed mode.
> Tnx
>
>
|||> Hmmm, strange , have you got the same after restarting windows?
Hello Uri,
The machine was shut down when it was moved to new location.
I started to get this error after I turned on the machine and noticed that
SQL Server Agent was not running and when I tried to restart it.
|||
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed
> that
> SQL Server Agent was not running and when I tried to restart it.
I won't be able to reboot the machine until later, I will try to reboot in
about 6 hours time and see if this solves the problem.
Cheers
|||Hi
It seems like Agent couldn't connect.
Try to change the account to SQL Server authentication for only
troubleshooting.
"Annon" <Annon@.gmail_.com> wrote in message
news:e689170a63e78c97fb3c8a7f156@.msnews.microsoft. com...
> Hello Uri,
> The machine was shut down when it was moved to new location.
> I started to get this error after I turned on the machine and noticed that
> SQL Server Agent was not running and when I tried to restart it.
>
|||> Hi
> It seems like Agent couldn't connect.
> Try to change the account to SQL Server authentication for only
> troubleshooting.
Hi Uri,
SQL Server is already configured to use mixed mode authentication. I also
tried by creating a new user, adding this new user to the Administrator group
and then added this user to serverAdmin/Sysadmin group in SQL Server. I still
get the same error.
Funny thing is I moved two SQL Server machines, one of them is running just
fine without any problem.
The machine in question never had any problems - It was running for last
145 days w/o any problem at all. Fairly strange.
Tnx

ERROR - SQL Server 7, Reporting Services, and SQL 2000 Functions

I sincerely hope this is not the case...
Is it safe to assume that SQL Server Reporting Services cannot "talk" to SQL
Server 7 databases?
One of our developers is trying to run a simple test query against our SQL
Server 7 database; however, he is getting errors : "'DATABASEPROPERTYEX' is
not a recognized function name.". This is native to SQL 2000, though - so we
know why the error is occuring.
The question is why not use DATABASEPROPERTY for backwards compatibility?
How can we work around this limitation? We have tried modifying the provider
properties with no success; it appears this function call occurs behind the
scenes.
Thank you for your insight.
Elliot M. Rodriguez, MCSD
My .Net blog, with tips here and there:
http://derivedclass.europe.webmatrixhosting.netSQL7 did not support collations like SQL2000 does and the DATABASEPROPERTY
function does not have a Collation property. Having said that, this could
have been handled better :-)
You need to go to the "Data Options" tab of the "Dataset" dialog in
report designer for any datasets originating from SQL7
On the Data Options tab you will see that all settings contain "Auto".
Replace the Auto-settings with the following settings:
Collation = Latin1_General
Case sensitivity = false
Kanatype sensitivity = false
Width sensitivity = false
Accent sensitivity = true
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Elliot M. Rodriguez" <someemail> wrote in message
news:%23LY0TvJ9DHA.2756@.TK2MSFTNGP10.phx.gbl...
> I sincerely hope this is not the case...
> Is it safe to assume that SQL Server Reporting Services cannot "talk" to
SQL
> Server 7 databases?
> One of our developers is trying to run a simple test query against our SQL
> Server 7 database; however, he is getting errors : "'DATABASEPROPERTYEX'
is
> not a recognized function name.". This is native to SQL 2000, though - so
we
> know why the error is occuring.
> The question is why not use DATABASEPROPERTY for backwards compatibility?
> How can we work around this limitation? We have tried modifying the
provider
> properties with no success; it appears this function call occurs behind
the
> scenes.
> Thank you for your insight.
> --
> Elliot M. Rodriguez, MCSD
> My .Net blog, with tips here and there:
> http://derivedclass.europe.webmatrixhosting.net
>|||Jasper:
MANY thanks - works as described. I hope a KB comes of this; this is going
on my blog (with credit to you, of course :D)
Elliot M. Rodriguez, MCSD
My .Net blog, with tips here and there:
http://derivedclass.europe.webmatrixhosting.net
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:etPHbvL9DHA.2028@.TK2MSFTNGP10.phx.gbl...
> SQL7 did not support collations like SQL2000 does and the DATABASEPROPERTY
> function does not have a Collation property. Having said that, this could
> have been handled better :-)
> You need to go to the "Data Options" tab of the "Dataset" dialog in
> report designer for any datasets originating from SQL7
> On the Data Options tab you will see that all settings contain "Auto".
> Replace the Auto-settings with the following settings:
> Collation = Latin1_General
> Case sensitivity = false
> Kanatype sensitivity = false
> Width sensitivity = false
> Accent sensitivity = true
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
>
> "Elliot M. Rodriguez" <someemail> wrote in message
> news:%23LY0TvJ9DHA.2756@.TK2MSFTNGP10.phx.gbl...
> SQL
SQL
> is
so
> we
compatibility?
> provider
> the
>

erratic behavior with dataset and report preview

I am on SQLServer 2005

I have a sp with lot of params. I checked my sp. It works fine for every param.

My dataset is using the sp. It seems to pick the field list and params, but it will not return any result. I passed the same param to the ds as I did to sp. But, the report preview seems to alternate between displaying all data irrespective of the rpt criteria or nothing.

I do not have permission to run trace on the server

Any idea how to resolve this?

If you are using the report preview through Visual Studio, then you should know that reporting services tries to cache data from the data source so that formatting changes on long running reports do not take ages to develop by having to wait for the query to rerun. This has often cause reports to display with inconsistent data in the preview pane.

Check the location where the RDL file sits in the file system (the project folder) and you should see files with the same name as your RDL with a .data extension. This is where the designer caches the data and they safe to delete.

I have not found a way to stop this behaviour (and I don't think I would want to as it speeds up development) but I think it would be useful to be able to set this as an option in Visual Sudio.

It could of course be a bug in your code so I also suggest you deploy the report to the report server and run your report from the browser. If this still has issues then it's a bug in your code.

|||

I did clear the .data file. Still the same result. Rpt preview fetches no records.

Thx

|||

And is it fine when you deploy the report and test it from the browser?