Incorrect Password Detection and Lockout - BCM 3.7

[BCM400Guy]

I forgot the underscore in eeadmin (_) password of BCM 3.7.
I am now locked out of BCM 3.7 Through UM and 9pin Serial at this point. How do I regain access? Lights are flashing green. This unit was a 3.5 upgraded 3.7 awaiting 4.0 upgrade which I should be performing shortly. Any help greatly appreciated?

 

[option11newby]

Have you tried the supervisor username and password

NCSS, NCDS, NCTS

 

[pccal]

If this happened during the 3.5 to 3.7 upgrade than I would suggest re-imaging drive to 3.5 doing a restore & trying the upgrade again. Have you checked to make sure that the capacitors on your base tray were O.K.?

 

[BCM400Guy]

3.7 Upgrade has been completed successfully. We were trying to access the unit to perform 3.7 to 4.0 upgrade when my most knowledgeable Assistant kept hammering wrong password eventually being locked out. Good help is so hard to find. I did gain access through Serial cable I restarted the system in hopes of resetting password and I now have lost access to serial as well.

Summary:
Flashing green lights on front panel.
No Access through UM
No Access through Serial Cable.

Option11newby: I no longer get a prompt when using hyperterminal or web browser to enter any password.
I am assuming ee_admin or supervisor will work providing we can get in. Not really sure though.

Any help will be greatly appreciated.

 

[gberger]

Did you revert the date back to 01-01-08 prior to do the upgrade from 3.5 to 3.7? Can it be the apache problem?

 

[BCM400Guy]

Gberger: Not apache problem 3.7 upgrade working fine installed aprox. 2 months ago. Now when logging into system to prepare for 4.0 upgrade we are locked out by system with password detection error message and flashing green lights.

I did connect monitor and keyboard to unit and get the following message:

Windows NT could not start because the following file is missing or corrupt.

<winnt root>\system32\ntoskrnl.exe

Any help would be nice.

 

[Dasheen]

Souds like a HD problem. I take it vmail is down?

 

[BCM400Guy]

Dasheen: System has no programing yet. No handsets connected as of yet. This machine scheduled to go into service after 4.0 upgrade. System worked fine until lockout message from numerous WRONG PASSWORD by my 22yr old protege. he forgot the _ in ee_admin and kept trying without it. System had message of password lockout.

 

[SupportDude]

Your HDD is corrupted.
Might as well get a 4.0 HDD at this point.

-SD-

http://www.mysupportguy.net

 

[BCM400Guy]

Can I replace With 4.0 HDD before 4.0 upgrade?

 

[SupportDude]

If you replace it with a 4.0 HDD, you don't need to do the upgrade. But, you will need to install the upgrade keycode in order to install all of previous the 3.x keycodes that were in the system.

-SD-

http://www.mysupportguy.net

 

[BCM400Guy]

2nd Question Supportdude:

Can I replace with raid drive from another BCM 400 4.0. This machine is new and has no programming yet?

 

[SupportDude]

I suppose you could, but you may run into keycode issues.
I would expect that when you install the 4.0 upgrade keycode it will overwrite the current keycode entries on the HDD from the other system.
It's worth a try if you're in a bind.

-SD-

http://www.mysupportguy.net

 

[BCM400Guy]

No keycodes on raid drives at all. Nothing to overwrite.

 

[BCM400Guy]

SD: can I just swap MSC Card into BCM 400 4.0 Raid Redundant Unit And All is Fine?

Just A thought.

 

[Dasheen]

Should be ok but u'll have to run the universal profile to sync the HD to the new MSC.

 

[gberger]

Yes you can but you might have to install the latest SU to force core download.

 

[BCM400Guy]

pccal: Capacitors are blue and fine. I missed this question.

Here's a progress report so far.

I pulled out one raid drive from BCM 400 4.0 Redundant and replaced with corrupt drive from 3.7 System alarm sounds due to drives not identical, but 4.0 begins to mirror and rebuild drive to 4.0 status this took about 20 minutes. I remove the 3.7 drive and replace the raid drive to orignal redundant status and 2nd mirror takes place to return this machine to it's rightful state. I place the 3.7 drive which is now a 4.0 into 3.7 BCM and machine boots up perfect with 2 exceptions.
No keycodes present ofcourse (This will hopefully be fixed when I apply upgrade keycode to unit) and 2nd it maintained expansion unit and extra fan status from other machine. I simple unchecked those as this is a standard unit with no expansion unit. So far So good.

SD: thanks for the tip to replace with 4.0

I did not run Universal Profile. Boths units did maintain there MSC integrity without it.

Although this worked out. Problem with lockout is problem within Windows NT. I guess the fix in this situation is to reimage HDD after lockout on 3.XX system.

I will post confirmation of system up and working when I apply keycode.

Thanks to All.

 

[BCM400Guy]

Here's the finish. I loaded upgrade Auth to 4.0. All keycodes converted from 3.7 to 4.0 without any trouble. All is well.

Thanks to All.