Jump to content

The "esentutl /g secedit.sdb" command is reporting Operation terminated with error -583 (JET_errSect


Recommended Posts

Guest NewsBot
Posted

Hi.

 

In application events I'm getting messages like these:

 

<span style="font-weight:bold;font-style:italic">Log Name</span><span style="font-style:italic">:Application,

</span><span style="font-weight:bold;font-style:italic">Source</span><span style="font-style:italic">:Microsoft-Windows-CAPI2,

</span><span style="font-weight:bold;font-style:italic">Event ID</span><span style="font-style:italic">:257,

</span><span style="font-weight:bold;font-style:italic">Level</span><span style="font-style:italic">:Error,

</span><span style="font-weight:bold;font-style:italic">Keywords</span><span style="font-style:italic">:Classic,

</span><span style="font-weight:bold;font-style:italic">User</span><span style="font-style:italic">:N/A,

</span><span style="font-weight:bold;font-style:italic">Description</span><span style="font-style:italic">: The Cryptographic Services service failed to initialize the Catalog Database. The ESENT error was: -583.</span>

 

<span style="font-weight:bold;font-style:italic">Log Name</span><span style="font-style:italic">:Application,

</span><span style="font-weight:bold;font-style:italic">Source</span><span style="font-style:italic">:SceCli,

</span><span style="font-weight:bold;font-style:italic">Event ID</span><span style="font-style:italic">:1005,

</span><span style="font-weight:bold;font-style:italic">Level</span><span style="font-style:italic">:Error,

</span>

<span style="font-weight:bold;font-style:italic">Keywords</span><span style="font-style:italic">:Classic,

</span><span style="font-weight:bold;font-style:italic">User</span><span style="font-style:italic">:N/A,

</span><span style="font-weight:bold;font-style:italic">Description</span><span style="font-style:italic">: Some JET database is corrupt. Run esentutl /g to check the integrity of the security database %%windir%%securityDatabasesecedit.sdb. If it is corrupt,

attempt a soft recovery first by running esentutl /r in the %%windir%%security directory. If soft recovery fails, attempt a repair with esentutl /p on %%windir%%securityDatabasesecedit.sdb. Then delete the log files in %%windir%%security. Ошибка при открытии

баз данных безопасности, таких, как %windir%securitydatabasesecedit.sdb.</span>

 

But when I was tried to run commands:

 

esentutl /g %windir%securityDatabasesecedit.sdb

 

esentutl /r %windir%security

 

esentutl /p %windir%securityDatabasesecedit.sdb

 

All of them are reporting the

 

"Operation terminated with error -583 (JET_errSectorSizeNotSupported, The physical sector size reported by the disk subsystem, is unsupported by ESE for a specific file type.)"

 

error.

 

Question is - how to fix it?

It looks esentutl tool cannot do anything in this case because always report the same error (-583). :-(

 

 

 

 

View the thread

  • Replies 0
  • Created
  • Last Reply

Popular Days

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...