Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

General Cryptographic error Expand / Collapse
Author
Message
Posted Monday, September 8, 2008 5:44 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, December 27, 2013 12:16 PM
Points: 309, Visits: 725
Any idea? SQL Server seems to hang. These errors are repeated in the log:

1.) "Problem creating symtom dump file due to internal exception"
2.) "Problem creating symtom dump file due to internal exception"
3.) "Error: 15296, Severyit: 16, State: 1"
4.) "General Cryptographic failure."
5.) "Sql Server is terminating a system or background task SSB Task due to errors in starting up the task"

Also, I found this stuff in the "exception.log" file. Any ideas?

09/08/08 11:00:00 spid 62 Exception 0xc0000005 EXCEPTION_ACCESS_VIOLATION reading address 00000004 at 0x61E8FAE9
09/08/08 11:00:00 spid 0 Exception 0xc0000005 EXCEPTION_ACCESS_VIOLATION reading address 00000018 at 0x76C92779
09/08/08 11:01:40 spid 0 Exception 0xc0000005 EXCEPTION_ACCESS_VIOLATION reading address 00000018 at 0x76C92779
09/08/08 11:03:51 spid 0 Exception 0xc0000005 EXCEPTION_ACCESS_VIOLATION reading address 00000000 at 0x7C82BC32


xp_msver =
1 ProductName NULL Microsoft SQL Server
2 ProductVersion 589824 9.00.3068.00
3 Language 1033 English (United States)
4 Platform NULL NT INTEL X86
5 Comments NULL NT INTEL X86
6 CompanyName NULL Microsoft Corporation
7 FileDescription NULL SQL Server Windows NT
8 FileVersion NULL 2005.090.3068.00
9 InternalName NULL SQLSERVR
10 LegalCopyright NULL © Microsoft Corp. All rights reserved.
11 LegalTrademarks NULL Microsoft® is a registered trademark of Microsoft Corporation. Windows(TM) is a trademark of Microsoft Corporation
12 OriginalFilename NULL SQLSERVR.EXE
13 PrivateBuild NULL NULL
14 SpecialBuild 201064448 NULL
15 WindowsVersion 248381957 5.2 (3790)
16 ProcessorCount 2 2
17 ProcessorActiveMask 3 00000003
18 ProcessorType 586 PROCESSOR_INTEL_PENTIUM
19 PhysicalMemory 4095 4095 (4294000640)
20 Product ID NULL NULL


.
Post #565836
Posted Monday, September 8, 2008 7:32 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, December 27, 2013 12:16 PM
Points: 309, Visits: 725
One more thing. Nothing on this DB server is encrypted.
Thx!


.
Post #565859
Posted Friday, September 17, 2010 8:23 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, July 10, 2014 4:13 AM
Points: 1,860, Visits: 3,597
I'm having similar issue on a SQL-2008 instance, where I have principal mirror databases, no idea what the cause is.

__________________________________________________________________________________

Turbocharge Your Database Maintenance With Service Broker: Part 2
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #988661
Posted Saturday, September 18, 2010 1:33 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, December 27, 2013 12:16 PM
Points: 309, Visits: 725
Wow, this is incredibly old. I forgot the specific details of the solution. I just remember that it was related to encrypted stored procedure(s). Sombody, or something was trying to access encrypted sprocs.

Hope this gets you moving in the right direction.


.
Post #988691
Posted Saturday, September 18, 2010 9:00 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, July 10, 2014 4:13 AM
Points: 1,860, Visits: 3,597
BSavoie (9/18/2010)
Wow, this is incredibly old. I forgot the specific details of the solution. I just remember that it was related to encrypted stored procedure(s). Sombody, or something was trying to access encrypted sprocs.

Hope this gets you moving in the right direction.


Thank you, it looks like this error is generic enough to appear in various situations. I don't have encrypted sprocs in that environment, but I do have mirroring set up to a reporting server, and that seems to be related somehow to what happened in my case.

I may need to ask Microsoft for help in figuring this one out.


__________________________________________________________________________________

Turbocharge Your Database Maintenance With Service Broker: Part 2
Turbocharge Your Database Maintenance With Service Broker: Part 1
Real-Time Tracking of Tempdb Utilization Through Reporting Services
Monitoring Database Blocking Through SCOM 2007 Custom Rules and Alerts
Preparing for the Unthinkable - a Disaster/Recovery Implementation
Post #988738
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse