Error when trying to log in to SQL server

I've just finished developing a web app, which works fine on my PC, running IIS locally. It uses windows authentication and a trusted connection to retrieve data from SQL server. So far so routine. When I deploy the app to my live server, it returns the error:

Login failed for user '\'

The stack trace seems to indicate that it's at the point where the app tries to retrieve data that the error occurs. I proved this by changing my connection string to explicitly define the log on, and it retrieved the data no problem.

I set up a very simple webform with a label on, to return what it thought the user's log on name was, and it returns the correct name.

Any ideas as to why the username isn't being correctly passed to SQL server?Have you made sure the Web Account is a valid user of the SQL Server? If the IIS box and the SQL box are different you have to ensure the user has network rights too.|||Yes, the user (me!) definitely has rights on the SQL server. How come it works locally on my PC, but not on the server?

What network rights do you think I should investigate?

Thanks.|||Sorry I mis-read your original post, I didn't notice that your site was using NT Authentication. So here is my mental checklist:
1. Web Server has access to the Domain server to authenticate the user
2. The Web Server isn't the Domain Server
3. SQL Server security logins knows about the Windows user/user group
4. The SQL Database knows about the Windows user/user group

I mentioned the network security because when you use anon web access the user must have network access to go across machines. That "shouldn't" be an issue here.

Also run SQL Profiler to see if the user is getting set to SQL and then going wrong. Sounds more like its a problem on the web server though, something wrong with the impersonation.|||I'm positive that the user is being authenticated properly on the app, because when I load a simple page with a label which displays the user name, it displays correctly. For some reason this user name isn't getting passed to SQL server correctly.

I tried deploying the application to the box which has the SQL server running, and gess what? It worked. So does this mean that the first box can't access the domain server? Any idea how I can check that?

I'll have a think, and let you know how I get on.

Cheers.|||Hang on, just cause you're using Web Authentication doesn't mean it will impersonate the user onto SQL Server. Do you set the principal security when the user connects?

Check out:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/SecNetch03.asp

Error When SQL 7.0 starts. Please Help.

This is what the error log says.

2003-08-12 14:09:53.49 server Copyright (C) 1988-2000 Microsoft Corporation.
2003-08-12 14:09:53.49 server All rights reserved.
2003-08-12 14:09:53.49 server Server Process ID is 418.
2003-08-12 14:09:53.49 server Logging SQL Server messages in file 'd:\data\MSSQL\log\ERRORLOG'.
2003-08-12 14:09:53.50 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2003-08-12 14:09:53.55 server SQL Server configured for thread mode processing.
2003-08-12 14:09:53.55 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2003-08-12 14:09:53.60 server Attempting to initialize Distributed Transaction Coordinator.
2003-08-12 14:09:54.63 spid2 Starting up database 'master'.
2003-08-12 14:09:54.74 server Using 'SSNETLIB.DLL' version '8.0.534'.
2003-08-12 14:09:54.74 spid5 Starting up database 'model'.
2003-08-12 14:09:54.75 spid2 Server name is 'OPTICAL1'.
2003-08-12 14:09:54.75 spid9 Starting up database 'pubs'.
2003-08-12 14:09:54.75 spid8 Starting up database 'msdb'.
2003-08-12 14:09:54.75 spid10 Starting up database 'Northwind'.
2003-08-12 14:09:54.77 spid11 Starting up database 'otg'.
2003-08-12 14:09:54.77 server SQL server listening on 172.16.16.37: 1433.
2003-08-12 14:09:54.77 server SQL server listening on 127.0.0.1: 1433.
2003-08-12 14:09:54.78 server SQL server listening on TCP, Shared Memory, Named Pipes.
2003-08-12 14:09:54.78 server SQL Server is ready for client connections
2003-08-12 14:09:54.78 spid5 Error: 9003, Severity: 20, State: 1
2003-08-12 14:09:54.78 spid5 The LSN (4:396:1) passed to log scan in database 'model' is invalid..When this happens, the MSSQLSERVER Service fails to start. :(|||I copied the Model Database from the CD into the Data directory, and restarted the service.sql

Error when SQL 2000 start

When starting my SQL Server 2000 generate error and stop. This is the log:
Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)

2004-01-20 11:05:36.59 server Copyright (C) 1988-2000 Microsoft Corporation.
2004-01-20 11:05:36.59 server All rights reserved.
2004-01-20 11:05:36.59 server Server Process ID is 115.
2004-01-20 11:05:36.59 server Logging SQL Server messages in file 'C:\MSSQL7\log\ERRORLOG'.
2004-01-20 11:05:36.63 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-01-20 11:05:36.66 server SQL Server configured for thread mode processing.
2004-01-20 11:05:36.66 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2004-01-20 11:05:36.67 server Attempting to initialize Distributed Transaction Coordinator.
2004-01-20 11:05:38.69 spid3 Starting up database 'master'.
2004-01-20 11:05:38.85 spid3 Server name is 'DB_SERVER'.
2004-01-20 11:05:38.85 server Using 'SSNETLIB.DLL' version '8.0.194'.
2004-01-20 11:05:38.87 server SQL server listening on TCP, Shared Memory, Named Pipes.
2004-01-20 11:05:38.87 server SQL server listening on 192.168.1.29:1433, 172.16.48.10:1433, 127.0.0.1:1433.
2004-01-20 11:05:38.87 server SQL Server is ready for client connections
2004-01-20 11:05:38.87 spid5 Starting up database 'model'.
2004-01-20 11:05:38.87 spid8 Starting up database 'msdb'.
2004-01-20 11:05:38.87 spid9 Starting up database 'pubs'.
2004-01-20 11:05:38.87 spid10 Starting up database 'Northwind'.
2004-01-20 11:05:38.87 spid11 Starting up database 'SIM'.
2004-01-20 11:05:39.21 spid5 Error: 9003, Severity: 20, State: 1
2004-01-20 11:05:39.21 spid5 The LSN (5:377:1) passed to log scan in database 'model' is invalid..
2004-01-20 11:05:39.31 spid8 Bypassing recovery for database 'msdb' because it is marked SUSPECT.
2004-01-20 11:05:39.39 spid11 Starting up database 'GMS'.
2004-01-20 11:05:39.39 spid8 Starting up database 'euro'.
2004-01-20 11:05:40.14 spid10 Starting up database 'TigrisDB'.have you moved your system's devices around recently?|||Originally posted by ms_sql_dba
have you moved your system's devices around recently?

No, but 2 weeks before, I receive a message (Administrator alert) from PC with installed on SQL 2000.

"Drive Z: is nearly full. 1216688128 bytes are available.
Please warn users and delete unneeded files."

On "drive Z:" there is 9GB free space ...

Thanks for reading.
Best Regards|||looks like your system databases is having some problem.
try restarting sql server in single user mode and do a dbcc checkdb on model and msdb.

If this do not work, you might have to rebuild them

amit

Error when programmatically creating a data driven subscription

Hi,
any ideas what causes this?
An internal error occurred on the report server. See the error log for more
details. --> An internal error occurred on the report server. See the error
log for more details. --> Subquery returned more than 1 value. This is not
permitted when the subquery follows =, !=, <, <= , >, >= or when
the subquery is used as an expression.
The statement has been terminated.
The log file shows
aspnet_wp!library!8c0!7/09/2004-09:08:27:: Using folder C:\Program
Files\Microsoft SQL Server\MSSQL\Reporting Services\RSTempFiles for
temporary files.
aspnet_wp!library!8c0!7/09/2004-09:08:27:: i INFO: Cleaned 0 batch records,
0 policies, 0 sessions, 0 cache entries, 1 snapshots, 4 chunks, 0 running
jobs
aspnet_wp!library!88c!09/07/2004-09:12:32:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details. --> System.Data.SqlClient.SqlException: Subquery returned more
than 1 value. This is not permitted when the subquery follows =, !=, <, <= ,
>, >= or when the subquery is used as an expression.
The statement has been terminated.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at
Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
at
Microsoft.ReportingServices.Library.SubscriptionDB.CreateSubscription(Subscr
iptionImpl subscription)
-- End of inner exception stack trace --
thanks
MattActually, this is also occuring when trying to create a subscription via
report manager. I wonder if the reporting service installation is stuffed.
Any suggestions?
thanks
"Matt" <NoSpam:Matthew.Moran@.Computercorp.com.au> wrote in message
news:OxffpsHlEHA.3428@.TK2MSFTNGP14.phx.gbl...
> Hi,
> any ideas what causes this?
> An internal error occurred on the report server. See the error log for
more
> details. --> An internal error occurred on the report server. See the
error
> log for more details. --> Subquery returned more than 1 value. This is not
> permitted when the subquery follows =, !=, <, <= , >, >= or
when
> the subquery is used as an expression.
> The statement has been terminated.
> The log file shows
> aspnet_wp!library!8c0!7/09/2004-09:08:27:: Using folder C:\Program
> Files\Microsoft SQL Server\MSSQL\Reporting Services\RSTempFiles for
> temporary files.
> aspnet_wp!library!8c0!7/09/2004-09:08:27:: i INFO: Cleaned 0 batch
records,
> 0 policies, 0 sessions, 0 cache entries, 1 snapshots, 4 chunks, 0 running
> jobs
> aspnet_wp!library!88c!09/07/2004-09:12:32:: e ERROR: Throwing
>
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for
more
> details., ;
> Info:
>
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for
more
> details. --> System.Data.SqlClient.SqlException: Subquery returned more
> than 1 value. This is not permitted when the subquery follows =, !=, <, <=,
> >, >= or when the subquery is used as an expression.
> The statement has been terminated.
> at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
> cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
> at
>
Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
> at
>
Microsoft.ReportingServices.Library.SubscriptionDB.CreateSubscription(Subscr
> iptionImpl subscription)
> -- End of inner exception stack trace --
> thanks
> Matt
>

Error when issuing BACKUP LOG mydb with truncate_only

Hi,

Following error appears in the SQL Server error log when I execute BACKUP Log db with truncate_only using a stored procedure. The stored proc I am using is as follows:

CREATE procedure spm_tranlog as

declare @.DBName as Varchar(120)

select @.DBName = DB_name()

dump transaction @.DBName with truncate_only

GO

There are data import processes running in the night, before starting the processes we are executing spm_tranlog procedure to clear the transaction logs. The following error appears in log after executing the spm_tranlog:

