Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. Problem with certificate

Problem with certificate

Scheduled Pinned Locked Moved Database
databasesysadminhelpsql-serversecurity
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    DerekFL
    wrote on last edited by
    #1

    I created a certificate in the master database so that my endpoint could use the certificate. I dropped the endpoint and dropped the certificate and added a new one and created a new endpoint because the earlier one had a weak password. This is SQL 2005 service pack 1. Everything has been fine till we restarted the server. Master, model start up fine but now I am getting these errors. (1.) FallBack certificate initialization failed with error code: 1. (2.) Warning:Encryption is not available, could not find a valid certificate to load. (3.) TDSSNIClient initialization failed with error 0x7e, status code 0x60. (4.) TDSSNIClient initialization failed with error 0x7e, status code 0x1. Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log. (5.) SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems. Is there a way to just start sql with master only? Ive tried moving the certificates to another location, renaming the database mdf file that uses the endpoint so it would go suspect.

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups