Showing posts with label generate. Show all posts
Showing posts with label generate. Show all posts

Tuesday, March 27, 2012

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

Wednesday, February 15, 2012

Error Scripting Procs: Failed to retrieve dependency information

How can I resolve the following error when I try to script out some procs. In SSMS I right click the db and I choose 'Tasks > Generate Script', then I select 10 stored procs (without changing any of the default options). If I don't include the proc mentioned in the error below, then it works OK.

TITLE: Microsoft.SqlServer.SqlEnum

Failed to retrieve dependency information (object_id(System.Int32) 1271727633.object_type(System.Int16) 4.relative_id(System.Int32)

1879729799.relative_type(System.DBNull) .object_name(System.String) usp_SEL_RCEPCompanyHistory.object_schema(System.String)

dbo.relative_name(System.DBNull) .relative_schema(System.DBNull) .).

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476


ADDITIONAL INFORMATION:

Specified cast is not valid. (Microsoft.SqlServer.SqlEnum)


I'm having this problem, too. Any resolution?|||

Please help us understand what kind of object caused the problem better by running the following queries and telling us what do they return.

select * from sys.objects where object_id = xxxx

select * from sys.sql_dependencies where object_id = xxxx or referenced_major_id=xxxx

select * from sys.assembly_modules where object_id = xxxx

You want to replace xxxx with the number that shows in the error message after relative_id.

Thanks,

Ciprian Gerea

|||

The object is a user-defined aggregate function ('Microsoft.Samples.SqlServer.Concatenate'). I think this problem has already been submitted in feedback here:

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125881

|||

I set up my machine as directed in the above issue report, using our current sp2 build, and was unable to reproduce the error reported here.

It may be the case that the two feedback items are evidence of two issues, with distinct repro scenarios, but I am assuming that we have fixed this, and that you can expect to see it in the upcoming release of sql server sp2.

|||

I was experiencing the same type of error. Your script above was helpful to me in identifying the SQL_dependencies for the procs that was throwing the errors. It turns out in my situation there were procs which were referencing the service queue objects and for what ever reasons it did not like those procs. I excluded those procs from my script generator and it worked.

Error Scripting Procs: Failed to retrieve dependency information

How can I resolve the following error when I try to script out some procs. In SSMS I right click the db and I choose 'Tasks > Generate Script', then I select 10 stored procs (without changing any of the default options). If I don't include the proc mentioned in the error below, then it works OK.

TITLE: Microsoft.SqlServer.SqlEnum

Failed to retrieve dependency information (object_id(System.Int32) 1271727633.object_type(System.Int16) 4.relative_id(System.Int32)

1879729799.relative_type(System.DBNull) .object_name(System.String) usp_SEL_RCEPCompanyHistory.object_schema(System.String)

dbo.relative_name(System.DBNull) .relative_schema(System.DBNull) .).

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476


ADDITIONAL INFORMATION:

Specified cast is not valid. (Microsoft.SqlServer.SqlEnum)


I'm having this problem, too. Any resolution?|||

Please help us understand what kind of object caused the problem better by running the following queries and telling us what do they return.

select * from sys.objects where object_id = xxxx

select * from sys.sql_dependencies where object_id = xxxx or referenced_major_id=xxxx

select * from sys.assembly_modules where object_id = xxxx

You want to replace xxxx with the number that shows in the error message after relative_id.

Thanks,

Ciprian Gerea

|||

The object is a user-defined aggregate function ('Microsoft.Samples.SqlServer.Concatenate'). I think this problem has already been submitted in feedback here:

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125881

|||

I set up my machine as directed in the above issue report, using our current sp2 build, and was unable to reproduce the error reported here.

It may be the case that the two feedback items are evidence of two issues, with distinct repro scenarios, but I am assuming that we have fixed this, and that you can expect to see it in the upcoming release of sql server sp2.

|||

I was experiencing the same type of error. Your script above was helpful to me in identifying the SQL_dependencies for the procs that was throwing the errors. It turns out in my situation there were procs which were referencing the service queue objects and for what ever reasons it did not like those procs. I excluded those procs from my script generator and it worked.