“BACKUP failed to complete the command exec spm_tranlog”

This always happens after weekly server maintenance tasks. The scheduled maintenance tasks I am running are:Index rebuild, truncate log and shrinking database. There were no other processes running during that time when the spm_tranlog prodecure fail.

The Database size is 40GB, Log size is 80MB.

The database is in the simple recovery model.The database is in the simple recovery model.

I am running SQL Server 2000 (SP4) on windows server 2003.

Please help me to resolve this issue.

Thanks,

Roshan.

Hello Roshan,

Try this instead:

create procedure spm_tranlog

as

declare @.DBName asvarchar(120), @.sql asvarchar(200)

select @.DBName =DB_name()

select @.sql ='backup log '+ @.DBName +' with truncate_only'

execute(@.sql)
go

Hope this helps.

Jarret

|||

Hi Jarret,

Thanks for your reply. I have changed the DUMP TRANSACTION to BACKUP LOG in my stored proc, but still shows same error message.

Usualy the dump transaction (or Backup Log) fails only when server is backing up databases or shrinking.

My problem is Backup Log satement fails even there are no database backups running. This is really strange.

Thanks,

Roshan.

|||

Can you run the backup log statement directly without getting an error?

backup log DB_Name with truncate_only

Jarret

|||

No. its not allowing me to run the backup log statement directly.

Roshan.

|||

Can you post the error message you are getting and the exact statement you are running?

Are you sure you have permissions to do this? You need to be a sysadmin on the server or in the db_owner role of the database.

Jarret

|||

Hi Jarret,

I am receiving following error in the SQL server log: "BACKUP failed to complete the command exec spm_tranlog"

and I am running following stored proc:

CREATE procedure spm_tranlog as

/* 29/03/2006 RXP: Modified to get the database name using system function
* DB_name(), to avoid hardcoding database name.
*
*/

declare @.DBName as Varchar(120)

select @.DBName = DB_name()
dump transaction @.DBName with truncate_only
GO

This was running perfecctly for a long time, suddenly start creating problems. The user running this proc has sysadmin rights.

Thanks,

Roshan.

|||

How are you running the stored procedure, just 'exec spm_tranlog' from a new query window?

Bypassing the stored procedure, can you try to run this:

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
dump transaction @.DBName with truncate_only

And also...

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
backup log @.DBName with truncate_only

If these still don't work, post the error message(s) you get from each.

Jarret

|||You cant truncate the Log with SIMPLE PLAN in a DB. Because it is doing by itself.

Error when issuing BACKUP LOG mydb with truncate_only

Hi,

Following error appears in the SQL Server error log when I execute BACKUP Log db with truncate_only using a stored procedure. The stored proc I am using is as follows:

CREATE procedure spm_tranlog as

declare @.DBName as Varchar(120)

select @.DBName = DB_name()

dump transaction @.DBName with truncate_only

GO

There are data import processes running in the night, before starting the processes we are executing spm_tranlog procedure to clear the transaction logs. The following error appears in log after executing the spm_tranlog:

“BACKUP failed to complete the command exec spm_tranlog”

This always happens after weekly server maintenance tasks. The scheduled maintenance tasks I am running are:Index rebuild, truncate log and shrinking database. There were no other processes running during that time when the spm_tranlog prodecure fail.

The Database size is 40GB, Log size is 80MB.

The database is in the simple recovery model.The database is in the simple recovery model.

I am running SQL Server 2000 (SP4) on windows server 2003.

Please help me to resolve this issue.

Thanks,

Roshan.

Hello Roshan,

Try this instead:

create procedure spm_tranlog

as

declare @.DBName asvarchar(120), @.sql asvarchar(200)

select @.DBName =DB_name()

select @.sql ='backup log '+ @.DBName +' with truncate_only'

execute(@.sql)
go

Hope this helps.

Jarret

|||

Hi Jarret,

Thanks for your reply. I have changed the DUMP TRANSACTION to BACKUP LOG in my stored proc, but still shows same error message.

Usualy the dump transaction (or Backup Log) fails only when server is backing up databases or shrinking.

My problem is Backup Log satement fails even there are no database backups running. This is really strange.

Thanks,

Roshan.

|||

Can you run the backup log statement directly without getting an error?

backup log DB_Name with truncate_only

Jarret

|||

No. its not allowing me to run the backup log statement directly.

Roshan.

|||

Can you post the error message you are getting and the exact statement you are running?

Are you sure you have permissions to do this? You need to be a sysadmin on the server or in the db_owner role of the database.

Jarret

|||

Hi Jarret,

I am receiving following error in the SQL server log: "BACKUP failed to complete the command exec spm_tranlog"

and I am running following stored proc:

CREATE procedure spm_tranlog as

/* 29/03/2006 RXP: Modified to get the database name using system function
* DB_name(), to avoid hardcoding database name.
*
*/

declare @.DBName as Varchar(120)

select @.DBName = DB_name()
dump transaction @.DBName with truncate_only
GO

This was running perfecctly for a long time, suddenly start creating problems. The user running this proc has sysadmin rights.

Thanks,

Roshan.

|||

How are you running the stored procedure, just 'exec spm_tranlog' from a new query window?

Bypassing the stored procedure, can you try to run this:

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
dump transaction @.DBName with truncate_only

