Will Cumulative Update 12 for SQL Server 2008R2 SP2 fix: Warning: Unable to Verify TimeStamp for Path\ProgramName?
Hello,
I had a server crash recently and our outsource hosting tech support suggested applying Cumulative Upade 12 for SQL server 2008R2 SP2 to fix the issue. The exception from our dump file "Warning: Unable to Verify TimeStamp for Path\ProgramName"
is not in the list of hotfixes for this CU. Do you know if this will fix this issue? The CU warns not to apply the CU if your issue id not addressed by the CU. Here is a portion of the dump file with the relevant error:
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(7e8.2ab4): Unknown exception - code 000042ac (first/second chance not available)
ntdll!NtWaitForSingleObject+0xa:
00000000`777412fa c3 ret
0:240> .sympath srv*c:\Websymbols*http://msdl.microsoft.com/download/symbols;
Symbol search path is: srv*c:\Websymbols*http://msdl.microsoft.com/download/symbols
Expanded Symbol search path is: srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
0:240> .reload /f
.Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqlservr.exe
..........Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlos.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqlos.dll
...............Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\opends60.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for opends60.dll
.......Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\BatchParser.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for BatchParser.dll
....Unable to load image C:\Program Files\Microsoft SQL Server\100\Shared\instapi10.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for instapi10.dll
*** ERROR: Module load completed but symbols could not be loaded for instapi10.dll
..Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\sqlevn70.rll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqlevn70.rll
*** ERROR: Module load completed but symbols could not be loaded for sqlevn70.rll
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.................Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\ftimport.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ftimport.dll
.Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\msfte.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for msfte.dll
*** ERROR: Module load completed but symbols could not be loaded for msfte.dll
...........Unable to load image C:\Windows\System32\sqlncli10.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqlncli10.dll
...Unable to load image C:\Windows\System32\1033\SQLNCLIR10.RLL, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SQLNCLIR10.RLL
*** ERROR: Module load completed but symbols could not be loaded for SQLNCLIR10.RLL
..Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\xpsqlbot.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for xpsqlbot.dll
.Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\XPStar.DLL, Win32 error 0n2
*** WARNING: Unable to verify timestamp for XPStar.DLL
.Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlscm.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sqlscm.dll
...*** ERROR: Module load completed but symbols could not be loaded for odbcint.dll
...Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\XPStar.RLL, Win32 error 0n2
*** WARNING: Unable to verify timestamp for XPStar.RLL
Thank you,
Steve -
The error message appears to be related to a debug session and not come from the actual crash.
So all I know is that you hade a server crash. I don't even know exactly what that means. Did Windows bite the dust? Or was it only SQL Server?
Assuming the latter, I would expect the SQL Server errorlog to have some information (and that would be ERRORLOG.1 or earlier, since the server have been restarted), but if SQL Server died the output may be incomplete.
There may be also dump files, but as I rarely look into these, I am not sure how to interpret them. But I am quite confident that "Unable to verify TimeStamp..." is not the reason SQL Server went down.
I would suggest the following course:
* If the server is not critical, do nothing. As long as it has onlyl happened once, it has only happened once.
* If the server is critical, open a case with Microsoft if you are not able to figure out the reason yourself. The key here is "Unknown exception - code 000042ac".
* If it happens again, you should absolutely open a case. An important thing here is whether the stack dump is identical or something different. If the stack dumps are identical, you may have hit a bug in SQL Server or the OS, and applying CUs or OS
fixes could help if it is a known issue. If the stack dump is something else, you have ghosts in the machine - that is, bad hardware.
Erland Sommarskog, SQL Server MVP, [email protected]
Similar Messages
-
Hello,
Starting yesterday I started getting the BSOD. I have uploaded my dump files to this dropbox account:
www.dropbox.com/sh/w3ryago8pfcw2y2/AAAR5i6Crx5q-p--xdESJjnMa
There are lots of them as my PC crashed many times.
I attempted to analyze them with windbg but all I can see is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Also I ran sfc /scannow and it found no integrity violations.
After the first BSOD I was barely able to get Windows to load without another immediate crash. I couldn't boot my PC last night but today seems okay so far. CPU temp was fine, actually quite cool as I had my window open right by the PC with the side off
the case and it was cold last night. Today, so far, seems to be running okay...so far anyways..
Windows update recently installed a driver for my on-board video card (Nvidia GeForce 6150n) on the 18th I think as I started using a 2nd monitor using the on-board card in addition to my PCI Express Ati Radeon HD. To use the second screen, I switched
the primary video in CMOS to on-board instead of PCI-E 16x so the on-board Nvidia card would be enabled.
I also installed brand new ram (4gb DDR2) about a month ago
and a new power supply 2 months ago. The power supply is not "exactly" the same voltage as the one that was in there but it's dang close. But I don't have any power leeching components.
Other than that nothing new has happened. After I got the crash, I tried to enter CMOS yesterday and it glitched out on me twice. I hope it's not my motherboard..
I am willing to do a system re-format as I am running Windows 7 32bit on a 64bit AMD so I wouldn't mind having 64 bit Windows anyways but I'd like to know what the problem is before I do this. Thank you.
Update: Just did a MalwareByte's Anti-Malware scan and no malware but found these items:
Scan Date: 5/22/2014
Scan Time: 6:08:00 PM
Logfile:
OS: Windows 7 Service Pack 1
CPU: x86
File System: NTFS
Scan Type: Threat Scan
Result: Completed
Objects Scanned: 261539
Time Elapsed: 8 min, 10 sec
Processes: 0
(No malicious items detected)
Modules: 0
(No malicious items detected)
Registry Keys: 0
(No malicious items detected)
Registry Values: 0
(No malicious items detected)
Registry Data: 0
(No malicious items detected)
Folders: 2
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode, , [dd97c58f413a74c2503e7106649ec23e],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0, , [dd97c58f413a74c2503e7106649ec23e],
Files: 9
PUP.Optional.OptimumInstaller.A, C:\Users\Justin\Downloads\Player-Chrome.exe, , [6b090a4a4437d363a05f361717ea718f],
PUP.Optional.Outbrowse, C:\Users\Justin\Downloads\install-flashplayer.exe, , [561ee173fe7d1125edf4d9a443be5aa6],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0\icon-128.png, , [dd97c58f413a74c2503e7106649ec23e],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0\icon-16.png, , [dd97c58f413a74c2503e7106649ec23e],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0\icon-48.png, , [dd97c58f413a74c2503e7106649ec23e],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0\jquery-1.10.2.min.js, , [dd97c58f413a74c2503e7106649ec23e],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0\manifest.json, , [dd97c58f413a74c2503e7106649ec23e],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0\tweetwiki.js, , [dd97c58f413a74c2503e7106649ec23e],
PUP.Optional.CrossRider.A, C:\Users\Justin\AppData\Local\Google\Chrome\User Data\Default\Extensions\ecoccdldklbjglocbgbfpmpehjegkode\0.1_0\_DS_Store, , [dd97c58f413a74c2503e7106649ec23e],
Physical Sectors: 0
(No malicious items detected)Hi,
All of the attached DMP files are of the
WHEA_UNCORRECTABLE_ERROR (124) bug check.
A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).
If we run an !errrec on the 2nd parameter of the bug check (address of the WER structure) we get the following:
BugCheck 124, {0, 867d2024, b2000010, 10c0f}
===============================================================================
Section 2 : x86/x64 MCA
Descriptor @ 867d2134
Section @ 867d22bc
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)
Status : 0xb200001000010c0f
This is a pretty complicated error compared to other possibilities it could have been, as it implies you have a hardware fault somewhere along the bus (not very definitive on its own).
In our case however, we can go a bit deeper with this one:
0: kd> .formats 0xb200001000010c0f
Evaluate expression:
Hex: b2000010`00010c0f
Decimal: -5620492266238833649
Octal: 1310000001000000206017
Binary: 10110010 00000000 00000000 00010000 00000000 00000001 00001100 00001111
Chars: ........
Time: ***** Invalid FILETIME
Float: low 9.61613e-041 high -7.45059e-009
Double: -7.41853e-068
Now that we have this info, we'd refer to the AMD manual:
63 VAL Valid
62 OVER Status Register Overflow
61 UC Uncorrected Error
60 EN Error Condition Enabled
59 MISCV Miscellaneous-Error Register Valid
58 ADDRV Error-Address Register Valid
57 PCC Processor-Context Corrupt
56–32 Other Information
31–16 Model-Specific Error Code
15–0 MCA Error Code
In our specific case, bit 63 of the status code is set, so it is valid. Bit 62 of the status code is
unset, therefore there's no overflow. Bit 61 implies an uncorrected error has occurred, and Bit 60 implies an error condition was enabled. Last but not least, Bit 57 is
set and implies a corrupted processor context.
If we take a look at the last 15 bits of the binary:
Binary: [trimming] 00001100 00001111
In our case, the MSB in binary (00001100 ), implies a bus error occurred (as I mentioned above). We need to further decode the bits to understand more:
[0000]1100 00001111
0000 = 1PPT RRRR IILL.
PP = Participation Processor, T = Timeout,
R = Memory Transaction Type, I = Memory and/or I/O, and finally
L = Cache Level.
With this said, it appears we actually have a faulty motherboard as the processor seems fine, etc. The only other thing I see possible is bad RAM, which you can figure out whether or not is the case by running no less than ~8 passes of Memtest:
Memtest86+:
Download Memtest86+ here:
http://www.memtest.org/
Which should I download?
You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary
files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).
Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).
How Memtest works:
Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.
The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because
of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.
Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance
is error-free with these faster settings.
Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.
This information, if available to the program, can be displayed via a menu option.
Any other questions, they can most likely be answered by reading this great guide here:
http://forum.canardpc.com/threads/28864-FAQ-please-read-before-posting
Regards,
Patrick
“Be kind whenever possible. It is always possible.” - Dalai Lama -
Cumulative update 5 for SQL Server 2012 SP2 is released
Cumulative update 5 for SQL Server 2012 SP2 is released
https://support.microsoft.com/en-us/kb/3037255
MDS related fix is:
FIX: The notification email link is broken when a special character is part of the URL in SQL Server 2012 MDS
http://support.microsoft.com/en-us/kb/3036201Hello,
The following blog shows the latest builds (updates) available for each version of SQL Server.
http://sqlserverbuilds.blogspot.com/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Which .exe file I should choose to apply SP2 for SQL Server 2008r2 Enterprise Edition 64Bit
Hi All,
Which .exe file I should choose to apply SP2 for SQL Server 2008r2 Enterprise Edition 64Bit.
And what is the difference between below .exe files.
SQLServer2008R2SP2-KB2630458-x64-ENU.exe
SQLServer2008R2SP2-KB2630458-IA64-ENU.exe
Grateful to your time and support. Regards, ShivaGood day
Shiva Shakthi,
I have change the type of the thread to a question, as this is a question :-)
please chose the right type next time. If you have a question then use a question thread (this is the default), and that will let you mark the answers that you get.
Have a nice day :-)
[Personal Site] [Blog] [Facebook] -
SQL Server 2008R2 SP2 Query optimizer memory leak ?
It looks like we are facing a SQL Server 2008R2 queery optimizer memory leak.
We have below version of SQL Server
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)
Jun 28 2012 08:36:30
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
The instance is set MAximum memory tro 20 GB.
After executing a huge query (2277 kB generated by IBM SPSS Clementine) with tons of CASE and a lot of AND/OR statements in the WHERE and CASE statements and muliple subqueries the server stops responding on Out of memory in the internal pool
and the query optimizer has allocated all the memory.
From Management Data Warehouse we can find that the query was executed at
7.11.2014 22:40:57
Then at 1:22:48 we recieve FAIL_PACE_ALLOCATION 1
2014-11-08 01:22:48.70 spid75 Failed allocate pages: FAIL_PAGE_ALLOCATION 1
And then tons of below errors
2014-11-08 01:24:02.22 spid87 There is insufficient system memory in resource pool 'internal' to run this query.
2014-11-08 01:24:02.22 Server Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
2014-11-08 01:24:02.22 Server Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
2014-11-08 01:24:02.30 Server Error: 17312, Severity: 16, State: 1.
2014-11-08 01:24:02.30 Server SQL Server is terminating a system or background task Fulltext Host Controller Timer Task due to errors in starting up the task (setup state 1).
2014-11-08 01:24:02.22 spid74 Error: 701, Severity: 17, State: 123.
2014-11-08 01:24:02.22 spid74 There is insufficient system memory in resource pool 'internal' to run this query.
2014-11-08 01:24:13.22 Server Error: 17312, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
2014-11-08 01:24:13.22 spid87 Error: 701, Severity: 17, State: 123.
2014-11-08 01:24:13.22 spid87 There is insufficient system memory in resource pool 'internal' to run this query.
2014-11-08 01:24:13.22 spid63 Error: 701, Severity: 17, State: 130.
2014-11-08 01:24:13.22 spid63 There is insufficient system memory in resource pool 'internal' to run this query.
2014-11-08 01:24:13.22 spid57 Error: 701, Severity: 17, State: 123.
2014-11-08 01:24:13.22 spid57 There is insufficient system memory in resource pool 'internal' to run this query.
2014-11-08 01:24:13.22 Server Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
2014-11-08 01:24:18.26 Server Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
2014-11-08 01:24:24.43 spid81 Error: 701, Severity: 17, State: 123.
2014-11-08 01:24:24.43 spid81 There is insufficient system memory in resource pool 'internal' to run this query.
2014-11-08 01:24:18.25 Server Error: 18052, Severity: -1, State: 0. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
2014-11-08 01:24:18.25 Server BRKR TASK: Operating system error Exception 0x1 encountered.
2014-11-08 01:24:30.11 Server Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
2014-11-08 01:24:30.11 Server Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
2014-11-08 01:24:35.18 spid57 Error: 701, Severity: 17, State: 131.
2014-11-08 01:24:35.18 spid57 There is insufficient system memory in resource pool 'internal' to run this query.
2014-11-08 01:24:35.18 spid71 Error: 701, Severity: 17, State: 193.
2014-11-08 01:24:35.18 spid71 There is insufficient system memory in resource pool 'internal' to run this query.
2014-11-08 01:24:35.18 Server Error: 17312, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
2014-11-08 01:24:35.41 Server Error: 17312, Severity: 16, State: 1.
2014-11-08 01:24:35.41 Server SQL Server is terminating a system or background task SSB Task due to errors in starting up the task (setup state 1).
2014-11-08 01:24:35.71 Server Error: 17053, Severity: 16, State: 1.
2014-11-08 01:24:35.71 Server BRKR TASK: Operating system error Exception 0x1 encountered.
2014-11-08 01:24:35.71 spid73 Error: 701, Severity: 17, State: 123.
2014-11-08 01:24:35.71 spid73 There is insufficient system memory in resource pool 'internal' to run this query.
2014-11-08 01:24:46.30 Server Error: 17312, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
2014-11-08 01:24:51.31 Server Error: 17053, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
2014-11-08 01:24:51.31 Server Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
2014-11-08 01:24:51.31 Logon Error: 18052, Severity: -1, State: 0. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
Last error message is half an hour after the inital Out of memory at 2014-11-08 01:52:54.03. Then the Instance is completely shut down
From the memory information in the error log we can see that all the memory is consumed by the QUERY_OPTIMIZER
Buffer Pool Value
Committed 2621440
Target 2621440
Database 130726
Dirty 3682
In IO
0
Latched
1
Free
346
Stolen 2490368
Reserved 0
Visible 2621440
Stolen Potential 0
Limiting Factor 17
Last OOM Factor 0
Last OS Error 0
Page Life Expectancy 28
2014-11-08 01:22:48.90 spid75
Process/System Counts Value
Available Physical Memory 29361627136
Available Virtual Memory 8691842715648
Available Paging File 51593969664
Working Set 628932608
Percent of Committed Memory in WS 100
Page Faults 48955000
System physical memory high 1
System physical memory low 0
Process physical memory low 1
Process virtual memory low 0
MEMORYCLERK_SQLOPTIMIZER (node 1) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 19419712
MultiPage Allocator 128
Memory Manager KB
VM Reserved 100960236
VM Committed 277664
Locked Pages Allocated 21483904
Reserved Memory 1024
Reserved Memory In Use 0
On the other side MDW reports that the MEMORYCLERK_SQLOPTIMIZER increases since the execution of the query up to the point of OUTOF MEMORY, but the Average value is 54.7 MB during that period as can be seen on attached graph.
We have encountered this issue already two times (every time the critical query is executed).Hi,
This does seems to me kind of memory Leak and actually it is from SQL Optimizer which leaked memory from buffer pool so much that it did not had any memory to be allocated for new page.
MEMORYCLERK_SQLOPTIMIZER (node 1) KB
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
SinglePage Allocator 19419712
MultiPage Allocator 128
Can you post complete DBCC MEMORYSTATUS output which was generated in errorlog. Is this the only message in errorlog or there are some more messages before and after it.
select (SUM(single_pages_kb)*1024)/8192 as total_stolen_pages, type
from sys.dm_os_memory_clerks
group by typeorder by total_stolen_pages desc
and
select sum(pages_allocated_count * page_size_in_bytes)/1024,type from sys.dm_os_memory_objects
group by type
If you can post the output of above two queries with dbcc memorystaus output on some shared drive and share location with us here. I would try to find out what is leaking memory.
You can very well apply SQL Server 2008 r2 SP3 and see if this issue subsides but I am not sure whether this is fixed or actually it is a bug.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP -
Use rptproj SSRS for SQL Server 2008R2 in VS 2010 (and/or VS 2012 better(
In my company, I use VS 2008 and SQLServer 2008R2, and I have rptproj projects in VS 2008.
The rptproj project has several rdl files.
I would like use VS 2010 or VS 2012 with SSRS and SQLServer 2008R2.
SSDT, which was introduced with SQL Server 2012. I suggest not possible migration rpt projects in VS 2008 to VS 2010 / VS 2012
Any alternative solution to do it ?
I have seen, but I'm confused it
http://stackoverflow.com/questions/12503976/how-to-edit-ssrs-2008r2-reports-in-visual-studio-2012/16112721#16112721
Iko says
You can now use Visual Studio 2010 to edit .rtproj report projects and .rdl reports.
You need VS10 SP1, then install the Data Tools for VS10, followed by the installation of SQL Server Express 2012 with Reporting Services and Data Tools.
Reference: http://stackoverflow.com/a/14599850/206730
But I'm confused about it.
www.kiquenet.com/profesionalHi Kiquenet,
According to your description, you installed VS 2008 and SQL Server 2008 R2, and create Reporting Services projects. Now you want to use VS 2010 or VS 2012 to open and manage the reports.
SQL Server Data Tools - Business Intelligence for Visual Studio 2012 supports versions of SQL Server 2012 or lower, we can directly download Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2012 from
https://www.microsoft.com/en-us/download/details.aspx?id=36843, then select SQL Server Data Tools - Business Intelligence for Visual Studio 2012 and SQL Client Connectivity SDK as
new shard features to install.
We can open the projects in both Visual Studio 2012 and Visual Studio 2010. For local mode only (that is, when not connected to SQL Server), we won’t get the design-time experience for controls that are associated with the viewer in Visual Studio 2008, but
the project will function correctly at runtime. If we add a feature that’s specific to Visual Studio 2012, the report schema is upgraded automatically and you can no longer open the project in Visual Studio 2008.
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
Wendy Fu
TechNet Community Support -
Services configuration for sql server 2008r2 in a Windows Cluster
Hello,
We have a Windows Server 2008 Cluster with Sql Server 2008r2 installed on node 2; when node 2 fails (we don't still know why, it's a 'bluescreen' long history), the service goes from node2 to node1, but sometimes the services are not automatically activated.
What is the theoretical startup settings for sql services (for the sql and the agent), manual, disabled, automatic... ?
Also, sometimes, the service for the sql server in node2 stops, but we don't know why, and we are not able to see any significant information on the event viewer. How can we trace why Sql Server stopped ?
Thanks !>What is the theoretical startup settings for sql services
Manual. The cluster will start them.
>How can we trace why Sql Server stopped ?
Look in the SQL Server Log.
David
David http://blogs.msdn.com/b/dbrowne/ -
Package Failing after update to SQL Server 2012 SP2
I have a package that was running fine with SQL Server 2012 until an upgrade to SP2 the package now fails in a derived column step where a bunch of type casts are done
(DT_NTEXT)"\" " + (DT_NTEXT)@[User::phantomScriptLoc] + (DT_NTEXT)"getautomatedtable.js " + (DT_NTEXT)"--ignore-ssl-errors=yes -user \"" + (DT_NTEXT)Username + (DT_NTEXT)"\" -pass \"" + (DT_NTEXT)Password + (DT_NTEXT)"\" -url \"" + (DT_NTEXT)@[User::gatewayWebLoc] + (DT_NTEXT)"\" -module \"/" + (DT_NTEXT)module_name + (DT_NTEXT)"/index.cfm\" -reportpage \"" + (DT_NTEXT)report_name + (DT_NTEXT)"\" -deptid \"" + (DT_NTEXT)cast_deptid + (DT_NTEXT)"\" -reportname \"" + (DT_NTEXT)report_title + (DT_NTEXT)"\" -outfile \"" + (DT_NTEXT)@[User::storeReportsLoc] + (DT_NTEXT)filename + (DT_NTEXT)"\" -format \"" + (DT_NTEXT)RTRIM(AutoRpt_FileFmt_Txt) + (DT_NTEXT)"\" -querystring \"" + (DT_NTEXT)queryString + (DT_NTEXT)"&debugMode=1\"\""
The package does not return an error but instaed call SQLDUMPER and creates a dump file.
Any one else had an issue since an SP2 upgrade?Hi tbrown10a,
I am able to reproduce the issue after installing SP2 for SQL Server 2012. The issue occurs when trying to cast one data type to DT_NTEXT or DT_TEXT data type. As Arthur mentioned, I would suggest you file a connect at
https://connect.microsoft.com/sql.
Connect site is a connection point between you and Microsoft, and ultimately the larger community. Your feedback enables Microsoft to make software and services the best that they can be, and you can learn about and contribute to exciting projects.
Regards,
Mike Yin
TechNet Community Support -
2014-03-08 13:28:51 SQLEngine: : File versions : ['D:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\SQSRVRES.DLL':2009.2009.4266.0], ['C:\Windows\system32\SQSRVRES.DLL':2009.2009.4266.0].
2014-03-08 13:28:51 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-03-08 13:28:51 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls
2014-03-08 13:28:51 Slp: Sco: Attempting to get registry value C:\Windows\system32\SQSRVRES.DLL
2014-03-08 13:28:51 SQLEngine: : Incrementing value for DLL C:\Windows\system32\SQSRVRES.DLL, current value = 6
2014-03-08 13:28:51 Slp: Sco: Attempting to get registry value C:\Windows\system32\SQSRVRES.DLL
2014-03-08 13:28:51 Slp: Sco: Attempting to set value C:\Windows\system32\SQSRVRES.DLL
2014-03-08 13:28:51 Slp: SetValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls, Name = C:\Windows\system32\SQSRVRES.DLL
2014-03-08 13:28:51 SQLEngine: : Leaving ConfigureSQLEngineResourceType
2014-03-08 13:28:51 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-03-08 13:28:51 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\Setup
2014-03-08 13:28:51 Slp: Sco: Attempting to get registry value PatchLevel
2014-03-08 13:28:51 SQLEngine: --PerfmonRegistration: Checking whether to patch performance counters for service 'MSSQLSERVER'
2014-03-08 13:28:51 SQLEngine: --PerfmonRegistration: Getting perfmon DLL name from key at 'System\CurrentControlSet\Services\MSSQLSERVER\Performance'
2014-03-08 13:28:51 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2014-03-08 13:28:51 Slp: Sco: Attempting to open registry subkey System\CurrentControlSet\Services\MSSQLSERVER\Performance
2014-03-08 13:28:51 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
2014-03-08 13:28:51 Slp: The registry key System\CurrentControlSet\Services\MSSQLSERVER\Performance is missing.
2014-03-08 13:28:51 Slp: The configuration failure category of current exception is ConfigurationFailure
2014-03-08 13:28:51 Slp: Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigRC and scenario ConfigRC.
2014-03-08 13:28:51 Slp: Microsoft.SqlServer.Configuration.SqlEngine.MissingRegistryKeyException: The registry key System\CurrentControlSet\Services\MSSQLSERVER\Performance is missing.
2014-03-08 13:28:51 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.Globals.GetSqlRegistryKeyHKLM(ServiceContainer context, String key, String machineName, Boolean createIfNotFound)
2014-03-08 13:28:51 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.PerfmonRegistration.GetDLLNameFromRegistry()
2014-03-08 13:28:51 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.PerfmonRegistration.NeedToPatch()
2014-03-08 13:28:51 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.PatchPerfmonCounters(EffectiveProperties properties)
2014-03-08 13:28:51 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.Patch(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb)
2014-03-08 13:28:51 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
2014-03-08 13:28:51 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
2014-03-08 13:28:51 Slp: Exception: Microsoft.SqlServer.Configuration.SqlEngine.MissingRegistryKeyException.
2014-03-08 13:28:51 Slp: Source: Microsoft.SqlServer.Configuration.SqlServer_ConfigExtension.
2014-03-08 13:28:51 Slp: Message: The registry key System\CurrentControlSet\Services\MSSQLSERVER\Performance is missing..
2014-03-08 13:28:52 Slp: Watson Bucket 1
Original Parameter Values
2014-03-08 13:28:52 Slp: Parameter 0 : SQL2008@RTM@KB2754552
2014-03-08 13:28:52 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.SqlEngine.Globals.GetSqlRegistryKeyHKLM
2014-03-08 13:28:52 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.SqlEngine.Globals.GetSqlRegistryKeyHKLM
2014-03-08 13:28:52 Slp: Parameter 3 : Microsoft.SqlServer.Configuration.SqlEngine.MissingRegistryKeyException@1306@30
2014-03-08 13:28:52 Slp: Parameter 4 : Microsoft.SqlServer.Configuration.SqlEngine.MissingRegistryKeyException@1306@30
2014-03-08 13:28:52 Slp: Parameter 5 : SqlEngineConfigAction_patch_configrc
2014-03-08 13:28:52 Slp: Parameter 6 : PATCH@CONFIGRC@SQL_ENGINE_CORE_INST
2014-03-08 13:28:52 Slp:
Final Parameter Values
2014-03-08 13:28:52 Slp: Parameter 0 : SQL2008@RTM@KB2754552
2014-03-08 13:28:52 Slp: Parameter 1 : 0x4E0712AD
2014-03-08 13:28:52 Slp: Parameter 2 : 0x4E0712AD
2014-03-08 13:28:52 Slp: Parameter 3 : 0x2F2F19BE@1306@30
2014-03-08 13:28:52 Slp: Parameter 4 : 0x2F2F19BE@1306@30
2014-03-08 13:28:52 Slp: Parameter 5 : SqlEngineConfigAction_patch_configrc
2014-03-08 13:28:52 Slp: Parameter 6 : 0x94D05575
Sangamesh msHi,
Backup system\CurrentControlSet\Services\MSSQLSERVER\ first.
For loading the performance counter, we need a perf-<instancename>sqlctr.ini file, a sqlctr.h file matching the .ini file, and the
registry key under System\CurrentControlSet\Services\MSSQLSERVER\Performance.
According the description, I understand that it is missing the correct perf-<instancename>sqlctr.ini and the
registry in your environment.
I suggest you manually add the registry key values under the
System\CurrentControlSet\Services\MSSQLSERVER\Performance with referring the value of registry on other working machine. Also I copy the perf-<instancename>sqlctr.ini file from other working
machine as they are both SQL Server 2008 R2. Then, restart the server.
You can reload the system performance counter by lodctr /R and lodctr /T:MSSQLSERVER to set the SQL Server performance counter service as trusted.
Lodctr
http://technet.microsoft.com/en-us/library/hh875560.aspx
Thanks.
Tracy Cai
TechNet Community Support -
SQL Server 2012 SP2 Cumulative Update 5
We are starting to take a look at Cumulative update 5 for SQL Server 2012 SP2. The Installation was going smooth until the very in, where it sat on trying to start MSSQLServer for several minutes and finally timed out. Why does Cumulative
patch 5 says it failed to start the service when the server is already running? Version number changed, and everthing looks ok, except for the error message in the log file.
Is this a valid installation or do I need to try again?
Thanks.
DJThanks for the reply. The ErrorLog is too large to post in 1 reply. Will post multiple times.
Version of the SQL Server shows 11.0.5582.0
Dj
Post 1
2015-03-24 14:13:23.82 Server Microsoft SQL Server 2012 - 11.0.5582.0 (X64)
Feb 27 2015 18:10:15
Copyright (c) Microsoft Corporation
Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
2015-03-24 14:13:23.82 Server (c) Microsoft Corporation.
2015-03-24 14:13:23.82 Server All rights reserved.
2015-03-24 14:13:23.82 Server Server process ID is 37184.
2015-03-24 14:13:23.82 Server System Manufacturer: 'VMware, Inc.', System Model: 'VMware Virtual Platform'.
2015-03-24 14:13:23.82 Server Authentication mode is MIXED.
2015-03-24 14:13:23.82 Server Logging SQL Server messages in file 'L:\SQL Server\Log Files\ERRORLOG'.
2015-03-24 14:13:23.82 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2015-03-24 14:13:23.82 Server Registry startup parameters:
-d H:\\System DB\Data\master.mdf
-e L:\SQL Server\Log Files\ERRORLOG
-l G:\\System DB\Logs\mastlog.ldf
2015-03-24 14:13:23.82 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2015-03-24 14:13:24.15 Server SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational
message; no user action is required.
2015-03-24 14:13:24.15 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-03-24 14:13:24.15 Server Detected 8191 MB of RAM. This is an informational message; no user action is required.
2015-03-24 14:13:24.15 Server Using locked pages in the memory manager.
2015-03-24 14:13:24.15 Server Common Criteria compliance mode is enabled. This is an informational message only; no user action is required.
2015-03-24 14:13:24.22 Server This instance of SQL Server last reported using a process ID of 39820 at 3/24/2015 2:09:46 PM (local) 3/24/2015 6:09:46 PM (UTC). This is an informational message only; no user action is required.
2015-03-24 14:13:24.23 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2015-03-24 14:13:24.23 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2015-03-24 14:13:24.24 Server Software Usage Metrics is disabled.
2015-03-24 14:13:24.24 spid4s Starting up database 'master'.
2015-03-24 14:13:24.30 spid4s 9 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-03-24 14:13:24.32 spid4s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-03-24 14:13:24.32 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2015-03-24 14:13:24.33 Server CLR version v4.0.30319 loaded.
2015-03-24 14:13:24.36 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-03-24 14:13:39.41 spid6s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [H:\\System DB\Data\master.mdf] in database [master] (1). The OS file handle is 0x0000000000000598.
The offset of the latest long I/O is: 0x0000000002a000
2015-03-24 14:13:53.94 spid4s Recovery completed for database master (database ID 1) in 29 second(s) (analysis 3 ms, redo 39 ms, undo 8 ms.) This is an informational message only. No user action is required.
2015-03-24 14:13:54.19 spid4s CHECKDB for database 'master' finished without errors on 2015-03-06 08:35:22.387 (local time). This is an informational message only; no user action is required.
2015-03-24 14:13:54.19 spid4s Resource governor reconfiguration succeeded.
2015-03-24 14:13:54.19 spid4s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-03-24 14:13:54.19 spid4s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-03-24 14:13:54.21 spid4s Server name is 'Server'. This is an informational message only. No user action is required.
2015-03-24 14:13:54.22 spid4s Failed to verify Authenticode signature on DLL 'S:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Binn\ftimport.dll'.
2015-03-24 14:13:54.22 spid9s Starting up database 'mssqlsystemresource'.
2015-03-24 14:13:54.22 spid14s Starting up database 'msdb'.
2015-03-24 14:13:54.23 spid15s Starting up database 'Mgmt'.
2015-03-24 14:13:54.24 spid16s Starting up database 'Web2'.
2015-03-24 14:13:54.24 spid12s The certificate [Cert Hash(sha1) "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"] was successfully loaded for encryption.
2015-03-24 14:13:54.24 spid18s Starting up database 'Web2A'.
2015-03-24 14:13:54.24 spid9s The resource database build version is 11.00.5582. This is an informational message only. No user action is required.
2015-03-24 14:13:54.25 spid12s Server is listening on [ 'any' <ipv6> 1433].
2015-03-24 14:13:54.25 spid12s Server is listening on [ 'any' <ipv4> 1433].
2015-03-24 14:13:54.25 spid12s Server local connection provider is ready to accept connection on [
\\.\pipe\SQLLocal\MSSQLSERVER ].
2015-03-24 14:13:54.26 spid12s Server local connection provider is ready to accept connection on [
\\.\pipe\sql\query ].
2015-03-24 14:13:54.26 Server Server is listening on [ ::1 <ipv6> 1434].
2015-03-24 14:13:54.26 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2015-03-24 14:13:54.26 Server Dedicated admin connection support was established for listening locally on port 1434.
2015-03-24 14:13:54.26 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This
is an informational message. No user action is required.
2015-03-24 14:13:54.33 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/Server.local ] for the SQL Server service.
2015-03-24 14:13:54.33 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/Server.local:1433 ] for the SQL Server service.
2015-03-24 14:13:54.39 spid9s Starting up database 'model'.
2015-03-24 14:13:54.42 spid4s 1 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2015-03-24 14:13:54.42 spid4s Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2015-03-24 14:13:54.46 spid9s 1 transactions rolled forward in database 'model' (3:0). This is an informational message only. No user action is required.
2015-03-24 14:13:54.47 spid9s 0 transactions rolled back in database 'model' (3:0). This is an informational message only. No user action is required.
2015-03-24 14:13:54.62 spid9s Clearing tempdb database.
2015-03-24 14:14:17.34 spid9s Starting up database 'tempdb'.
2015-03-24 14:14:27.05 spid19s The Service Broker endpoint is in disabled or stopped state.
2015-03-24 14:14:27.06 spid19s The Database Mirroring endpoint is in disabled or stopped state.
2015-03-24 14:14:27.07 spid19s Service Broker manager has started.
2015-03-24 14:14:27.21 spid15s CHECKDB for database 'Mgmt' finished without errors on 2014-09-14 00:02:54.637 (local time). This is an informational message only; no user action is required.
2015-03-24 14:14:27.58 spid16s CHECKDB for database 'Web2' finished without errors on 2015-03-22 00:00:43.253 (local time). This is an informational message only; no user action is required.
2015-03-24 14:14:27.65 spid4s Database 'master' is upgrading script 'ProvisionAgentIdentity.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:27.65 spid4s Database 'master' is upgrading script 'no_op.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:27.93 spid4s Database 'master' is upgrading script 'no_op.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:27.94 spid4s -----------------------------------------
2015-03-24 14:14:27.94 spid4s Starting execution of dummy.sql
2015-03-24 14:14:27.94 spid4s -----------------------------------------
2015-03-24 14:14:27.94 spid4s Database 'master' is upgrading script 'repl_upgrade.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:27.94 spid4s Executing replication upgrade scripts.
2015-03-24 14:14:27.99 spid4s Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2015-03-24 14:14:28.07 spid4s Using 'xpstar.dll' version '2011.110.5058' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2015-03-24 14:14:28.09 spid4s Executing sp_vupgrade_replication.
2015-03-24 14:14:28.50 spid4s Upgrading publication settings and system objects in database [Mgmt].
2015-03-24 14:14:28.89 spid4s Upgrading publication settings and system objects in database [Web2].
2015-03-24 14:14:29.98 spid4s Upgrading publication settings and system objects in database [Web2A].
2015-03-24 14:14:30.48 spid4s Could not open database [LEGACY_DSS]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:30.48 spid4s Could not open database [PROD_1]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the
database is available.
2015-03-24 14:14:30.48 spid4s Could not open database [PROD_LS]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:30.48 spid4s Could not open database [PROD_NG]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:30.48 spid4s Could not open database [PROD_RSV]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:30.52 spid4s Upgrading subscription settings and system objects in database [Mgmt].
2015-03-24 14:14:31.17 spid4s Attempting to load library 'xprepl.dll' into memory. This is an informational message only. No user action is required.
2015-03-24 14:14:31.19 spid4s Using 'xprepl.dll' version '2011.110.5582' to execute extended stored procedure 'xp_repl_encrypt'. This is an informational message only; no user action is required.
2015-03-24 14:14:31.19 spid4s Upgrading subscription settings and system objects in database [Web2].
2015-03-24 14:14:31.75 spid4s Upgrading subscription settings and system objects in database [Web2A].
2015-03-24 14:14:32.31 spid4s Could not open database [LEGACY]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the
database is available.
2015-03-24 14:14:32.31 spid4s Could not open database [PROD_1]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when the
database is available.
2015-03-24 14:14:32.31 spid4s Could not open database [PROD_LS]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:32.31 spid4s Could not open database [PROD_NG]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:32.31 spid4s Could not open database [PROD_RSV]. Replication settings and system objects could not be upgraded. If the database is used for replication, run sp_vupgrade_replication in the [master] database when
the database is available.
2015-03-24 14:14:32.33 spid4s Attempting to copy article resolvers from SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11.MSSQLSERVER\Replication\ArticleResolver
2015-03-24 14:14:32.59 spid4s sp_vupgrade_replication executed successfully
2015-03-24 14:14:32.59 spid4s Saving upgrade script status to 'SOFTWARE\Microsoft\MSSQLServer\Replication\Setup'.
2015-03-24 14:14:32.59 spid4s Saved upgrade script status successfully.
2015-03-24 14:14:32.59 spid4s Database 'master' is upgrading script 'upgrade_ucp_cmdw_discovery.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:32.92 spid4s Database 'master' is upgrading script 'msdb110_upgrade.sql' from level 184554434 to level 184554958.
2015-03-24 14:14:32.92 spid4s ----------------------------------
2015-03-24 14:14:32.92 spid4s Starting execution of PRE_MSDB.SQL
2015-03-24 14:14:32.92 spid4s ----------------------------------
2015-03-24 14:14:33.08 spid4s Setting database option COMPATIBILITY_LEVEL to 100 for database 'msdb'.
2015-03-24 14:14:33.17 spid4s -----------------------------------------
2015-03-24 14:14:33.17 spid4s Starting execution of PRE_SQLAGENT100.SQL
2015-03-24 14:14:33.17 spid4s -----------------------------------------
2015-03-24 14:14:33.17 spid4s Setting database option COMPATIBILITY_LEVEL to 110 for database 'msdb'.
2015-03-24 14:14:33.22 spid4s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 14:14:33.22 spid4s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 14:15:00.06 spid6s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [G:\\System DB\Logs\MSDBLog.ldf] in database [msdb] (4). The OS file handle is 0x0000000000000790.
The offset of the latest long I/O is: 0x00000000efac00
2015-03-24 14:16:00.87 spid4s DBCC TRACEOFF 1717, server process ID (SPID) 4. This is an informational message only; no user action is required.
2015-03-24 14:16:00.87 spid4s DBCC execution completed. If DBCC printed error messages, contact your system administrator.
2015-03-24 14:16:00.88 spid4s
2015-03-24 14:16:00.88 spid4s Creating table temp_sysjobschedules
2015-03-24 14:16:01.00 spid4s
2015-03-24 14:16:01.00 spid4s Alter table sysdownloadlist...
2015-03-24 14:16:01.00 spid4s
2015-03-24 14:16:01.00 spid4s Alter table sysjobhistory...
2015-03-24 14:16:01.02 spid4s
2015-03-24 14:16:01.02 spid4s Alter table systargetservers...
2015-03-24 14:16:01.02 spid4s
2015-03-24 14:16:01.02 spid4s Alter table sysjobsteps...
2015-03-24 14:16:01.09 spid4s Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-03-24 14:16:01.09 spid4s Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2015-03-24 14:16:01.09 spid4s
2015-03-24 14:16:01.09 spid4s -----------------------------------------
2015-03-24 14:16:01.09 spid4s Execution of PRE_SQLAGENT100.SQL complete
2015-03-24 14:16:01.09 spid4s -----------------------------------------
2015-03-24 14:16:01.10 spid4s DMF pre-upgrade steps...
2015-03-24 14:16:01.25 spid4s DC pre-upgrade steps...
2015-03-24 14:16:01.25 spid4s Check if Data collector config table exists...
2015-03-24 14:16:01.25 spid4s Data Collector state before upgrade: 0
2015-03-24 14:16:01.25 spid4s pre_dc100::Check if syscollector_collection_sets_internal table exists...
2015-03-24 14:16:01.25 spid4s pre_dc100::Capturing Collection set status in temp table...
2015-03-24 14:16:01.33 spid4s Deleting cached auto-generated T-SQL Data Collection packages from msdb...
2015-03-24 14:16:01.33 spid4s End of DC pre-upgrade steps.
2015-03-24 14:16:01.33 spid4s DAC pre-upgrade steps...
2015-03-24 14:16:01.33 spid4s Starting DAC pre-upgrade steps ...
2015-03-24 14:16:01.33 spid4s End of DAC pre-upgrade steps.
2015-03-24 14:16:01.33 spid4s ----------------------------------
2015-03-24 14:16:01.33 spid4s Starting execution of MSDB.SQL
2015-03-24 14:16:01.33 spid4s ----------------------------------
2015-03-24 14:16:01.39 spid4s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 14:16:01.39 spid4s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2015-03-24 14:16:01.42 spid4s Checking the size of MSDB...
2015-03-24 14:16:01.60 spid4s
2015-03-24 14:16:01.60 spid4s Setting database option TRUSTWORTHY to ON for database 'msdb'.
2015-03-24 14:16:01.60 spid4s Setting database option RECOVERY to SIMPLE for database 'msdb'.
2015-03-24 14:16:01.63 spid4s ----------------------------------
2015-03-24 14:16:01.63 spid4s Finished execution of MSDB.SQL
2015-03-24 14:16:01.63 spid4s ----------------------------------
2015-03-24 14:16:01.63 spid4s -----------------------------------------
2015-03-24 14:16:01.63 spid4s Starting execution of MSDB_VERSIONING.SQL
2015-03-24 14:16:01.63 spid4s -----------------------------------------
2015-03-24 14:16:01.63 spid4s -----------------------------------------
2015-03-24 14:16:01.63 spid4s Finished execution of MSDB_VERSIONING.SQL
2015-03-24 14:16:01.63 spid4s -----------------------------------------
2015-03-24 14:16:01.63 spid4s Dropping view MSdatatype_mappings...
2015-03-24 14:16:01.63 spid4s Dropping view sysdatatypemappings...
2015-03-24 14:16:30.94 spid4s Dropping table MSdbms_datatype_mapping...
2015-03-24 14:16:30.95 spid4s Dropping table MSdbms_map...
2015-03-24 14:16:30.96 spid4s Dropping table MSdbms_datatype...
2015-03-24 14:16:30.96 spid4s Dropping table MSdbms...
2015-03-24 14:16:30.99 spid4s Creating table MSdbms
2015-03-24 14:16:31.00 spid4s Creating table MSdbms_datatype
2015-03-24 14:17:30.96 spid4s Creating table MSdbms_map
2015-03-24 14:17:30.96 spid4s Creating table MSdbms_datatype_mapping
2015-03-24 14:17:30.97 spid4s Definining default datatype mappings
2015-03-24 14:17:30.98 spid4s Creating datatype mappings for MSSQLSERVER to ORACLE8
2015-03-24 14:17:31.08 spid4s Creating datatype mappings for MSSQLSERVER to ORACLE9
2015-03-24 14:17:31.12 spid4s Creating datatype mappings for MSSQLSERVER to ORACLE10
2015-03-24 14:17:31.17 spid4s Creating datatype mappings for MSSQLSERVER to ORACLE11
2015-03-24 14:17:31.22 spid4s Creating datatype mappings for MSSQLSERVER to DB2
2015-03-24 14:17:31.28 spid4s Creating datatype mappings for MSSQLSERVER to SYBASE
2015-03-24 14:17:31.33 spid4s Creating datatype mappings for ORACLE8 to MSSQLSERVER
2015-03-24 14:17:31.38 spid4s Creating datatype mappings for ORACLE9 to MSSQLSERVER
2015-03-24 14:17:31.45 spid4s Creating datatype mappings for ORACLE10 to MSSQLServer
2015-03-24 14:17:50.00 spid4s Creating datatype mappings for ORACLE11 to MSSQLServer
2015-03-24 14:17:59.30 spid4s Creating view MSdatatype_mappings
2015-03-24 14:17:59.31 spid4s Creating view sysdatatypemappings
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_enum_proxy_for_subsystem
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_enum_login_for_proxy
2015-03-24 14:17:59.89 spid4s Dropping signature from: sysmail_delete_mailitems_sp
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_sqlagent_get_startup_info
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_sqlagent_has_server_access
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_sqlagent_get_perf_counters
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_sqlagent_notify
2015-03-24 14:17:59.89 spid4s Dropping signature from: sysmail_delete_log_sp
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_is_sqlagent_starting
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_verify_job_identifiers
2015-03-24 14:17:59.89 spid4s Dropping signature from: sp_verify_schedule_identifiers
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_verify_jobproc_caller
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_downloaded_row_limiter
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_post_msx_operation
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_verify_performance_condition
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_verify_job_date
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_verify_job_time
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_verify_alert
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_update_alert
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_delete_job_references
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_delete_all_msx_jobs
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_verify_accountparams_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_generate_target_server_job_assignment_sql
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_generate_server_description
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_verify_principal_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_msx_set_account
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_verify_profile_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_msx_get_account
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_verify_account_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_delete_operator
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_add_profile_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_msx_defect
2015-03-24 14:17:59.90 spid4s Dropping signature from: sysmail_update_profile_sp
2015-03-24 14:17:59.90 spid4s Dropping signature from: sp_msx_enlist
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_delete_profile_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_delete_targetserver
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_help_profile_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_enlist_tsx
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_create_user_credential_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_get_sqlagent_properties
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_alter_user_credential_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_set_sqlagent_properties
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_drop_user_credential_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_add_targetservergroup
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_add_account_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_update_targetservergroup
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_update_account_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_delete_targetservergroup
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_delete_account_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_help_targetservergroup
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_help_account_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_add_targetsvrgrp_member
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_help_admin_account_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_delete_targetsvrgrp_member
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_add_profileaccount_sp
2015-03-24 14:17:59.91 spid4s Dropping signature from: sp_verify_category
2015-03-24 14:17:59.91 spid4s Dropping signature from: sysmail_update_profileaccount_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_add_category
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_delete_profileaccount_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_update_category
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_help_profileaccount_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_delete_category
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_configure_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_help_category
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_help_configure_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_help_targetserver
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_help_configure_value_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_resync_targetserver
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_add_principalprofile_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_purge_jobhistory
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_update_principalprofile_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_help_jobhistory_full
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_delete_principalprofile_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_help_jobhistory_summary
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_help_principalprofile_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_help_jobhistory
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_logmailevent_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_add_jobserver
2015-03-24 14:17:59.92 spid4s Dropping signature from: sysmail_start_sp
2015-03-24 14:17:59.92 spid4s Dropping signature from: sp_delete_jobserver
2015-03-24 14:17:59.93 spid4s Dropping signature from: sysmail_stop_sp
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_help_jobserver
2015-03-24 14:17:59.93 spid4s Dropping signature from: sysmail_help_status_sp
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_help_downloadlist
2015-03-24 14:17:59.93 spid4s Dropping signature from: sysmail_help_queue_sp
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_enum_sqlagent_subsystems_internal
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_SendMailMessage
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_enum_sqlagent_subsystems
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_isprohibited
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_verify_subsystem
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_SendMailQueues
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_verify_schedule
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_ProcessResponse
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_add_schedule
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_MailItemResultSets
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_attach_schedule
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_process_DialogTimer
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_detach_schedule
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_readrequest
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_update_replication_job_parameter
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_GetAttachmentData
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_update_schedule
2015-03-24 14:17:59.93 spid4s Dropping signature from: sp_RunMailQuery
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_delete_schedule
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_validate_user
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_get_jobstep_db_username
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_send_dbmail
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_verify_jobstep
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_ExternalMailQueueListener
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_add_jobstep_internal
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_sysmail_activate
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_add_jobstep
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_update_jobstep
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_delete_jobstep
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_help_jobstep
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_write_sysjobstep_log
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_maintplan_delete_log
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_help_jobsteplog
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_maintplan_delete_subplan
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_delete_jobsteplog
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_maintplan_update_subplan_tsx
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_get_schedule_description
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_maintplan_subplans_by_job
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_add_jobschedule
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_maintplan_open_logentry
2015-03-24 14:17:59.94 spid4s Dropping signature from: sp_update_jobschedule
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_maintplan_close_logentry
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_delete_jobschedule
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_maintplan_update_log
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_help_schedule
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_maintplan_update_subplan
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_help_jobschedule
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_maintplan_delete_plan
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_verify_job
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_maintplan_start
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_add_job
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_get_script
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_update_job
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_clear_dbmaintplan_by_db
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_delete_job
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_add_maintenance_plan
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_get_composite_job_info
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_delete_maintenance_plan
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_help_job
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_add_maintenance_plan_db
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_help_jobcount
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_delete_maintenance_plan_db
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_help_jobs_in_schedule
2015-03-24 14:17:59.95 spid4s Dropping signature from: sp_add_maintenance_plan_job
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_manage_jobs_by_login
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_delete_maintenance_plan_job
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_apply_job_to_targets
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_help_maintenance_plan
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_remove_job_from_targets
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_get_job_alerts
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_start_job
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_stop_job
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_add_log_shipping_monitor_jobs
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_cycle_agent_errorlog
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_add_log_shipping_primary
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_get_chunked_jobstep_params
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_add_log_shipping_secondary
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_check_for_owned_jobs
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_delete_log_shipping_monitor_jobs
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_check_for_owned_jobsteps
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_delete_log_shipping_primary
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_sqlagent_refresh_job
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_delete_log_shipping_secondary
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_jobhistory_row_limiter
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_log_shipping_in_sync
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_sqlagent_log_jobhistory
2015-03-24 14:17:59.96 spid4s Dropping signature from: sp_log_shipping_get_date_from_file
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_sqlagent_check_msx_version
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_get_log_shipping_monitor_info
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_sqlagent_probe_msx
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_update_log_shipping_monitor_info
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_set_local_time
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_delete_log_shipping_monitor_info
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_multi_server_job_summary
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_remove_log_shipping_monitor_account
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_target_server_summary
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_log_shipping_monitor_backup
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_uniquetaskname
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_log_shipping_monitor_restore
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_addtask
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_change_monitor_role
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_droptask
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_create_log_shipping_monitor_account
2015-03-24 14:17:59.97 spid4s Dropping signature from: trig_targetserver_insert
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_add_alert_internal
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_ssis_addlogentry
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_add_alert
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_ssis_listpackages
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_delete_alert
2015-03-24 14:17:59.97 spid4s Dropping signature from: sp_ssis_listfolders
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_help_alert
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_deletepackage
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_operator
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_deletefolder
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_add_operator
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_sqlagent_is_srvrolemember
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_getpackage
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_update_operator
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_category_identifiers
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_getfolder
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_help_operator
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_putpackage
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_help_operator_jobs
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_proxy_identifiers
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_operator_identifiers
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_credential_identifiers
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_addfolder
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_notify_operator
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_subsystems
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_renamefolder
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_notification
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_verify_subsystem_identifiers
2015-03-24 14:17:59.98 spid4s Dropping signature from: sp_ssis_setpackageroles
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_add_notification
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_verify_login_identifiers
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_ssis_getpackageroles
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_update_notification
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_verify_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_delete_notification
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_add_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_help_notification
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_delete_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_help_jobactivity
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_update_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_sqlagent_is_member
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_verify_proxy_permissions
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_sem_add_message
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_help_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_sem_drop_message
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_get_message_description
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_grant_proxy_to_subsystem
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_help_jobhistory_sem
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_grant_login_to_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_convert_jobid_to_char
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_revoke_login_from_proxy
2015-03-24 14:17:59.99 spid4s Dropping signature from: sp_revoke_proxy_from_subsystem -
Kerberos Configuration Manager for SQL Server: Access of system information failed!
I'm trying to use the new Kerberos Configuration Manager for SQL Server tool that was released recently to verify SPN on several SQL Servers, but any time I attempt to connect to a server I get the following error in the log:
6/24/2013 3:48:22 PM Info: Connect to WMI, \\<HOSTNAME>\root\cimv2
6/24/2013 3:48:25 PM Error: Access of system information failed System.DirectoryServices.AccountManagement.PrincipalOperationException: An error (1332) occurred while enumerating the group membership. The member's SID could not be resolved.
at System.DirectoryServices.AccountManagement.SAMMembersSet.IsLocalMember(Byte[] sid)
at System.DirectoryServices.AccountManagement.SAMMembersSet.MoveNextLocal()
at System.DirectoryServices.AccountManagement.SAMMembersSet.MoveNext()
at System.DirectoryServices.AccountManagement.FindResultEnumerator`1.MoveNext()
at System.Linq.Enumerable.Contains[TSource](IEnumerable`1 source, TSource value, IEqualityComparer`1 comparer)
at KerberosCM.WMIHelper.isUserLocalAdmin(SystemInfo si, UserPrincipal user)
at KerberosCM.WMIHelper.getUserInfo(SystemInfo mi)
6/24/2013 3:48:25 PM Error: Error System.Exception: Access of system information failed!
at KerberosCM.WMIHelper.getUserInfo(SystemInfo mi)
at KerberosCM.SystemInfo.GetInfo()
at KerberosConfigMgr.Utility.Login(String serverName, String login, String password, Boolean isCmdLine, Form uiForm)
Things I have tried to resolve this:
1. Verified that my account is a Domain Admin.
2. Attempt to connect locally without inputting any information for server/user/pw
3. Attempt to connect remotely using server/user/pw
I always receive the same error message and log: Access of system information failed!
Has anyone else run into this issue?Update to this:
There were some invalid user accounts added to the Local Administrators group only showing up as a GUID. This caused the enumeration of the group to fail and generate the error in my original post. Removing those user accounts from the Administrators group
got past the enumeration error.
However, now when attempting to connect to the servers (locally or remotely) I get this error:
6/27/2013 10:24:24 AM Info: Connect to WMI, \root\cimv2
6/27/2013 10:24:38 AM Error: Access of system information failed System.Runtime.InteropServices.COMException (0x80070035): The network path was not found.
at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_AdsObject()
at System.DirectoryServices.PropertyValueCollection.PopulateList()
at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)
at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)
at System.DirectoryServices.AccountManagement.SAMStoreCtx.ResolveCrossStoreRefToPrincipal(Object o)
at System.DirectoryServices.AccountManagement.SAMMembersSet.MoveNextForeign()
at System.DirectoryServices.AccountManagement.SAMMembersSet.MoveNext()
at System.DirectoryServices.AccountManagement.FindResultEnumerator`1.MoveNext()
at System.Linq.Enumerable.Contains[TSource](IEnumerable`1 source, TSource value, IEqualityComparer`1 comparer)
at KerberosCM.WMIHelper.isUserLocalAdmin(SystemInfo si, UserPrincipal user)
at KerberosCM.WMIHelper.getUserInfo(SystemInfo mi)
6/27/2013 10:24:38 AM Error: Error System.Exception: Access of system information failed!
at KerberosCM.WMIHelper.getUserInfo(SystemInfo mi)
at KerberosCM.SystemInfo.GetInfo()
at KerberosConfigMgr.Utility.Login(String serverName, String login, String password, Boolean isCmdLine, Form uiForm) -
SQL Server 2008R2 Download Link
Hi All,
After browsing for SQL Server 2008R2 enterprise evaluation edition I came across below link for SQL Server 2008 evaluation but not R2.
http://www.microsoft.com/en-US/download/details.aspx?id=1279
Please share me the link if available for SQL Server 2008R2 enterprise evaluation edition.
Regards,
Kalyan
Grateful to your time and support. Regards, ShivaHi Kalyan,
I found below link from Alberto Morrillo's post you can download from below
http://sqlserver.dlservice.microsoft.com/download/9/C/0/9C036510-3218-4258-8B03-67DC1D6A497C/SQLFULL_ENU.iso?lcid=1033
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP -
HADR Solution for SQL Server Analysis Services (SSAS) 2014 on Azure Iaas
Hi All
I am required to build a HA/DR solution for SQL Server and SSAS 2014 on Azure. So far I could build AlwaysOn high availability solution for SQL Server on Azure but haven't found any solution for SSAS.
Failover Clustering is not an option on azure because of the restriction of not been able to use shared storage. We also determined that the cost savings of using SQL + the cost of the 3rd Party replication tool was a wash (ie no real cost savings).
Any lead on this would be appreciated.
Thanks,
Viral Shah
Thanks - ViralHi Viral,
A clustered implementation of SSAS can be configured in Microsoft Azure. Such a configuration would need to meet all the requirements stated in the following document including Active Directory and storage.
How to Cluster SQL Server Analysis Services
http://download.microsoft.com/download/D/2/0/D20E1C5F-72EA-4505-9F26-FEF9550EFD44/SSAS_Failover_Cluster_V4.docx
Thanks,
Lydia Zhang -
HI,
I have installed Cumulative Update 12 for SQL Server 2008 R2 SP2 on my SharePoint instances. This was to resolve a known issue faced with the instance. CU12 helped resolve the issue. My company is rather strict regarding security hotfixes. But I am
not sure if this particular hotfix [Security Hotfix (KB2977319)] is required if the instance has CU12 applied.
Tested this on a Lab server, the installation did run fine, the summary log also stated that the KB is applied. But the Build Number did not change. Hence the doubt.
Overall summary:
Final result: Passed
Exit code (Decimal): 0
Exit message: Passed
Start time: 2014-09-06 10:31:21
End time: 2014-09-06 10:55:49
Requested action: Patch
Instance SPNTSQLTRN overall summary:
Final result: Passed
Exit code (Decimal): 0
Exit message: Passed
Start time: 2014-09-06 10:48:08
End time: 2014-09-06 10:55:45
Requested action: Patch
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 2
KBArticle: KB2977319
KBArticleHyperlink: http://support.microsoft.com/?kbid=2977319
PatchType: QFE
AssociatedHotfixBuild: 0
Platform: x64
PatchLevel: 10.52.4321.0
ProductVersion: 10.52.4000.0
GDRReservedRange: 10.50.4001.0:10.50.4199.0;10.50.4200.0:10.50.4250.0
PackageName: SQLServer2008-KB2977319-x64.exe
Installation location: e:\ac2af22d88ee645b5b32b5c178\x64\setup\
Please inform if I need to apply the hotfix on CU12. Thanks in advance.
John SYes you must install Security update mentioned in KB 2977319 it is important for SQL Server to be patches with this security update. Without this it could allow an attacker to compromise your system and gain control over it.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles -
Cumulative update 15 for SQL Server 2012 SP1 is released
Cumulative update 15 for SQL Server 2012 SP1 is released
http://support.microsoft.com/en-us/kb/3038001
MDS related fix is:
FIX: Add three stored procedures to clean up history that is created when you use SQL Server 2012 MDS
http://support.microsoft.com/en-us/kb/3036601
After using MDS for a while, the transaction/validation/staging history may grow very large. In this CU we provide 3 store procedure to clean them up manually.
The fix will be ported over to SQL 2012 SP2 and SQL 2014 CUs in the coming 2 months.
In next SQL Server release, it will be automated by MDS maintenance job.
--@ModelID is the model ID that you clean up the log for.
--@CLeanupOlderThanDate is the date before that the logs or records is deleted.
DECLARE @CleanupOlderThanDate date = '<Date>', @ModelID INT = <ID>
--Cleanup Transaction History
EXEC mdm.udpTransactionsCleanup @ModelID, @CleanupOlderThanDate;
--Cleanup Validation History
EXEC mdm.udpValidationsCleanup @ModelID, @CleanupOlderThanDate;
--Cleanup entity-based staging table
EXEC mdm.udpEntityStagingBatchTableCleanup @ModelID, @CleanupOlderThanDate;Hi SelvaOnline,
I would recommend to install SP2 and the hotfix that came after it.
If you don't have a reason to install a CU than don't bother with it.
SP2:
http://www.microsoft.com/en-us/download/details.aspx?id=43340
Hotfix for SP2;
http://support.microsoft.com/kb/2969896/en-us
Thanks,
Teun
Maybe you are looking for
-
Export to WORD - what's with these boxes around the text?
Post Author: Emily CA Forum: Exporting I am new to CR. I am using version 10.0.0.533 We use CR with ClearQuest for problem reporting and other data collection. Rational (ClearQuest Vendor) tells me it's a CR X problem. I use a CR report exported to
-
Will it work with a monitor...
will the new macbook air work with a monitor as I see it has a touch screen? This will be my primary computer as I like that it is small and light.
-
Contrct number in the billing doc
We have revenure recognition implemented.We create contract and then billing and revenue recogniton.When the revenue recognition is done with VF44 against the contract ..hence the contract number is captured in the Revenue recogniton document.However
-
Interested in Learning Java Programming.
Hello All, I a college student and I am interested in learning Java programming. Where would be a good place for me to start? Thanks
-
Need help with SMS Helper Driver for W520 Windows 7 64--bit
Greetings to all, I have a Windows 7 64--bit laptop. The solutions center indicates that that a driver for a device manager has not been installed. The message is for SMS Helper Driver (SMIHIP) STATUS not installed. Thank you. Ldxrunner