VMware ESXi - Microsoft Windows 2012 R2 Ad problem

What Version/Build is your ESXi Version?

Are you using E1000E or VMXNet3 adapters?

What SCSI Controller hardware is set on the VM? i cannot tell for sure but did you upgrade a potential Server 2003 to 2012 R2? (The Controller in 2003 would be LSI Parallel where in 2012 it should be SAS) and that could cause some issues as well.
 
dasaint said:
What Version/Build is your ESXi Version?

Are you using E1000E or VMXNet3 adapters?

What SCSI Controller hardware is set on the VM? i cannot tell for sure but did you upgrade a potential Server 2003 to 2012 R2? (The Controller in 2003 would be LSI Parallel where in 2012 it should be SAS) and that could cause some issues as well.
Click to expand...

Hello
Thanks for your replay.

I am using VMxNet3 adapter - network is working i am connected via RDP to local administrator account.

I didnt upgrade 2003 to 2012. This is pure installation from .iso

I settings VM i have SCSI controller 0 LSI Logic SAS (Current type)

Also I took print screen

http://oi62.tinypic.com/2jdrsxl.jpg

About version of my ESXi

~ # uname -a
VMkernel esxi.olivia.net 5.5.0 #1 SMP Release build-1331820 Sep 18 2013 23:08:31 x86_64 GNU/Linux
Click to expand...

What do you think ?
 
You had a catastrophic failure. Corruption may occur. I'd be checking to see if any files are damaged, and what the error on the service actually is.
 
Do you need more info from my side ?

How to solve error: 0x00002e2
 
from ntdsutil

C:\Windows\system32>ntdsutil files info
ntdsutil: files
Active Instance not set. To set an active instance use "Activate Instance ".
ntdsutil: info
Error parsing Input - Invalid Syntax.
ntdsutil: activate instance ntld
AD LDS Instance "ntld" not found on this machine.
No active instance set.
ntdsutil: activate instance NTDS
Active instance set to "NTDS".
ntdsutil: authoritative restore
Could not initialize the Jet engine: database is inconsistent.
Could not check if the domain controller is read-only, 0x8000ffff(Catastrophic f
ailure)
Error parsing Input - Invalid Syntax.
ntdsutil:
Click to expand...
 
Yep, the jet database is toast. Ping technet, see if they have any fixes - that one I don't know how to fix :(
 
I am trying on myslf to do something ..

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Administrator.W2K12R2-SRV>ESENTUTL /r

Extensible Storage Engine Utilities for Microsoft(R) Windows(R)
Version 6.3
Copyright (C) Microsoft Corporation. All Rights Reserved.

Usage Error: Missing logfile base name specification.

Operation terminated with error -1003 (JET_errInvalidParameter, Invalid API para
meter) after 0.0 seconds.




C:\Users\Administrator.W2K12R2-SRV>ESENTUTL /r ntds

Extensible Storage Engine Utilities for Microsoft(R) Windows(R)
Version 6.3
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating RECOVERY mode...
Logfile base name: ntds
Log files: <current directory>
System files: <current directory>

Operation terminated with error -1003 (JET_errInvalidParameter, Invalid API para
meter) after 0.0 seconds.




C:\Users\Administrator.W2K12R2-SRV>ESENTUTL /r ntds.dit

Extensible Storage Engine Utilities for Microsoft(R) Windows(R)
Version 6.3
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating RECOVERY mode...
Logfile base name: ntds.dit
Log files: <current directory>
System files: <current directory>

Operation terminated with error -1003 (JET_errInvalidParameter, Invalid API para
meter) after 0.0 seconds.




C:\Users\Administrator.W2K12R2-SRV>cd Downloads

C:\Users\Administrator.W2K12R2-SRV>cd cd:
The filename, directory name, or volume label syntax is incorrect.

C:\Users\Administrator.W2K12R2-SRV>cd cd:/
The filename, directory name, or volume label syntax is incorrect.

C:\Users\Administrator.W2K12R2-SRV>cd Cookies

C:\Users\Administrator.W2K12R2-SRV>cd c:
C:\Users\Administrator.W2K12R2-SRV

C:\Users\Administrator.W2K12R2-SRV>cd c:/

c:\>cd "AD DS Database"

c:\AD DS Database>ls
'ls' is not recognized as an internal or external command,
operable program or batch file.

c:\AD DS Database>dir
Volume in drive C has no label.
Volume Serial Number is 82A1-1AD4

Directory of c:\AD DS Database

2013-12-09 17:45 <DIR> .
2013-12-09 17:45 <DIR> ..
2014-03-18 14:44 <DIR> NTDS
2013-12-09 17:45 <DIR> SYSVOL
0 File(s) 0 bytes
4 Dir(s) 86626553856 bytes free

c:\AD DS Database>cd NTDS

c:\AD DS Database\NTDS>dir
Volume in drive C has no label.
Volume Serial Number is 82A1-1AD4

Directory of c:\AD DS Database\NTDS

2014-03-18 14:44 <DIR> .
2014-03-18 14:44 <DIR> ..
2014-03-18 17:45 8192 edb.chk
2014-03-18 17:45 10485760 edb.log
2013-12-09 17:45 10485760 edbres00001.jrs
2013-12-09 17:45 10485760 edbres00002.jrs
2014-03-18 14:44 10485760 edbtmp.log
2014-03-16 13:35 20987904 ntds.dit
2014-03-16 13:35 2113536 temp.edb
7 File(s) 65052672 bytes
2 Dir(s) 86626553856 bytes free

c:\AD DS Database\NTDS>ESENTUTL /g ntds.dit

Extensible Storage Engine Utilities for Microsoft(R) Windows(R)
Version 6.3
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating INTEGRITY mode...
Database: ntds.dit
Temp. Database: .\TEMPINTEG1856.EDB

Checking database integrity.

The database is not up-to-date. This operation may find that
this database is corrupt because data from the log files has
yet to be placed in the database.

To ensure the database is up-to-date please use the 'Recovery' operation.


Scanning Status (% complete)

0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
...................................................


Integrity check completed. Database is CORRUPTED!




Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database fi
le or corrupted db) after 26.562 seconds.




c:\AD DS Database\NTDS>ESENTUTL /p ntds.dit

Extensible Storage Engine Utilities for Microsoft(R) Windows(R)
Version 6.3
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating REPAIR mode...
Database: ntds.dit
Temp. Database: TEMPREPAIR3800.EDB

Checking database integrity.

The database is not up-to-date. This operation may find that
this database is corrupt because data from the log files has
yet to be placed in the database.

To ensure the database is up-to-date please use the 'Recovery' operation.


Scanning Status (% complete)

0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
...................................................

Initiating DEFRAGMENTATION mode...
Database: ntds.dit

Defragmentation Status (% complete)

0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
...................................................


Moving 'TEMPREPAIR3800.EDB' to 'ntds.dit'... DONE!

Note:
It is recommended that you immediately perform a full backup
of this database. If you restore a backup made before the
defragmentation, the database will be rolled back to the state
it was in at the time of that backup.

Operation completed successfully in 16.891 seconds.


c:\AD DS Database\NTDS>
Click to expand...

I am still fighting :)
 
You must log in or register to reply here.
Back
Top