And also...

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
backup log @.DBName with truncate_only

If these still don't work, post the error message(s) you get from each.

Jarret

|||You cant truncate the Log with SIMPLE PLAN in a DB. Because it is doing by itself.

Error when issuing BACKUP LOG mydb with truncate_only

Hi,

Following error appears in the SQL Server error log when I execute BACKUP Log db with truncate_only using a stored procedure. The stored proc I am using is as follows:

CREATE procedure spm_tranlog as

declare @.DBName as Varchar(120)

select @.DBName = DB_name()

dump transaction @.DBName with truncate_only

GO

There are data import processes running in the night, before starting the processes we are executing spm_tranlog procedure to clear the transaction logs. The following error appears in log after executing the spm_tranlog:

“BACKUP failed to complete the command exec spm_tranlog”

This always happens after weekly server maintenance tasks. The scheduled maintenance tasks I am running are:Index rebuild, truncate log and shrinking database. There were no other processes running during that time when the spm_tranlog prodecure fail.

The Database size is 40GB, Log size is 80MB.

The database is in the simple recovery model.The database is in the simple recovery model.

I am running SQL Server 2000 (SP4) on windows server 2003.

Please help me to resolve this issue.

Thanks,

Roshan.

Hello Roshan,

Try this instead:

create procedure spm_tranlog

as

declare @.DBName asvarchar(120), @.sql asvarchar(200)

select @.DBName =DB_name()

select @.sql ='backup log '+ @.DBName +' with truncate_only'

execute(@.sql)
go

Hope this helps.

Jarret

|||

Hi Jarret,

Thanks for your reply. I have changed the DUMP TRANSACTION to BACKUP LOG in my stored proc, but still shows same error message.

Usualy the dump transaction (or Backup Log) fails only when server is backing up databases or shrinking.

My problem is Backup Log satement fails even there are no database backups running. This is really strange.

Thanks,

Roshan.

|||

Can you run the backup log statement directly without getting an error?

backup log DB_Name with truncate_only

Jarret

|||

No. its not allowing me to run the backup log statement directly.

Roshan.

|||

Can you post the error message you are getting and the exact statement you are running?

Are you sure you have permissions to do this? You need to be a sysadmin on the server or in the db_owner role of the database.

Jarret

|||

Hi Jarret,

I am receiving following error in the SQL server log: "BACKUP failed to complete the command exec spm_tranlog"

and I am running following stored proc:

CREATE procedure spm_tranlog as

/* 29/03/2006 RXP: Modified to get the database name using system function
* DB_name(), to avoid hardcoding database name.
*
*/

declare @.DBName as Varchar(120)

select @.DBName = DB_name()
dump transaction @.DBName with truncate_only
GO

This was running perfecctly for a long time, suddenly start creating problems. The user running this proc has sysadmin rights.

Thanks,

Roshan.

|||

How are you running the stored procedure, just 'exec spm_tranlog' from a new query window?

Bypassing the stored procedure, can you try to run this:

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
dump transaction @.DBName with truncate_only

And also...

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
backup log @.DBName with truncate_only

If these still don't work, post the error message(s) you get from each.

Jarret

|||You cant truncate the Log with SIMPLE PLAN in a DB. Because it is doing by itself.sql

Error when issuing BACKUP LOG mydb with truncate_only

Hi,

Following error appears in the SQL Server error log when I execute BACKUP Log db with truncate_only using a stored procedure. The stored proc I am using is as follows:

CREATE procedure spm_tranlog as

declare @.DBName as Varchar(120)

select @.DBName = DB_name()

dump transaction @.DBName with truncate_only

GO

There are data import processes running in the night, before starting the processes we are executing spm_tranlog procedure to clear the transaction logs. The following error appears in log after executing the spm_tranlog:

“BACKUP failed to complete the command exec spm_tranlog”

This always happens after weekly server maintenance tasks. The scheduled maintenance tasks I am running are: Index rebuild, truncate log and shrinking database. There were no other processes running during that time when the spm_tranlog prodecure fail.

The Database size is 40GB, Log size is 80MB.

The database is in the simple recovery model.The database is in the simple recovery model.

I am running SQL Server 2000 (SP4) on windows server 2003.

Please help me to resolve this issue.

Thanks,

Roshan.

Hello Roshan,

Try this instead:

create procedure spm_tranlog

as

declare @.DBName as varchar(120), @.sql as varchar(200)

select @.DBName = DB_name()

select @.sql = 'backup log ' + @.DBName + ' with truncate_only'

execute (@.sql)
go

Hope this helps.

Jarret

|||

Hi Jarret,

Thanks for your reply. I have changed the DUMP TRANSACTION to BACKUP LOG in my stored proc, but still shows same error message.

Usualy the dump transaction (or Backup Log) fails only when server is backing up databases or shrinking.

My problem is Backup Log satement fails even there are no database backups running. This is really strange.

Thanks,

Roshan.

|||

Can you run the backup log statement directly without getting an error?

backup log DB_Name with truncate_only

Jarret

|||

No. its not allowing me to run the backup log statement directly.

Roshan.

|||

Can you post the error message you are getting and the exact statement you are running?

Are you sure you have permissions to do this? You need to be a sysadmin on the server or in the db_owner role of the database.

