%3CLINGO-SUB%20id%3D%22lingo-sub-1128909%22%20slang%3D%22en-US%22%3ERequest%20File%20Can%E2%80%99t%20be%20Located%20during%20CA%20Certificate%20Renewal%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1128909%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20TECHNET%20on%20May%2029%2C%202012%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CP%3EDuring%20my%20work%20with%20a%20customer%20renewing%20their%20Issuing%20CA%E2%80%99s%20certificate%20based%20on%20the%20steps%20documented%20in%20this%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fcc776691(v%3Dws.10).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20article%20%3C%2FA%3E%20%2C%20I%20discovered%20that%20the%20Request%20file%20generated%20couldn%E2%80%99t%20be%20located%20in%20the%20default%20location%20of%20%25systemDrive%25%20.%20The%20Issuing%20CA%20didn%E2%80%99t%20log%20any%20errors%20in%20the%20Event%20Log%2C%20nor%20did%20it%20post%20any%20error%20messages.%20I%20also%20searched%20for%20all%20files%20with%20the%20extension%20*.req%20on%20all%20drives%2C%20and%20still%20couldn%E2%80%99t%20find%20the%20file.%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EAfter%20some%20more%20research%2C%20I%20discovered%20that%20my%20customer%20changed%20the%20default%20location%20of%20the%20%3CB%3E%20RequestFileName%20%3C%2FB%3E%20Registry%20Key%20during%20their%20installation%20to%20a%20drive%20that%20no%20longer%20exists%20on%20the%20CA.%20The%20location%20configured%20was%20%3CB%3E%20a%3A%5C%251_%253%254.req.%20%3C%2FB%3E%20I%20followed%20these%20steps%20to%20fix%20this%20issue%3A%3C%2FP%3E%3CBR%20%2F%3E%3COL%3E%3CBR%20%2F%3E%3CLI%3EStart%20the%20%3CB%3E%20Registry%20Editor%3C%2FB%3E%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3ENavigate%20to%20%3CB%3E%20HKLM%5CSystem%5CCurrentControlSet%5CServices%5CCertsvc%5CConfiguration%5C%3CCASANITIZEDNAME%3E%3C%2FCASANITIZEDNAME%3E%3C%2FB%3E%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3ELocate%20the%20Registry%20String%20%3CB%3E%20RequestFileName%3C%2FB%3E%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EChange%20the%20value%20from%20%3CB%3E%20a%3A%5C%251_%253%254.req%20%3C%2FB%3E%20to%20%3CB%3E%20C%3A%5C%251_%253%254.req%3C%2FB%3E%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EStop%20and%20Start%20the%20Certification%20%3CB%3E%20Active%20Directory%20Certificate%20Services%20%3C%2FB%3E%20service%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FOL%3E%3CBR%20%2F%3E%3CP%3EI%20was%20then%20able%20to%20create%20the%20Request%20File%20and%20submit%20it%20to%20the%20Offline%20Root%20CA%20to%20process%20it.%3C%2FP%3E%3CBR%20%2F%3E%3CP%3E%3C%2FP%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1128909%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20TECHNET%20on%20May%2029%2C%202012%20During%20my%20work%20with%20a%20customer%20renewing%20their%20Issuing%20CA%E2%80%99s%20certificate%20based%20on%20the%20steps%20documented%20in%20this%20article%2C%20I%20discovered%20that%20the%20Request%20file%20generated%20couldn%E2%80%99t%20be%20located%20in%20the%20default%20location%20of%20%25systemDrive%25%20.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1128909%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ea%20certificate%20could%20not%20be%20created%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ead%20cs%20documentation%20updates%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eca%20maintenance%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eca%20renewal%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ecertificate%20requests%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ecertificates%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ecertifiication%20authority%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

First published on TECHNET on May 29, 2012

During my work with a customer renewing their Issuing CA’s certificate based on the steps documented in this article , I discovered that the Request file generated couldn’t be located in the default location of %systemDrive% . The Issuing CA didn’t log any errors in the Event Log, nor did it post any error messages. I also searched for all files with the extension *.req on all drives, and still couldn’t find the file.

 

After some more research, I discovered that my customer changed the default location of the RequestFileName Registry Key during their installation to a drive that no longer exists on the CA. The location configured was a:\%1_%3%4.req. I followed these steps to fix this issue:



    1. Start the Registry Editor

 

    1. Navigate to HKLM\System\CurrentControlSet\Services\Certsvc\Configuration\<CASanitizedName>

 

    1. Locate the Registry String RequestFileName

 

    1. Change the value from a:\%1_%3%4.req to C:\%1_%3%4.req

 

    1. Stop and Start the Certification Active Directory Certificate Services service



I was then able to create the Request File and submit it to the Offline Root CA to process it.