Upgrading .NET Server Standard to Windows Server 2003

Discussion in 'Server Setup' started by LES, Aug 21, 2003.

  1. LES

    LES Guest

    Dear All,

    I'm trying to upgrade .NET server 2002 with DC to server 2003. During the
    Hardware compatibility check, it says:
    1. Softmodem
    2. Softmodem
    3. Previous Windows 95, 98 .... etc
    4. RAS VPN ..... etc
    All Just Warning Sign not STOP Sign. The stop sign is only to prepare DC for
    upgrading, and I'd done the two steps successfully.

    I went ahead performing the upgrade. Once the upgrade came to INSTALLING
    DEVICES at 32 - 34 minutes of time left on the installation, I received the
    BSOD with BAD_POOL_CALLER.

    The Stop Error is 0x000000C2 (0x00000044, 0x00000000, 0x80000000,
    0x00000000)

    I searched MS to find answers. Although I don't know which will solve my
    problem, I found one which suggests the use of Verifier.exe at System32
    folder. However, I still cannot log into windows server 2003 any available
    modes. Every mode will only lead me to continuing the installation process,
    and, as it can be guessed, it will stop with the same Error and Number.

    One other suggestion I've found at MS is to keep Dumping - Rebooting the
    system numerous time until the OS (Upgrading server 2003) finally leads to
    Logon Dialog Box. Is this safe?

    Please kindly help me:
    1. Whether I still can undo the upgrading process?
    2. Whether I still can continue finishing the upgrading process?

    Thx & Rgd.
    LES
     
    LES, Aug 21, 2003
    #1
    1. Advertisements

  2. LES,

    What exactly is .Net Server 2002? Are you talking about an older build of
    Windows Server 2003?

    Remember Microsoft usually ONLY recommends upgrades from the Release
    Canditates of products to production (sometimes Beta 3's).

    I don't want to recommend anything more than this, as it is possible that
    the upgrade simply is not taking because an older DLL or important file does
    not get overwritten properly during the attempted upgrade.


    Bill F. (Windows Setup MVP)
     
    Bill Frisbee [MVP], Aug 22, 2003
    #2
    1. Advertisements

  3. LES

    LES Guest

    Dear Bill,

    Yes, you've got it all right. We've been using two servers. One is Windows
    2000 server as main server, and the other one is NT 4.0 as backup server.
    But when MS introduced the .NET Server 2002, we replaced the NT 4.0 system
    with it.

    We currently would like to upgrade both servers to Windows Server 2003. The
    Windows 2000 Server upgarded just fine. When I'm trying to upgrade the .NET
    Server 2002 Beta 3, the error occurred.

    You're right again that it has something to do with the DLLs. In the
    setupapi.log, I've found:
    Error: Register DLLs Crypto DLLs Module: "%11% \r .........

    and, in the setupact.log, I've found the following error:
    C:\Windows\System32\dssenh.dll , and
    C:\Windows\System32\initpki.dll

    What exactly do they mean? Can I just bypass those files? How to recover
    from this situation?
    I'd appreciate your help on this, Bill.

    Thx & Rgd
    LES
     
    LES, Aug 22, 2003
    #3
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.