Jarret

|||

Hi Jarret,

I am receiving following error in the SQL server log: "BACKUP failed to complete the command exec spm_tranlog"

and I am running following stored proc:

CREATE procedure spm_tranlog as

/* 29/03/2006 RXP: Modified to get the database name using system function
* DB_name(), to avoid hardcoding database name.
*
*/

declare @.DBName as Varchar(120)

select @.DBName = DB_name()
dump transaction @.DBName with truncate_only
GO

This was running perfecctly for a long time, suddenly start creating problems. The user running this proc has sysadmin rights.

Thanks,

Roshan.

|||

How are you running the stored procedure, just 'exec spm_tranlog' from a new query window?

Bypassing the stored procedure, can you try to run this:

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
dump transaction @.DBName with truncate_only

And also...

declare @.DBName as Varchar(120)
select @.DBName = DB_name()
backup log @.DBName with truncate_only

If these still don't work, post the error message(s) you get from each.

Jarret

|||You cant truncate the Log with SIMPLE PLAN in a DB. Because it is doing by itself.

Error when installing SQL Server Express

Hi All,

I have a problem when installing SQL Server Express Advanced Edition

It crash when installing Database Services, the log file contains this message

.....

<Func Name='GetSkuIt'>
GetServiceUserGroup failed for SQLEXPRESS, 5
Error Code: 0x80070534 (1332)
Windows Error Text: Le mappage entre les noms de compte et les ID de scurit n'a pas t effectu.
Source File Name: sqlca\sqlcax.cpp
Compiler Timestamp: Fri Feb 9 22:35:05 2007
Function Name: SetInstanceProperty
Source Line Number: 1223

Error Code: 1332
MSI (s) (E0!E8) [10:34:39:288]: Produit : Microsoft SQL Server 2005 -- Erreur 29528. Le programme d'installation a rencontr une erreur inattendue pendant Dfinition des proprits internes. L'erreur est : Erreur irrcuprable lors de l'installation.

Erreur 29528. Le programme d'installation a rencontr une erreur inattendue pendant Dfinition des proprits internes. L'erreur est : Erreur irrcuprable lors de l'installation.

<EndFunc Name='LaunchFunction' Return='1332' GetLastError='203'>
Fin de l'action 10:34:39 : SetInstanceProperty.D20239D7_E87C_40C9_9837_E70B8D4882C2. Valeur renvoye : 3.
Fin de l'action 10:34:39 : INSTALL. Valeur renvoye : 3.
.......

Can someone help me ?

Thx

Hi,

this might helps http://support.microsoft.com/default.aspx/kb/925976.

|||

No, it won't.

Maybe my windows was in a bad state.

I've see that there is no group in local group ..... and a lot of bad news.

I format .........

Thx for your help.

Error when executing ALTER DATABASE statement

Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
ALTER DATABASE <Your database name>
SET RECOVERY FULL
but I am getting the following error:
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
Rajesh
It looks like a permission issue. Are you a member of sysadmin, dbcreator
or db_owner?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Rajesh" <Rajesh@.discussions.microsoft.com> wrote in message
news:4EC91AF7-A227-4A52-86F1-C4F0529A8AAD@.microsoft.com...
Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
ALTER DATABASE <Your database name>
SET RECOVERY FULL
but I am getting the following error:
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
Rajesh

Error when executing ALTER DATABASE statement

Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
---
ALTER DATABASE <Your database name>
SET RECOVERY FULL
----
but I am getting the following error:
----
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
----
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
RajeshIt looks like a permission issue. Are you a member of sysadmin, dbcreator
or db_owner?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Rajesh" <Rajesh@.discussions.microsoft.com> wrote in message
news:4EC91AF7-A227-4A52-86F1-C4F0529A8AAD@.microsoft.com...
Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
---
ALTER DATABASE <Your database name>
SET RECOVERY FULL
----
but I am getting the following error:
----
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
----
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
Rajesh

Error when executing ALTER DATABASE statement

Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
---
ALTER DATABASE <Your database name>
SET RECOVERY FULL
----
but I am getting the following error:
----
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
----
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
RajeshIt looks like a permission issue. Are you a member of sysadmin, dbcreator
or db_owner?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Rajesh" <Rajesh@.discussions.microsoft.com> wrote in message
news:4EC91AF7-A227-4A52-86F1-C4F0529A8AAD@.microsoft.com...
Hi,
Problem description:
For taking transactional log backup of sql sever2005, I need to put database
into "RECOVERY FULL" mode. To do that I am using the following query in
master database as:
---
ALTER DATABASE <Your database name>
SET RECOVERY FULL
----
but I am getting the following error:
----
Msg 5011, Level 14, State 5, Line 1
User does not have permission to alter database 'ipr_qxcr239146' or the
database does not exist.
Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
----
I am using windows authentication while connecting to SQL server and
database name is also correct in query. But not able to find where is the
problem
Please help me out.
Regards,
Rajeshsql

error when backup transaction log

hi guys,

I'm using sql 2000 and I got this error when I run backup transaction log in maintenence plan.
"The job failed. The Job was invoked by Schedule 38 (Schedule 1). The last step to run was step 1 (Step 1)."

but even it return an error the backup file is created.

please advice.