Error Scripting Procs: Failed to retrieve dependency information

How can I resolve the following error when I try to script out some procs. In SSMS I right click the db and I choose 'Tasks > Generate Script', then I select 10 stored procs (without changing any of the default options). If I don't include the proc mentioned in the error below, then it works OK.

TITLE: Microsoft.SqlServer.SqlEnum

Failed to retrieve dependency information (object_id(System.Int32) 1271727633.object_type(System.Int16) 4.relative_id(System.Int32)

1879729799.relative_type(System.DBNull) .object_name(System.String) usp_SEL_RCEPCompanyHistory.object_schema(System.String)

dbo.relative_name(System.DBNull) .relative_schema(System.DBNull) .).

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476


ADDITIONAL INFORMATION:

Specified cast is not valid. (Microsoft.SqlServer.SqlEnum)


I'm having this problem, too. Any resolution?
|||

Please help us understand what kind of object caused the problem better by running the following queries and telling us what do they return.

select * from sys.objects where object_id = xxxx

select * from sys.sql_dependencies where object_id = xxxx or referenced_major_id=xxxx

select * from sys.assembly_modules where object_id = xxxx

You want to replace xxxx with the number that shows in the error message after relative_id.

Thanks,

Ciprian Gerea

|||

The object is a user-defined aggregate function ('Microsoft.Samples.SqlServer.Concatenate'). I think this problem has already been submitted in feedback here:

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125881

|||

I set up my machine as directed in the above issue report, using our current sp2 build, and was unable to reproduce the error reported here.

It may be the case that the two feedback items are evidence of two issues, with distinct repro scenarios, but I am assuming that we have fixed this, and that you can expect to see it in the upcoming release of sql server sp2.

|||

I was experiencing the same type of error. Your script above was helpful to me in identifying the SQL_dependencies for the procs that was throwing the errors. It turns out in my situation there were procs which were referencing the service queue objects and for what ever reasons it did not like those procs. I excluded those procs from my script generator and it worked.

Error Scripting Procs: Failed to retrieve dependency information

How can I resolve the following error when I try to script out some procs. In SSMS I right click the db and I choose 'Tasks > Generate Script', then I select 10 stored procs (without changing any of the default options). If I don't include the proc mentioned in the error below, then it works OK.

TITLE: Microsoft.SqlServer.SqlEnum

Failed to retrieve dependency information (object_id(System.Int32) 1271727633.object_type(System.Int16) 4.relative_id(System.Int32)

1879729799.relative_type(System.DBNull) .object_name(System.String) usp_SEL_RCEPCompanyHistory.object_schema(System.String)

dbo.relative_name(System.DBNull) .relative_schema(System.DBNull) .).

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476


ADDITIONAL INFORMATION:

Specified cast is not valid. (Microsoft.SqlServer.SqlEnum)


I'm having this problem, too. Any resolution?
|||

Please help us understand what kind of object caused the problem better by running the following queries and telling us what do they return.

select * from sys.objects where object_id = xxxx

select * from sys.sql_dependencies where object_id = xxxx or referenced_major_id=xxxx

select * from sys.assembly_modules where object_id = xxxx

You want to replace xxxx with the number that shows in the error message after relative_id.

Thanks,

Ciprian Gerea

|||

The object is a user-defined aggregate function ('Microsoft.Samples.SqlServer.Concatenate'). I think this problem has already been submitted in feedback here:

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125881

|||

I set up my machine as directed in the above issue report, using our current sp2 build, and was unable to reproduce the error reported here.

It may be the case that the two feedback items are evidence of two issues, with distinct repro scenarios, but I am assuming that we have fixed this, and that you can expect to see it in the upcoming release of sql server sp2.

|||

I was experiencing the same type of error. Your script above was helpful to me in identifying the SQL_dependencies for the procs that was throwing the errors. It turns out in my situation there were procs which were referencing the service queue objects and for what ever reasons it did not like those procs. I excluded those procs from my script generator and it worked.