cancel
Showing results for 
Search instead for 
Did you mean: 

Error db00004 - name was not found in database

Jump to solution

Hoping someone can shed some light on what is happening.  Background: two days ago I upgrade EEM/EEPC from v5.1.7 to v5.2.3.5.  Everything went great, no problems were encountered.  Today I performed my normal index rebuild operation and afterwards couldn't login to the console with any of my admin accounts.  The error i get is "Error db00004 - name was not found in database" 

I'm currently restoring SBDATA from last night's backup to recover from this problem.

I went to my test 5.2.3 server and tested the same process I used in production and got the same error.  The process I followed was, stop the DB server, deleted all names files in 0000001 and 0000002 forlders (didn't deleted the names.dat files in either folder) started the DB server then ran get counts.  The getcounts command returned the follwoing error but did create index files: 

Connection result:

ResultCode = 0xdb000004
ResultDescription = The name was not found in the database

Before deleting the original names files I saved them to a different location.  On a hunch I decided to delete all the new names files and restore the originals.  Sure enough I was able to login. 

Here's my DBCFG.ini config:

[NameIndex]
Enabled=Yes
LockTimeout=3000
LockSleep=10
HashCount=44
MinEntrySize=16
LifeTime=0

[Attribs]
SingleFile-No
AutoConvert=No

[Tracking]
ObjectChanges=No

I have 4135 machines and about 3900 users currently.

SbAdmin file version: 5.2.3.5

SbAdmCl.exe v5.2.3.5

Any help would be greatly appreciated.. 

Message was edited by: mrepine on 2/18/11 11:02:43 AM GMT-05:00
1 Solution

Accepted Solutions
Reliable Contributor SafeBoot
Reliable Contributor
Report Inappropriate Content
Message 6 of 8

Error db00004 - name was not found in database

Jump to solution

turn it back on in the ini file and then wait - watch to see if a name index gets created. This would mean you have something connecting directly to the files of the DB. You need to stop this bad behaviour.

If the name index does not rebuild, restart your sbdbserver - it should rebuild the index. This may take some time. After the index has been rebuilt you should be able to log in fine.

If not, then you have a corrupt object somewhere which is polluting the index - you'll have to run with it disabled. It's probably then a good time to think about upgrading to a current release - 5.2.3 is pretty old.

7 Replies

Error db00004 - name was not found in database

Jump to solution

You need to get counts before you start database.

Error db00004 - name was not found in database

Jump to solution

Tried that, still get Resultcode = 0xdb000004  ResultDescription = The name was not found in the database. 

Reliable Contributor SafeBoot
Reliable Contributor
Report Inappropriate Content
Message 4 of 8

Error db00004 - name was not found in database

Jump to solution

first thing is to turn your nameindex off and then restart your server - try to login now.

if it does not work then something has renamed the users - you need to work out what happened (perhaps a rogue admin?)

you can check the ACTUAL name of the user by probing the actual files of the db. the *1.dat file is the name file - just open it in notepad. You'll of course need to know the ID of the user to test this though - I always start at user 1 because that's the one created when the db was initialized.

If you are going to clear the index, you need to delete all the names.dat files - don't leave any behind.

Finally, make sure you only have ONE connection to the files of the database - one instance of sbdbserver etc. There's never a good reason to have multiple things accessing the db at once.

Error db00004 - name was not found in database

Jump to solution

Truning off nameindex allowed me to login.  I only have one instance of the DB server.

So now that I know logins succeed with nameindex disabled, what can i do to get indexing to working again?

Reliable Contributor SafeBoot
Reliable Contributor
Report Inappropriate Content
Message 6 of 8

Error db00004 - name was not found in database

Jump to solution

turn it back on in the ini file and then wait - watch to see if a name index gets created. This would mean you have something connecting directly to the files of the DB. You need to stop this bad behaviour.

If the name index does not rebuild, restart your sbdbserver - it should rebuild the index. This may take some time. After the index has been rebuilt you should be able to log in fine.

If not, then you have a corrupt object somewhere which is polluting the index - you'll have to run with it disabled. It's probably then a good time to think about upgrading to a current release - 5.2.3 is pretty old.

Error db00004 - name was not found in database

Jump to solution

Ok, so went ahead and turned indexing back on for the test machine, deleted all name.* files (including names.dat) then ran getcounts.  Took about 20 minutes to complete.  I then started the DB server and was able to login to EEM.  So i think the problem was that I wasn't deleting the name.dat file for machines and users.  I'm in the process of doing the same thing in production.  Hopefully it will work there as well.  Will follow-up shortly with the results.

Highlighted

Error db00004 - name was not found in database

Jump to solution

Life is good again!  Indexing is working in production.  Thanks for all the help!!

More McAfee Tools to Help You
  • Subscription Service Notification (SNS)
  • How-to: Endpoint Removal Tool
  • Support: Endpoint Security
  • eSupport: Policy Orchestrator
  • Community Help Hub

      New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

    • Find Forum FAQs
    • Learn How to Earn Badges
    • Ask for Help
    Go to Community Help

    Join the Community

      Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

    • Get helpful solutions from McAfee experts.
    • Stay connected to product conversations that matter to you.
    • Participate in product groups led by McAfee employees.
    Join the Community
    Join the Community