thanks

There has to be a more detailed error, if you did not choose to log the job execution, try to do this, as this. Otherwiese you will only get this common exception which does not really help very much.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

hi jens,

after I try to backup just 1 database. it went ok.

maybe it because I backup master and msdb also. but I wonder why is my transaction log file is keep on growing ?

should it get truncated everytime the backup is successfull ? either full backup or transaction log backup right

regards,

-dedys

Error when attempting to delete rows

I have a log table with no indexes, triggers, or keys. During the course of development, I will clean out the entries by selecting all the rows (in Database Explorer) and hitting the delete key.

Occassionally, I will end up with couple rows (out of many) that won't delete. I get the following error when I attempt to delete the "affected" rows:

A problem occurred attempting to delete row 1.
Error Source: Microosft.VisualStudio.DataTools.
Error Message: The row value(s) updated or deleted either do not make the
unique or they alter multiple rows (2 rows).

I'm also not able to modify any of the data of the affected rows. There don't seem to be anything really special or unique about these affected rows (compared to the ones I'm able to delete). I've tried rebooting the machine and that did resolve the issue.

This is the second time I've encountered this issue. By any chance, is this a known bug with the beta (it's SQL Server 2005 June CTP)? Or is it some else I'm not aware of?

I've also tried deleting the rows using SQL Server Management, same results.

RichardCan you run SQL Profiler to check the different events executing while you delete these records? There must be something happening in the background that is causing all these.|||

Did you ever get the problem resolved? I am having the same problem.

Thanks, Bob

|||

Does the table have a primary key or unique constraint?

|||I just saw this. I'm sure it was resolved since the post was awhile ago, but that error message can occur if there is a constraint which the deletion violates. A common one might be that a field is set to "NOT NULL".

Error when attempting to delete rows

I have a log table with no indexes, triggers, or keys. During the course of development, I will clean out the entries by selecting all the rows (in Database Explorer) and hitting the delete key.

Occassionally, I will end up with couple rows (out of many) that won't delete. I get the following error when I attempt to delete the "affected" rows:

A problem occurred attempting to delete row 1.
Error Source: Microosft.VisualStudio.DataTools.
Error Message: The row value(s) updated or deleted either do not make the
unique or they alter multiple rows (2 rows).

I'm also not able to modify any of the data of the affected rows. There don't seem to be anything really special or unique about these affected rows (compared to the ones I'm able to delete). I've tried rebooting the machine and that did resolve the issue.

This is the second time I've encountered this issue. By any chance, is this a known bug with the beta (it's SQL Server 2005 June CTP)? Or is it some else I'm not aware of?

I've also tried deleting the rows using SQL Server Management, same results.

Richard
Can you run SQL Profiler to check the different events executing while you delete these records? There must be something happening in the background that is causing all these.|||

Did you ever get the problem resolved? I am having the same problem.

Thanks, Bob

|||

Does the table have a primary key or unique constraint?

|||I just saw this. I'm sure it was resolved since the post was awhile ago, but that error message can occur if there is a constraint which the deletion violates. A common one might be that a field is set to "NOT NULL".

Error when attempting to delete rows

I have a log table with no indexes, triggers, or keys. During the course of development, I will clean out the entries by selecting all the rows (in Database Explorer) and hitting the delete key.

Occassionally, I will end up with couple rows (out of many) that won't delete. I get the following error when I attempt to delete the "affected" rows:

A problem occurred attempting to delete row 1.
Error Source: Microosft.VisualStudio.DataTools.
Error Message: The row value(s) updated or deleted either do not make the
unique or they alter multiple rows (2 rows).

I'm also not able to modify any of the data of the affected rows. There don't seem to be anything really special or unique about these affected rows (compared to the ones I'm able to delete). I've tried rebooting the machine and that did resolve the issue.

This is the second time I've encountered this issue. By any chance, is this a known bug with the beta (it's SQL Server 2005 June CTP)? Or is it some else I'm not aware of?

I've also tried deleting the rows using SQL Server Management, same results.

Richard
Can you run SQL Profiler to check the different events executing while you delete these records? There must be something happening in the background that is causing all these.|||

Did you ever get the problem resolved? I am having the same problem.

Thanks, Bob

|||

Does the table have a primary key or unique constraint?

|||I just saw this. I'm sure it was resolved since the post was awhile ago, but that error message can occur if there is a constraint which the deletion violates. A common one might be that a field is set to "NOT NULL".

Error starting the SQL service after renaming one of the log files..

