I have a new server setup running sql2000 as default instance. I wanted
to move all the jobs and dts packages from another server which is running
multiple instances of sql server. I backed up and restored the msdb database
to the new server and now I can't edit any jobs. I get this error?
can't edit or delete the job that originated from MSX server.
How do I fix this problem. Any help will be appreciated.
I'am doing functionality test on DTS packages and saving my DTS packages to meta data services instead of saving them as local packages. We would like to see what information would be provided by saving them this way, but when we try to open the meta data browser (the 3rd icon under DTS) we get the following error:
An error occurred while trying to access the database information. The msdb database could not be opened.
Whenever I start my SQL Express 2005 database, I get the following in the logs :
View 10 Replies View Related1) How do I reinstall a fresh copy of the MSDB database (since my current
one is corrupt). Is there any script available?
2) What is the purpose of the MSDB database? Backups and jobs/ Wizards?
Thanks for your help.
Ziggy
Hi Everyone,
Couple of days back my server was down because of hardware problem and it was rectefied and sql server 6.5 started yesterday afternoon and the backup schedules was run in demand yesterday but it failed, and some of the schedules which are suppose to take backup in the night also failed today, it was also not showing anything in the schedule history, and when I run the schedule on demand today again it failed, so I created a newdevice and scheduled a newtask and I run in demand and the history shows that:-
schedule history (Could not insert a backup or restore history/detail record in msdb.dbo.sysbackuphistory or sysrestorehistory. This may indicate a problem with the MSDB database. DUMP/LOAD was still successful. (Message 3009)).
I checked the sysbackuphistory it shows three days back history, can any body give me the solution, what are the things to be checked, please give me the solution.
waiting for the immediate reply.
Thanks,
Madhu
I have to rename some Originating_Server fields in the msdb database. I'm pretty sure I have to run a script that makes the msdb database editable but I can't find it anywhere. Am I wrong?
View 3 Replies View RelatedFriends -
I am not able to connect to MSDB database under SQL Server 2005 Integration services. i am getting the following error.
TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in Server 2005 Books Online.
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (MsDtsSrvr)
------------------------------
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)
------------------------------
BUTTONS:
OK
Please advise on this.
cheers :)
Satish
Hi all
when i try to restore a database called ddaa, i am getting the following message after the restore is completed.. and the database icon in the enterprize manager is having ddaa(loading).now i am not able to access that database..
the message i am getting is..
database msdb cannot be opened due to anaccessible files or insufficient memory or disk space. could not insert a backup/restore history detail record in the msdb database.this may indicate a problem with the msdb database.
how to resolve this issue..
Thanks in advance.
Dear Experts,
in one of our servers, the MSDB database is in suspect mode, and i've used the command sp_resetstatus
and i restarted the service also but still it is in suspect mode.
how can i change that to normal state?
it is asking to check the errorlog.
Vinod
Even you learn 1%, Learn it with 100% confidence.
My msdb database is marked as suspect. This means that my maintenance plandoesn't work. I'm a novice when it comes to sql server so now I'm wonderingif anyone could give a hint on how to fix the suspect msdb database? Doesthis database contain any vital information? What could be the reason thatthis database become suspect?Appreciate any suggestions in this matter.Thanks!--mvhHallgeir
View 2 Replies View RelatedA client improperly shutdown a PC running MSDE and it corrupted the MSDB database which contained several DTS packages. I have tried fixing the problem on my own but have exhausted all the simple options like restarting SQL Server.
I googled the problem and found the following SQL script:
USE MasterGO-- Determine the original database statusSELECT [Name], DBID, StatusFROM master.dbo.sysdatabasesGO-- Enable system changessp_configure 'allow updates',1GORECONFIGURE WITH OVERRIDEGO-- Update the database statusUPDATE master.dbo.sysdatabasesSET Status = 24WHERE [Name] = 'msdb'GO-- Disable system changessp_configure 'allow updates',0GORECONFIGURE WITH OVERRIDEGO-- Determine the final database statusSELECT [Name], DBID, StatusFROM master.dbo.sysdatabasesGO
I ran it and and it generated the log file below. I restarted MS SQL but the database was still marked as suspect (as I would expect from the log file).
Any help in interpreting and recovering from this problem would be greatly appreciated.
Thank,
MickeyBob
Log file:
2007-07-09 15:47:39.39 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)2007-07-09 15:47:39.39 server Copyright (C) 1988-2002 Microsoft Corporation.2007-07-09 15:47:39.39 server All rights reserved.2007-07-09 15:47:39.39 server Server Process ID is 2324.2007-07-09 15:47:39.39 server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQLLOGERRORLOG'.2007-07-09 15:47:39.40 server SQL Server is starting at priority class 'normal'(2 CPUs detected).2007-07-09 15:47:39.84 server SQL Server configured for thread mode processing.2007-07-09 15:47:39.84 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.2007-07-09 15:47:39.89 spid3 Starting up database 'master'.2007-07-09 15:47:40.01 server Using 'SSNETLIB.DLL' version '8.0.766'.2007-07-09 15:47:40.01 spid5 Starting up database 'model'.2007-07-09 15:47:40.01 server SQL server listening on Shared Memory.2007-07-09 15:47:40.01 server SQL Server is ready for client connections2007-07-09 15:47:40.04 spid3 Server name is 'BALEHANDLING'.2007-07-09 15:47:40.04 spid3 Skipping startup of clean database id 52007-07-09 15:47:40.04 spid3 Skipping startup of clean database id 62007-07-09 15:47:40.04 spid3 Starting up database 'msdb'.2007-07-09 15:47:40.23 spid5 Clearing tempdb database.2007-07-09 15:47:41.18 spid5 Starting up database 'tempdb'.2007-07-09 15:47:55.56 spid51 Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.2007-07-09 15:48:01.60 spid3 Analysis of database 'msdb' (4) is 100% complete (approximately 0 more seconds)2007-07-09 15:48:01.62 spid3 Recovery of database 'msdb' (4) is 0% complete (approximately 9 more seconds) (Phase 2 of 3).2007-07-09 15:48:43.95 spid3 Recovery of database 'msdb' (4) is 40% complete (approximately 5 more seconds) (Phase 2 of 3).2007-07-09 15:48:43.96 spid3 7678 transactions rolled forward in database 'msdb' (4).2007-07-09 15:48:43.96 spid3 Recovery of database 'msdb' (4) is 40% complete (approximately 5 more seconds) (Phase 3 of 3).2007-07-09 15:48:44.01 spid3 Using 'dbghelp.dll' version '4.0.5'*Dump thread - spid = 3, PSS = 0x42c2c098, EC = 0x42c2c3c0*Stack Dump being sent to C:Program FilesMicrosoft SQL ServerMSSQLlogSQLDump0030.txt* ********************************************************************************* BEGIN STACK DUMP:* 07/09/07 15:48:44 spid 3** ** ** MODULE BASE END SIZE* sqlservr 00400000 00B2CFFF 0072d000* ntdll 7C900000 7C9AFFFF 000b0000* kernel32 7C800000 7C8F3FFF 000f4000* ADVAPI32 77DD0000 77E6AFFF 0009b000* RPCRT4 77E70000 77F00FFF 00091000* USER32 77D40000 77DCFFFF 00090000* GDI32 77F10000 77F56FFF 00047000* OPENDS60 41060000 41065FFF 00006000* MSVCRT 77C10000 77C67FFF 00058000* UMS 41070000 4107CFFF 0000d000* SQLSORT 42AE0000 42B6FFFF 00090000* MSVCIRT 002A0000 002B0FFF 00011000* sqlevn70 41080000 41086FFF 00007000* NETAPI32 024F0000 02543FFF 00054000* SSNETLIB 00DC0000 00DD4FFF 00015000* WSOCK32 00DF0000 00DF8FFF 00009000* WS2_32 00E00000 00E16FFF 00017000* WS2HELP 00E20000 00E27FFF 00008000* SSNMPN70 02CD0000 02CD5FFF 00006000* security 02FD0000 02FD3FFF 00004000* SECUR32 02FE0000 02FF0FFF 00011000* VERSION 030C0000 030C7FFF 00008000* SSmsLPCn 03000000 03006FFF 00007000* ntdsapi 030A0000 030B2FFF 00013000* DNSAPI 030D0000 030F6FFF 00027000* WLDAP32 03100000 0312BFFF 0002c000* msv1_0 03330000 03352FFF 00023000* iphlpapi 03360000 03378FFF 00019000* OLE32 03390000 034CBFFF 0013c000* xpsp2res 034D0000 03794FFF 002c5000* CLBCATQ 037A0000 0381EFFF 0007f000* OLEAUT32 03820000 038ABFFF 0008c000* COMRes 038B0000 03974FFF 000c5000* sqloledb 03990000 03A10FFF 00081000* MSDART 03A20000 03A44FFF 00025000* COMCTL32 03A50000 03AE9FFF 0009a000* comdlg32 03AF0000 03B38FFF 00049000* SHLWAPI 03B40000 03BB5FFF 00076000* SHELL32 03BC0000 043D4FFF 00815000* MSDATL3 043E0000 043F6FFF 00017000* comctl32 044C0000 045C2FFF 00103000* oledb32 04810000 04886FFF 00077000* OLEDB32R 04480000 04490FFF 00011000* xpstar 04890000 048D6FFF 00047000* SQLRESLD 04420000 04426FFF 00007000* SQLSVC 048E0000 048F6FFF 00017000* ODBC32 04900000 0493CFFF 0003d000* odbcbcp 044A0000 044A5FFF 00006000* W95SCM 04940000 0494BFFF 0000c000* SQLUNIRL 04950000 0497CFFF 0002d000* WINSPOOL 04980000 049A5FFF 00026000* SHFOLDER 049B0000 049B8FFF 00009000* odbcint 04B00000 04B16FFF 00017000* clusapi 04B20000 04B30FFF 00011000* resutils 04B40000 04B51FFF 00012000* USERENV 04B60000 04C12FFF 000b3000* NDDEAPI 04C30000 04C37FFF 00008000* SQLSVC 04C40000 04C45FFF 00006000* xpstar 04C50000 04C58FFF 00009000* dbghelp 04CA0000 04D54FFF 000b5000** Edi: 42C2C3C0: 42C2C098 42C2CB30 42C2CB30 42C2CD20 42C2CD20 42C2C030 * Esi: 00000000: * Eax: 00000000: * Ebx: 42C2C098: 01000003 00000000 00000000 00000000 00000000 00000000 * Ecx: 0294B43C: 00000000 0001003F 00000000 00000000 00000000 00000000 * Edx: 7C90EB94: 24A48DC3 00000000 0024648D 90909090 24548D90 C32ECD08 * Eip: 0087A90E: 4D830088 75FFFFFC 0875FF0C E8E04D8B 0000002D 64F04D8B * Ebp: 0294B420: 0294BC40 0087C41F 42C2C098 0294BDA4 0294C016 77C3F931 * SegCs: 0000001B: * EFlags: 00010246: 006C0069 00730065 0053005C 00650069 0065006D 0073006E * Esp: 0294B3F4: 42C2C3C0 00000000 42C2C098 0294B43C 42C2C000 0294B3F4 * SegSs: 00000023: * ******************************************************************************** -------------------------------------------------------------------------------* Short Stack Dump* 0087A90E Module(sqlservr+0047A90E) (GetOSErrString+00003BDB)* 0087C41F Module(sqlservr+0047C41F) (GetOSErrString+000056EC)* 00931097 Module(sqlservr+00531097) (CDStream:umpBytesHex+000A9840)* 007FC8A6 Module(sqlservr+003FC8A6) (CDStream:perator=+00005B0E)* 00403B44 Module(sqlservr+00003B44)* 004416A7 Module(sqlservr+000416A7)* 0040F1E5 Module(sqlservr+0000F1E5)* 0040FF2B Module(sqlservr+0000FF2B)* 0040FE45 Module(sqlservr+0000FE45)* 00436DD6 Module(sqlservr+00036DD6)* 0043683C Module(sqlservr+0003683C)* 0040FD6F Module(sqlservr+0000FD6F)* 0040FB39 Module(sqlservr+0000FB39)* 008607CA Module(sqlservr+004607CA) (CDStream:perator=+00069A32)* 0086C203 Module(sqlservr+0046C203) (CDStream:perator=+0007546B)* 004401D7 Module(sqlservr+000401D7)* 0085EA07 Module(sqlservr+0045EA07) (CDStream:perator=+00067C6F)* 0050C003 Module(sqlservr+0010C003)* 005100FF Module(sqlservr+001100FF)* 0050F152 Module(sqlservr+0010F152)* 00519C2D Module(sqlservr+00119C2D)* 00829863 Module(sqlservr+00429863) (CDStream:perator=+00032ACB)* 005196A1 Module(sqlservr+001196A1)* 00518066 Module(sqlservr+00118066)* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)* 542868FF Module(UNKNOWN+00000000)* -------------------------------------------------------------------------------2007-07-09 15:48:44.06 spid3 SQL Server Assertion: File: <recbase.cpp>, line=1378 Failed Assertion = 'm_offBeginVar < m_SizeRec'.2007-07-09 15:48:44.06 spid3 Location: recbase.cpp:1378Expression: m_offBeginVar < m_SizeRecSPID: 3Process ID: 23242007-07-09 15:48:44.06 spid3 Error: 3624, Severity: 20, State: 1.2007-07-09 15:48:44.06 spid3 Error: 3314, Severity: 21, State: 32007-07-09 15:48:44.06 spid3 Error while undoing logged operation in database 'msdb'. Error at log record ID (97997:269:86)..2007-07-09 15:48:44.09 spid3 Using 'dbghelp.dll' version '4.0.5'*Dump thread - spid = 3, PSS = 0x42c2c098, EC = 0x42c2c3c0*Stack Dump being sent to C:Program FilesMicrosoft SQL ServerMSSQLlogSQLDump0031.txt* ********************************************************************************* BEGIN STACK DUMP:* 07/09/07 15:48:44 spid 3** ** ** MODULE BASE END SIZE* sqlservr 00400000 00B2CFFF 0072d000* ntdll 7C900000 7C9AFFFF 000b0000* kernel32 7C800000 7C8F3FFF 000f4000* ADVAPI32 77DD0000 77E6AFFF 0009b000* RPCRT4 77E70000 77F00FFF 00091000* USER32 77D40000 77DCFFFF 00090000* GDI32 77F10000 77F56FFF 00047000* OPENDS60 41060000 41065FFF 00006000* MSVCRT 77C10000 77C67FFF 00058000* UMS 41070000 4107CFFF 0000d000* SQLSORT 42AE0000 42B6FFFF 00090000* MSVCIRT 002A0000 002B0FFF 00011000* sqlevn70 41080000 41086FFF 00007000* NETAPI32 024F0000 02543FFF 00054000* SSNETLIB 00DC0000 00DD4FFF 00015000* WSOCK32 00DF0000 00DF8FFF 00009000* WS2_32 00E00000 00E16FFF 00017000* WS2HELP 00E20000 00E27FFF 00008000* SSNMPN70 02CD0000 02CD5FFF 00006000* security 02FD0000 02FD3FFF 00004000* SECUR32 02FE0000 02FF0FFF 00011000* VERSION 030C0000 030C7FFF 00008000* SSmsLPCn 03000000 03006FFF 00007000* ntdsapi 030A0000 030B2FFF 00013000* DNSAPI 030D0000 030F6FFF 00027000* WLDAP32 03100000 0312BFFF 0002c000* msv1_0 03330000 03352FFF 00023000* iphlpapi 03360000 03378FFF 00019000* OLE32 03390000 034CBFFF 0013c000* xpsp2res 034D0000 03794FFF 002c5000* CLBCATQ 037A0000 0381EFFF 0007f000* OLEAUT32 03820000 038ABFFF 0008c000* COMRes 038B0000 03974FFF 000c5000* sqloledb 03990000 03A10FFF 00081000* MSDART 03A20000 03A44FFF 00025000* COMCTL32 03A50000 03AE9FFF 0009a000* comdlg32 03AF0000 03B38FFF 00049000* SHLWAPI 03B40000 03BB5FFF 00076000* SHELL32 03BC0000 043D4FFF 00815000* MSDATL3 043E0000 043F6FFF 00017000* comctl32 044C0000 045C2FFF 00103000* oledb32 04810000 04886FFF 00077000* OLEDB32R 04480000 04490FFF 00011000* xpstar 04890000 048D6FFF 00047000* SQLRESLD 04420000 04426FFF 00007000* SQLSVC 048E0000 048F6FFF 00017000* ODBC32 04900000 0493CFFF 0003d000* odbcbcp 044A0000 044A5FFF 00006000* W95SCM 04940000 0494BFFF 0000c000* SQLUNIRL 04950000 0497CFFF 0002d000* WINSPOOL 04980000 049A5FFF 00026000* SHFOLDER 049B0000 049B8FFF 00009000* odbcint 04B00000 04B16FFF 00017000* clusapi 04B20000 04B30FFF 00011000* resutils 04B40000 04B51FFF 00012000* USERENV 04B60000 04C12FFF 000b3000* NDDEAPI 04C30000 04C37FFF 00008000* SQLSVC 04C40000 04C45FFF 00006000* xpstar 04C50000 04C58FFF 00009000* dbghelp 04CA0000 04D54FFF 000b5000** Edi: 42C2C3C0: 42C2C098 42C2C3C4 42C2C3C4 42C2CD20 42C2CB30 42C2C030 * Esi: 00000000: * Eax: 00000000: * Ebx: 42C2C098: 01000003 00000000 00000000 00000000 00000000 00000000 * Ecx: 02946B44: 00000000 0001003F 00000000 00000000 00000000 00000000 * Edx: 7C90EB94: 24A48DC3 00000000 0024648D 90909090 24548D90 C32ECD08 * Eip: 0087A90E: 4D830088 75FFFFFC 0875FF0C E8E04D8B 0000002D 64F04D8B * Ebp: 02946B28: 02947348 0087C41F 42C2C098 029474AC 02947735 77C3F931 * SegCs: 0000001B: * EFlags: 00010246: 006C0069 00730065 0053005C 00650069 0065006D 0073006E * Esp: 02946AFC: 42C2C3C0 00000000 42C2C098 02946B44 42C2C000 02946AFC * SegSs: 00000023: * ******************************************************************************** -------------------------------------------------------------------------------* Short Stack Dump* 0087A90E Module(sqlservr+0047A90E) (GetOSErrString+00003BDB)* 0087C41F Module(sqlservr+0047C41F) (GetOSErrString+000056EC)* 00931097 Module(sqlservr+00531097) (CDStream:umpBytesHex+000A9840)* 0085C09D Module(sqlservr+0045C09D) (CDStream:perator=+00065305)* 0050A016 Module(sqlservr+0010A016)* 008D048F Module(sqlservr+004D048F) (CDStream:umpBytesHex+00048C38)* 0085D84B Module(sqlservr+0045D84B) (CDStream:perator=+00066AB3)* 005100FF Module(sqlservr+001100FF)* 0050F152 Module(sqlservr+0010F152)* 00519C2D Module(sqlservr+00119C2D)* 00829863 Module(sqlservr+00429863) (CDStream:perator=+00032ACB)* 005196A1 Module(sqlservr+001196A1)* 00518066 Module(sqlservr+00118066)* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)* 542868FF Module(UNKNOWN+00000000)* -------------------------------------------------------------------------------2007-07-09 15:48:44.14 spid3 SQL Server Assertion: File: <logscan.cpp>, line=3063 Failed Assertion = '(m_lastLSN == NullLSN) || (m_lastLSN > m_curLSN)'.2007-07-09 15:48:44.14 spid3 Location: logscan.cpp:3063Expression: (m_lastLSN == NullLSN) || (m_lastLSN > m_curLSN)SPID: 3Process ID: 23242007-07-09 15:48:44.14 spid3 Using 'dbghelp.dll' version '4.0.5'*Dump thread - spid = 3, PSS = 0x42c2c098, EC = 0x42c2c3c0*Stack Dump being sent to C:Program FilesMicrosoft SQL ServerMSSQLlogSQLDump0032.txt* ********************************************************************************* BEGIN STACK DUMP:* 07/09/07 15:48:44 spid 3** ** ** MODULE BASE END SIZE* sqlservr 00400000 00B2CFFF 0072d000* ntdll 7C900000 7C9AFFFF 000b0000* kernel32 7C800000 7C8F3FFF 000f4000* ADVAPI32 77DD0000 77E6AFFF 0009b000* RPCRT4 77E70000 77F00FFF 00091000* USER32 77D40000 77DCFFFF 00090000* GDI32 77F10000 77F56FFF 00047000* OPENDS60 41060000 41065FFF 00006000* MSVCRT 77C10000 77C67FFF 00058000* UMS 41070000 4107CFFF 0000d000* SQLSORT 42AE0000 42B6FFFF 00090000* MSVCIRT 002A0000 002B0FFF 00011000* sqlevn70 41080000 41086FFF 00007000* NETAPI32 024F0000 02543FFF 00054000* SSNETLIB 00DC0000 00DD4FFF 00015000* WSOCK32 00DF0000 00DF8FFF 00009000* WS2_32 00E00000 00E16FFF 00017000* WS2HELP 00E20000 00E27FFF 00008000* SSNMPN70 02CD0000 02CD5FFF 00006000* security 02FD0000 02FD3FFF 00004000* SECUR32 02FE0000 02FF0FFF 00011000* VERSION 030C0000 030C7FFF 00008000* SSmsLPCn 03000000 03006FFF 00007000* ntdsapi 030A0000 030B2FFF 00013000* DNSAPI 030D0000 030F6FFF 00027000* WLDAP32 03100000 0312BFFF 0002c000* msv1_0 03330000 03352FFF 00023000* iphlpapi 03360000 03378FFF 00019000* OLE32 03390000 034CBFFF 0013c000* xpsp2res 034D0000 03794FFF 002c5000* CLBCATQ 037A0000 0381EFFF 0007f000* OLEAUT32 03820000 038ABFFF 0008c000* COMRes 038B0000 03974FFF 000c5000* sqloledb 03990000 03A10FFF 00081000* MSDART 03A20000 03A44FFF 00025000* COMCTL32 03A50000 03AE9FFF 0009a000* comdlg32 03AF0000 03B38FFF 00049000* SHLWAPI 03B40000 03BB5FFF 00076000* SHELL32 03BC0000 043D4FFF 00815000* MSDATL3 043E0000 043F6FFF 00017000* comctl32 044C0000 045C2FFF 00103000* oledb32 04810000 04886FFF 00077000* OLEDB32R 04480000 04490FFF 00011000* xpstar 04890000 048D6FFF 00047000* SQLRESLD 04420000 04426FFF 00007000* SQLSVC 048E0000 048F6FFF 00017000* ODBC32 04900000 0493CFFF 0003d000* odbcbcp 044A0000 044A5FFF 00006000* W95SCM 04940000 0494BFFF 0000c000* SQLUNIRL 04950000 0497CFFF 0002d000* WINSPOOL 04980000 049A5FFF 00026000* SHFOLDER 049B0000 049B8FFF 00009000* odbcint 04B00000 04B16FFF 00017000* clusapi 04B20000 04B30FFF 00011000* resutils 04B40000 04B51FFF 00012000* USERENV 04B60000 04C12FFF 000b3000* NDDEAPI 04C30000 04C37FFF 00008000* SQLSVC 04C40000 04C45FFF 00006000* xpstar 04C50000 04C58FFF 00009000* dbghelp 04CA0000 04D54FFF 000b5000** Edi: 42C2C3C0: 42C2C098 42C2C3C4 42C2C3C4 42C2CD20 42C2CB30 42C2C030 * Esi: 00000000: * Eax: 00000000: * Ebx: 42C2C098: 01000003 00000000 00000000 00000000 00000000 00000000 * Ecx: 029468EC: 00000000 0001003F 00000000 00000000 00000000 00000000 * Edx: 7C90EB94: 24A48DC3 00000000 0024648D 90909090 24548D90 C32ECD08 * Eip: 0087A90E: 4D830088 75FFFFFC 0875FF0C E8E04D8B 0000002D 64F04D8B * Ebp: 029468D0: 029470F0 0087C41F 42C2C098 02947254 029474D9 77C3F931 * SegCs: 0000001B: * EFlags: 00010246: 006C0069 00730065 0053005C 00650069 0065006D 0073006E * Esp: 029468A4: 42C2C3C0 00000000 42C2C098 029468EC 42C2C000 029468A4 * SegSs: 00000023: * ******************************************************************************** -------------------------------------------------------------------------------* Short Stack Dump* 0087A90E Module(sqlservr+0047A90E) (GetOSErrString+00003BDB)* 0087C41F Module(sqlservr+0047C41F) (GetOSErrString+000056EC)* 00931097 Module(sqlservr+00531097) (CDStream:umpBytesHex+000A9840)* 0085C2C1 Module(sqlservr+0045C2C1) (CDStream:perator=+00065529)* 0050A17A Module(sqlservr+0010A17A)* 0050A0BF Module(sqlservr+0010A0BF)* 0050A016 Module(sqlservr+0010A016)* 008D048F Module(sqlservr+004D048F) (CDStream:umpBytesHex+00048C38)* 0085D84B Module(sqlservr+0045D84B) (CDStream:perator=+00066AB3)* 005100FF Module(sqlservr+001100FF)* 0050F152 Module(sqlservr+0010F152)* 00519C2D Module(sqlservr+00119C2D)* 00829863 Module(sqlservr+00429863) (CDStream:perator=+00032ACB)* 005196A1 Module(sqlservr+001196A1)* 00518066 Module(sqlservr+00118066)* 41074698 Module(UMS+00004698) (UmsThreadScheduler::~UmsThreadScheduler+00000198)* 542868FF Module(UNKNOWN+00000000)* -------------------------------------------------------------------------------2007-07-09 15:48:44.17 spid3 SQL Server Assertion: File: <logscan.cpp>, line=3282 Failed Assertion = 'm_lastLSN == NullLSN || startLSN < m_lastLSN'.2007-07-09 15:48:44.17 spid3 Location: logscan.cpp:3282Expression: m_lastLSN == NullLSN || startLSN < m_lastLSNSPID: 3Process ID: 23242007-07-09 15:48:44.20 spid3 Error: 9004, Severity: 23, State: 72007-07-09 15:48:44.20 spid3 An error occurred while processing the log for database 'msdb'..2007-07-09 15:48:44.20 spid3 Error: 3414, Severity: 21, State: 12007-07-09 15:48:44.20 spid3 Database 'msdb' (database ID 4) could not recover. Contact Technical Support..2007-07-09 15:48:44.20 spid3 Recovery complete.2007-07-09 15:48:44.20 spid3 SQL global counter collection task is created.2007-07-09 15:49:21.09 spid51 Starting up database 'Baling'.2007-07-09 15:49:21.18 spid51 Starting up database 'WWAlmDb'.2007-07-09 15:49:21.29 spid51 Starting up database 'Baling'.2007-07-09 15:49:21.39 spid51 Starting up database 'WWAlmDb'.2007-07-09 15:51:11.90 spid53 Starting up database 'Baling'.2007-07-09 15:51:11.96 spid53 Starting up database 'WWAlmDb'.2007-07-09 15:51:33.82 spid52 Error: 15457, Severity: 0, State: 12007-07-09 15:51:33.82 spid52 Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install..2007-07-09 15:51:33.89 spid52 Error: 15457, Severity: 0, State: 12007-07-09 15:51:33.89 spid52 Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install..
Anyone help?
I opened SQL Server management studio and tried to connect with the local database and received the error message:
Database 'msdb' cannot be opened. It has been marked suspect.....
I have pasted the only error from the event log I could find below, but it doesn't mean much to me.
In the event I can't find what the problem is, and not being a database administrator, can anyone tell me what I can do to get back in working order without messing up all the databases in my SQL Server 2005. I'm afraid I only have a MASTER backup from several months ago, and am afraid if I use this, I will loose the latest data. I'm a novice, and do not understand the relationship of the master/msdb/model databases to my core custom databases. Can I do some sort of master rebuild without affecting the other databases I have?
I have tried sp_resetstatus but this didn't fix the problem, but it did enable me to actually connect to the SQL server instance so I could access all the other databases.
Many thanks
Gerard
Event log error detail:
The log scan number (152:284:1) passed to log scan in database 'msdb' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup.
Dear Experts,
I'm using sql server 2005, and now i'm trying to restore with one backup. then i'm getting error saying that MSDB database in suspect mode.
how to make the DB to the normal mode....
please help me in this regard
Vinod
Even you learn 1%, Learn it with 100% confidence.
HiI have a problem creating a backup in SQL Server 6.5. Although, thebackup produced does restore ok, I want to stop this error messageappearing everytime I make a backup. The error message is:"[SQL Server ]Can't allocate space for object 'sysbackupdetail' indatabase 'msdb' because the 'default' segment is full. If you ran outof space in Syslogs, dump the transaction log. Otherwise, use ALTERDATABASE or sp_extendsegment to increase the size of the segment."this articles appears to describe the problem and the solution:http://support.microsoft.com/defaul...kb;EN-US;152354It recommends creating a stored procedure to delete old entries. Thestored procedure cannot be created due tro a memory problem. What Iwas wondering, although the article doesn't mention it, can a newdevice be created and added to the msdb database. This should fix theproblem or is there problems doing this ?Thanks in advance
View 1 Replies View RelatedWhen I try to delete a job from Enterprise Manager Console I get the following error:
Erro 644: Could not find the index entry for RID '163bd10000010000' in index page (1:553), index ID 0 database 'msdb'
Oh and this is on MSDE.
Here is my complete output of DBCC CHECKDB
DBCC results for 'msdb'.
DBCC results for 'sysobjects'.
There are 280 rows in 6 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
There are 143 rows in 6 pages for object 'sysindexes'.
DBCC results for 'syscolumns'.
There are 1567 rows in 26 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 357 rows in 108 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 116 rows in 1 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 13 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 0 rows in 0 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 1635 rows in 8 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 12 rows in 1 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
DBCC results for 'backupset'.
There are 1045 rows in 44 pages for object 'backupset'.
DBCC results for 'sysjobschedules'.
There are 7 rows in 1 pages for object 'sysjobschedules'.
DBCC results for 'syscategories'.
There are 19 rows in 1 pages for object 'syscategories'.
DBCC results for 'systargetservers'.
There are 0 rows in 0 pages for object 'systargetservers'.
DBCC results for 'backupfile'.
There are 1451 rows in 24 pages for object 'backupfile'.
DBCC results for 'systargetservergroups'.
There are 0 rows in 0 pages for object 'systargetservergroups'.
DBCC results for 'systargetservergroupmembers'.
There are 0 rows in 0 pages for object 'systargetservergroupmembers'.
DBCC results for 'restorehistory'.
There are 1 rows in 1 pages for object 'restorehistory'.
DBCC results for 'sysalerts'.
There are 9 rows in 1 pages for object 'sysalerts'.
DBCC results for 'sysoperators'.
There are 0 rows in 0 pages for object 'sysoperators'.
DBCC results for 'sysnotifications'.
There are 0 rows in 0 pages for object 'sysnotifications'.
DBCC results for 'restorefile'.
There are 2 rows in 1 pages for object 'restorefile'.
DBCC results for 'systaskids'.
There are 0 rows in 0 pages for object 'systaskids'.
DBCC results for 'syscachedcredentials'.
There are 0 rows in 0 pages for object 'syscachedcredentials'.
DBCC results for 'restorefilegroup'.
There are 1 rows in 1 pages for object 'restorefilegroup'.
DBCC results for 'logmarkhistory'.
There are 0 rows in 0 pages for object 'logmarkhistory'.
DBCC results for 'sysdtscategories'.
There are 3 rows in 1 pages for object 'sysdtscategories'.
DBCC results for 'sysdtspackages'.
There are 0 rows in 0 pages for object 'sysdtspackages'.
DBCC results for 'sysdtspackagelog'.
There are 0 rows in 0 pages for object 'sysdtspackagelog'.
DBCC results for 'sysdtssteplog'.
Server: Msg 8935, Level 16, State 1, Line 1
Table error: Object ID 2073058421, index ID 1. The previous link (1:343) on page (1:371) does not match the previous page (1:382) that the parent (1:300), slot 32 expects for this page.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 2073058421, index ID 1. Page (1:371) is missing a reference from previous page (1:343). Possible chain linkage problem.
There are 0 rows in 0 pages for object 'sysdtssteplog'.
DBCC results for 'sysdtstasklog'.
There are 0 rows in 0 pages for object 'sysdtstasklog'.
DBCC results for 'sysdbmaintplans'.
There are 4 rows in 1 pages for object 'sysdbmaintplans'.
DBCC results for 'sysdbmaintplan_jobs'.
There are 4 rows in 1 pages for object 'sysdbmaintplan_jobs'.
DBCC results for 'sysdbmaintplan_databases'.
There are 12 rows in 1 pages for object 'sysdbmaintplan_databases'.
DBCC results for 'sysdbmaintplan_history'.
There are 724 rows in 23 pages for object 'sysdbmaintplan_history'.
DBCC results for 'log_shipping_primaries'.
There are 0 rows in 0 pages for object 'log_shipping_primaries'.
DBCC results for 'log_shipping_secondaries'.
There are 0 rows in 0 pages for object 'log_shipping_secondaries'.
DBCC results for 'mswebtasks'.
There are 0 rows in 0 pages for object 'mswebtasks'.
DBCC results for 'sqlagent_info'.
There are 0 rows in 0 pages for object 'sqlagent_info'.
DBCC results for 'sysdownloadlist'.
There are 0 rows in 0 pages for object 'sysdownloadlist'.
DBCC results for 'backupmediaset'.
There are 1045 rows in 11 pages for object 'backupmediaset'.
DBCC results for 'sysjobhistory'.
Server: Msg 8935, Level 16, State 1, Line 1
Table error: Object ID 2073058421, index ID 1. The previous link (1:382) on page (1:564) does not match the previous page (1:371) that the parent (1:300), slot 33 expects for this page.
There are 626 rows in 208 pages for object 'sysjobhistory'.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'sysjobhistory' (object ID 2073058421).
DBCC results for 'sysjobs'.
There are 7 rows in 1 pages for object 'sysjobs'.
DBCC results for 'backupmediafamily'.
There are 1045 rows in 20 pages for object 'backupmediafamily'.
DBCC results for 'sysjobservers'.
There are 7 rows in 1 pages for object 'sysjobservers'.
DBCC results for 'sysjobsteps'.
There are 9 rows in 1 pages for object 'sysjobsteps'.
CHECKDB found 0 allocation errors and 3 consistency errors in database 'msdb'.
repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (msdb ).
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
We are running SQL Server 2000, SP4. I recently noticed that my DTS packages were missing from the local server. Since I had saved them as Structure Storage Files, I imported them back into DTS Local Packages. That was yesterday. Today I opened the Meta Data browser to see what was in it. (We don't use Meta Data Services.) It displayed a message:"An error occurred while trying to access the database information. The msdb database could not be opened." These (restore of DTS pkgs and Meta Data error) may not be related, but I need to know why I am getting this error, because I am about to upgrade to SQL Server 2005 for Workgroups.
1. Does anyone know what causes this error message?
2. Are local DTS packages stored in the MSDB database?
How to move master , model and msdb database to some other location. Can we overwrite the master, model and msdb files
Any idea what this error is?
error 911: could not locate entry in sysdatabases for database 'msdb'. No entry found with that name
Thanks.
Sa
While checking the SQL server error logs, I notice that the pubs and msdb database are automatically being backed up, even though no job is set up to do so....in addition, its backing up to a directory that I cannot find on our network.....does anybody have an idea of whats going on ?
the path its backingup to is:
(FILE=1, TYPE=PIPE: {'.pipedbasql70dbagent0s0'}).
Thank you in advance
Hi All,
I'm just upgrading my business database to SQL 2005 and hit a problem when executing a stored procedure in the msdb database. Error message reading "EXECUTE permission denied on object 'sp_delete_job'".
Obviously this message tells me that I do not have permissions to execute stored procedures in the MSDB database.
In SQL 2000 I never had to mess around with permissions on this database as the security was already pre-configured.
I'm still familiarising myself with SQL 2005 so rather than making a finger in the air guess I'd like to understand how SQL 2000 was configured and the best solution for resolving this in SQL2005.
I'm really after some advice/suggestions!
I've just imported some SSIS packages onto my instance but my users aren't able to run the jobs for these packages (if thats the write terminology) it keeps failing with this error: Non-SysAdmins have been denied permission to run DTS Execution job steps without a proxy account. The step failed.
I've been looking around and I've been told I can assign the logins to the database roles in msdb but when I look for the roles in msdb they don't exist. SSIS is definitely installed on the server. How do I go about getting these added?
I was wondering if there was another method to determine when a database was last backed up without using the backup history tables in msdb? whether using DBCC DBINFO, DBCC PAGE on a specific database page...etc.
Also, when restoring a database, is there a trace flag you can use to force restore details to be written to the error log?
Hello anyone / everyone,
If you are having trouble accessing Meta Data Services on W2k3 and SQL 2000 and get the error that the "msdb database could not be opened" I found that hot fix 912812 on the operating system is the culprit. Remove it and Meta Data goes back to working, although I am being asked to approve the ActiveX control every time the page refreshes.
Hope this helps somebody, to took me long enough to track it down.
If anyone has a resolution to the ActiveX question I'd love to know the answer.
Thank you,
Uncle Davy
What is the best way to restore a database from a folder of backups (including full, diff and log backups) without using the backup history in msdb?
I have a restore process that restores all backups on a regular schedule in order to fully verify their integrity. To do this, I use the backup history in msdb on each server that I'm monitoring. I had a thought the other day that I would be in trouble if I lost msdb. Then my backup history would only be as good as the last backup of msdb.
What I'd like to do is read a folder of backup files and generate a restore script up to a specified time. Would I use RESTORE HEADERONLY to do this? If so, would I use PowerShell to traverse each file in the folder?
Hi All
Will Rebooting the SQLServer 2000,Is it change recovery model of MSDB Database
Please help...
Hi,
When I am trying to drop a user using following statement
--First remove access from all databases
Set @SQL =
'
USE [?];
if ''' + @login_name + ''' in (Select name from sysusers )
EXEC [?].dbo.sp_revokedbaccess @name_in_db = N''' + @login_name + ''';
'
Exec sp_msforeachdb @SQL
Print 'Access Removed.'
exec @ret_value=master.dbo.sp_droplogin @login_name
I am getting an error,
User has been dropped from current database.
User has been dropped from current database.
Access Removed.
No permission to access database 'model'.
Server: Msg 229, Level 14, State 5, Line 1
SELECT permission denied on object 'sysjobs', database 'msdb', owner 'dbo'.
Login dropped.
The SQL Version I am using is
-------------------------------------------
Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
Please help me to solve this issue.
Mujeeb.
Hello
I have a very large base msdb, I do not arrive has to purify it with sp_delete_backuphistory, it is much too long, have another solution? thank you
Hi ,
I am facing a paculiar problem.I got some jobs scheduled in MSDB.They are running fine for some time. Yesterday when i tried to open the properties of a job from EM i am getting an error 'Select Into Bulk copy option not enabled'
Can anyone got this before? I appreciate if any one can throw some thoughts on this.
thanks in advancce
MM
I know that msdb is used to manage the job schedulers in sql server 7.0 ( job agent ). Does this (msdb) like other databases, where I can control its size, shrink it or expand it.
IF am backing up the msdb, and I errased all jobs scheduled in sql agen. Can I restore all the deleted Jobs by restoring the msdb.
Ahmed
Does anyone know how to fix this message?
Message: Could not insert a backup or restore history/detail record in
msdb.dbo.sysbackuphistory or sysrestorehistory.
I ran DBCC CHECKDB (msdb) and no errors were reported.
Thanks
Hi ,
I have a job called JOBA scheduled to run every 10 min.
Is there a way in Tsql that I can find out whether the job is currently running or not.Is there any table/field in msdb database that gives me the desired info.
TIA,
Kinnu
My MSDB is too big [about 14 GB]. When I closely looked all tables, here is what I found -
Top 3 biggest tables are -
sysmaintplan_logdetail - rows- 124923 - data - 13375456 KB
DTA_Tuninglog - 181658 rows - data - 163248 KB
sysmail_mailitems - records - 14227 data - 126208 KB
I am not a DBA, so if any one can explain in simple terms how I can cleanup this maintenance plan log detail without increasing the size of tempdb? How can I stop this database growing in the future?
I have only a gig of space left on that drive.
Thanks in advance
I made a few changes to backup jobs. Within a few hours the MSDB grew to like 355MB. ANY ideas why this happened??
View 1 Replies View Related