RE: Problems setting up SQL Server in FIPS 140-2 compliant mode
- From: Anonymous <Anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 14 Apr 2008 03:41:00 -0700
I'm facing the same problem, Have you got the solution to it?
"Greg Larsen" wrote:
I'm following the instructions in KB920995 to setup up a SQL Server 2005 SP2.
instances to be FIPS 140-2 compliant. I've enabled the local security policy
"System cryptograpy:....". Stopped, and restored SQL server, even rebooted my
machine. But I can't get the SQL Server ERRORLOG file to contain the message
"Service Broker Transport is running in FIPS compliance mode". I'm wondering
if Service Broker needs to be enabled, because I see this error message in
the log "The Service Broker protocol transport is disabled or not
configured."
Any thoughts on what additional steps I need to take to get my SQL Server
2005 SP2 version running on Windows XP to run in FIPs 140-2 compliance mode?
Is XP not a certified OS for FIPS 140-2?
Any suggestions would be greatly appreciated.
--
If you are looking for SQL Server examples or a free SQL Server DBA
Dashboard tool check out my Website at http://www.sqlserverexamples.com
- Prev by Date: Extended Stored procedure dll with FIPS_mode_set(1)
- Next by Date: Reconfiguring the data access authentication
- Previous by thread: Extended Stored procedure dll with FIPS_mode_set(1)
- Next by thread: Reconfiguring the data access authentication
- Index(es):
Relevant Pages
|
|