Is there anyone out there who can help me ? Please ? ?
The log file for one of the MSSQL 2000 databases ha grown really big.
(15 GB)
After setting a limit on the size to grow, the log file date did not
modifie.
After a few weaks I stopped the SQL service, and renamed the log file.
When I was trying to start the SQL again, it would not start. Even
not when I gave the log file back its old name.
Is there any way to restart / restore the SQL service / database
without a backup ? ?
Regards,
ØivindWhen you try to start the service, what message do you get?
"oeej" <oeej@.netpower.no> wrote in message
news:ca674822.0309071518.24feabb9@.posting.google.com...
> Is there anyone out there who can help me ? Please ? ?
> The log file for one of the MSSQL 2000 databases ha grown really big.
> (15 GB)
> After setting a limit on the size to grow, the log file date did not
> modifie.
> After a few weaks I stopped the SQL service, and renamed the log file.
> When I was trying to start the SQL again, it would not start. Even
> not when I gave the log file back its old name.
> Is there any way to restart / restore the SQL service / database
> without a backup ? ?
> Regards,
> Øivind|||If the error messages are correct... simply
Restore database model with recovery
Restore database axdb with recovery
the error messages say you have started a recovery that was not completed..
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"oeej" <oeej@.netpower.no> wrote in message
news:ca674822.0309071518.24feabb9@.posting.google.com...
> Is there anyone out there who can help me ? Please ? ?
> The log file for one of the MSSQL 2000 databases ha grown really big.
> (15 GB)
> After setting a limit on the size to grow, the log file date did not
> modifie.
> After a few weaks I stopped the SQL service, and renamed the log file.
> When I was trying to start the SQL again, it would not start. Even
> not when I gave the log file back its old name.
> Is there any way to restart / restore the SQL service / database
> without a backup ? ?
> Regards,
> Øivind

Error starting SQLserver on windows 2000

When starting the SQLserver service on a Windows 2000 server, we get
following error:
17050 :
initerrlog: Could not open error log file
's:\MSSQL8\MSSQL\log\ERRORLOG'. Operating system error = 3(error not
found).
We're running SQL 2000 std ed.. This is no cluster, access rights on
file are correct, the file is not locked by another process.
I've compared registry settings with a working server (same config) and
there identical.
registry setting:
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSSQLServer\MSSQLServer\Parameter
s]
"SQLArg0"="-ds:\\MSSQL8\\MSSQL\\data\\master.mdf"
"SQLArg1"="-es:\\MSSQL8\\MSSQL\\log\\ERRORLOG"
"SQLArg2"="-ls:\\MSSQL8\\MSSQL\\data\\mastlog.ldf".
There's a local d, e and l-drive (No SAN)
Anyone has an idea what's going wrongHi Olivier
The parameters are expecting a S drive, where are the files supposed to be?
You could start sqlservr.exe from the command prompt and specify the correct
file names, see the topic "sqlservr Application" in Books Online and change
the values through Enterprise Manager, if you don't want to change the
registry directly.
John
"sqlservr Application"
"olivier.lammens@.gmail.com" wrote:

> When starting the SQLserver service on a Windows 2000 server, we get
> following error:
> 17050 :
> initerrlog: Could not open error log file
> 's:\MSSQL8\MSSQL\log\ERRORLOG'. Operating system error = 3(error not
> found).
> We're running SQL 2000 std ed.. This is no cluster, access rights on
> file are correct, the file is not locked by another process.
> I've compared registry settings with a working server (same config) and
> there identical.
> registry setting:
> & #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSSQLServer\MSSQLServer\Paramet
ers]
> "SQLArg0"="-ds:\\MSSQL8\\MSSQL\\data\\master.mdf"
> "SQLArg1"="-es:\\MSSQL8\\MSSQL\\log\\ERRORLOG"
> "SQLArg2"="-ls:\\MSSQL8\\MSSQL\\data\\mastlog.ldf".
> There's a local d, e and l-drive (No SAN)
> Anyone has an idea what's going wrong
>|||Hi Olivier
The parameters are expecting a S drive, where are the files supposed to be?
You could start sqlservr.exe from the command prompt and specify the correct
file names, see the topic "sqlservr Application" in Books Online and change
the values through Enterprise Manager, if you don't want to change the
registry directly.
John
"sqlservr Application"
"olivier.lammens@.gmail.com" wrote:

> When starting the SQLserver service on a Windows 2000 server, we get
> following error:
> 17050 :
> initerrlog: Could not open error log file
> 's:\MSSQL8\MSSQL\log\ERRORLOG'. Operating system error = 3(error not
> found).
> We're running SQL 2000 std ed.. This is no cluster, access rights on
> file are correct, the file is not locked by another process.
> I've compared registry settings with a working server (same config) and
> there identical.
> registry setting:
> & #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSSQLServer\MSSQLServer\Paramet
ers]
> "SQLArg0"="-ds:\\MSSQL8\\MSSQL\\data\\master.mdf"
> "SQLArg1"="-es:\\MSSQL8\\MSSQL\\log\\ERRORLOG"
> "SQLArg2"="-ls:\\MSSQL8\\MSSQL\\data\\mastlog.ldf".
> There's a local d, e and l-drive (No SAN)
> Anyone has an idea what's going wrong
>

Error starting SQLserver on windows 2000

