EV11.0.1 SCOM EVWebsiteConnectivity.monitor error
Hello all, We use SCOM to monitor our EV environment, and we see on one of our installs the following alert: Source: http://evservername.domain.com:80/EnterpriseVaultAPI Full Path Name: evservername.domain.com\servername\Common\Server connectivity\http://evservername.domain.com:80/EnterpriseVaultAPI Alert Monitor: EVWebsiteConnectivity.Monitor Created: 20/04/2015 11:24:48 Alert Description: Cannot connect to website on server evservername. Website URL: http://evservername.domain.com:80/EnterpriseVaultAPI There are no events in the eventlogs (Enterprise Vault, System, Application). There are no issues reported using the search, There are no other issues reported. Does anyone know if this warning is a false alert? I do not see a reason to investigate or try to fix, but the SCOM team worries there is something wrong what needs to be fixed. this environment has been upgraded from 10SP4CHF2 to EV11SP1CHF1 on 18/04/2015 without issues. Thanks. GJ
Exchange 2013 OWA EV Office App Initalization Failed Error
Hello all. After configuring the OWA/EV webapp we see the Enterprise Vault tab however when we click on it we get an "initialization failed" message. I read a few other community posts and some support threads and nothing has worked to correct the issue. EV is published externally as well but at this point we are just trying to get it working internally. Trying it internal and external has the same result error "initialization failed". The environment is as follows: x3 Exchange 2013 CAS/MBX servers SP1 RU8 2x EV v.11.01 (mailbox archiving, journaling) F5 load balancer Script we implemented: $Mbx = get-mailbox "mailbox" New-App -OrganizationApp -DefaultStateForUser:enabled -Url ("http://evarchive1.xyz.com/EnterpriseVault/OfficeMailAppManifest.aspx?LegacyMbxDn=" + $Mbx.LegacyExchangeDN + "&BaseURL=https://evarchive1.xyz.com/EnterpriseVault") Errors Shown: When running a trace in the browser i see the following error after clicking on the Enterprise Vault tab on a message in OWA EVOMA (ERROR) 11:24:50.232: logAndReportFailure: EWSFindAssociatedItem.onEwsRequestComplete ID[ERROR_EWS_ERRORRESULTSTATUS] Err[Failed to send a request to the Exchange Server] [Result status:failed] Things we have tried... The Exchange Auth Cert thumprint matches an appears to be correct as per http://www.symantec.com/docs/TECH222757 We tried bypassing the Hardware Load balancer via host file and point direct to EV and Exchange as appropirate and get the same result. We have tested EWS virtual direcotries on Exchange and have used other webapps such as bing maps and everything checks out ok. No errors. When i run a dtrace i dont see anything - i believe its because i am not even making it to Exchange yet. Also tried the basic things like restarting IIS on EV and Exchange servers, etc. Any help would be appreciated.Publish EV for Outlook Anywhere Users
Hi, I need a clarificationregarding the publication of the enterprise vault site. Lets say we have a EV Server with a vault site name EVSITE - no domain suffix was added during the configuration. For interns,EV is available viahttp://evsite/enterprisevault We also have a external customer domain contoso.com. The customer now wants EV to be available via RPC over HTTPS, sohttps://evsite.contoso.com/enterprisevaultwaspublished. But, if external users click an element in outlookthe sitehttp://evsite/enterprisevault is called. Willthe RPC over HTTP Connection and Proxy URL Setting in the Desktop Policy change this behaviour? I would set the connection to "Use proxy" and the url to "https://evsite.contoso.com/enterprisevault" So the EV is reachable for interns athttp://evsite/enterprisevault and as soon as Outlook is in Outlook Anywhere mode it would contacthttps://evsite.contoso.com/enterprisevault" - correct? Regards vmds
Rules for Usage and Setting SynchInMigrationMode in Registry
Dear Experts, we have a user who has moved between various countries, taking her outlook mail file from Exchange Server to Exchange Server in various domains,finally returning to the UK and the domain where she started ! We use EV ver 10.3, currently. I tried to enable her mailbox that had been migrated back to our UK based Exchange Servers, but ran into problems and an error message that recommended use of an additional Registry Setting 'SynchInMigrationMode'. https://www.veritas.com/support/en_US/article.HOWTO98184 I checked the Registry for our EV server and 'SynchInMigrationMode' is not currently present in the described location. Reading the blurb for 'SynchInMigrationMode', default setting is0, '1' makes EV assign a new mailbox to an existing archive, if the LegacyMbxDN matches, '2' creates new entries for the new mailbox and renames old entries that have a matching LegacyMbxDN, by adding timestamps to the LegacyMbxDN fields. I guess, that as the user has returned to the UK and wants her re-migrated mailbox to be archived into the same existing Archive, the best setting is '1'. However, I am not happy about adding a registry setting to a live, running production server with lots of users using it, if that means an unscheduled reboot or unscheduled restart of the EV services.The document does not tell me if this is or is not a risky approach, or if it is necessary to stop or restart any services. So, can I add this registry setting 'on the fly' and change its setting from 0 to 1 without risking service outage or the need to either reboot OR restart any services ? Appreciate your advice and guidance ! thanks.
