Forum Discussion

Pending_Shortcu's avatar
Pending_Shortcu
Level 4
20 years ago
Solved

EV OWA setup on BE Exchange server throws error and doesn't create virt dir

Hi guys...running v6 sp1 OWA setup on BE Exchange server (clustered) and getting two errors pop up after running the cscript version...

Error : CreateKVSSchemaFolder : Failed to create folder, error: -2147217895 Object or data matching the name, range, or selection criteria was not found within the scope of this operation.

AND then

Line: 224
Char: 3
error: "Operation is not allowed when the object is closed"
code: 800A0E78
ADODB.Record

Setup stops and no EV virtual directories are created...

Exchange 2003 SP1 running on Weindows 2003 with NO SP

EV is Windows 2003 SP1


Can we manually create the virtual directories and be ok or is this going to screw something else up down the road?

Any ideas?

Thanks a bunch

D
Enterprise Vault
Information Governance
  • TonySterling's avatar
    TonySterling
    20 years ago
    I would try to Run This script from the command line:

    Cscript backend2003setup.wsf /regform /formregmbx:(get system MB from .wsf log) /logondomain

    or Cscript backend2003setup.wsf /regform /formregmbx:(get system MB from .wsf log) /formregdomain :(domain of the system mailbox)

    If you get the same ADO connection error: -2147217895 Object or data matching the name, range, or selection criteria was not found within the scope of this operation.
    Check the following;
    Open Active Directory Computers and Users
    Click View>Advanced Features
    Expand Object>Click Microsoft Exchange System Objects
    Find the SystemMB from the .wsf log and make sure it is not Disabled or Hidden.
    To check if it is hidden open the properites of the Mailox and Click the Exchange Adv. tab

    Re-run the script.
  • Jason_Szeto's avatar
    Jason_Szeto
    Level 6
    20 years ago
    Hey dude,

    I think you should be able to create the virtual directories manually. Just remember to do all the proxycfg stuff.

    What happens if you try the setup on the other node of the cluster?
  • TonySterling's avatar
    TonySterling
    Moderator
    20 years ago
    I would try to Run This script from the command line:

    Cscript backend2003setup.wsf /regform /formregmbx:(get system MB from .wsf log) /logondomain

    or Cscript backend2003setup.wsf /regform /formregmbx:(get system MB from .wsf log) /formregdomain :(domain of the system mailbox)

    If you get the same ADO connection error: -2147217895 Object or data matching the name, range, or selection criteria was not found within the scope of this operation.
    Check the following;
    Open Active Directory Computers and Users
    Click View>Advanced Features
    Expand Object>Click Microsoft Exchange System Objects
    Find the SystemMB from the .wsf log and make sure it is not Disabled or Hidden.
    To check if it is hidden open the properites of the Mailox and Click the Exchange Adv. tab

    Re-run the script.
  • Pending_Shortcu's avatar
    Pending_Shortcu
    Level 4
    20 years ago
    > Hey dude,
    >
    > I think you should be able to create the virtual
    > directories manually. Just remember to do all the
    > proxycfg stuff.
    >
    > What happens if you try the setup on the other node
    > of the cluster?

    Thanks for the response Jay...I did try it on another BE exchange server (wasn't in the cluster) and got the same error. Turns out EV was trying to use a system mailbox that was disabled...
  • Fredrik_Bj_rk's avatar
    Fredrik_Bj_rk
    Level 2
    20 years ago
    The Vir directory wont appear until you run the Configuration program under the EV-programgroup

    Rmember to change the "EnterpriseVaultProxy" directory-properties to "Script only" at the "Execute permissions"

    /Fredrik
  • Tremaine's avatar
    Tremaine
    Level 6
    20 years ago
    The Exchange System Mailboxes are always disabled by default, so I would be very surprised if changing this had anything to do with getting your install to work.

    Cheers
  • Pending_Shortcu's avatar
    Pending_Shortcu
    Level 4
    20 years ago
    > The Exchange System Mailboxes are always disabled by
    > default, so I would be very surprised if changing
    > this had anything to do with getting your install to
    > work.
    >
    > Cheers

    You are correct sir...perhaps something screwy was going on with the system mailbox it was trying to use...after specifying a different sys mailbox, the script ran with no problems.

    Something else was strange there..they had three schema-root folders, and the admins didn't know why (and neither do I)...thought that may have been the cause initially, and I still can't say for sure...
  • Jason_Szeto's avatar
    Jason_Szeto
    Level 6
    20 years ago
    Multiple schema root folders always bombs out the OWA setup. I came across that a few times and the customer had to have Microsoft clean up the extra root folders before we could complete the OWA setup.