When starting the SQLserver service on a windows 2000 server, we get
following error:
17050 :
initerrlog: Could not open error log file
's:\MSSQL8\MSSQL\log\ERRORLOG'. Operating system error = 3(error not
found).
We're running SQL 2000 std ed.. This is no cluster, access rights on
file are correct, the file is not locked by another process.
I've compared registry settings with a working server (same config) and
there identical.
registry setting:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters]
"SQLArg0"="-ds:\\MSSQL8\\MSSQL\\data\\master.mdf"
"SQLArg1"="-es:\\MSSQL8\\MSSQL\\log\\ERRORLOG"
"SQLArg2"="-ls:\\MSSQL8\\MSSQL\\data\\mastlog.ldf".
There's a local d, e and l-drive (No SAN)
Anyone has an idea what's going wrongHi Olivier
The parameters are expecting a S drive, where are the files supposed to be?
You could start sqlservr.exe from the command prompt and specify the correct
file names, see the topic "sqlservr Application" in Books Online and change
the values through Enterprise Manager, if you don't want to change the
registry directly.
John
"sqlservr Application"
"olivier.lammens@.gmail.com" wrote:
> When starting the SQLserver service on a windows 2000 server, we get
> following error:
> 17050 :
> initerrlog: Could not open error log file
> 's:\MSSQL8\MSSQL\log\ERRORLOG'. Operating system error = 3(error not
> found).
> We're running SQL 2000 std ed.. This is no cluster, access rights on
> file are correct, the file is not locked by another process.
> I've compared registry settings with a working server (same config) and
> there identical.
> registry setting:
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters]
> "SQLArg0"="-ds:\\MSSQL8\\MSSQL\\data\\master.mdf"
> "SQLArg1"="-es:\\MSSQL8\\MSSQL\\log\\ERRORLOG"
> "SQLArg2"="-ls:\\MSSQL8\\MSSQL\\data\\mastlog.ldf".
> There's a local d, e and l-drive (No SAN)
> Anyone has an idea what's going wrong
>

error stack dump

Hi people! abruptly i found in the sql server log the next error:
Short Stack Dump
0x77f94956 Module(ntdll+14956) (RtlNewSecurityObjectEx+35)
0x0078a1d0 Module(sqlservr+38a1d0) (utassert_fail+1a0)
0x006dd15d Module(sqlservr+2dd15d) (LockClass::ReleaseLocks+43)
0x0054cc3f Module(sqlservr+14cc3f) (CQueryScan::DestroyLockClasses+3c)
0x0041da88 Module(sqlservr+1da88) (CQueryScan::Shutdown+67)
0x005d7738 Module(sqlservr+1d7738) (CFetchPopulate::PopulateWorkTable+15c)
0x005d733e Module(sqlservr+1d733e) (CFetchPopulate::FnPopulateThread+ca)
0x004ad883 Module(sqlservr+ad883) (subproc_main+f4)
0x41092a15 Module(ums+2a15) (ProcessWorkRequests+ed)
0x410932cb Module(ums+32cb) (ThreadStartRoutine+139)
0x7800c9eb Module(MSVCRT+c9eb) (beginthread+ce)
0x7c57438b Module(KERNEL32+438b) (RegisterWowExec+7e2)
2004-05-27 19:19:46.64 kernel SQL Server Assertion: File: <lckclass.cpp>,
line=111
Failed Assertion = 'm_status == ACTIVE || m_status == ORPHANED'.
2004-05-27 19:19:46.70 spid470 Using 'sqlimage.dll' version '4.0.5'
Dump thread - spid = 470, PSS = 0x4ed5f0d4, EC = 0xb669e084
i'm searching in the MS support web site but i can't found anything about th
at, whats up with my server? any ideas?
i've got a ms sql 7.0 SP3 running over NT 2000 sp3
thanks in advance...
Lucho FarjeLUCHOF,
Contact Microsoft Support for a solution to this. Try and reproduce the
problem before calling them, as they will ask you to do that.
http://support.microsoft.com/defaul...id=fh;EN-US;sql
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
LUCHOF wrote:
> Hi people! abruptly i found in the sql server log the next error:
> Short Stack Dump
> 0x77f94956 Module(ntdll+14956) (RtlNewSecurityObjectEx+35)
> 0x0078a1d0 Module(sqlservr+38a1d0) (utassert_fail+1a0)
> 0x006dd15d Module(sqlservr+2dd15d) (LockClass::ReleaseLocks+43)
> 0x0054cc3f Module(sqlservr+14cc3f) (CQueryScan::DestroyLockClasses+3c)
> 0x0041da88 Module(sqlservr+1da88) (CQueryScan::Shutdown+67)
> 0x005d7738 Module(sqlservr+1d7738) (CFetchPopulate::PopulateWorkTable+15c)
> 0x005d733e Module(sqlservr+1d733e) (CFetchPopulate::FnPopulateThread+ca)
> 0x004ad883 Module(sqlservr+ad883) (subproc_main+f4)
> 0x41092a15 Module(ums+2a15) (ProcessWorkRequests+ed)
> 0x410932cb Module(ums+32cb) (ThreadStartRoutine+139)
> 0x7800c9eb Module(MSVCRT+c9eb) (beginthread+ce)
> 0x7c57438b Module(KERNEL32+438b) (RegisterWowExec+7e2)
> 2004-05-27 19:19:46.64 kernel SQL Server Assertion: File: <lckclass.cpp>
, line=111
> Failed Assertion = 'm_status == ACTIVE || m_status == ORPHANED'.
> 2004-05-27 19:19:46.70 spid470 Using 'sqlimage.dll' version '4.0.5'
> Dump thread - spid = 470, PSS = 0x4ed5f0d4, EC = 0xb669e084
> i'm searching in the MS support web site but i can't found anything about
that, whats up with my server? any ideas?
> i've got a ms sql 7.0 SP3 running over NT 2000 sp3
> thanks in advance...
> Lucho Farje